1 May
2016
1 May
'16
11:31 a.m.
VB4 is what, mid 90s? How about you upgrade the code?
Bill Degnan
twitter: billdeg
vintagecomputer.net
On May 1, 2016 1:29 PM, "Mike Whalen" <mikew at thecomputervalet.com>
wrote:
I can?t really tell if this is on-topic, but there?s
[no|some|much] shame
in trying?
I have a Visual Basic 4 application that I need to run on modern 64-bit
hardware I can do this in a VM, but I really need this VM to be wicked
small, like under a gig. The smallest XP VM I?ve seen is 600MB (which might
be good) but XP is becoming very hard to source these days.
I am bummed that there doesn?t seem to be something like vDOS or DOSBOX for
VB applications. Or? maybe there is?
Does anyone have any suggestions on how I might go about doing this?
m
1 May
1 May
11:36 a.m.
Wayne
On May 1, 2016, at 11:31 AM, william degnan
<billdegnan at gmail.com> wrote:
VB4 is what, mid 90s? How about you upgrade the code?
Bill Degnan
twitter: billdeg
vintagecomputer.net
> On May 1, 2016 1:29 PM, "Mike Whalen" <mikew at thecomputervalet.com>
wrote:
>
> I can?t really tell if this is on-topic, but there?s [no|some|much] shame
> in trying?
>
> I have a Visual Basic 4 application that I need to run on modern 64-bit
> hardware I can do this in a VM, but I really need this VM to be wicked
> small, like under a gig. The smallest XP VM I?ve seen is 600MB (which might
> be good) but XP is becoming very hard to source these days.
>
> I am bummed that there doesn?t seem to be something like vDOS or DOSBOX for
> VB applications. Or? maybe there is?
>
> Does anyone have any suggestions on how I might go about doing this?
>
> m
>
Not exactly what you asked but the app should run okay as is on 64 bit
hardware. You might have to copy the vb4 runtime dlls and any ocx's to the new
machine.
I run a vb4 .exe on win 7 64 bit.
12:07 p.m.
Wayne,
You know, I thought so, but all I really get when trying to run it is a
message on the screen, ?This app cannot run on this PC. Contact the
software manufacturer.? This is Windows 10. The message is pretty, blue,
and takes up the entire screen. I?m sure someone meant well, but I don?t
know what the matter is exactly.
Thanks. I?ll keep poking at it.
On Sun, May 1, 2016 at 1:36 PM, Wayne Sudol <wsudol at freedom.com> wrote:
Wayne
On May 1, 2016, at 11:31 AM, william degnan
<billdegnan at gmail.com>
wrote:
VB4 is what, mid 90s? How about you upgrade the code?
Bill Degnan
twitter: billdeg
vintagecomputer.net
> On May 1, 2016 1:29 PM, "Mike Whalen" <mikew at thecomputervalet.com>
wrote:
>
> I can?t really tell if this is on-topic, but there?s [no|some|much]
shame
> in trying?
>
> I have a Visual Basic 4 application that I need to run on modern 64-bit
> hardware I can do this in a VM, but I really need this VM to be wicked
> small, like under a gig. The smallest XP VM I?ve seen is 600MB (which
might
> be good) but XP is becoming very hard to
source these days.
>
> I am bummed that there doesn?t seem to be something like vDOS or DOSBOX
for
> VB applications. Or? maybe there is?
>
> Does anyone have any suggestions on how I might go about doing this?
>
> m
>
Not exactly what you asked but the app should run okay as is on 64 bit
hardware. You might have to copy the vb4 runtime dlls and any ocx's to the
new machine.
I run a vb4 .exe on win 7 64 bit.
12:08 p.m.
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.
On Sun, May 1, 2016 at 1:31 PM, william degnan <billdegnan at gmail.com> wrote:
VB4 is what, mid 90s? How about you upgrade the
code?
Bill Degnan
twitter: billdeg
vintagecomputer.net
On May 1, 2016 1:29 PM, "Mike Whalen" <mikew at thecomputervalet.com>
wrote:
I can?t really tell if this is on-topic, but
there?s [no|some|much] shame
in trying?
I have a Visual Basic 4 application that I need to run on modern 64-bit
hardware I can do this in a VM, but I really need this VM to be wicked
small, like under a gig. The smallest XP VM I?ve seen is 600MB (which
might
be good) but XP is becoming very hard to source
these days.
I am bummed that there doesn?t seem to be something like vDOS or DOSBOX
for
VB applications. Or? maybe there is?
Does anyone have any suggestions on how I might go about doing this?
m
12:52 p.m.
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
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
3156
days inactive
3156
days old
5 comments
4 participants
participants (4)
-
billdegnan＠gmail.com -
brendan＠bslabs.net -
mikew＠thecomputervalet.com -
wsudol＠freedom.com