I just totally reconfigured my computer with XP, installed all service packs and updates then I installed Jemplode, I can open it use it and it works great but when I close it.. the app goes away and within 2 seconds the computer beeps and starts the boot process again. Everytime! I tried to uninstall it.... it got all the way through the process and rebooted my machine, it's still in the list of software when it gets rebooted.

Anyone had this issue? I really wanna use Jemplode...

Wasn't XP the one where they didn't ship it with a Java runtime engine?

Anyway, to get Jemplode working well on my Windows box, I had to install the Sun JRE and use it just for Jemplode. But in order to run certain other web-based Java stuff from within IE, I have to use the Microsoft JRE. Someone here on the BBS showed me that there's an advanced option in IE to deselect the Sun JRE for IE.

Anyway, so I installed the Sun JRE, then I deselected it in the IE advanced options, and now Jemplode works great and all web-based Java stuff works great in IE.

I've been using Jemplode for almost a year now with Windows XP and I have never had any issues. I'm currently using version 44 but have used a couple of other versions also.

Edit: Downloaded Java from http://www.sun.com/

Cool, thanks guys, I figured it probably had something to do with java. Just haven't had the time to fix it up right (until it started making my computer crash)...

Wow this blows... downloaded the latest Jre... no dice, I know it's a java issue now because even when I open the webstart utility (came with the Jre) and close it, the computer reboots. I re-installed IE, slapped on directx 9 (don't know what I thought that would help but hey ya never know), re-installed Sp1 for XP and went through all the settings for the java plugin and all the settings for IE... I'm at a loss now..

Oh, and it only seems to do this for programs that deal with java (other then the microsoft vm)

Oh, and it only seems to do this for programs that deal with java (other then the microsoft vm)

Wait a minute, you expect us to believe that the Microsoft VM works and the Sun one doesn't? On a Windows OS? Say it ain't so!

At least one of the systems I "maintain" for someone has the Sun Java VM set up for the Airport Modem dialer utility, and works fine. At this point I can't think who still has a pre-XP machine there so it must work at least occasionally

In reply to:

---

Wait a minute, you expect us to believe that the Microsoft VM works and the Sun one doesn't? On a Windows OS?

---

Thats not what I'm saying at all... Windows broke it for everything else except it's own.... damn you Gates!

Honestly, I think something has gone terribly wrong with this new installation... hyperterm is acting funky, the java thing... I think after I get all my music back in place (lost it all thanks to MS dynamic disks, damn you microsoft, why are you so user friendly) I'm going to do a full reinstall and start from scratch.

I'm going to do a full reinstall and start from scratch.

May I suggest choosing Win2k instead of XP when you do this?

but XP is so cute and fluffy... 2k was what i'd been using before, I noticed some pretty convicing speed increases with XP especially with booting (but then again if my PC's not rebooting every 5 minutes it wouldn't matter). I might go ahead and use 2k again... without dynamic disks of course.

I've also seen this with JEmplode 45 and had to go back to version 44. I don't know if the Java versions are different in 44 vs 45 - I didn't have time to check into it.

-Chuck

he he.... get this... Video Drivers... more specifically ATI All in wonder radeon drivers, I don't get why it only acted up when closing java applications. Actually tried everything and ended up using the XP system restore feature. Working like a charm now.

In reply to:

---

he he.... get this... Video Drivers... more specifically ATI All in wonder radeon drivers, I don't get why it only acted up when closing java applications. Actually tried everything and ended up using the XP system restore feature. Working like a charm now.

---

Bet ya can't guess what the video card in this machine is?

Yup, you guessed it - ATI Radeon...

-Chuck

Hope Bruno is watching this.

In ATI's feeble defense, it is a first gen Radeo in fact I believe the model is simply All in wonder Radeon. But still no excuse for ATI's crappy drivers.

This is a known issue (to an extent) with ATI's drivers. Its stems from sun's use of D3D calls in their latest java machine and there less then steller use of those calls. Anyway, i've been looking around rage3d and found this tidbit:

quote:
----------------------------------
"You can use Java 1.4.1_01, but you have to disable Direct3D hardware support in Sun Java.

You can either use the command line option of "-Dsun.java2d.d3d=false" or set it in the Sun Java plugin control panel.


Here's the steps you need to take:

Note: if you can't disable the use of ddraw by java prior to
installing it, you can still disable the use of ddraw by the
system, install java, set the -Dsun.java2d.d3d=false in
the plugin control panel, and then enable ddraw in the
system again.

The ddraw can be disabled by either running "Program
Files/DirectX/Setup/dxsetup" application, or in the Display
Properties panel: click 'Advanced' button, then go to
'Troubleshoot' tab, and set the slider on the second mark
from the left."
--------------------------------
taken from: http://www.rage3d.com/board/showthread.php?s=&threadid=33666213&highlight=java+reboot

I really hope this fixes the problem; I'm going to try it when i get home.

mike

Very interesting, thanks!

I can't believe that ATI (or an ATI defender) can possibly say that it's Java's fault that your computer reboots because it uses an API that ATI implements. Perhaps Sun doesn't use it correctly, but that means that ATI should return an error, not reboot.

I believe i stated in the first line of my post that this is an Issue with ATI's driver's. I was simply attempting to expain why it was the JavaVM and not most windows apps that cause this issue. Quite frankly neither Sun nor ATI seems to show much proficency in writing windows Applications for their repsective products. ATI should prevent the reboot when it receives bad data, Sun should improve their writing for windows (alpha transparency is another example of these sort of problems).

mike

Sorry. Didn't mean to implicate you.

Believe me, when I say I'm no ATI defender, I've suffered through terrible drivers with 3 different All in wonder cards. Why I keep buying them is beyond me, but the functionality is pretty good. Supposedly ATI is really working hard on cleaning up their drivers, and for the most part this is the first abomination I've seen in a while, however I do believe ATI has a long road ahead of them as far as driver stability.

The Java issues come to no surprise to me, after talking to a few of our developers one being the co-author of this book and a few others (not to be a name dropper I just think it's cool that I work with a guy that writes books on java) but basically he said it's just like any other open source platform in that if it breaks theres normally a switch or something that will make it not break.

Believe me, when I say I'm no ATI defender,

I am. Doesn't work for you? Send it to me. Works fine in my Linux machines.

You mean that your ATI hardware works fine when you avoid ATI software?

I think you made our point.

You mean that your ATI hardware works fine when you avoid ATI software?

ATI doesn't make any software for me to avoid, do they?

I'm not interested in running Bill the Gates' operating system.

Video drivers are software. Your ATI video card works fine. People running Windows have problems. Your video drivers are written by XFree86 contributors. Windows users' video drivers are written by ATI.

Draw your own conclusions.

Personally, I think that ATI software deveoplers spend way too much time trying to make their software avoid Windows UI specifications. I've always had problems with ATI software, both technically and aesthetically. I've occasionally had technical problems with nVidia drivers, but less often than with ATI. I've never had any aesthetic problems with them. So until ATI gets its software act together, I'll continue to avoid them, at least for my Windows machines. I'd prefer to avoid them elsewhere as well, in hopes that the lack of sales will encourage them to write better drivers for those stuck with crappy OSes.

Video drivers are software. Your ATI video card works fine. People running Windows have problems. Your video drivers are written by XFree86 contributors. Windows users' video drivers are written by ATI.

The point was, I'm not running Windows, so there is no ATI software for me to try.

You are doubtless correct; I've heard such complaints before. You won't like my answer, so I won't give it, but you're welcome to read between the lines and flame me for it