OT: Ideas for running a VB4 application on modern hardware?

[Mike Whalen]

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.