VOGONS


First post, by BengalEmpire767

User metadata
Rank Newbie
Rank
Newbie

This would be a great thing if it existed. Would have helped debugging things a lot easier. Dependency Walker can run on old versions of NT (I tested NT 3.51), so why can't it work on Win32s, and is there any way to get it working, to be blunt?

Reply 1 of 3, by doshea

User metadata
Rank Member
Rank
Member

I wouldn't know how to get it working, sorry, but have you found any alternatives?

If not I'd be happy to help you figure out how to get the same sort of information from some utility like Borland's TDUMP, if you're interested in that. It wouldn't be as nice as Dependency Walker but you could get the information you need, I think.

Do you want to use it for a Win32s or Win16 binary?

Reply 2 of 3, by Dwedit

User metadata
Rank Newbie
Rank
Newbie

Win32s can only run EXEs that are relocatable, meaning they have a .reloc section. There are also many other restrictions as well, but that is the biggest one.
Most EXEs made for Win32 do not contain relocation information, unlike DLLs which always do.
`objdump -h file.exe` will list the sections of an EXE, as will `dumpbin /headers file.exe`. (objdump comes with GCC, dumpbin comes with visual c++)
My copy of dependency walker from 2006 has no reloc section.

http://www.dwedit.org/

Reply 3 of 3, by K32x86

User metadata
Rank Newbie
Rank
Newbie

Not sure if this is useful, but there’s a alternative to Dependency Walker called Scanbin, it works in Windows 3.1x and I use it all the time to check missing DLLs and functions. I got it from here:
https://web.archive.org/web/20071005114603/ht … en/scanbin.html

It requires Win32s and works in Windows for Workgroups 3.1x.

If you want to install it in regular Windows 3.1x you’ll need to get the WINSOCK.DLL from Windows from Workgroups and then place it the directory where Windows is installed.