Peter,

> Clement is right with his warning: there is a bug in 4.3.0 that we just
> fixed last week which causes problems surrounding restarting of clients
> and servers. (We are about to come out with 4.6.0 which has the fix).
> (Rebooting has never been necessary here. )

Hmm, well, I'll try updating to the new version then.

> However, in your case, I think it is something else.  More or less the
> only thing that RPC2_Init does is to create a socket and bind to port
> 1361.
> 
> You should NOT have a client running the before you have a server that is
> working.  Is your networking up? Is there a message in /vice/srv/SrvErr?

Yes, networking is up.  No, there's nothing in /vice/srv/SrvErr.

> You can debug this by typing "startserver -d 10 (or even higher like
> 1000,100000 for very verbose debugging)&" and trying again.

Ok, done that.  In /vice/srv/SrvLog there is:

1:18:47 New SrvLog started at Fri Jun 12 11:18:47 1998

11:18:47 Resource limit on data size are set to 2147483647

11:18:48 Server etext 0x815aac4, edata 0x81b22a0
11:18:48 RvmType is Rvm
11:18:48 Main process doing a LWP_Init()
11:18:48 Main thread just did a RVM_SET_THREAD_DATA

Partition /vicepa: inodes in use: 0, total: 262144.
11:18:49 Partition /vicepa: 1117444 available size (1K blocks,
minfree=5%), 1579
26 free blocks.
11:18:49 Setting Rvm Truncate threshhold to 5. 

> If all goes well you would see a message "File Server Started" in the
> SrvLog file.   Then you must make your root volume (that is mounted
> automatically on /coda by the client) and you can fire up a client.

Hmm, well, as you can see from the SrvLog above, the file server doesn't
seem to be starting.

There is a srv process running, as follows:

srv -d 10 -trunc 5 -nosalvageonshutdown -nodumpvm -rvm /var/log/rvm.log
/var/log/rvm.data 20480000

I'm using files, as I'm just testing the server at the moment.

Thanks,
Brad
-- 
Bradley Marshall
Sysadmin
Plugged In Software