DOS ain't dead

No (Cute)Mouse problem, No "raw" mode problem (DOSX)

posted by Japheth , Germany (South), 13.01.2008, 08:51
(edited by Japheth on 13.01.2008, 10:12)

> HDPMI32, no mouse driver: still TripleFault
>
> CWSDPMI, no mouse driver: hey, seems to start and work ... just the mouse
> doesn't for unknown reason
>
> CWSDPMI, LOGITECH driver 6.50: The very same PF in RMCB
>
> Are RCMB's used in TEXT based mouse controlled apps at all ?
> I don't see any in INFOPAD's source

It's obviously not a mouse problem then. Also, you wrote that the crash occurs in "raw" mode only. That's true, but it's just because in "xms" mode - and most likely "VCPI" as well, which I didn't test - the included dos extender doesn't use the external DPMI host.

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 -> ...)

---
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