From: dcasale AT my-deja DOT com
Newsgroups: comp.os.msdos.djgpp
Subject: Re: DJGPP timer slowdown
Date: Thu, 01 Feb 2001 00:40:05 GMT
Organization: Deja.com
Lines: 43
Message-ID: <95ab94$e4n$1@nnrp1.deja.com>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 1010131103626 DOT 29266V-100000 AT is> <959emd$g57sf$1 AT ID-57378 DOT news DOT dfncis DOT de> <9003-Wed31Jan2001192619+0200-eliz AT is DOT elta DOT co DOT il> <95a1qh$gkt4b$1 AT ID-57378 DOT news DOT dfncis DOT de> <95a7as$aie$1 AT nnrp1 DOT deja DOT com>
NNTP-Posting-Host: 199.249.234.30
X-Article-Creation-Date: Thu Feb 01 00:40:05 2001 GMT
X-Http-User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows 98)
X-Http-Proxy: 1.1 x72.deja.com:80 (Squid/1.1.22) for client 199.249.234.30
X-MyDeja-Info: XMYDJUIDdcasale
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

In article <95a7as$aie$1 AT nnrp1 DOT deja DOT com>,
  dcasale AT my-deja DOT com wrote:

[snip]

> Maybe I'd better explain what's going on with this program of
> mine.  :-)
>
> First of all, I wrote a compression program using DJGPP to store all
> of the files and file information (including long filenames, file
> attributes, etc.) in one big file.  To access the file information
> not available through straight DOS -- since that's what I'm running
> under -- I use direct disk access (INT13h, AH=042h, as well as other
> disk access calls) to get at the info (for example, long filenames).
>
> With compression off, the disk is constantly being read or written
> to.  I'm using direct file reads -- that is, I don't use DOS calls
> but instead read the files directly by caching the FAT and pulling
> sectors off of the drive.  The system clock runs at its normal speed,
> apparently.  But with compression on, there are periods of disk
> inactivity during which the program does its number crunching.  And,
> the system clock ends up running about 30% slower than normal.
>
> Rebooting resets the system clock to its proper time.
>
> I tried running the program again without SmartDrive loaded, and _the
> slowdown did not happen_!!
>
> Whatever the explanation, I just wanted to pass this along.

[snip]

Argh!  I switched to a different hard drive, still without loading
SmartDrive, and the slowdown is back.  ;_;

Now I have no idea what might be causing it.

Damon Casale, damon AT WRONG DOT redshift DOT com (remove the obvious)
If I liked heavy metal, I'd be headbanging right about now.


Sent via Deja.com
http://www.deja.com/