Custom Query (69 matches)
Results (52 - 54 of 69)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #5 | fixed | Trap after flash disk eject | ||
| Description |
e-co: FAT32.IFS filesystem eject flash disk goto filecommander - you see the driver letter is still there C: 1 second.. system traps tested with 3 flash disks. btw, new flash disk (formatted) works fine. eject works without troubles. In N days I should chkdsk the flashdisk. After this event the problem with trap starts to happen. |
|||
| #6 | fixed | Trap in FSH_FORCENOSWAP | ||
| Description |
Hi, after upgrading my hard drive and cloning (using dfsee) my C: partition to the new hard drive I now get this while booting, The system detected an internal processing error at location ##1200:04ba-0002:04ba. FAT32:FSH_FORCENOSWAP on rqRQ Segment failed, rc=8 06860631 Internal revision 14.105_W4 I updated to fat32_09121.zip which didn't help (trap info from 09121). System is Warp v4 with all free updates and a few from testcase. Drive is a 160 GB maxtor. Drive C: is Win98 which boots fine. |
|||
| #24 | fixed | Trap in FS_FSINFO because of NULL "pBootFSInfo" pointer in pVolInfo | ||
| Description |
Recently I had a trap in FAT32.IFS and I tracked it down to routine "FS_FSINFO" in file "fat32.c". The trap occurred in version 0.9.13 version but the code is still unchanged in the current version 0.10.x. The trap occurred in this line of code: pAlloc->cUnitAvail = pVolInfo->pBootFSInfo->ulFreeClusters; The trap occurs because at this point, pBootFSInfo is NULL. The trap happened because OS2DASD/OS2LVM got confused of if a (removable) USB stick was present or not and the said USB stick was formatted with FAT32 filesystem. |
|||
