Andrew Phelps wrote:
>
> In setting up the first V-Net server Ive ever installed -- I get a slew of
> errors surrounding the ServerSocket portion of the code. So, I made a very
> simple ServerSocket test app, and that threw the very same errors. Now I
> dont admin the server, but if anyone could look at this and tell me what is
> going on I'd be grateful, I think its odd that it can compile all the java
> progs without error and then error at runtime due to things not in the path
> ( ?? )
Yeow.
I have been doing a lot of playing of the code on Linux systems, and
it all works very well.
IS this a PC running Windows [nt/95]?? I'd expect that the registry
needs some library; or the registery knows about the library, but
it really is not on the system, or something like that.
(the loadLibrary error looks like it is indicating a dynamic library
not found)
Good luck! After burning my fingers tooo much whilst working with
Microsoft OS's, I turned to one that I could work easily on.
Cheers;
John Stewart.
> Which in return will throw the following errors:
>
> the-server-machine: {65} % java test1
> java.lang.UnsatisfiedLinkError: no net in shared library path
> at java/lang/Throwable.<init>(line unknown, pc 0x1a718f)
> at java/lang/Error.<init>(line unknown, pc 0x1a72e1)
> at java/lang/LinkageError.<init>(line unknown, pc 0x1a7269)
> at java/lang/UnsatisfiedLinkError.<init>(line unknown, pc 0x1a71f1)
> at java/lang/Runtime.loadLibrary(line unknown, pc 0x1a473f)
> at java/lang/System.loadLibrary(line unknown, pc 0x1a0979)
> at java/net/PlainSocketImpl.<clinit>(67)
> at java/net/ServerSocket.<init>(59)
> at java/net/ServerSocket.<init>(131)
> at java/net/ServerSocket.<init>(83)
> at test1.main(11)
> the-server-machine: {66} %
