Custom Query (69 matches)
Results (25 - 27 of 69)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #36 | fixed | Packaging: documentation and symbol files for os2dasd.f32 and partfilt.flt should not be installed by default | ||
| Description |
As os2dasd.f32 and partfilt.flt should not be installed on an LVM system, and as these are in a separate pack in the installer, their related documentation and symbol files should also be moved to a separate pack so that they are not left "orphaned" when os2dasd.f32 and partfilt.flt have not been installed. |
|||
| #37 | fixed | Change config.sys call to run for cachef32 | ||
| Description |
I am suggesting changing the call statement for the cachef32 in config.sys be changed to run. Index: lib/fat32_010.wis =================================================================== --- lib/fat32_010.wis (revision 197) +++ lib/fat32_010.wis (working copy) @@ -148,7 +148,7 @@
+ CONFIGSYS="run=$(3)\cachef32.exe /f /p:2 /m:50000 /b:250 /d:5000 | UNIQUE(cachef32.exe) ADDAFTER(fat32.ifs)"
|
|||
| #39 | fixed | SIGSEGV/SIGTERM/SIGBREAK Signals are not caught | ||
| Description |
I have signals handler set up for some cleanup procedures in FORMAT/SYS/CHKDSK, like remounting the disk, but if I interrupt CHKDSK by Ctrl-Break, I see ^C External process cancelled by a Ctrl+Break or another process This is when running from UFAT32.DLL. But if I run the standalone version of CHKDSK, I get: Signal 4 was received and it cleanly remounts disk. In UFAT32.DLL case, we have disk in intermediary state (mounted in MOUNT_ACCEPT mode). The cause, as I suspect, is that CHKDSK is a 32-bit program and sets up 32-bit exception handler, but CHKDSK routine is a 16-bit wrapper around a 32-bit "chkdsk" routine. So, we indeed run 16-bit routine, but an exception handler is 32-bit. This seems to be inconsistent, and thus, the 32-bit exception handler doesn't activate. So, we need a solution for this problem. |
|||
