Just a follow-up on my research of this problem. It appears that this is a problem with the WTK itself rather than with the Java Runtime or the way that EclipseME is making the call. For an easy example of this, just use "cmd.exe". Change directory to (for instance) "c:\". Execute (for instance) "c:\program files\wtk25\bin\emulator.exe -version". You will get the same error that EclipseME is getting. It appears that this executable is turning around and calling something else. It is that secondary call that is being done incorrectly by the WTK. Calling emulator.exe is the specified approach for UEI compliance, so I'm hesitant to do anything too crazy to make this work that might also break other UEI emulators. This must also be the reason that things just broke... Perhaps the WTK handled this correctly in past versions.
I'm going to play with a few options to see if I can work around this problem. Barring that, it will likely remain a restriction that EclipseME will only deal with the WTK being installed to a path without spaces. Craig ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Eclipseme-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/eclipseme-users
