Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!rutgers!bellcore-2!bellcore!rruxi.bae.bellcore.com!louie
From: louie@rruxi.bae.bellcore.com (Paul Louie)
Newsgroups: comp.dcom.lans
Subject: Novell Error Message
Message-ID: <26106@bellcore.bellcore.com>
Date: 16 Aug 90 16:15:00 GMT
Sender: news@bellcore.bellcore.com
Reply-To: louie@rruxi.bae.bellcore.com (Paul Louie)
Organization: Bell Communications Research
Lines: 32

conway@wam.umd.edu (Thomas F. Conway) asked:

>Greetings.  I have a problem, and do not know where else to turn.  This is
>what I am currently doing: I am installing (attempting to install) Novell
>Advanced Netware 286 v 2.15 Rev A. on an IBM 8570-121 Non-dedicated
>File Server.  The networking hardware is IBM Token-Ring.(The joy of 
>exclusive contracts in state government!)  After configuring the server and
>attempting to boot up, I get the following error message:
>
>Error initializing LAN Driver: Time out error waiting for SSB Free during init
>
>The manual that covers error messages seems to have forgotten about this
>one, and the vendor doesn't have tech support fot his, and Novell Tech
>support is expensive--HELP!!!  What does this message mean?  The hardware
>all checked out OK during diagnostics, and the 8570 was configured
>properly using the reference diskette.  Does anyone have any idea what is
>happening?  If so, please let me know.  Any ideas or information would be
>GREATLY appreciated.  Thanks in advance.

The IBM PC-TRN card comes with a diskette with two drivers.  These two drivers
is responsible for the actual (physical) communication and error handling
on the network.  The Netware IPX interface does not handle these functions as
it does on Ethernet or Arcnet network.  To solve your problem (assumming that
you are not running a non-dedicated server.  If yes, then you can do the
following in you DOS partition), you need to boot from a diskette.  Specify 
these drivers in CONFIG.SYS (i.e.- device=xxxxxx.sys).  Create an AUTOEXEC.BAT
that have the line NET$OS.EXE to start the server.  Don't forget to have
NET$OS.EX1, NET$OS.EX2, and the drivers on the same diskette.
 
If the above procedures wouldn't solve your problem, then you must have 
specify wrong LAN DRIVER information during NETGEN.