been using Virtual Box (VBox).  It was picked up by Cisco, but they haven't ruined it ... yet

Isn't that Oracle? (www.virtualbox.org, check page-footer)

@nkormanik: What f0dder said:

Also, almost forgot: what's the symptoms when you try to launch the application? If it's a "Windows failed to load JVM.DLL" kinda message, it might be as simple as a x64 vs x86 JRE version issue.

You have (also) installed the x86 version of Java I assume? It sure looks like the SAS application is x86, and those are not capable of loading a x64 edition of the Java dll's. (If the application just shells out to a Java.exe then it would have worked as expected.)

Best suggestion for this direction so far is that it runs fine on Windows XP. It's highly unlikely that you are running XP x64, and unlike other software, Java needs to be installed in the bitness (x86/x64) of the application trying to use it, not the OS. On my x64 Windows I only have x86 Java installed, as I use no application(s) that require a x64 JVM.

NB: Full-blown Java applications shouldn't care nor matter what edition of the JVM is installed, except that the x64 edition has more memory available for applications.

Maybe an OS issue, maybe a hardware issue, we never did pin it down, but we were leaning toward hardware before we quit - not enough return for the effort  .

Never attribute to hardware that which can be attributed to retarded enterprise application developers.

I concur.  Just thought I'd throw it to you folks.

Skwire, done with this one.