HDPMI=1 did help Ladsoft also | DOS/32A is "paranoid" :-( (DOSX)
> "set hdpmi=1" most likely will avoid the loop.
YES. Old INFOPAD does no longer TripleFault
> It has been implemented exactly for those DOS extenders which behave
> paranoid: they except all interrupt and exception vectors and
Intercept ?
> route IRQs from real-mode to protected-mode themselves - apparently they
> don't trust any external code. The latter thing is dangerous to do,
> because it's the DPMI host's job.
Acceptable idea for interrupts, faulty for exceptions ?
Still strange why only INFOPAD had this bug
But it's indeed fixed in 3.70 release , no TripleFault with HDPMI=0, no RCMB Page Fault with CWSDPMI. Regrettably I'm banned from the CC386 forum so I can't ask there soon
---
This is a LOGITECH mouse driver, but some software expect here
the following string:*** This is Copyright 1983 Microsoft ***
Complete thread:
- [BUG] ESP=0 | push | TripleFault | BOOM! | inside HDPMI32 ? - DOS386, 10.01.2008, 01:51 (DOSX)
- What about CuteMouse? - Japheth, 10.01.2008, 07:01
- TripleFault HDPMI32 | CuteMouse is INNOCENT (exceptionally) - DOS386, 12.01.2008, 02:38
- TripleFault HDPMI32 | CuteMouse is INNOCENT (exceptionally) - jaybur, 12.01.2008, 07:59
- No (Cute)Mouse problem, No "raw" mode problem - Japheth, 13.01.2008, 08:51
- SET HDPMI=1 should help - Japheth, 14.01.2008, 03:26
- bug in ??? fixed ??? - DOS386, 14.01.2008, 10:18
- HDPMI=1 did help Ladsoft also | DOS/32A is "paranoid" :-( - DOS386, 14.01.2008, 11:06
- SET HDPMI=1 should help - Japheth, 14.01.2008, 03:26
- TripleFault HDPMI32 | CuteMouse is INNOCENT (exceptionally) - DOS386, 12.01.2008, 02:38
- What about CuteMouse? - Japheth, 10.01.2008, 07:01