Opened 5 years ago
Last modified 5 years ago
#80 assigned defect
Traps with (rather rare) IBM ThinkPad 600X
| Reported by: | xynixme | Owned by: | martini |
|---|---|---|---|
| Priority: | trivial | Milestone: | GA |
| Component: | IFS | Version: | |
| Severity: | medium | Keywords: | |
| Cc: |
Description
Fatal TRAP when displaying the WPS of eComStation 1.2. No details mentioned below, because a Pentium III IBM ThinkPad 600X should be rather rare, but should be reproducable if wanted. a REM in front of the IF=/CALL=drivers "solved " it. Same setup as other hardware, newer and older, including no UF*.DLL in x:\ECS\DLL.
No FAT32 in use, do a fix is not required. IIRC the latest version 0.9.x worked, albeit it wasn't used. It didn't crash just before the WPS would be displayed.
Drivers loaded okay, no error messages.
Change History (5)
comment:2 by , 5 years ago
2xynixme: Yes, please, tell us, which version of fat32.ifs it is. Please, take a snapshot of the trap screen. Or, better take a COM port log. What do you mean by "No details mentioned below, because a Pentium III IBM ThinkPad? 600X should be rather rare, but should be reproducable if wanted."? Details are always required, otherwise nothing to talk about.
As the trap occurs during WPS startup, I'd suspect that it occurs during a FAT drives remount during cachef32.exe startup. Cachef32.exe does a remount of FAT/FAT32/exFAT drives when it's starting up. Maybe, trap is occured during a remount of some drive (a flash disk inserted?). Can you comment out cachef32 only? Does it start without it? What happens if you run cachef32 manually, after OS/2 is booted?
comment:3 by , 5 years ago
Hi
Is there any more feedback on this ticket? Since it more than 8 months since the last feedback is it ok to close it?
Regards
comment:4 by , 5 years ago
| Owner: | set to |
|---|---|
| Status: | new → assigned |
comment:5 by , 5 years ago
| Owner: | changed from to |
|---|
1) Without a trap screen and the exact used version of FAT32.IFS, this info is not really helpful. For the trap screen you will either have to retype the trap screen contents or you will need to take a JPG picture with a digital camera and attach it here.
2) make sure that all IFS entries precede all MAC/Protocol driver entries. This has been a longstanding problem and is a flaw of the kernel in that if this sequence is not followed, IFS drivers can trap. But it is not predictable if they will trap or not.
It is unlikely that this has anything to do with the HW in use.