Changes between Version 3 and Version 4 of Ticket #17, comment 5


Ignore:
Timestamp:
Aug 4, 2015, 8:02:50 PM (9 years ago)
Author:
Valery V. Sedletski
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #17, comment 5

    v3 v4  
    1313-bt=os2 is "generate OS/2 code". Also, don't see a sense to use it, as I use "system os2 dll" linker directive
    1414
    15 So, -fpi87 helps? What is the principal difference between using FPU and its emulation? So, it won't throw a floating point exceptions? Really, I think, better to eliminate using the FP at all. I know the FORMAT routine uses it when showing the % complete. Not sure about CHKDSK. Also, didn't touched cachef32.exe and other utilities at all.
     15To Lars: So, -fpi87 helps? What is the principal difference between using FPU and its emulation? So, it won't throw a floating point exceptions? Really, I think, better to eliminate using the FP at all. And yes, the FP emulation was used in fat32.dll, not the IFS driver. I know that using FP is not recomended in drivers, but here is not a driver, but an utility DLL. I know the FORMAT routine uses it when showing the % complete. Not sure about CHKDSK. But the IFS (either dumpfs or fat32) could trap trying to mount a FS in inconsistent state.
     16
     17PS: Also, didn't touched cachef32.exe and other utilities at all.
    1618
    1719Also, why the next patch? The remount_media() is in fact DSK_REDETERMINEMEDIA ioctl, it needs to be done after format is complete. Before FORMAT or CHKDSK, you must issue the DSK_BEGINFORMAT, to remount the volume before formatting/checking IFS's in DASD mode. After all, you make DSK_REDETERMINEMEDIA, which remounts it in normal mode again (where all FS structures are valid). Trying to zero-out structures (including the boot block) after remounting the drive can lead to a trap.