[comp.dcom.lans] NW Token Ring File Server install prob.

ccoombs@pilot.njin.net (Cliff Coombs) (09/20/90)

I'm installing a Netware (2.15) server on Token Ring.  I have
installed a few before on Ethernet.  The server is a PS/2 model 80
with 2 meg o' RAM.

After completing NETGEN, I boot the server and get:

Error Initializing LAN Driver: Error initializing IBM Token Ring Board
The server will be shut down.

I'm using the drivers supplied with Netware version 2something.

Any Ideas?  I tried the whole NETGEN process a couple times...
Am I forgetting something?  What's different about token Ring or the
model 80?  Should I use different drivers?  Maybe settings on the
Token Ring card?

Thanks in advance, Cliff
-- 
 Cliff Coombs                        Voice (201) 527-2729  Fax (201) 355-5143 
 Campus Network Administrator                          ccoombs@pilot.njin.net
 Kean College of New Jersey                             ccoombs@bart.kean.edu
 Disclaimer: "I know noth-ing" -Schultz (Hogan's Heros)   ccoombs@NJIN.BITNET

sylvia@brahms.udel.edu (Sylvia M Berta) (09/22/90)

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

keith@ca.excelan.com (Keith Brown) (09/22/90)

Lateley, there appears to have been a run on problems concerning the use of
the IBM PS/2 model 80 as a NetWare file server platform. So..... I grep'd
around in our technical bulletins and found what follows. Hope it helps
some of you.....

------------------------------------------------------------------------

             NUMBER  : P3TH062190U61
            SUBJECT  : PS/2 Machines With IBM SCSI and Token Ring
               DATE  : 6/21/90
         OS VERSION  :
           REVISION  :
      SHELL VERSION  :

GENERAL INFORMATION  : Customers using IBM PS/2 Machines which have BOTH the
IBM SCSI adapter and the IBM TOKEN RING card installed need to be aware of the
following situation.

The IBM SCSI adapter uses d800h for its Ram address. Most of the options for
the Token Ring Card to be set up as PRIMARY also use Ram address of d800h.

Option 8 (at CC00h) is the only Primary option that doesn't conflict with the
IBM SCSI.

Option 4 (at DC00h) is the only Alternate option that doesn't conflict with the
IBM SCSI.

The SCSI adapter was at its default aptions.

(Check all that apply)

  (XX)    This information was verified verbally.

  (XX)    This information was verified in the lab.


                                       TECHNICAL BULLETIN
                                         Bulletin #1-263

Date:  March 13, 1990

                  IBM 386 Memory Boards in NetWare 286 File Servers

IBM 386 memory boards with IBM part number 34F2811 will function under
NetWare in IBM 386 PS/2 machines.  These memory boards place a device driver
on track 0.  Since this is the same area in which NetWare stores the cold
boot loader, you must create a boot diskette to boot NetWare 286 (as
explained below), rather than booting from the hard disk.  (NetWare 386
is unaffected since it already requires a boot diskette and does not boot
from the network disk drive.)

To use the full functionality of the memory board, you must complete the
following:

    1)    Install the memory board exactly as explained in the installation
          instructions that come with the board.

    2)    Place the memory board drivers and a CONFIG.SYS file on a bootable
          floppy diskette.  Follow the instructions provided with the memory
          board for booting from a floppy diskette.

    3)    Place the file server operating system on the same bootable diskette.

    4)    Use the diskette as a NetWare boot diskette.  Boot DOS; then issue
          the NET$OS command.

No detailed memory test was performed beyond assuring that NetWare was able to
see all installed memory.  If you need more specific information, contact the
hardware manufacturer.


          Note:

          A second IBM 386 PS/2 memory board (IBM part number 6450605) was
          tested; however, since this memory board does not require device
          drivers, it had no bearing on the NetWare 286 booting process.


----------------------------------------------------------------------------
Keith Brown                                      Phone: (408) 473 8308
Novell San Jose Development Centre               Fax:   (408) 433 0775
San Jose, California 95131                       Net:   keith@novell.COM
----------------------------------------------------------------------------