Facebook
Google
GitHub
Linkedin
Hello everyone, I’m working with an older bending machine that uses an OSAI controller and an OSAI WinMedia HMI panel running Windows 2000. The HMI application SpiraForm.exe runs on this panel and provides the operator interface, communicating with the OSAI controller over Ethernet. Since the original WinMedia panel has become unstable and sometimes fails to boot, I created a full disk backup of its hard drive using Norton Ghost 11.5 and R-Image. To confirm the backup, I restored it onto a new HDD and installed it back into the original OSAI HMI panel — everything works perfectly, and SpiraForm.exe launches and operates normally. What I tried next: I attempted to migrate the system to alternative hardware.
1. Modern PC: Windows 2000 is not compatible with the hardware.
2. Older PC: The original HDD boots, Windows 2000 runs, Ethernet communication with the OSAI controller works, but SpiraForm.exe opens for a second and immediately closes/crashes.
3. Virtual machines (VMware, VirtualBox, QEMU): Windows 2000 boots fine, network communication with the controller works as expected, but SpiraForm.exe still crashes instantly on startup, exactly like on the non-original PC. So the backup is good, and the OS runs on other hardware, but SpiraForm.exe only works on the original OSAI WinMedia hardware. My question: What hardware-specific device, driver, or system component does SpiraForm.exe depend on, that only exists on the original WinMedia panel? Has anyone successfully migrated an OSAI WinMedia + SpiraForm setup to different hardware or into a virtual machine? Any clues about what SpiraForm.exe checks during startup (hardware ID, driver, PCI device, etc.) would be greatly appreciated.
Thanks in advance.
1. Modern PC: Windows 2000 is not compatible with the hardware.
2. Older PC: The original HDD boots, Windows 2000 runs, Ethernet communication with the OSAI controller works, but SpiraForm.exe opens for a second and immediately closes/crashes.
3. Virtual machines (VMware, VirtualBox, QEMU): Windows 2000 boots fine, network communication with the controller works as expected, but SpiraForm.exe still crashes instantly on startup, exactly like on the non-original PC. So the backup is good, and the OS runs on other hardware, but SpiraForm.exe only works on the original OSAI WinMedia hardware. My question: What hardware-specific device, driver, or system component does SpiraForm.exe depend on, that only exists on the original WinMedia panel? Has anyone successfully migrated an OSAI WinMedia + SpiraForm setup to different hardware or into a virtual machine? Any clues about what SpiraForm.exe checks during startup (hardware ID, driver, PCI device, etc.) would be greatly appreciated.
Thanks in advance.
