Modern XP?

sorcerer

Active Member
Reaction score
77
Location
Preston, Lancs, UK
A friend has an old Windows XP machine that he's having problems with. He needs XP because the software he has won't run on anything else.

I think I already know the answer to this - drivers - but if he were to buy a brand new machine could he run XP on it? I assume not, because I doubt that components on store shelves today won't have XP-compatible drivers written for them, but I just wanted to check with you more knowledgeable folks.
 
Virtualisation is probably the best solution. You're not likely to find much modern hardware supporting XP directly now.

I have a few customers in the same boat, some with software that only runs on 95/98 even. I would just set him up with an XP VM, preferably one that has no internet access. If it must have permanent internet access (because the the software he needs uses it), keep a backup of the VM to enable quick restoration for when it gets infected.
 
I do XP builds all the time. You can still get brand new motherboards that support XP from Newegg, eBay, etc. I prefer LGA 775 socket boards but you can also get some newer boards that support the AM3+ socket processors or 3rd/4th gen i3/i5/i7 processors that have driver support for Windows XP.

Doing a brand new build that can support 98 is a little more difficult, but still doable. I just did a build with an Intel motherboard that had a 3rd gen i7 processor and I loaded Windows 98 on it. One word of warning though - SSD's don't always perform as expected with the SATA ports in "compatibility mode" (in this mode the BIOS reads the SATA controller as an IDE controller). If you want to use flash based storage, I'd recommend a CF card connected to a dedicated PCI IDE controller card (this is assuming that your motherboard doesn't have a built-in IDE controller - which most boards that support i3/i5/i7 processors don't).

One more thing...Windows 98 doesn't work quite right with more than 512MB of RAM. Seeing as the motherboard only supports DDR3 memory and the smallest DDR3 memory module you can find is 1GB, you have to limit the amount of memory the OS addresses either through the OS itself or in the BIOS.
 
Recommended a printer a few months ago, a Brother that has the big ink tanks built in. Turns out it didn't work with XP. First time I'd run into that. Stopped in an Office Depot after that and looked at all their printers. At the time they all still listed XP except for the Brother. Since then I think I've noticed a few more that don't support XP now.

I have a client I need to setup an XP VM for right now. They had been using XP Mode in Windows 7. But I think they've already upgraded to Windows 10 and not sure about XP Mode in 10.

What do you guys recommend as a VM environment for XP on Windows 10? Hyper-V? Virtual Box? VMware Player?

Also, how do you activate XP? Do you have to find an old key somewhere?
 
This. While you can, as @sapphirescales points out find hardware that supports it that is getting harder to do and running it in a VM makes it far more transportable to new hardware should stuff happen.

A VM is more versatile, but nothing beats using original hardware. Until the old hardware is no longer available, that's what I'm going to recommend 99% of the time.
 
Has he told you that his software will only work on XP - or have you checked yourself to confirm that it definitely only work on XP?

If you're going solely on what he's told you, is it worth you checking over his software yourself to see if it'll run on a newer OS in compatibility mode?
 
Has he told you that his software will only work on XP - or have you checked yourself to confirm that it definitely only work on XP?

If you're going solely on what he's told you, is it worth you checking over his software yourself to see if it'll run on a newer OS in compatibility mode?
Agreed. Also find out if he has the installers or the disks.
 
What do you guys recommend as a VM environment for XP on Windows 10? Hyper-V? Virtual Box? VMware Player?

Also, how do you activate XP? Do you have to find an old key somewhere?

VMware Player has worked well for me over the years, for XP and older OSes. I would probably go with Hyper-V now, depending on the use-case and the virtual hardware requirements. For example, the most common requirement for my customers has been to run some old software that uses RS232/serial ports to control old (but expensive to replace) equipment, such as CNC engraving machines. VMware has worked reliably for me in that application, passing the required ports from the host to the guest. I'm yet to try the same setup with Hyper-V but I do prefer Hyper-V over VMware now, so I intend using that in future, when the need arises.

As for activation, pretty much yes, you'll need a valid retail licence key. If you're lucky the old physical XP machine you're replacing/virtualising will have a retail licence attached to it that you can use. If not, personally, I would try to acquire a valid key somehow to keep it as legit as possible. There are numerous ways around activation of course, and I would not normally condone the use of any type of activation 'hack' but, in the absence of any other options, I wouldn't rule it out. I mean, Microsoft no longer sell XP licences (as far as I know), so it's not like you're taking money out of their pockets by defeating activation, particularly if you're virtualising a system that was previously activated and had a legit (paid for) licence. And, if you feel bad about having to defeat XP activation in some way, you could always purchase an additional, equivalent Windows 10 licence to stick on the machine. Not that the Windows 10 key will work with XP of course, but by way of compensation, just to keep Microsoft happy and out of the poor house. ;) If you're doing a fresh virtual installation of XP though, that shouldn't be necessary.
 
Last edited:
For printers, check the specifications of any printer being considered and see if it has native PCL or Postscript (or BR-script for Brother...). If so you should be able to get just about anything to print to it; if not things may be touchier.
 
As for activation, pretty much yes, you'll need a valid retail licence key. If you're lucky the old physical XP machine you're replacing/virtualising will have a retail licence attached to it that you can use. If not, personally, I would try to acquire a valid key somehow to keep it as legit as possible.

This is what stops the whole idea cold in most all cases I've seen. The chance of that computer having a retail license for XP has got to be extremely small. In all my years in IT, I think I can count on one hand the number of retail licenses I've seen. Everything is OEM, which means virtualizing it is against TOS, and if you decide to ignore that and P2V the thing, it won't activate anyway.

Frustrating, but there we are. I can't professionally recommend or help a client get around EULA/TOS.

I helped a woodworker setup a computer for a C&C machine. This was at the time Windows 7 was winding down and I had this exact discussion with him and recommended we buy a retail license of (at the time) Windows 7 just so we could preserve the ability to virtualize it. He had purchased the machine at auction and paid full rate to the manufacturer to get the control software.

Edit Addition: Unfortunately, this was also the only opportunity I've ever had to address this kind of issue. Every other job that has come around was for a failing or aging machine with OEM licensing already on it, which scuttles the "fix" of virtualizing it so it could be run on newer hardware.
 
Last edited:
It's nice to know you can still build physical machines that support XP with new out of the box parts, but I prefer virtualization simply for the fact it's so easy to make clones / snapshots and perform damage control crazy fast. As long as you can get a virtual setup rolled that ticks all of the necessary boxes and it's not too much of a learning curve for the people who have to use it.
 
Back
Top