pjp wrote:
In article , says...
On 2/10/2019 3:11 PM, pjp wrote:
In article ,
says...
Got 16 bit stuff ?

Create a virtual machine running an older version of Windows
( e.g. XP ) in memory. See Oracle VirtualBox. Very easy, handy and
quick.

I've got 28 great apps written in QuickBasic v4.5, and 14 in Windows
Visual Basic v3 .

I know there is a provision for running things in a compatibility mode
for older versions of Windows, but I could never get it to work.

In the virtual machine I have a desktop with 42 icons. Comes right up
and all apps work great.

Would be nice to have an app to convert all to VB6 which I use
extensively for all ny contenporary stuff.
I just installeed both Virtual PC and VirtualBox. VirtualPC and no USB
means it got deleted quickly. VirtualBox didn't seem to want to use the
network card properly and I gave up in frustation and deleted it also.

Can't tell your definition of 'properly', but there are several network
options in Virutalbox.

I could not get it to properly be seen over my Workgoup ethernet. On a
2nd pc that did Workgroup Browse properly it would sometimes appear
depending on the network choice I made in VirtualBox but it would not
connect or even see the shared folder I'd setup on the vm pc. On the
virtual machine It would see itself under Workgroup browsing and nothing
else. That's the best I could get which was useless.

Shared Folder didn't make any sense to me. Does it just setup a network
share?

You'd think a default fresh install of VirtualBox on Win7 Pro 64 bit
with 8 Gb memory and almost empty 500Gb hard disk with all perphiperals
working properly and then install Win7 as a virtual machine you'ld end
up with something that had everything working (installed 32 bit with 3
GB mem). Apparently not and I just didn't feel inclined to muck with it
further. Fact is I have so many unused PC's here that I can use for
testing I just won't waste the time, least right now Maybe again
future version.

I gotta LOL at your last paragraph :-)

Virtual Machines will try your patience. They are
always finding new and creative ways to foul up.

For example, I just tried to set up a Shared Folder
to take a picture to show you. And do you think that
MF would work ? Nope. It must have taken around two hours,
and while I didn't change anything, I could see after opening
Host Network Manager in the File menu, suddenly it started
working.

I could see somewhere in my travels, the Guest "\\VBOXSVR"
had no workgroup value showing, whereas other things on my
network are workgroup=WORKGROUP. That accounts for why I could
define a shared folder in the Host settings panel, but nothing
could see it. Maybe I was using "nbtstat -a hostname" or something
to check.

In any case, here's a picture of a Host folder, being served
to a Guest via a network node called "\\VBOXSVR". If you look
in Task Manager, you might see a service like that running
as a task.

https://i.postimg.cc/hvYDLKLG/shared...virtualbox.gif

If you think that's bad, getting USB passthru to work is also
a challenge. I think on the third installation attempt, it
randomly started to work. I'm pretty sure I wasn't doing
anything different. I've had installs on other OS disks,
where it worked the first time.

On the left of the picture, a partition called L: is being
shared as "RAMDRIVE", instead of its normal Host SMB name of "RAMDISK".
That's so I could distinguish between two potential mounts
of the same volume.

The right side of the picture, shows the item showing up
in the Network Neighborhood of the Guest.

Now, at one time, VPC2007 could pass a Host drive directly
to the Guest. That worked so well, I managed to *corrupt*
the Host partition from the Guest. Because I forgot
the hosting software was only good for 128GB of partition,
and I wrote a 200GB file from the Guest to the Host drive.
And it corrupted. And I'm like "do you think the .vhd limit
applies to passthru partitions too ? Doh!". So in its way, the
slow VBOXSVR idea is at least a bit better insulated and not likely
to "blow up" Host storage.

Paul