Category Archives: Virtual PC

Slackware 3.5

Posted on by
4

A friend of mine was having a hard time trying to configure XF86 from the old Slackware 3.5 days… 1998.

Wow time sure has flown!

Anyways I kind of liked Linux back then as a lot of distros had OpenLook, which made my Linux box feel like a way cheaper SUN box.

While Slackware 3.5 installs great on Virtual PC, the networking just crashes out… So I thought I’d just fire it up on Qemu.

qemu.exe -net nic,model=ne2k_pci -net user -hda Slackware 3.5 Hard Disk.vhd” -L pc-bios -redir tcp:58080::80

And with a bit of tweaking I managed to get it running!

Although with normal VGA there is some weird issues with the cursor…

Slackware 3.5 running openlook

Slackware 3.5 running openlook

It was about as hard as I remember for the xf86config days… you kind of had to mash a few together to get it working…

And if it saves anyone the hassle, here is the XF86Config. (gzipped!)

This is basically regular VGA with a PS/2 mouse… It works on Qemu & Virtual PC, so I’m sure your favorite emulator ought to work as well.

IDE-CDROM for OS/2 2.0

Posted on by
3

I’ve slowly been trying to piece together my old Netware 4.1 stuff to try to run it on Virtual PC… the best I can find is that I’d need parts of Netware 6 to get the networking to run….

But then the other day, I had remembered that you could run Netware 4.1 under OS/2 (the 32bit ones)..

The only ‘snag’ is that I’d need a working CD-ROM driver… And IDE-CD’s didn’t become somewhat popular until the 3.0 WARP days.

Well I did manage to find this zip file, CL_ATAPI.ZIP (Mirror CL_ATAPI.ZIP) that contains the IDE drivers!.. And as it mentions in the BBS description it’ll work on 2.0! Except that it gives NO hints on how to install it.

