Back to home page

DOS ain't dead

Forum index page

Log in | Register

Back to the forum
Board view  Mix view

HXDOS : how do you identify import missing from system dll ? (DOSX)

posted by DOS386(R), 19.06.2014, 10:05

> Hi, Pals !

Hi NTSC's :-)

> I'm back with a question re. HXDOS : having SET DPMILDR=128,
> if a PE fails at run time because an unresolved import is called,
> how do you determine which was the missing function ?

No way :-( (IIRC I had proposed exactly this already 1'000'000'000'000 times ... look at the source of DPMILDR ...)

> Is there a relatively quick and straightforward method, or would
> you need long and painful debugging sessions ?

Compare the import list of your PE (usually NOT sorted) with the export lists of the HX DLL's.

> Test case : my version of Bochs.exe, compiled from CVS with personal
> options fails early in DKRNL32.DLL, whereas the official build works well
> under the HX extender. This is the failure being logged

> Is there a way to identify the missing import name and or ordinal just
> from the register dump ?

I fear NO ...

Again, look at the import list of your PE, identify the missing imports, and try to track them in the source. AFAIK the official BOCHS binaries do use even some obscure imports by ordinal:

; BOCHS needs 4 imports by ordinal:
; $04 GetEffectiveClientRect
; $06 CreateStatusWindowA
; $10 CreateUpDownControl (unconditionally imported but not called)
; $11 InitCommonControls


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, 11 users online (0 registered, 11 guests)
DOS ain't dead | Admin contact
RSS Feed
powered by my little forum