Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!wuarchive!udel!udccvax1!brahms.udel.edu!sylvia
From: sylvia@brahms.udel.edu (Sylvia M Berta)
Newsgroups: comp.dcom.lans
Subject: Re: NW Token Ring File Server install prob.
Message-ID: <13936@brahms.udel.edu>
Date: 21 Sep 90 20:12:13 GMT
Distribution: usa
Organization: University of Delaware
Lines: 25

I am also having problems with a first-time token ring installation of
ELS Level II.  We did get some new files and driver from NetWire, which
included a VAP for Source Routing.  

With the initial network and shell generation, the network came up fine,
but the workstation would hang at the shell call (NET3).  Running
COMCHECK I could not even see the station at which I was sitting.

With the new files, and the fresh generation of IPX as well as the
network, I can now see all stations on the network (including the
server, if I boot it from DOS), so I know that my cabling and MAU are
okay (I presume)...but I still get a hung machine when NET3 is called.
The server comes up fine and the VAP loads successfully.  

The work station calls are IPX, then ROUTE, then NET3...nothing fancy.
The driver assignment is LAN_DRV_050.  I have changed the FILEINFO.DAT
file on the GENDATA diskette to call for the loading of the ROUTE.VP0
and SRCONFIG.COM files, etc.  I am at my wit's end after 4 hours 
yesterday, and several more today.  This should have been a simple
install.  Any help would be appreciated!!!  I know now why we've always
stayed with ethernet instead of token ring!  By now, I would have had
all the batch files written and the applications installed!!

HELP!!!  I'm sure that I'm probably missing something obvious, but today
I'm blind.  Thanks in advance  ...  Syl Berta