harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Antony Miguel <aemig...@gmail.com>
Subject [general] Windows 7 support
Date Mon, 28 Jun 2010 19:56:54 GMT

I apologise in advance if this is not the appropriate category, I'm not sure
exactly where the issue would be here.

Today I downloaded the latest stable builds of Harmony (5.0 r946978 and 6.0
r946981) and ran them on Windows 7. In both cases I got:

Windows 6.1 is not supported
HMYEXEL062E Internal VM error: Failed to create Java VM
FAILED to invoked JVM.

I searched around and all I could find was this:


this was from 2007 and referred to Vista, the stable builds are from May
2010 and my issue is on Windows 7, however looking at the latest version of
the bit of code the above bug mentions (vm_init.cpp) it seems it is perhaps
just erroring because windows 7 isn't specifically listed as a supported

if((osvi.dwMajorVersion == 4 && osvi.dwMinorVersion == 0) ||  // NT 4.0
       (osvi.dwMajorVersion == 5 && osvi.dwMinorVersion == 0) ||  //
Windows 2000
       (osvi.dwMajorVersion == 5 && osvi.dwMinorVersion == 1) ||  // Windows XP
       (osvi.dwMajorVersion == 5 && osvi.dwMinorVersion == 2) ||  //
       (osvi.dwMajorVersion == 6 && osvi.dwMinorVersion == 0)) {  //
Windows Vista
            return JNI_OK;
    printf("Windows %d.%d is not supported\n", osvi.dwMajorVersion,
    return JNI_ERR;

It seems this error is occurring just because the above code tries to detect
specific versions rather than minimum versions (as was suggested in the post
back in 2007), having said that Windows 7 has been out for almost 12
months... has it been left out specifically because there are issues on
Windows 7 which mean Harmony doesn't work on it?

If not then wouldn't it be a good idea to change the above code to let the
JVM run and *try* to work on versions later than those specifically listed
(given that I would imagine the vast majority of JVM features will work on
subsequent Windows versions)? or at least allow the user to specify a
command line switch to not just exit?  As it stands, it seems that if
someone tries to use Harmony on an updated version of windows that hasn't
been specifically hard coded into the above list it will just fail whether
it needs to or not?



  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message