Java Completely Broken in I.E 6.0, WinXP

[Jennerstein]

I'm at my wits end trying to get Java working on my Win XP box , . Here's my current problem:

Neither Sun Java VM nor Microsoft Java VM work on my machine. Java applets do not run at all.

I believe this started after I downloaded Sun Java VM to replace the MS VM. Something happened with my system, or I.E 6.0 got tweaked, and now Java refuses to work. I've tried almost everything. I've googled pages, followed Microsoft Support instructions, followed other webpage instructions. Tried reinstalling MS VM, and/or Sun Java VM here. Didn't work. Tried reinstalling I.E. 6.0 see here. Didn't work. Even tried repairing Win XP with sfc /scannow link. No dice.

Short of completely reinstalling Windows XP, what can I do? Is there a fix for this? I've tried reinstalling one, or both VM's many times, with the appropriate checkboxes checked in Tools, Internet Options, Advanced inside of I.E 6.0. I wish it were it that easy.

Anyway, hoping someone can help, it'd be greatly appreciated!

 

[JZilla]

Have you tried this ?

Oops...didn't read your intire message...stupid me...

 

[prosaic]

The first rule of holes is this -- when you're already in over your head, stop digging.

It sounds as though you may already have sunk yourself. In future, you need to remember that Windows XP has a very good method of recovering from situations like this. It's called System Restore. If you have reinstalled the two different JVMs too many times that alternative may have been killed off. Only a certain amount of disk space is allotted for System Restore.

I suggest looking in System Restore to see if you still have a restore point for the system that predates the first attempt at installing the alternate JVM. If so, use it! Be aware that anything that you have installed in the interim between that restore point and now will have to be reinstalled -- excepting that JVM, of course. Also, many types of system configuration changes will be reset to their pre-restore-point configuration.

Next time you start to make a major change to a Windows XP system you might want to manually set a restore point so that, if the installation / reconfiguration blows up, you'll be able to take the system back to the condition it enjoyed just prior to the foul-up.

Good luck!

- prosaic

 

[Rilescat]

We had a very similiar issue. Instead of installing the JVM, install the SDK. Sun's 1.3.4 SDK worked slick for us. It is a little fatter, obviously, but for some reason....it worked.

 

[Jennerstein]

Hmm, I'll try that. I've been installing Java Standard Edition, 1.4.1_02.

 

[Jennerstein]

Hot diggity that worked!

Here's what I did:

After trying to install both the MS Java VM, and the Sun 1.4.1 VM's unsuccessfully, I restored a recent Ghost Image to get back to my previous broken state. This was to avoid an installation of MS Java VM conflicting with any other Java installation.

I then tried installing the Java 1.4 Standard Edition, didn't work.

Uninstalled that, rebooted, and then tried Rilescat's suggestion to install 1.3. Worked great!

Thanks for everyone's help.

BTW, I haven't dared tried installing 1.4 yet, but I'll let you guys know my results when I do.

 

[Rilescat]

Originally posted by: Jennerstein
Hot diggity that worked!

Here's what I did:

After trying to install both the MS Java VM, and the Sun 1.4.1 VM's unsuccessfully, I restored a recent Ghost Image to get back to my previous broken state. This was to avoid an installation of MS Java VM conflicting with any other Java installation.

I then tried installing the Java 1.4 Standard Edition, didn't work.

Uninstalled that, rebooted, and then tried Rilescat's suggestion to install 1.3. Worked great!

Thanks for everyone's help.

BTW, I haven't dared tried installing 1.4 yet, but I'll let you guys know my results when I do.

Glad to be of help

Looking back at my notes, it seems that the problem with the 1.4.1 JVM is with a path and group of system variables that will litterally eat each other. The SDK doesn't seem to have the problems. It is able to handle the variables correctly.