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?
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?
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.
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.
AFAIK Dependency Walker can't process 16-bit programs/DLLs at all. It will report an error if such files were passed into it.
While Dependency Walker is indeed useful in NT 3.51, if ScanBin is as good when it comes to 32-bit programs it might be a better alternative for use cases with older WinNT OSes...
doshea wrote on 2024-05-27, 11:39: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?
Yep, WIn32s binary. Microsoft Visual C++ 4.1 has a debugger, it seems, but it requires extra setup.
Also Thanks for the suggestion, will check TDUMP out.
Dwedit wrote on 2024-05-31, 05:27:Win32s can only run EXEs that are relocatable, meaning they have a .reloc section. There are also many other restrictions as we […]
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.
OH, is that the reason why it says invalid format? that would make sense, actually.
WAIT, does that mean... firefox....
nah, im kidding, but had some luck a few days ago getting an old version of mozilla application suite to try to run, before it failed due to outdated dependency (i think, if you haven't guessed yet, this is one of the reasons i'm asking), and just... ran in the background for time immemorial.
K32x86 wrote on 2024-06-14, 23:46: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 […]
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.
Thx for that, will check it out.
LSS10999 wrote on 2024-06-16, 06:16:AFAIK Dependency Walker can't process 16-bit programs/DLLs at all. It will report an error if such files were passed into it.
While Dependency Walker is indeed useful in NT 3.51, if ScanBin is as good when it comes to 32-bit programs it might be a better alternative for use cases with older WinNT OSes...
Ummm.... not to sound imposing or anything but ummm... title? I want to test a few 32-bit apps, but they either throw cryptic errors, or don't run at all.
