🚀 go-pugleaf

dnoyeB <lamont_gilbert @ rigidsoftware.com> wrote:
> Yes, installing JB4 also hosed my local setup.  I dont know what its
> setting, but my java started behaving funny after its installation.  Now JB4
> is working just fine...

JBuilder's installer provides a copy of Sun's Java2 SDK for Windows.
Sun's license for distributing the SDK demands that Borland's installers
update the windows registry to point to the newly-installed version of
Java.  Naturally, this tends to break any Java jvms already installed on
the machine.  Other apps already present, which depend upon the older
JVMs, might also break.

I think you can simply re-install the prior JDK, the registry will be
reset back to its original settings by the older software.  This won't
affect JBuilder, which does not rely upon the registry for anything.
(The only reason its installers touch the registry is because Sun
demands it be done that way.)

> <wuliao999 none> wrote in message news:3b3ae3b8$1_1@dnews...
>>
>> When I just install JB4, it's all right. After a period time,
>> java applications cannot run from command line. For example, I
>> run an app:
>> c:>java myApp
>> then it says:
>> Exception in thread "main" java.lang.NoClassDefFoundError: myApp
>>
>> But it runs well before,and in JB4 IDE,it runs as well.
>>
>> regards



-- 
Joi Ellis (TeamB)               http://www.teamb.com/
No direct email, please.
For best results, post on news server newsgroups.borland.com!
Newsgroup Info: http://www.borland.com/newsgroups/guide.html