Hi Roy,

 PK> Another warning, if an OS/2 machine has TCP/IP AND NETBIOS 
 PK> configured, then checking for network connectivity using TCP/IP 
 PK> (EG PING) is going to work LONG before PEER Services (and 
 PK> subsequently the NET USE command) is up and running.

 RJT> Yeah,  that's another aspect of this stuff that is 
 RJT> somewhat puzzling to me, why it takes so long for that 
 RJT> to come up. 

There is logic to it.......;-) TCP/IP is simply a communications protocol
suite, so as a transport layer it gets up and running very quickly. 

OS/2 Peer Services is an SMB Service, and thats a completely different beast.
You need the transport layer runing similar to TCP/IP (NETBIOS), then you need 
to start a Server process, and a Client process (in most cases you can't start 
a Client until the Server is running because the Client uses the Server for
local control). Once they are running you then need to log in a user, and if
that user needs to access a resource on a remote machine then cross platform
communmications need to be established and only then can you use commands such 
as NET USE.

 RJT> I see "The requester service is 
 RJT> starting........" (or something close to that) and it 
 RJT> sits there,  on the screen.  Any idea how I'd make 
 RJT> that one come up minimized?

I am guessing that you are using a shadow of the "Start OS/2 Peer" icon in the 
STARTUP folder. I dont use that, I remove the shadow from STARTUP and just run 
a commandline LOGIN from STARTUP2.CMD and that causes the Requestor to
automatically start without the panel you are probably seeing. its no faster,
but it stops that panel messing the screen......;-)

NOTE: 
It is possible to speed up the startup of OS/2 Peer Services by reducing some
of the timeout intervals, BUT this requires extensive knowledge of the SMB
environment AND the other machines on the LAN with which OS/2 PEER is
communicating. The speed upgrade requires some manual tweaking of various text 
configuration files and if you get just one of the hundreds of options wrong,
your networking (and possibly the entire OS/2 machine) is dead!

Regards...........pk.

--- Maximus/2 3.01