Difference between Mac and Windows Host for XP Guest in VirtualBox
Here's the setup: I have an older piece of remote monitoring equipment, known as a Badger. The GUI control software that runs on Windows is a Java app, the CD has a date of 2003 but I think the software is much older. The setup.exe does not run on my AMD64 Windows 7 installation, I receive a 32 bit/ 64 Bit error, I suspect it might be a 16 Bit app (it's surely ugly enough).
Anyway, I tried to solve this with an XP VM Guest in VirtualBox on the AMD64 Windows 7 host. The setup.exe runs fine but when I try to launch the Java application I get an immediate Windows error:
java.exe has encountered a problem and needs to close.
If I click here to see what data this error report contains, I get:
AppName: java.exe AppVer: 0.0.0.0
ModName: javai.dll ModVer: 0.0.0.0
Offset: 0009b4e
When I view technical information about the error report, there is the usual binhex gibberish but some of the text complains about being out of memory, bad superclass, bad index, class storage allocation error, among others.
Behind the error is the CMD window with:
Symantec Java! JustInTime Compiler Version 3.00.029(i) for JDK 1.1.x, Copyright 1996-98 Symantec Corporation
Later, at home on my iMac which also had an XP VM Guest in VirtualBox available, I installed the software and successfully launched it. I then exported the VM, imported it into my Windows 7 AMD64 host and ran right into the same error as described above.
Obviously, the Hosts are very different from each other but I'm wondering what specifically is the cause for this behavior, where it works on the Mac host but not on the AMD/Windows host?
Some CPU differences are visible to guests in virtual machines like VMware, Virtual PC (current version) and VirtualBox which use native code execution.
Try:
- disabling hardware virtualization. Machine -> Settings -> System -> Acceletation; uncheck Enable VT-x/AMD-V
- using a different virtual machine program, maybe an actual emulator such as Bochs or QEMU (the latter would have to be appropriately configured as it can use native execution as well as emulation).
- running it on a different PC
I actually worked on the software that you're referring. Things we've done in the past to get around strange java/OS issues was to change the GUI shortcut target to use your installed Java version rather than the Java version we sandboxed on the CD. Try changing that and then running the shortcut to see if that helps.
Good Luck!