Windows 2000 in VM Under Win 7??

What the heck is "decndis.sys"???

Edit: I see entries about "OpenVMS" at google while I search for "decndis.sys"...

zzz2496

decndis is part of the DEC (Digital Equipment Corp) LAT protocol that we use to access the VAX. You can see the DEC stuff here on my network properties.

Now, I can disable these (or uninstall them) and try the VirtualBox install again. The IT guy said I could try installing the DEC LAT stuff after the VM workstation software installed (assuming it does) and perhaps that might work. Without the LAT stuff, I can't access the VAX, but that's not that big a deal as I access it very very infrequently. I also have a second machine in my work area (an XP machine) that can access the VAX should I need to.

This is a common denominator between the two machines that won't install any VM software (other than the Microsoft Virtual PC that came with W7).

Aahhhh !!!

Can you try that please? Uninstall it, restart, install VirtualBox see if it works.
If it does work, I suggest you access the VAX from Win2K if that's reasonable, assuming you want to run your 2K as your "main workstation".

zzz2496

OK. Success. I removed the DEC driver and VirtualBox installed OK this time.

I have to look back in the thread to see what the next step was for importing my VHD.

Alright !!!
Good for you, report back as soon as you got the VM running
zzz2496

I was able to create the VM using the existing VHD, and start it. Now the Windows 2K VM blue screens! The BSOD is inside the VM window, not the W7 machine.

I will have screen captures for you after lunch.

Well, it's some progress anyway...

I forgot, the VM you created... I assume it's from a physical machine, right? If so, it has plenty of device drivers for that particular physical machine. Either you repair install the Windows 2000 installation, or sysprep it (meaning you need to have access to the original machine, sysprep it, then re-image), or you can use 3rd party program to "modify" the image, so that when it's restored, it will accept the "new virtualized computer".

I personally recommend Macrium's Reflect to create the image. Here's what I did when I move my physical XP installation to Windows Virtual PC (this will also work with VirtualBox/VMware/etc).

1. I image my partition XP partition.
2. I create a new virtual harddisk inside "Disk Management", mount it and assign it some drive letter.
3. I restore the image to the virtual disk. While you're restoring, there's a section on the restore process that provides you with an option to change the MBR, since this is a Windows 2000, I don't know if this will work or not, but you can always try. In that stage, select restore a "Replace with the standard XP Master Boot Record".
4. Restore the image.
5. Once done, detach this virtual hdd from "Disk Management", attach it to the Windows 2000 VM, see if it boots up.

zzz2496

Out of curiosity, try the Windows Virtual PC once again. Check the "Settings" => "Network" part again, see if you can find the missing option after uninstalling the DEC protocol thingie...

zzz2496

Using the VMDK file from MyOldPCs, I am able to boot without the blue screen.

The first time through, when I was prompted for my login password, it took it, and I got to the desktop, which was 16 color 640x480 (this must be increased!). I was prompted for a video driver (which I didn't do),then the machine said it needed to reboot. When it rebooted, it would no longer accept my login password and I can't get past that point.

Ideas?

Question 2: Any way to prevent the mouse from being "captured"? I have a non-standard keyboard, and the uncapture key doesn't work, so I'm trapped. The only way out is a shutdown.

Is there a way to make it so when the mouse pointer is inside the confines of the VM window, those clicks go to the VM, allowing me to freely move the pointer outside the window and back to the host?

What do I want networking set to? It's set to NAT. There are other choices available.