I remember some articles talking about ancient versions of Windows having issues with the clock speeds of more modern hardware. In order to get them to work at all they had to be hacked with unofficial patches.
Not saying that's the issue here, but as @ColoradoMarmot says the CPU in question may be the difference between it working, and not working.
Also, Fusion is using Apple's Hypervisor Framework as a hypervisor instead of their own hypervisor kernel extensions. Perhaps that's a difference as well between where your VM runs on Workstation (which may.or may not be using Hyper-V as the hypervisor) and your Mac running Fusion.
Net: It's way past time to get off it, no matter what it runs. Glare right back at the customer :-).
Sometimes "No" is the right answer.
And if they insist, try running it on UTM / QEMU. It emulates those ancient Intel CPUs and may run that code where Fusion won't. But then they'll complain about the speed.
- Paul (Technogeezer)
Editor of the Unofficial Fusion Companion Guides
