Windows 10: Hyper-V: Windows XP 64 bit > cannot configure network adapters

Hello All:
I am new to Hyper-V, so please pardon any stupid question(s) . . . I have researched this but do not seem to be able to pin down my problem.

I have set up the virtual machine with a legacy network adapter but it does not work (tried the other way as well and that doesn't work, either).
I have used the original XP driver install CD that came with this motherboard (ASUS P6X58D) but the install fails.

Any suggestions?

Thanks very much.

Mike














:)

 

Hyper V: How to install guest operating OS?

I want to use a licensed version of Windows XP Pro within Hyper-V on the host running Windows 10 Pro 64. I used ImgBurn to create an iso copy of the Windows XP Pro installation DVD. But I cannot figure out how to actually install XP in Hyper V. I need
step by step instructions. I've created the virtual disk, but when I run "connect" I get the following Virtual Machine Boot Summary:

1. Network Adapter (00155D06600) The network media is disconnected

2. SCSI Disk (0.0) No UEFI-compatible file system was found.

Please Help!

 

How do I configure Hyper-V on Windows 10?

I had XP mode in Windows 7 Ultimate 64 bits with some software that not runs on 64 bits plus my scanner. When I upgraded end of July, I got Windows 10 Pro 64 bits, but the XP mode with the installed software disappeared. I found a step by step info
about Hyper-V. First step is to turn on the Hyper-V feature, no problem with that. The second step is about a "virtual switch", I am not sure what option to choose or if I need it, can I get help with that? What I want is something like I had with XP mode
in Windows 7 -> I was able to exchange files between Windows 7 and XP mode, like open and save files on any folder on the HD. That is all I need. I not want to access internet when inside Windows XP (for this I have Windows 10). So, do I need this "virtual
switch"? If yes, what would be the best option: external, internal or private network?

 

Just a thought: WinXP Pro was the only edition available as 32-bit or 64-bit, back in the day there wasn't much yet available for 64-bit and I'd wonder the same about any drivers that didn't come with a computer running 64-bit WinXP. I had a copy of that edition but never installed is as I didn't have suitable hardware. I think I'd try running the 32-bit WinXP.

 

Hi Berton:

Thanks for your response. I have installed both 32 & 64 bit versions of XP with the same result. I had hoped that there might be something obvious but it looks like it just might be some bad luck with this hardware/software combination. As I have now used up my entire wife-tolerated allotment of time on this problem, it looks like I may have to throw in the towel.

Some background on my PC: I was the beneficiary of some free hardware from a colleague at work who was upgrading to a new build. As the i7-960 is still a capable CPU, along with some DDR3 RAM I had on the shelf that I purchased way back (when memory prices are about half of what they are now) I filled every RAM slot and, along with some other spare parts, put together a perfectly fine PC.

I also have an ancient CanoScan FB 620P (somewhat low-end) scanner that is so old, there have not been any new drivers since Windows Vista. That and, of course, my newer MB no longer has a parallel port, however, I found a PCIe parallel port card and popped that in (however, I have had some trouble with that, too, but one thing at a time). I figured I'd install a nifty Hyper-V Windows XP virtual machine and be able to continue to use my perfectly good scanner. However, a cost-benefit analysis is not required to conclude that I should just go out and get a new scanner (better capability for probably half of what I paid for my old one).

Time to move on, I suppose.

Mike

 

Think I might give vmware a shot . . . will report back results.

 

Hi there
@MikeM54

XP 64 works fine in VMWARE workstation / player -- you simply use the HOST network adapter and the VM will use that as a "Virtual" network adapter - no NIC driver needed.

depending on your network you might find one of the options "Bridged" or "Nat" won't work - just test each one -- from the VM settings just change --you don't even have to re-boot the VM.

Install VMware tools on the VM after first boot of your guest.

(Might also work on VBOX too --in that case install vbox additions - similar function to VMware tools).

For old legacy stuff like this I find it generally better to forget HYPER-V -- remember though when running VBOX or VMWARE products you have to disable HYPER-V.

Cheers
jimbo

 

Hi Jimbo:
Cool. Thank you for pointing me in the right direction.
I will do as you suggest and let you know the result.
Mike