After a LOT of googling around, I was able to piece together a working solution. Adding this to the config sys by first commenting out the ibm1s506.add.. (Naturally unzip CL_ATAPI.zip into the os2 directory!

BASEDEV=IBM1FLPY.ADD
rem BASEDEV=IBM1S506.ADD
BASEDEV=IBM1s506.add
BASEDEV=IBM1s506.add /A:1 /U:0 /ATAPI
ifs=c:\os2\cdfs.ifs /q
basedev=ibmidecd.flt
device=c:\os2\os2cdrom.dmd
BASEDEV=OS2DASD.DMD

And there we go, drive D all set!

MS-DOS lan client for Virtual PC 2007

Posted on by
Reply

So while I was going through the motion of making my tradewars more… multi user friendly, I needed to test between all kinds of clients and a server…

Since I’m using MS-DOS, Windows 3.0 as my test bed (if it’ll run there, it’ll run anywhere!) I had MAJOR issues with the 3.0 lan client… But digging around on the NT 4.0 Server CD I tried the lanman.dos client.

Using the lan drivers from here: http://wiki.oldos.org/Downloads/DriversAndBootdisks

It was a snap!

I’ve built an NT 4.0 domain controller with both NetBIOS & TCPIP protocols that way all my machines can map into it…

I wonder if there ever was a ms net requester for MacOS..?

OS/2 1.3 on a real pc

Posted on by
1

 

Ok so this isn’t much of an update, but I thought I’d share some Microsoft OS/2 1.3 on REAL hardware…. Yeah, so it’s not emulation but this is COOL!

I scored a copy of Microsoft OS/2 1.3 IN THE BOX.

OS/2 1.3 on a real computer!

Which is beyond rare. But they needed something as a ‘server platform’ for Microsoft Mail 3.x before Windows NT (OS/2 NT) was ready.

Minor tip for Virtual PC 2007 users

Posted on by
Reply

On vista with some fancy multi core machines I’ve found that some OS’s will just DOG big time, inducing major latency, disk errors, and of course it’ll eventually corrupt the guest OS into not working.

As an instance, NT 3.1 takes about 30 minutes to install (compare to Qemu in about 2 minutes tops) and every time I’d try to convert the disk to NTFS it would either corrupt the disk so it couldn’t boot or it would fail saying the disk was unable to convert

Anyways back when Virtual PC was a connectix product it was meant to run on a SINGLE CPU/CORE.  Back then multiproc machines were servers  And who would be running Windows NT 4.0 server on a Windows NT 4.0 server??

Anyways the ‘fix’ here is to set Virtual PC’s affinity to a single core BEFORE you start any VM’s.  I’ve been setting mine to 0, but i suspect it doesn’t matter as long as no other VM’s have started before hand.  Anyways start up Virtual PC, then launch task manager, and set it’s affinity to a single core, then you’ll be good to go!

So far it would seem that Virtual Server is not hit by this, and I have to wonder if you install Virtual server onto a machine running Virtual PC with the new ‘core’ would it work correctly..?

Anyways this fix is good enough for me.  It’s nice to boot up in a few seconds.

Networking with Windows NT 3.1 under emulation

Posted on by
20

 

Windows NT 3.1 does NOT support the PCI bus, making most emulation difficult to impossible.

However some vendors wrote their own PCI routines allowing their PCI devices to work under Windows NT 3.1!

And as luck would have it, the two that I found should work for both VMWare & Virtual PC users!

First the Virtual PC users, you’ll want this file GF10011.EXE , and just extract it, and put it on a floppy.  x64 users will either need to do this under dosbox / MS-DOS in a VM… Also another note about Virtual PC & NT 3.1 is that it has massive pauses, to where it seems to be unusable.  I’ve found that altering the Virtual PC process, and binding it to only a single CPU, and boosting it’s priority helps a great deal, although it’s nothing compared to the speed of Qemu…

VMWare users can download an AMD Pcnet driver here that will happily bind on PCI.  Once you install the driver, you can have it scan the appropriate busses and it should pull up and work.

Another fun thing I found for Virtual PC users, is that the HP Pavilion 5000 desktop shipped ready for Windows NT 3.1, and it was equiped with a S3 video card! And it’s video driver will work with Virtual PC! You can download it from HP’s site here.

This brings Windows NT 3.1 into a far more usable state. Another fun thing I found is that Netscape 2 & 3 for Windows 3.1 WILL RUN! One of these days I’ll have to sort out the exchange client situation…

And if anyone wants to see it in action, be sure to check out Apache running on Windows NT 3.1!

Or you can hit it directly:

http://winnt31.superglobalmegacorp.com/

Security update for Virtual PC/Virtual Server

Posted on by
Reply

The articles from Microsoft are available here and here.  It sounds like some good fun….

FTA:

This security update resolves a privately reported vulnerability in Microsoft Virtual PC and Microsoft Virtual Server. An attacker who successfully exploited this vulnerability could execute arbitrary code and take complete control of an affected guest operating system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.

I know I’ll be updating all my machines…!

Windows XP Mode in Windows 7

Posted on by
1

Well it seems to be all the rage in the world of emulation on Windows 7. Windows XP mode, from the user standpoint is just like the old days of WIN/OS2 from OS/2 2.0 and above.

While WIN/OS2 used specialized device drivers that could ‘punch thru’ the virtual machine, and render each window on the OS/2 PM display, Windows XP mode, takes the Citrix like approach of using Terminal Services (RDP) to initiate a remote display to the local desktop.

Since RDP is the mechanism used, only XP and above will work, sorry Windows 2000 users. Another minor (is it?) annoyance is that the new version of Virtual PC has NO floppy driver support! It also seems to not have sound support, although it’s totally unverified at the moment. I’ll have to snag a VHD with MS-DOS pre-installed along with whatever integration tools I have around.

Anyways, the install is a snap, you can find all the components here.

Setup is straight forward, just install the Virtual PC component, then Windows 7 will want to reboot. Then install the Windows XP msi file (it’s over 450MB) and you’ll get a fully installed copy of Windows XP ready to go, and best of all you don’t have to configure anything. Start Windows XP in a “normal” desktop environment, install whatever it is you want to run. Publishing apps to the Windows 7 desktop is easy, just paste a shortcut under the “all users” start menu, and the screen will blink and it’s available.

The down side, is that other OS’s seem to perform poorly under this version of VPC. The mouse is very erratic on RHEL 4 that I had to setup to emulate a production environment. Also you need to have a CPU with the new virtualization extensions. It seems this VPC version is more like the hypervisor in 2008, then like the old Virtual PC we all knew. I almost wonder if there is a way to run VPC 2004 or 5 on Windows 7 natively for running older stuff…

It will be interesting to see where Microsoft goes with this, as this could leave a major rift in their product lineup. And as I’m sure a few people will find out, just because you have a ‘new’ machine doesn’t mean the CPU is up to the task… Not all new CPUs have the virtualization environment built in…

Another issue I’ve been having is that the network from time to time disconnects and will remain disconnected… It seems if you shut down & power the VM on/off (no hibernation!) eventually the NAT adapter will reconnect. Clearly it’s a beta. Also it won’t let you publish solitary, pinball, nor any of the other games. However it will let you publish cmd.exe so you can run them that way.

 

 

Virtual disks revisted…

Posted on by
6
Again for Linux/ OSX users, it’s no big deal as they have access to the ‘dd’ command. Well I was installing AT&T SYSVr4 when it hit me that you can somewhat convert physical disks with Virtual PC & Qemu…
linked disk1
In Virtual PC you can create a ‘virtual disk’ that links to a physical volume..
linked disk2

And again, just select a physical slave disk with your legacy OS already installed.

Once the disk is linked, re-run the utility and you can then convert the linked disk into a dynamic disk. Once you have your .vhd, you can use Qemu’s qemu-img tool to convert the disk image into qcow,qcow2 (Qemu) or even VMDK for VMWare. The syntax is pretty simple..

qemu-img convert –f vpc attsysv.vhd –O qcow attsysv.dsk

I’ve tested it with AT&T SYSVr4 & OS/2 1.3! Much to my amazement with the fixpacks, OS/2 1.3 will actually RUN on Virtual PC 2007. It’s a shame that IBM saw the SDK’s for OS/2 as a revenue generation opportunity, as it’s amazing how quick it is (once it’s done initializing….) but I guess that’s a given of any 16bit OS that’s written in assembly….

For the heck of it, here’s a screenshot.

OS/2 1.3 running from a linked disk

OS/2 1.3 running from a linked disk

 

OpenBSD 4.4 on VirtualPC 2007

Posted on by
Reply

Well it’s about that time, and OpenBSD has now just released version 4.4!
I’m a big fan of OpenBSD, and of course I wanted to load it up on my laptop. I’ve been wanting to do some tests with Quake1 so I have setup a test server, and now I was needing a client, so I figured OpenBSD should be able to do this.

I installed OpenBSD 4.4, ran ‘startx‘ and naturally had a completely deformed screen.

I did find out that manually running ‘xorgconfig‘ and setting up the wsmouse (protocol & port!), and then selecting the S3 driver “** S3 (not ViRGE or Savage) (generic) [s3]” Option number 25 I think… Anyways from there I told it to use 800×600 16bit depth, and now I’m able to use X11 no worries!