1 May
2016
1 May
'16
12:55 p.m.
Wikipedia says that VB4 was the first version able to produce Win32 binaries, but could
also still generate Win16. If the app is Win16, that would explain why it doesn?t work on
64-bit Windows.
Brendan
On May 1, 2016, at 12:52 PM, william degnan
<billdegnan at gmail.com> wrote:
On Sun, May 1, 2016 at 3:08 PM, Mike Whalen <mikew at thecomputervalet.com>
wrote:
Bill,
I don?t have the source. It?s a custom app written a long time ago by an
organization that no longer exists.
Thanks.
Informally, assuming your emulated environment is working correctly, are
you missing DLL files? Perhaps the error you're getting (Look it up) may
be at the VB4 interprer level, if DLLs were missing, as a catch all DIE
abort sequence. There may be a way to get verbose errors by using a
switch at the command line when you run the program.
Does this program load and run on a vanilla win NT/95 or other
VB4-compatible system? If it does run on a real machine, compare the DLLs
there with your virtual machine. There may be a set of DLLs that need to
be copied over, too for the program to operate.
If not Win NT or Win95, does it work on Windows 3.1? Win 2000?
You could attempt to hexedit the executable.
Bill