Back to home page

DOS ain't dead

Forum index page

Log in | Register

Back to the forum
Board view  Mix view


posted by DOS386(R), 14.06.2008, 15:02

> have severe difficulties to accept this as a bug

OK ... have severe doubt whether a deadlock can / should be considered as a desirable effect :confused:

> Then just don't do that!

Thanks for the hint ... trivial as hell (since I already know what the reason of the deadlock is, 3 days ago I didn't :-( ) ... but this won't damage the fact that DPMILD32 has a bug :confused:

> Please provide a real Win32 application which doesn't run in HX

IIRC real Win32 applications ( Mozilla Firefox, Adobe Photosh**, IDE of WATCOM/CC386/VCC2010/... , ... ) don't run on HX anyway because of lack of the high level GUY API :-( And since 99.99% of the "market" is occupied by M$-linker and LD, apparently setting the bit, there is not much space to find one :-|

> BUG? What BUG?

The bug I already had isolated and exhaustively described above ? :confused:

BTW, it's of course not my BUG ... I "imported" it from Tomasz's DLL example ... and since nobody has complained so far one can assume that all versions of Windaube + possibly ReactOS + possibly Wine (or even Beer ??? :lol: ) don't care about this bit. And, if you want to be very rigid about 100% PE compliance, you can raise an error message rather than a deadlock :ok:

I wonder how the answer might have differed if I just pointed about Tomasz's DLL example not working with HX, without investigating / revealing why :surprised:

> My fantastic deb32f debugger still uses DPMILD32 and 16bit dlls.

I see : This program requires Microsoft Windows :clap: ... anyway, roots of this debugger seem to be very old, parts have been converted to PE already, and IIRC cca 2 years ago you wrote something like "needs a redesign, already for 10 years" ...

> To gain 2 kB extended-memory/disk space?

Maybe a bit more ?

> And possibly introducing new bugs during the removal?

It's no way critical ;-) just the DPMILD32 source seems to be a bit ancient, PE support is "hacked" on the top of NE, and seems before a PE can be loaded, first the MZ header is read, analyzed, seeking to "next level", searching for "NE", failure, close the file, if PE is enabled at all, reopen the file, re-read MZ header, re-seek, re-read "next level" ... no big problem, since the debugger uses NE it's of course NOT a good idea for now ;-)

This is a LOGITECH mouse driver, but some software expect here
the following string:*** This is Copyright 1983 Microsoft ***


Complete thread:

Back to the forum
Board view  Mix view
15297 Postings in 1378 Threads, 254 registered users, 12 users online (0 registered, 12 guests)
DOS ain't dead | Admin contact
RSS Feed
powered by my little forum