Custom Query (69 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (4 - 6 of 69)

1 2 3 4 5 6 7 8 9 10 11 12
Ticket Resolution Summary Owner Reporter
#25 fixed Binaries started from FAT32, become corrupted, if booted from FAT32 Valery V. Sedletski
Description

When playing with our Team Boot/2 bootable fat32 flash disk, I noticed the following problem: when I booted from a fat32 volume (usually, flash disk), and trying to start binaries like format.com, wget.exe, from the same FAT32 volume, I get the error like "The file format.com cannot be run in OS/2 session". If I look into the binary, I now see it being zeroed, if I view it in the hex viewer. But some binaries don't get corrupted, like shutdown.exe. I sometimes see that shutdown.exe fail to start, but after some number of attempts, it gets started, but didn't become corrupted. As it is known, the binaries are opened by the kernel Loader component, with read-write access, so it could be potentially overwritten, and it got really overwritten. What is interesting, I tried to start binaries from a non-bootable FAT32 medium, and I did not had any case when it got corrupted.

#62 fixed CACHEF32.EXE no longer respects the /S parameter ataylor
Description

Using build 0.10.r288. CACHEF32.EXE displays the message: FAT32: Unicode translate table for codepage xxx loaded. even when the /S (silent) switch is specified.

This is a regression to a long-running bug which was present in FAT32 builds 0.9.12 and earlier. This was fixed in 0.9.13 and the /S switch functioned as expected in that and later versions until the appearance of this regression.

#32 fixed CHKDSK message advising to run check under Windows needs updating Lewis Rosenthal
Description

Currently (0.10a7), when CHKDSK cannot fully correct a disk, the message displayed is:

Still errors found on disk. Please run Windows 95 ScanDisk!

I think we need to update/correct this to:

Errors may still exist on this volume. Recommended action: Run CHKDSK under Windows.
1 2 3 4 5 6 7 8 9 10 11 12
Note: See TracQuery for help on using queries.