Category : Network Files
Archive   : NOVELFAX.ZIP
Filename : 1012606.TXT

 
Output of file : 1012606.TXT contained in archive : NOVELFAX.ZIP


FYI

(Note: The origin of this information may be internal or external to Novell.
Novell makes every effort within its means to verify this information.
However, the information provided in this document is FOR YOUR INFORMATION
ONLY. Novell makes no explicit or implied claims to the validity of this
information.)

TITLE: Troubleshooting Lockup (Hanging) Problems
DOCUMENT ID#: FYI.P.6086
DATE: 26JAN93
PRODUCT: NetWare Lite
PRODUCT VERSION: All versions
SUPERSEDES: FYI.P.6074
LITE FAX DOC #: 2606

SYMPTOM

NA

ISSUE/PROBLEM

Troubleshooting Lockup (Hanging) Problems

While using a networking system, problems may be met; locking could be
one of them. This document, which is divided into two areas of hardware
and software, is intended to help diagnose and resolve lockup problems.

Hardware

1. Most Local Area Network (LAN) boards come with the ability to change
the interrupt line, base I/O address, and memory address settings
(in some cases). This is done by either setting switches located on
the network board or through a software setup utility. When NetWare
Lite is installed, it must be told what the interrupt line, base
I/O, and the memory address settings are on the board. If the board
does not agree with the settings that the network is searching for,
it could cause lockups. This usually happens when the network board
driver is loaded, when SERVER.EXE is loaded, when CLIENT.EXE is
loaded, or when the NET utility is used.

The solution for this type of problem is straight forward. The
settings on the board need to be determined by checking the switches
and sometimes cross referencing it with the documentation provided
with the network board. After they are found, the install process
is repeated for NetWare Lite and the correct options chosen to
correspond to the hardware.

2. Another lockup problem may occur when the interrupt line, base I/O
address, or memory address conflict with another device in the same
machine. Each of these settings must be unique to the network
board. Devices that may conflict include modems or mice. Lockups
in this case can show up anytime after the network has been loaded.
A reference list is provided that contains the interrupt line and
Base I/O address for many devices. For more information on
interrupts, see Fax Document 2601 or FYI.P.6054. (Call
1-800-NET-WARE and press the * key during the initial recording.)


ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
³ Options ³IRQ ³ Base I/O ³
ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´
³ Com1 ³ 4 ³ 3F8-3FF ³
³ Com2 ³ 3 ³ 2F8-2FF ³
³ LPT1 ³ 7 ³ 378-37F ³
³ LPT2 ³ 5 ³ 278-27F ³
³ VGA ³ 2 ³ 3C0-3CF ³
³ EGA ³ 2 ³ 3C0-3CF ³
³ CGA ³ ³ 3D0-3DF ³
³ Hercules ³ ³ 3B4-3BF ³
³ Mono ³ ³ 3B0-3BF ³
³ AT controller ³ 14 ³ 1F0-1F8, 170-177 ³
³ Floppy controller ³ 6 ³ 1F0-1F8, 3F0-3F7 ³
³ Tape controller ³ 5 ³ 280-28F ³
³ XT controller ³ 5 ³ 320-32F ³
³ ³ ³ ³
ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÁÄÄÄÄÁÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ

Note: Along with the above mentioned I/O address conflicts, address 360
should be avoided. This address may overlap with beginning address 378
that is used in LPT1 processes. (This is hardware defined and may depend
on the particular network board used.) The best solution for this is to
configure the network board I/O address at 300, 320, or 340. These
settings will work for most systems.

3. The switch settings on the board are not the only things that can
cause problems. Some network boards, when not fully compatible with
Novell certified boards, can also cause problems. When locking
problems do not seem related to any of the settings on the board,
try using a different board to see if it does clear up.
Occasionally, a bad board is run across.

Software

1. Some software can cause a lockup when it is simply not compatible
with NetWare Lite. These programs usually use protocol that tries
to print, gain access to RAM, or gain access to the hard drive
without going through DOS. Because NetWare Lite is written to work
with DOS these programs cannot be used.

2. NetWare Lite is a memory resident program that occupies part of RAM.
This limits the amount of room allowed for other programs. When
conventional memory is too low, it can cause applications to crash.
One solution for this is to load as much as possible into upper
memory. Out of the files loaded through the STARTNET.BAT file, all
but SERVER.EXE can be loaded high. This is done in MS-DOS 5.0 by
putting "LOADHIGH" before the file name to be loaded. This is done
in DR-DOS 6.0 by putting "HILOAD" before the file name to be loaded.
(Third-party memory managers may also be used but not loaded at the
same time with other memory managers.) Note that many memory
resident programs can be loaded high but others cannot. If you load
a particular program high and find that your system locks more
frequently, load it back into conventional memory again.

Example for loading most of STARTNET.BAT high using MS-DOS format:

loadhigh lsl
loadhigh ne2000
loadhigh ipxodi a
loadhigh share

server
loadhigh client

3. Some network boards use upper memory for their own processes that
range from C000h to E000h. If this is the case, they do not require
a memory manager to control them. Furthermore, this area in upper
memory should be excluded from the memory manager's control. To do
so, insert the following in CONFIG.SYS:

For MS-DOS 5.0 use:
device=c:\DOS\emm386.exe x=mmmm-nnnn
For DR-DOS 6.0 use:
device=c:\drDOS\emm386.sys /exclude=mmmm-nnnn
(mmmm is beginning and nnnn is the ending address.)

Note: Most network-board drivers occupy about 8 to 16 KB of memory.
Check the references for your specific device.

4. CONFIG.SYS also has a parameter that can be changed that may cause
computers to lock. That is "files=xx." The xx is the number of
files that machine can have open at one time. The suggested amount
is 10 files per client plus 30 more.

5. Along the same line as the above paragraph, the number of client
tasks could have the same effect. To change the client tasks you
must run the NET utility, go to "supervise the network," then
"server configuration." This parameter is normally set between 5
and 10 per client.

6. Terminate-Stay-Resident (TSR) programs can also cause lockups. They
can show up in several ways of which most commonly is when the TSR
is functioning. It can also happen when the TSR seems inactive.

The easiest way to find out if a TSR is causing the lockup is by
renaming AUTOEXEC.BAT and CONFIG.SYS and then putting the following
in the CONFIG.SYS:

FILES=30
LASTDRIVE=G

If the problem no longer persists, add each component back into
AUTOEXEC.BAT and CONFIG.SYS one by one until you find the one that
is causing the problem. Modifications may be necessary to make the
conflicting TSR work properly, or it may even be incompatible with
the network environment.

7. Some incompatibilities have been found with certain hardware and
software configurations. NetWare Lite has made some modification to
adapt to these systems. These modifications come in the form of a
patch that is applied once to each machine in the network. More
specifics on these patches can be faxed to you through NetWare
Lite's automated Fax Document 2903 or see FYI.P.6087.

SOLUTION

NA


  3 Responses to “Category : Network Files
Archive   : NOVELFAX.ZIP
Filename : 1012606.TXT

  1. Very nice! Thank you for this wonderful archive. I wonder why I found it only now. Long live the BBS file archives!

  2. This is so awesome! 😀 I’d be cool if you could download an entire archive of this at once, though.

  3. But one thing that puzzles me is the “mtswslnkmcjklsdlsbdmMICROSOFT” string. There is an article about it here. It is definitely worth a read: http://www.os2museum.com/wp/mtswslnk/