Ref: 17310007
Title: Diagnosing Cause of "RunMinds Failed" Message on a 3Server
date: 1/31/90

Copyright 3Com Corporation, 1991.  All rights reserved.

If a 3Server running 3+ fails to boot and displays the message
"RunMinds Failed" on the server LCD, the device drivers have failed
during the binding process "Loading Minds."  This failure can be
caused by a corrupt or missing device driver file referred to in the
CONFIG.SYS file.  It can also be caused by a hardware device, such as
a faulty port expansion board (PEB).

To determine if a faulty port expansion board is the cause of
the error, simply disable it:

1.  Disconnect the PEB from the motherboard.

2.  Replace the W009 jumper located on the server motherboard near
the battery.

3.  Reboot the server in the operation mode.

If the server does not fail while "Loading Minds," then the PEB
may have failed.   (If any of the ports on the disabled PEB are
configured for use by 3+, the server will fail during startup because
they are not available.)

If the PEB is identified as a faulty device, replace it with a working
one, then remove the W009 jumper.  The server should now operate
correctly and all ports will be available.

Another way to identify a port expansion board failure is to use the
RunMinds diagnostic option:

1.  Make a backup copy of the file so that the original file can be
easily replaced.

2.  Make a console connection to the server.

3.  Open the \3Plus\3Config\3Plus_on.bat file for editing, using
3Edlin or another editor.

4.  Locate the Runminds statement for dedicated server startup.
For 3+ 1.3.1 and subsequent versions, this line is
located in the section labeled "Do the appropriate RUNMINDS".

5.  At the end of the Runminds statement (which spans two lines),
place the characters /d, then save the file.

6.  Restart the server in the operation mode.

7.  Following the display of "RunMinds Failure," make a console
connection to the server.

8.  If the server is operating 3+ 1.3.1 or a subsequent version,
use the command LastBoot to display the results of the server startup
process which occurred during the "RunMinds Failure."  (For a previous
versions of 3+, make a Local console display.  See the 3Server guide
for details.)

As each driver binds, a message will be placed in the Lastboot
listing.  For example, when the Ethernet driver binds successfully,
the message "'MINDSETH' binding complete" will be produced.  The
message "'MINDSIDP' Binding Incomplete" will be produced if the port
expansion board has failed and the serial ports are not available.

