...or I could try downloading the win95 versions of the binaries.
"iainmac" <[EMAIL PROTECTED]> escribi� en el mensaje
akfhkc$[EMAIL PROTECTED]">news:akfhkc$[EMAIL PROTECTED]...
> Thanks for the explanation of my first problem - I am now accessing the
> Internal Storage Token on my W2K machine without problems, however I still
> cannot overcome the "Unable to load JSS library ..." despite several
> colleagues casting thier eyes over my configuration and the "Gather
> Compenonents" section of that web page. My next step I think is to pick
up
> the mouse and, speaking into say "Computer, why can't you find those
****ing
> files" but alas I dont think my Windows 98 will respond. This stuff does
> work on windows 98 doesnt it?
>
> "Jamie Nicolson" <[EMAIL PROTECTED]> escribi� en el mensaje
> news:[EMAIL PROTECTED]...
> > iainmac wrote:
> > > Hi
> > >
> > > 2 questions:
> > >
> > > I have downloaded JSS and installed it such that I can run
> TestCryptoStore -
> > > when I give the token name "Communicator Certificate DB" (copied and
> pasted
> > > from "Token Name: Communicator Certificate DB" in Netscape) I get no
> such
> > > Token Exists - but I don't know why.
> >
> > The token name is different depending on which application you are
> > running. In JSS, the token is called "Internal Key Storage Token". You
> > can look it up by name using CryptoManager.getTokenByName(), but a
> > better way is to call CryptoManager.getInternalKeyStorageToken(), which
> > works no matter what the token is named.
> >
> > >
> > > When I try to run this on a different machine (with a card reader
> installed)
> > > I get "Unable to load JSS library..." yet all the dependant files are
in
> the
> > > path, just the same as in the other machine, although the other
machine
> is
> > > W2k and this machine is Win98.
> > >
> > > Any ideas?
> >
> > This one is trickier to debug. The dependencies of JSS are listed in
> > http://www.mozilla.org/projects/security/pki/jss/using_jss.html. Beware
> > of putting any of these libraries anywhere in the C:\WIN* hierarchy. Any
> > DLLs put there will get loaded first, before your PATH is consulted.
> >
> >
> >
>
>
