its possible the j3d runtime is leaving d3d in a bad state.
 
if you have the dx sdk, run killhelp or pview from MSVC tools and kill the ddhelp process.
 
another test is can you run a plain d3d application after exit and/or kill ddhelp?
 
that helps isolate whether its the j3d or the d3d runtime that is in a bad state.
 
if its just the dlls and runtime are left in a bad state I find about 8 out of 10 times killing ddhelp enables me to run applications without reboot. if the card is truly wedged that does require a reboot..
 
an alternate path is to help debug the j3d runtime with a kernel debugger like soft-ice and post the results.
-----Original Message-----
From: Malguy, Eric G. [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 11, 2000 7:13 AM
To: [EMAIL PROTECTED]
Subject: Re: [JAVA3D] Freeze under Windows98

We've had the same problem and no solution!
-----Original Message-----
From: kwc [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 10, 2000 10:09 PM
To: [EMAIL PROTECTED]
Subject: [JAVA3D] Freeze under Windows98

I'm getting a freeze on my Windows98 system.  The first time I run any Java3d application everything is fine.  The second time I get a hard system freeze that requires a system reset.  It feels like a nasty dll problem.
 
System Info: Windows98
Dell400/128Meg/STB 128
DirectX 6.1
Java3D DirectX version 1.1.3
 
Anyone run into a similar issue? Thanks.
 
kwc
 
 

Reply via email to