🚀 go-pugleaf

Hello Conrad,

I had the same problem until I registered JBuilder via the installation
program.  Then for some reason it worked :)  I thought I had registered it
previously, but apparently I either hadn't or it didn't take the first time.

Conrad Hoesle-Kienzlen wrote:

> That is the first thing I checked (as a Java user I am very "case sensitive
> <g>). It does not work in either case.
> ...Conrad
>
> Michael J. Rozlog wrote:
>
> > Conrad:
> >
> > The part number is case sensitive.  This should solve the problem.
> >
> > Mike
> > rozm@msn.com
> >
> > Conrad Hoesle-Kienzlen wrote:
> >
> > > Finally it looked like the bug-situation would be alleviated a little.
> > > But I knew it would be a vain hope.
> > > "Your CD part number doesn't match" is all I get, although I typed it in
> > > letter by letter, digit by digit, exactly as it is printed on the CD.
> > > Oh, BTW: there is a sticker on the CD cover which also looks like a
> > > valid part number but is slightly different (one digit is a 0 instead of
> > > a 5), but that doesn't "match" either.
> > > ...Conrad
> > >
> > > Edwin DeSouza wrote:
> > >
> > > > Here is the URL for downloading the updates:
> > > > http://www.borland.com/jbuilder/updates/
> > > >
> > > > In addition, we have added 4 new newsgroups for JBuilder:
> > > > borland.public.jbuilder.deployment
> > > >   - This newsgroup will deal with applet and application deployment
> > > >     issues. It's meant to relieve some of the stress on
> > > >     applet-issues, and should allow new users to scan recent
> > > >     posts easier.
> > > >
> > > > borland.public.jbuilder.compiler
> > > >   - For posts concerning the compiler in JBuilder
> > > >
> > > > borland.public.jbuilder.debugger
> > > >   - For posts concerning the debugger in JBuilder
> > > >
> > > > borland.public.jbuilder.as400
> > > >   - For posts concerning IBM AS/400 connectivity with JBuilder