Ref: 10860004
Title: 3Install 1.1 problems: FORK FATAL ERRORs
Date:  7/28/88

Copyright 3Com Corporation, 1991.  All rights reserved.

Problem:  The 1.1 Install, when using 3Console in thumbwheel 4 on
a 3Server3 with Cache card blows up.  Running N/F/P/M/R.  No
Backup.

Specifically, when selecting the options to adjust CIOSYS parms,
it gives the following error message when you attempt to change
any of the parameters:

"***FORK :FATAL ERROR:"C:\3PLUS\3CONFIG\3CISCK.EXE/
U*C:\3PLUS\3CONFIG\3..."    This is the EXACT error.

Also, when changing options in File/Print instead of CIOSYS, it
says: "***FORK :FATAL ERROR:"C:\3PLUS\3CONFIG\3SHRCK.EXE/
U*C:\3PLUS\3CONFIG\3..."    This is the EXACT error.

When modifying Route parms, it says:
"***FORK :FATAL ERROR:"C:\3PLUS\3CONFIG\3ROUCK.EXE/
U*C:\3PLUS\3CONFIG\3..."    This is the EXACT error.

Finally, when you quit out of 3INSTALL 1.1 from the menu, it
says: "***FORK :FATAL ERROR:"C:\3PLUS\3CONFIG\3CISCK.EXE/
M*C:\3PLUS\3CONFIG\/M..."    This is the EXACT error.

At this point, the SE re-installed from scratch using "A:INSTALL"
from Install Disk #1 with a fresh 3CONSOLE.  He received the
exact same errors.

He then reformatted using 3DISK and did a Normal Format.
After Re-formatting, the 3INSTALL 1.1 worked fine and the
3Server3 started OK.


Answer: The error messages are caused by errors detected in a
.NSP file or a .CFG file.  A .NSP file is what used to be called
a 'profile' file, e.g. 3NAME.NSP contains the network number,
default domain and organization, etc.  There are also two .CFG
files, SYSTEM.CFG and HWINFO.CFG.  These are configuration files.

The error messages are generated when a problem with one of these
files is detected.  When a problem is found an error code is
returned to the 3install program, which then displays a
generic error message.  You could get a more detailed message
by running the appropriate checker stand-alone, e.g., 3namck.

To solve the problem you will probably need to re-create these
files.  This is a simple task, just delete the corrupted file and
run the 3install program.  This is the only way to generate the
.CFG files.  You can also create new .NSP files this way, or you
could delete the .NSP file and run the proper checker stand-
alone.

Note that merely reinstalling the software may not solve the
problem as that process will not necessarily delete the old .NSP
or .CFG file.
