Well, it is worth a try, so here we go.
Background: Using XP Pro until recently, when the server died, totally. New build with SAS Mirror, Windows 10 Pro installed on a Hyper-X Predator on the PCI bus, 48 GB of memory, two sockets (8 cores), and the desperate need to run XP Pro again for Access 1997. With a copy of the XP install partition that would not boot - blue screen only - but also a VHD containing another XP Pro, that Hyper-v would not touch.
So, as by the above, I explored Hyper-v until I found it would not run XP Pro anyway. But Oracle's VM would, the manual said; and it does.
After a few test creates of machines only, no install of OS, I thought I will try to import the quite old VHD; and, voila, this started up XP Pro. After re-registering it as requested, I got XP Pro to work as before. I even managed to install a CanoScan 8400F scanner on it that now works. All of the drag 'n' drop functionality, installing from CD_ROM drive, display sizing, mouse, keyboard, internet, etc, now work beautifully. Even other programs still installed in XP Pro work as before. Just brilliant.
But now I have struck a problem I cannot solve: Having installed Microsoft Office 97 for Access alone, when I launch it, all I get is an error that says Out of memory! When I click OK, it expands a bit and says: A system error occurred, or there isn't enough free memory to start Microsoft Access. Close unneeded programs and try again.
This is with Task Manager reporting around 3GB of available memory and nil applications running.
Question 1) Might someone have had a similar issue; and solved it by kind of simple steps to take?
Question 2) How can I tell whether it is a System Error or a memory issue?
Having initially allocated 4GB of memory to the VM, I am fully aware of limitations by XP Pro and its limits of 3.2GB; nevertheless, I did change the allocation to 8GB. But, as expected, this had no positive effect on my problem.
If I could obtain some relevant input on this, that would be greatly appreciated. Peter, down under!