Mail Archives: djgpp-workers/2001/07/10/17:46:45
> > From: "Andrew Cottrell" <acottrel AT ihug DOT com DOT au>
> > Date: Tue, 10 Jul 2001 23:31:18 +1000
> >
> > The quirk I found was that if I remove the "| 0x1000" in the code as
> > commented then the DJDIR environment variable is inserted into the app's
> > environment on Windows 2000. It made no difference on the WIN 98SE box
> > that I used to compile the app on if it was included or not.
> >
> > What does the 0x1000 bit do? It is unused in Ralph's list as indicated
> > in the following table (interrupt.h file):
>
> No, it's not unused. See the table near the documentation of function
> 6Ch: this flag is extended FAT32 open, it is needed to support opening
> files that are larger than 2GB.
Thanks. I need to have a better look.
> So it seems like Windows 2000 doesn't support FAT32, either in its LFN
> API or at all. Could you please set LFN=n and see if DJGPP.ENV can be
> read, even without removing 0x1000 from the value of BX?
Tried this during the investigation and it worked okay. Windows 2000 shoudl
support FAT32 as my second hard drive (used to be the seocnd hard drive in
teh WIN98 box) is FAT32. Do you want any more info?
> Anyway, thanks a lot for working on this, it seems like we can now
> solve this bug, after you check what happens without LFN.
The only suggetion that I can make is for me to try the following:
1) I will see what the osmajor / os minor etc are in Windows 2000 to see if
we could put conditional code arround the LFN function call. I will reply
later tonight.
2) Re-build the DJGPP 204 dev snapshort from the CVS tarball of the 8th July
with the changes I find from the investigation in found so far and the
outcome of the msmajor / msminor investigation.
3) I have RHIDE 1.4.7.9, but I only have the sources for 1.4.7.8. If I build
1.4.7.8 and use GCC 2.9.5.2 (last one before the GCC 3.0 beta) are there any
other issues I may find that would cause me to go off on a tangent?
Thanks,
Andrew
- Raw text -