Mail Archives: djgpp/2001/02/01/16:56:20
In article <Pine DOT SUN DOT 3 DOT 91 DOT 1010201110948 DOT 13803L-100000 AT is>,
djgpp AT delorie DOT com wrote:
>
> On Wed, 31 Jan 2001 dcasale AT my-deja DOT com wrote:
>
> > 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).
>
> Int 13h, AH=42h is an EBIOS call. AFAIK, EBIOS is part of the IDE
> controller, not of the system BIOS. As such, it is much less
> standard, and might do all kinds of tricks that never show in normal
> DOS/Windows operation, because AFAIK most programs don't call these
> functions directly.
>
> In other words, you are well advised to avoid using them. (I don't
> even understand why did you need to go to low-level disk I/O functions
> instead of using normal file I/O.)
I thought I mentioned why. I'm running under straight DOS, which means
I don't have any other way to access LFN's and other file information
which isn't available through standard file i/o calls.
In any case, I tried running this program under Windows. No slowdown.
I'm beginning to think that it's either CWSDPMI itself or some strange
interaction of my program with CWSDPMI. It might possibly be Windows
fixing an egg my program might be laying, but I doubt it. I've checked
over all of the interrupt calls I make, and the code is very clean. If
you'd like, I can post the various calls I make so you can see whether
or not they might be causing a problem.
Damon Casale, damon AT WRONG DOT redshift DOT com (remove the obvious)
"Fezzik, you did something right!" -- Inigo Montoya, "The Princess
Bride"
Sent via Deja.com
http://www.deja.com/
- Raw text -