If, like any sensible person, you have anti-virus and anti-spyware active,
they could crum up an installation if you leave them running during it.
I apologize for being able to offer only stupid and obvious solutions.
"Jeff Hill" <NOSPAMdjhill@tampabay.rr.com.NOSPAM> wrote in message news:86203397-7F53-47DA-9A77-A625A42893A2@microsoft.com...
> I've made some progress on this. I suspect the Sun SGD 4.2.909 testing
> probably caused the original problem.
> It appears that what Windows was actually reporting via "the program will be
> closed" dialog was that it was disabling the Java 1.6 plugin in IE7. When I
> checked in Manage Add-Ins to see what version of the plugin showed up there,
> I saw that the "Java 1.6 Console" was listed but disabled, and the Java
> plugin I'd expected to see wasn't listed at all. Once I re-enabled the
> console and restarted IE7, "Java(TM) Platform SE environment 6" showed up,
> too, and was also enabled.
> So, it's not a JVM being killed, just the IE7 plugin, so that probably
> wouldn't affect a running JBoss instance. I can probably live with that, and
> at least proceed with other installs and testing.
> FWIW, I have reinstalled the 1.6 JRE with the latest version (b105). That
> didn't help IE7, but I can now get to the SGD login dialog using FireFox.
> In IE7,I haven't seen the runtime get disabled yet, but then I haven't
> retried SGD over and over either. I'll do that once the server admins give me
> a another working id and password (the ones I had have already expired).