SET HDPMI=1 should help (DOSX)
> edit: the triple fault's cause is a host stack overflow, that is, your
> application loops (real-mode -> real-mode callback -> prot-mode ->
> real-mode -> ...)
"set hdpmi=1" most likely will avoid the loop. It has been implemented exactly for those DOS extenders which behave paranoid: they except all interrupt and exception vectors and 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.
---
MS-DOS forever!
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