Howard,
We followed up with ZeroG’s support on this issue and found the following thread:
http://community.zerog.com/cgi-bin/ikonboard.cgi?s=3f4f96893a30ffff;act=ST;f=13;t=1892;hl=%indows+and+%erver+and+2003
Basically, it looks like JDK 1.4.2 reports the correct value for os.name when running on Windows Server 2003. Prior JDK’s did not, since they were release prior, and would report the platform was Window XP, allowing installers to proceed. It would seem that the workaround would be to run the installer with JDK 1.4.1, at this point. But it’s a little bit complicated. Install Anywhere actually sorts the command path (don’t ask me why) when looking for JDK’s to use for installation. So, you’d have to install 1.4.1 in a directory whose name would be lexicographically early when compared with all your other JDK directories (ie. like c:\\A1.4.1Install)
To turn on debugging so we can see exactly what is going on, please set the environment variable LAX_DEBUG=1 and rerun the installer. This should really be the first step.
–Scott
MyEclipse Support