DOS ain't dead

TripleFault HDPMI32 | CuteMouse is INNOCENT (exceptionally) (DOSX)

posted by DOS386, 12.01.2008, 02:38

> But that's YOUR typical style ...

OH well

> A crash in a real-mode callback (RMCB) is always somewhat dangerous,
> because the InDOS flag might be set, making a proper termination "impossible".

Thanks.

> However, the most stupid contributor to the unrecoverable crash possibly
> is a "known" bug in CuteMouse.

Did you or anyone else write about it before ? I was not aware of it (OTOH that no version of CT or any other mouse driver is 100% bugfree, YES).

> It doesn't "allow" an application to crash inside a mouse event proc.

There was trouble with HX, Blocek, GVFM, ...

> Did you also test without/another mouse driver?

Good idea , results:

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

> For example the very good one from Microsoft?

I would rather eat a rat than use a >100 KiB rat driver from M$

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