🚀 go-pugleaf

Robbert:

Man, this is like hunting in the dark for a black cat that isn't there!

What version JDK are you using outside of JBuilder?  If you run with the
AppletViewer that comes with JBuilder (\jbuilder\java\bin\appletviewer),
does the problem occur?  If not, try re-compiling with your other jdk
and running with that version of AppletViewer.  It's not supposed to
happen but I don't have a hard time imagining that a new JDK is not
fully backwards compatible with an old one (but that's just because I've
seen it happen a couple dozen times -- just never with .class files).

Trap 0E is, officially, a physical hardware problem.  That being said,
most Trap 0E errors I've come across in Windows (and OS/2 -- same basic
core) have all been related to something loaded in virtual memory
blowing out.

I doubt turning on the JIT will help, but you could run setvars (in the
jbuilder\bin directory) and then try running your app.  That'd be the
fastest way to get the JIT on.

-Rich

R.C. vd Zon wrote:
> 
> Rich Wilkman wrote:
> >
> > Do you get an error dialog or some form or stack trace when it dies or
> > just a GPF with no <Details> button?
> >
> 
> We are using Win95 and WinNT.
> 
> On Win95 we get a blue screen with the OE-exception.
> 
> On WinNt we get the message:
> ------
> java.exe - Application Error
> 
> The instruction at "0x77ed2164" referenced memory at "0x01050009".
> The memory could not be "read".
> 
> Click on OK to terminate the application.
> ------
> No <details> button.
> 
> It's strange that the application doesn't chrash when I'm running
> from within the IDE.
> 
> Does it help to compile the application by the JDK instead of JBuilder?
> 
> When running within the IDE we use the AppAccelerator. Can we use this
> from outside?
> Does that help?
> 
> Is this a known problem?
> 
> Can someone give me ANY hints on how to go on.
> 
> Thanks,
> 
> Robbert