13 total posts
I found my problem - no SLAT on CPU
Thanks, Bob. Now I see why I couldn't get anywhere. My CPU (Core 2 E5200) doesn't support SLAT. And here I thought SLATs were something you put in a bed to hold the mattress up. I have to say that guy on LockerGnome was somethin' else.
I guess this Virtual Box runs OK under Windows 8 and doesn't require a processor with SLAT?
I've used Virtual Box on less that optimal computers. Sorry I didn't have the answer so I shared what I use.
Well now I've it installed - sorta
I discovered that another old computer I have DOES have SLAT, it's a cheap Biostar mobo with a 4 year old AMD 3-core CPU but it has the pre-requisites, so I installed the 64 bit version of Windows 8 on it. You have to have the 64 bit version for Hyper-V. So after installing it and jumping through the hoops to get Hyper-V working, I created a new virtual machine and installed XP SP3. The install went pretty much as expected, taking about 50 min., and it booted up just fine. Just one problem. I haven't figured out how to get networking to work. I managed to get all the drivers installed, but it says all the NICs are disconnected. I've posted a question in the social.technet.microsoft.com forums am awaiting help. XP Mode was so simple and easy, but this beast is something else. I'm chasing my tail, scratching my head, and using a lot of 4 letter words. If anybody comes along with the answer, I'd sure love to hear it.
Hyper-V - By jove, I've GOT it! :-)
OK, I've hooked and crooked and finally I've actually GOT the sucker working. It's not all that hard once you hit on the right combination of settings, but finding that is like finding a sunken treasure ship. Here's what you have to do. First you set up an external virtual switch in the Hyper-V Management console. You don't want the VLAN box checked. You set this to connect with the real NIC you have with Windows 8. Then second you go to the Settings option below and set one of your network adapters to connect to that external virtual switch. BINGO, it works!
If MS in it's wisdom would just add that to their skimpy little documentation, it wouldn't be all that much harder than XP Mode, but they leave it to you to beat your head against the wall for a couple of days. Oh well, at least now the sucker works. I've activated XP and am now downloading and installing 120 updates. I have to say it seems to be extremely efficient; after watching it install 15 of the 120 updates, I haven't seen the CPU get more than 10% busy. This is with an AMD 3-core 2.8 GHz CPU in a 512 MB virtual machine. Right now I only have 2 GB total RAM, so I consider myself lucky to have it work; the specs say you should have 4, so I'll probably buy another couple of DIMMs and do the upgrade.
One thing I'm still trying to figure out is where all the virtual hard drive stuff is going. The install only saw the first hard drive, which is a 36 GB 10,000 RPM drive, but the XP install said it would use an unassigned 12 MB area on that drive. However the unassigned space on that drive is only 2 MB. I think it's using a file on the Win 8 C: drive, but I've got to research that. Also I haven't figured out how to access the other partitions on this PC or the USB ports, so I ended up burning a DVD with the stuff I wanted to have w/XP and copied it onto the virtual C: drive. This is definitely the hammer and tongs approach, but at least I got the files and data into XP like I wanted. At least I won't toss and turn any more trying to figure out how to get on the Internet.
Ain't technology wunnerful!
No USB support in Hyper-V!
Can you believe it? MS did away with XP Mode with Windows 8 and gave us Hyper-V. But there's no USB support!!! Since one of the popular uses for XP Mode was for old printers and scanners, that just rules out the main reasons I wanted XP with Windows 8. Methinks Mr. Balmer needs to go.
Bob your approach appears to have the advantages that (1) you don't need an XP license, and (2) it supports USB and access to the host partitions (which it doesn't appear you have with Hyper-V).
I did find out where the virtual disk files go. They go in a folder in the C:\Users\userid\Appdata folder.
At least now I know what to think when I hear/read comments about Hyper-V. Until MS gets around to adding at least USB support, I don't think most folks will find it for them, certainly not me.
Thanks for the update on USB
The last things I need XP for is an old USB Microscope which is not to say we won't replace it but it's just another thing to replace in the lab.
The other is one last software piece that didn't work on Vista or 7 not matter what bits we tried.
Hyper-V is basically a Virtual machine
client just like toolbox or VMware's product are VM only. XP mode for Windows 7 was a Virtual with Windows XP included for no cost. What thats basically means is the license to run Windows XP is free in XP mode and is installed when you install XP mode. Toolbox and the other virtual machines just give you the ability to set up a virtual machine and you have to get the OS software and install separately. To do this legally if a license needs to be purchased you will need to purchase it. If you already own a retail version of XP you can install any virtual machine and install XP using the XP DVD/CD and it's legal.
And it's a VM w/o USB :-(
Just a virtual machine without USB support! I remember when Windows 98 came out, Gates saying how great USB is. That was 15 years ago, now they put this in Windows 8 and call it a replacement for XP Mode - yuck. I guess when Windows 9 comes out, they'll come out with something that doesn't support networking.
I'm wondering if that's true.
VMWare and VirtualBox had the USB working fine. Microsoft has been bent on reducing the scope of the OS and we see the results. I wonder if this feature was lost along the way.
I'm going to look into that in a few months (projects here are underway.)
According to the MS answers forum...
Good discussion to link to. Note the "boot to VHD" ref...
Hyper V has the boot to VHD where the USB should work again.