build 255 not working with Windows 2000

I know what you are thinking why are we still running Windows 2000. Anyways we have a few boxes with Windows 2000 on them when i went to install the new multi platform build 255 i realized it wont launch on the win 2 k boxes. I can install the previous 247 build and it starts up fine. Its not just one server i had this problem but two of them do the exact same thing. They will run the last build but wont launch the new build.

The new build will not lunch on W2K only if you have wrong JDK version :)
I wonder if it is the cause of your problems with async jobs.

PS. We put a protection against using wrong Java because a lot of people think that Java releases are backward compatible. They are not. We spend great amount of time explaining this and troubleshooting related issues.
So please ensure you got 1.4 available and JAVA_HOME environment variable points to 1.4 home directory.

Well that fixed one of them The variable was pointing to C:\Program Files\Java\j2re1.4.2_16 but the Java wasnt there MY FAULT im sorry. I have been strict about using the correct version of Java but maybe someone here is changing things, which is my issue and i will correct.
As for the Asynch jobs i double checked that and its a 2000 box but has the correct vesion of Java. The only thing different is the User Variable JAVA_HOME was set not the system variable JAVA_HOME. So if i signed in as a different user i dont think the variable applied. Checking the instructions it says "-make sure your %JAVA_HOME% variable points to the right JDK\JRE installation. " If i changed the system variable it would have applied to all users. Im pretty sure thats what was hosing up trying to upgrade to 255 build i had the admins variable set not the system and tried launching the new install from a new user. I logged on as administrator and the 255 build starts. I will set system variable instead of user variable for JAVA_HOME. Sorry its been a learning experience.