since it works perfectly .. never change a running system ? (Developers)
> DPMIST32.BIN was formerly named DPMIST32.EXE and if it was launched
> accidentally it caused a crash. So it was created as an INVALID binary
> (there are some remnants of this issue like the "-b" option in hx's
> shrmzhdr.exe) which makes the DOS loader complain about it.
Any attempt to prevent bugs or make a piece of software more fool-proof is good ... but having success in this is even better
1. YES, it crashes if made VALID
2. Well, it also crashes as-is INVALID - thus the "fix" doesn't work
3. There is a horrible bug in VALX becuase of this. IIRC you were the linker lover and expert - don't you care ?
4. The bug causing the crash is elsewhere - see below
> it could possibly be created as a VALID binary without any harm now.
It should definitely
> But since it works perfectly ... never change a running system ...
1. Still crashing system (I never got this crash before you gave me the hint to rename BIN into EXE and run it as-is )
2. Bugged VALX
At least, I fixed this bug and many other bugs in DPMIST32.BIN, and also did a few other improvements:
http://board.flatassembler.net/topic.php?t=8316
---
This is a LOGITECH mouse driver, but some software expect here
the following string:*** This is Copyright 1983 Microsoft ***
Complete thread:
- [BUG] Criminal Mark-related bug | DPMIST32.BIN/PESTUB/ VALX - DOS386, 24.01.2008, 02:21 (Developers)
- [BUG] Criminal Mark-related bug | DPMIST32.BIN/PESTUB/ VALX - Japheth, 24.01.2008, 06:05
- since it works perfectly .. never change a running system ? - DOS386, 19.02.2008, 01:41
- since it works perfectly .. never change a running system ? - Japheth, 19.02.2008, 19:21
- since it works perfectly .. never change a running system ? - DOS386, 20.02.2008, 01:45
- since it works perfectly .. never change a running system ? - Japheth, 20.02.2008, 08:16
- since it works perfectly .. never change a running system ? - Japheth, 21.02.2008, 10:22
- since it works perfectly .. never change a running system ? - DOS386, 20.02.2008, 01:45
- since it works perfectly .. never change a running system ? - Japheth, 19.02.2008, 19:21
- SnglFault ->DblFault ->TripleFault -> BOOM - unavoidable ? - DOS386, 19.02.2008, 02:00
- SnglFault ->DblFault ->TripleFault -> BOOM - unavoidable ? - Japheth, 20.02.2008, 10:51
- SnglFault ->DblFault ->TripleFault -> BOOM - unavoidable ? - DOS386, 21.02.2008, 02:33
- SnglFault ->DblFault ->TripleFault -> BOOM - unavoidable ? - Japheth, 21.02.2008, 07:05
- SnglFault ->DblFault ->TripleFault -> BOOM - unavoidable ? - DOS386, 22.02.2008, 03:09
- SnglFault ->DblFault ->TripleFault -> BOOM - unavoidable ? - Japheth, 21.02.2008, 07:05
- SnglFault ->DblFault ->TripleFault -> BOOM - unavoidable ? - DOS386, 21.02.2008, 02:33
- SnglFault ->DblFault ->TripleFault -> BOOM - unavoidable ? - Japheth, 20.02.2008, 10:51
- since it works perfectly .. never change a running system ? - DOS386, 19.02.2008, 01:41
- [BUG] Criminal Mark-related bug | DPMIST32.BIN/PESTUB/ VALX - Laaca, 24.01.2008, 07:33
- [BUG] Criminal Mark-related bug | DPMIST32.BIN/PESTUB/ VALX - rr, 24.01.2008, 08:18
- [BUG] Criminal Mark-related bug | DPMIST32.BIN/PESTUB/ VALX - DOS386, 19.02.2008, 01:30
- [BUG] Criminal Mark-related bug | DPMIST32.BIN/PESTUB/ VALX - Japheth, 24.01.2008, 06:05