Greetings Peter!
   A long time ago, in a galaxy far, far away, a coded message from Peter 
Knapper to Don Guy was intercepted...
 PK> Lets just the check NETWORKING layers that you will need on each
 PK> machine, most (if not all) of these you probably already have

1 through 3 taken care of. Both systems have Acer PnP Ethernet cards in 'em, 
properly configured as far as I can tell...
 PK> What type of Network Card and what driver are you using for it on the
 PK> OS/2 machine? Is it the SAME type of card on all machines or are some
 PK> different?
Identical, save that the card in the WFWG system is set to be software 
configurable, while the other system lets Plug and Pray do the dirty work. 
)
 PK> I am not quite sure what you mean here by 'IBM Peer wont install'.
Sorry, I should've been more specific.
When installing it "locally" (to the same system that the CD's in), the 
installation aborts with error # 1604. I can't remember what each of the 
possible causes listed were (three or four of them), but two of them were an 
inability to access the CDROM across a network installation (not likely in my 
case ), and failure to find the network.
 PK> NETBEUI is just another name for a slightly extended NETBIOS flavour,
 PK> and the IBM standard NETBIOS protocol can communicate with NETBIOS or
 PK> NETBEUI enviroments anyway.
One learns something every day. 
 PK> I haven't touched a WFWG machine myself for many years so I can't
 PK> remember the EXACT name that uses, but it is likely to include
 PK> NETBIOS or NETBEUI in the title.
NetBEUI. :-)
 PK> The supplied NETBIOS drivers for each environment should work fine,
 PK> once the CARD drivers are operating...
I'm going to pick up the NS2000.ZIP archive you mentioned, and see if that 
makes any difference. Acer's drivers for the card work fine under NT, but the 
WFWG machine required a generic NE2000 driver... I may have a similar 
situation under OS/2...
-Don
... Set RestartObjects=DontRestartTheOneThatCrashed
---
---------------