I realize that this question seems very vague, but
perhaps anybody has seen something similar.
I have one program that works with ASPI devices, recently I replaced
PMODSTUB v1.3 with CWSDSTUB v5 and already received many reports
about strange behavior when working with bad ZIP discs. I was able to
recreate one typical situation: IOMEGA ZIP with native
drivers (any version from 3 to 6), if ZIP drive is corrupt (scratched
with a razor), then instead of reporting read error system hangs,
gives GPF or just prints garbage on the screen. It happens only
if I use CWSDPMI (not only stub), the same COFF with
attached PMODSTUB works fine. Obviously it not "NULL pointer assignment"
or something what CWSDPMI intercepts unlike PMODE. What can it be -
difference in PIC programming, ring 0, limited stack size ? It is highly
interesting because "CWSDMPI conflicts withIOMEGA ZIP drivers"
cannot be satisfactory explanation.
Thanks in advance,