This document (1203078) is provided subject to the disclaimer at the end of this document.
Click the filename to download: nwl11e.exe 571623 bytes 01Nov1995 06:09PM
NWL11E.EXE is an upgrade allowing a NetWare Lite v1.0 user to upgrade all 1.0 software to NetWare Lite 1.1 for DOS and Windows. This file is for the English version of NetWare Lite. Several enhancements have been made to NetWare Lite 1.1 for DOS and Windows.
See ISSUE for details
NetWare Lite v1.1 (7/02/92)
Print this file and save it for future reference.
To print this file to a local printer,
1. Insert the DRIVER diskette into drive A:.
2. At the DOS prompt, type "A:" and press <Enter>.
3. At the DOS prompt, type "COPY NWL11E.TXT PRN" and press <Enter>.
CONTENTS
1. New Features
2. Installing NetWare Lite and Logging In
3. Upgrading NetWare Lite v1.0 to NetWare Lite v.1.1
4. General Information
5. Optimize Your Network Server
6. Printing
7. Network Directory and File Sharing
8. Basic Network Application Configuring Tips
9. Basic Troubleshooting
10. NetWare Lite and NetWare Compatibility
11. Auxiliary NetWare Files
12. NetWare Lite and Windows
1. NEW FEATURES
* NetWare Lite Cache software makes the network run 3 to 6 times faster
by reducing time waiting for the hard disk.
For more information, after installing a NetWare Lite server, print the
CACHE.TXT file in the NWLITE directory.
* NET SAVE retains mapped drives, captured ports, and DOS environment
variables.
At the DOS prompt, type "NET SAVE" and press <Enter>. The mapped drives,
captured ports, and DOS environment variables are saved in a file named
NLLOGIN.BAT. Next time you want to log in, you can type "NLLOGIN" (instead
of "NET LOGIN") and press <Enter> to log in, automatically map the drives,
capture the ports, and set up the DOS environment to the settings in the
NLLOGIN.BAT file.
* SERVER.EXE and CLIENT.EXE can be loaded into upper memory (between 640
KB and 1024 KB).
You must have an upper memory block (UMB) with at least 64 KB
available to load SERVER.EXE into upper memory. Modify the SERVER and
CLIENT lines in STARTNET.BAT to include the specific load high command for
your memory manager. Example: If you use DR DOS 6.0, change the SERVER line
to HILOAD SERVER and the CLIENT line to HILOAD CLIENT.
Although SERVER.EXE needs an upper memory block of at least 64 KB to
load, it may not use the entire 64 KB. Once SERVER.EXE is loaded, the
remaining upper memory can be loaded with other programs like CLIENT.EXE.
If SERVER.EXE is configured so it requires more than 64 KB and it
will not fit in an upper memory block, you receive a message and SERVER.EXE
does not load.
* NetWare Lite v1.1 SERVER.EXE's default size is about 10 KB smaller
than in NetWare Lite 1.0 SERVER.EXE's default size. If you have a
two-computer network and set the server configuration to the minimum
values, SERVER.EXE would be approximately 33 KB. The size of SERVER.EXE is
relative to the server configuration settings.
* You can unload SERVER.EXE and CLIENT.EXE from memory.
This makes more memory available for applications when you are not
using the NetWare Lite network.
NOTE: You can only unload programs in reverse loading order.
CLIENT.EXE must be unloaded before SERVER.EXE on a server/client station.
To unload CLIENT.EXE from memory, at the DOS prompt, type "CLIENT U" and
press <Enter>.
To unload SERVER.EXE from memory, at the DOS prompt, type "SERVER U"
and press <Enter>.
* Commands are more like native NetWare.
Added a NET WHOAMI alias for NET INFO and a NET USERLIST alias for
NET ULIST.
* You can use the NET SLIST command to get a list of the servers on the
network without logging in.
At the DOS prompt, type "NET SLIST" and press <Enter>.
* NET AUDIT and NET RECEIVE display their status (on or off).
At the DOS prompt, type "NET RECEIVE" or "NET AUDIT" and press
<Enter>. The status (on or off) appears.
* You can use NET RECEIVE to set a message-display time limit at your
workstation.
At the DOS prompt, type "NET RECEIVE number" and press <Enter>.
Replace number with the number of seconds (0 to 1500) you want the message
to remain on the screen. If you enter 0, the message remains on the screen
until you simultaneously press <Ctrl> <Enter>.
* You can have client workstations notified when print jobs are
complete.
Set the NET CAPTURE notify option to yes. (The notify option default
is set at no.) Example: NET CAPTURE LPT1 N=Y
Your client workstation is notified when your print job is
completed. To clear the notification, simultaneously press <Ctrl><Enter>.
* CD-ROM drive support.
You can install CD-ROM drivers on a server-only computer or on a
server-client computer. Additional information is available on Novell's
automated fax system.
2. INSTALLING NETWARE LITE AND LOGGING IN
NOTE: If you have NetWare Lite v1.0 software on the computer, use the
upgrade option so your network configuration remains intact.
Determine Hardware Interrupt and Port Address Requirements
If your computer has an internal or external modem, bus mouse, fax
board, scanner, or other add-on board, determine if any of the device
interrupt levels (IRQ) or port addresses (I/O addresses) will conflict with
the NetWare Lite default interrupt 3 and port address 300 (most network
cards are set to these values at the factory).
If there is a conflict on the actual card, change the NetWare Lite
interrupt level or port address values so they don't conflict with the
other devices. Then select the corresponding interrupt and port address
setting during installation. For most computers, you can change the
interrupt level and port address during Step 3 of the NetWare Lite
installation. For IBM PS/2 computers, change the interrupt level and I/O,
EPROM (port address) on the PS/2 reference diskette.
Use an interrupt (IRQ) for your network card. The following table
shows what the IRQ levels are used for in XT and AT computers.
_______________________________________
|IRQ | XT | AT (286, 386, 486) |
|____|_____________|____________________|
| 0 | | timer output 0 |
| 1 | | keyboard |
| 2 | EGA/VGA | EGA/VGA |
| 3 | COM2 | COM2 |
| 4 | COM1 | COM1 |
| 5 | hard disk | LPT2 |
| 6 | | floppy disk |
| 7 | LPT1 | LPT1 |
| 8 |Not Available| real time clock |
| 9 |Not Available| |
| 10 |Not Available| |
| 11 |Not Available| |
| 12 |Not Available| |
| 13 |Not Available| co-processor |
| 14 |Not Available| hard disk |
| 15 |Not Available| |
|____|_____________|____________________|
The network card needs to use a unique I/O address. The following
table shows possible address conflicts.
____________________________________________________
| I/O ADDRESS | POTENTIAL CONFLICT DEVICES |
|_____________|______________________________________|
| 1F0 | AT disk controller |
| 200 | game controller/joystick (200-20F) |
| 220 | Novell network keycard |
| 240 | |
| 260 | LPT2: (278-27F) |
| 280 | LCD display on Wyse 2108 PC |
| 2A0 | |
| 2C0 | |
| 2E0 | COM4:, GPIB-Adapter 0 (2E1) |
| | COM2:, Data acquisition (300-31F) |
| 300 | |
| 320 | XT hard disk interface (320-32F) |
| 340 | |
| 360 | LPT1:(378-37F) |
| 380 | SLDC/Sec Bi-Sync interface (380-38C) |
| 3A0 | Primary Bi-Sync interface (3A0-3A9) |
| | Monochrome display (3B0-3BB) |
| 3C0 | EGA display control (3C0-3CF) |
| | CGA display control (3D0-3DF) |
| 3E0 | COM3: (3E8-3EF) |
| | floppy disk controller (3F0-3F7) |
| | COM1: (3F8-3FF) |
|_____________|______________________________________|
Install NetWare Lite Software
Insert the PROGRAM diskette into drive A:.
At the DOS prompt, type "A:" and press <Enter>.
At the DOS prompt, type "INSTALL" and press <Enter>.
Follow the instructions and help provided on the screen during
installation.
If your computer has an internal or external modem, bus mouse, fax
board, scanner, or other add-on board, at Step 3 change the interrupt level
(IRQ) and port address (I/O address) so that they do not conflict with
other device interrupt levels or port addresses. (You should have changed
the network board's interrupt level and port address before installing the
NetWare Lite software.)
NOTE: Your original AUTOEXEC.BAT and CONFIG.SYS files are saved in the
directory with a .BNL (Before NetWare Lite) extension. Your NET.CFG file is
saved in the NWLITE directory as NET.BNL.
Make sure that your AUTOEXEC.BAT path statement includes the DOS
directory. If it does not, the DOS SHARE program will not load.
Start NetWare Lite
Remove the disk from drive A:
Restart your computer by simultaneously pressing <Ctrl>, <Alt>, and
<Del>. As the computer is booting, the STARTNET.BAT file loads SHARE, LSL,
the LAN ODI driver, IPXODI, SERVER, and CLIENT.
If IPXODI reports an error (such as a conflict in the interrupt
setting or port address) when loading, check the interrupt settings and I/O
address (or port address) setting on other boards in the computer to
determine if they conflict with the network board's interrupt settings.
Also check NET.CFG to make sure the settings match the network board. Make
sure you set the network board setting correctly when installing NetWare
Lite.
If interrupt settings conflict, change the interrupt setting on the
network board and install NetWare Lite again or edit NET.CFG and reboot.
At the DOS prompt, type "NET" and press <Enter>. You will be prompted
for a username.
Verifying Network Connections
Insert the PROGRAM diskette into drive A:.
At the DOS prompt, type "A:" and press <Enter>.
At the DOS prompt, type "INSTALL" and press <Enter>.
Highlight "Verify network connections" and press <Enter>.
Make sure that the workstation name appears in the list.
Verify the network connections for all workstations on the network.
All the workstations on the network should appear on the list.
Let each computer run for at least 2 minutes to make sure there are no
intermittent problems. If a computer doesn't appear in the list, there is a
hardware problem (cards, cables, etc.) or the network card is configured
incorrectly.
Exit the installation program on each workstation.
Logging in After Installing NetWare Lite
After installing the first server on a new NetWare Lite network, log
in as SUPERVISOR (the only user defined on the network). Type "NET LOGIN
SUPERVISOR" and press <Enter>.
NOTE: The SUPERVISOR account on a newly installed network does not
have a password. For network security, set a password on the SUPERVISOR
account soon after the network is installed. DO NOT FORGET THE SUPERVISOR
PASSWORD.
When additional servers are installed on an existing NetWare Lite
network, defined users, network directories, and network printers are
automatically available. You should log in using one of the defined user
accounts.
Reinstall NetWare Lite Software
If you have to reinstall NetWare Lite, you can save the database of
network directories, network printers, server configuration, and printer
control and the database of network users by backing up the network
management system files before reinstalling NetWare Lite.
After reinstalling NetWare Lite, you can restore the system files so
the users, network printers, network servers, server configuration and
printer control are the same as they were when the last system file backup
was made.
For more information about backing up and restoring system files, see
page 28 in the manual.
3. UPGRADING NETWARE LITE v1.0 to NETWARE LITE v1.1
When you upgrade from v1.0 to v1.1, the server and network information
remain on the network. The users, network directories, and network printers
don't have to be set up again.
The upgrade option can be used on all computers that have NetWare Lite
v1.0 installed.
Insert the PROGRAM diskette into drive A:.
At the DOS prompt, type "A:" and press <Enter>.
At the DOS prompt, type "INSTALL" and press <Enter>.
When the NetWare Lite Install Menu appears, highlight "Upgrade this
machine to v1.1" and press <Enter>. The NetWare Lite v1.1 software is
loaded.
When upgrading floppy-only NetWare Lite software, the INSTALL program
asks for a path. Type "A:" and press <Enter>.
Reboot your computer so NetWare Lite 1.1 is loaded.
4. GENERAL INFORMATION
Files on NetWare Lite diskettes that end with an "@" are compacted and
will not work until they are unpacked. The INSTALL program unpacks
compacted files and renames them removing the "@".
* Questions and Answers
a. How can I tell if my hardware and drivers are functioning
properly?
After loading STARTNET.BAT, verify the network connections as
explained in the manual on page 7. Let each computer run for at least 2
minutes to make sure there are no intermittent problems. If a computer
doesn't appear in the list, there is a hardware problem (cards, cables,
etc.) or the network card is configured incorrectly.
b. I can't find an ODI driver for my card. Can I use IPX.COM?
Yes.
In the STARTNET.BAT file, replace the following statements with
IPX.COM:
lsl
NE2000 (Or applicable driver.)
ipxodi a
(The above three statements are equivalent to the older
IPX.COM.)
c. What causes network drivers, certain DOS commands, and some
programs to lock up and act unpredictably (i.e. DOS extend error 59,
WordPerfect disk error 51)?
This is probably a hardware conflict or a memory conflict with
the memory area between 640 KB and 1024 KB.
Some network cards use a shared memory address that resides in
system memory (upper memory). Often the memory address used by the card is
written over by another program which can cause unpredictable results.
You need a memory management program with the capability of
excluding specific areas of memory from other programs. See the memory
manager's documentation to see how to exclude the memory and refer to the
network card's documentation to see how much memory to exclude.
Other possible causes include a bad cable, a cable that is
non-standard, a homemade cable, a wrong terminator (use 50 ohm for Ethernet
and 93 ohm for ARCnet), no ground terminator, or noise on the wire. If
using 10Base-T, connect the 10Base-T cable to a concentrator, not directly
to the second computer.
d. What are the possible conflicts that could interfere with
default settings on network cards (IRQ 3 and I/O address 300)?
The most common IRQ3 conflicts occur when COM2 is used (as a
second serial port or for an internal modem, or fax board). These
conflicts may not show up until you try to use COM2:, or in the case of a
bus mouse, until you try to use the NET command with the bus mouse
initialized. Use fax document #212 or the chart previously given in this
document.
e. I receive errors in DOS applications such as share violations,
unable to access file XXXX errors, errors entering and exiting an
application, or the station hanging. What can I do?
Change the application directories' default rights to READ. Some
applications require Write access to the directory. If this is the case,
change the .EXE, .OVL and .COM files rights to READ ONLY using the DOS
command ATTRIB or third party software.
Remove the TSRs running on your computer one at a time and run
the application again to determine if a TSR is causing the problem. (Load
NetWare Lite using the STARTNET command before you load other TSRs.)
Check for conflicts on interrupts used by the hardware.
Increase the value of "FILES=XX" in CONFIG.SYS. Example:
"FILES=50."
Increase the value of the "Client tasks" in the Net Utility
Server Configuration. Make sure there are at least 10 tasks per client
connected to the server for DOS and at least 15 tasks per client connected
to the server for Windows.
Check the application's setup or the configuration section that
applies to network selection. Select NO NETWORK or OTHER. Do not select
NETWARE or NOVELL.
Check the server status. Make sure that the PEAK values are not
as high as the configured (CFG) values. If the PEAK values are approaching
the configured values, increase the applicable configured values and reboot
the computer.
Make sure the application directory is included in the PATH
statement in AUTOEXEC.BAT or STARTNET.BAT.
Check the memory requirements of the program and PC memory for
possible problems.
Increase the SHARE file and lock parameters in STARTNET.BAT or
AUTOEXEC.BAT.
Example: SHARE /F:8000 /L:200
[The file (/f) parameter is not applicable in DR DOS 6.0.]
* Load NETBIOS if an application requires it.
* Load SPX if an application requires it.
Modify the STARTNET.BAT file "IPXODI A" command to "IPXODI D." When
the "A" is removed, both IPXODI and SPX is loaded. You can type "IPXODI ?"
at the DOS prompt to see a list of all available options for IPXODI.
* Avoid mapping local drives as network drives.
You can map local drives (for example, A: or B:) and use them
temporarily as network drives; however, we Do Not recommend doing this. If
you run out of drive letters to map, increase LASTDRIVE in your CONFIG.SYS
file.
* Do Not use ASSIGN with NetWare Lite.
The DOS (3.3) reference manual recommends the use of SUBST instead
of ASSIGN.
* WARNING: Caches, other than the NetWare Lite Cache, may need to have
delayed writes, deferred writes, posted writes, or queued writes disabled
if they are used with NetWare Lite. Many cache programs "wake up" to do
writes in the background, they do not protect themselves from re-entry with
a DOS-critical section callout. If you use a cache (other than the NetWare
Lite Cache) with deferred writes, posted writes, or queued writes turned
on, you may get random hangs, data corruption, or other abnormal behavior.
To use a cache other then the NetWare Lite Cache, call the cache company's
technical support group to find out if their cache's deferred writes,
posted writes, or queued writes work with NetWare Lite.
Many caches don't allow delayed writes, deferred writes, posted
writes, or queued writes when using a peer-to-peer network. However, the
NetWare Lite Cache can use delayed writes. If you are using a cache that
has one of the above options, make sure the option is turned off.
* Do not make server names 15 characters long if you remotely manage
servers.
If you remotely manage a server with a name that is 15 characters
long, the server will hang. To fix the problem, make the server name less
than 15 characters long.
5. OPTIMIZING YOUR NETWORK SERVER
* Modify the number of receive buffers and number of I/O buffers.
Depending upon the number and frequency of requests to the server,
increasing the number of receive buffers and I/O buffers may enhance server
performance.
The number of receive buffers doesn't need to be more than 2 above
the number of simultaneous connections, but it shouldn't exceed 12.
Generally 8 to 12 receive buffers and 1 to 4 I/O buffers are
sufficient for up to 25 connections.
* Modify the receive buffer size and I/O buffer size for the network.
Using multiples of 512 bytes, increase the receive buffer size up to
the maximum supported by the network topology (for example, Ethernet or
Token ring) or a maximum of 8192 bytes. However, increasing the size of the
receive buffer increases the size of the server software when it is in RAM.
If you enter too large a number at the receive buffer size field in the
Server Configuration option, NetWare Lite truncates the value to the
highest value that the network card can transmit or receive.
Increasing the receive buffer size lets clients request more data
from or send more data to the server with each read and write operation.
When more data is sent, fewer requests to the disk are necessary so you get
better performance from the server.
* Unfragment files or optimize disk.
MAKE SURE THAT SERVER.EXE IS NOT RUNNING WHEN YOU UNFRAGMENT FILES!
Fragmented files adversely affect server performance. Periodically
unfragment files on each server's hard disk using a disk optimizing or a
disk compression tool.
Never run any low-level disk repair utilities (including CHKDSK /F
or disk optimizing utilities) on the hard disk while the server
(SERVER.EXE) is loaded. Doing so can corrupt data stored on the hard disk.
Do not run low-level utilities from a client that has a drive mapped to the
server.
* Use SUBST instead of MAP for network drives on a local server.
If your computer has network directories on its hard drive, you can
use the SUBST command instead of NET MAP command. It is more efficient to
use SUBST to access network directories on your hard disk than it is to use
NET MAP.
6. PRINTING
* Questions and Answers
a. Why does a status message "Printer off Line" or "Printer Out of
Paper" pop up when I try to print even though neither of these situations
is accurate?
Check the network printer configuration to make sure it is
configured for the port (LPT1, LPT2, LPT3) that it is actually connected
to.
Example: If the printer is connected to LPT1 on the server, the
network printer configuration must be set to LPT1.
If the network printer configuration and printer port are
correct, increase the printer configuration "Error wait time" by 15-second
increments and try again.
b. One of the servers has intermittent problems when trying to
print. Sometimes the server hangs and other times the print job disappears
without being printed.
If you are using LPT1 on the server, make sure that your network
card is NOT set to I/O 360. This port address overlaps with the I/O address
for LPT1 (378). If LPT2 is used, INT 5 will cause a conflict.
c. How can I let NetWare Lite know that I have changed the IRQ and
I/O address on my network LAN driver without reinstalling the program?
Edit C:\NWLITE\NET.CFG. If the file is not there, create one
like this:
#Setup the NE2000 card (This is a comment line)
link driver NE2000 (Enter the ODI driver name
here in place of NE2000.)
int 3
port 300
MEM D000 (This line is used only when
a card has a shared memory
address.)
Enter the correct settings into this file and reboot the
computer. The driver loads with the correct settings.
If you change network cards, change the NET.CFG file to match
the settings on the new card and change the STARTNET.BAT driver name to the
new driver name.
MicroChannel computers typically do not require NET.CFG.
* Using characters per second and print buffers.
The print buffer is an area in memory where characters are stored
before being printed. The larger the print buffer size, the fewer times the
server must to go to disk to read characters to print.
If the "Characters per sec" value is high (relatively speaking), the
printer is driven faster and the DOS running on the computer is interrupted
more often to send characters to the printer. The opposite is also true if
the value of the "Characters per sec" is low (relatively speaking) and the
print buffer size is small.
Tune these values to the speed or chosen speed of the printer. If
the printer is physically a "slow" printer (like a serial printer), setting
the "Characters per sec" parameter to a high number does not affect the
speed of printing, but it can adversely affect the foreground DOS process.
Self-Extracting File Name: nwl11e.exe
Files Included Size Date Time Version Checksum
\
3C503.CO@ 8574 14Jun1991 09:14AM
3C503.CO@ 8574 14Jun1991 09:14AM
3C503.INS 170 11Sep1991 07:11PM
3C523.CO@ 7604 29Jul1991 09:35AM
CACHE.TX@ 9753 01Jun1992 05:26PM
CLIENT.EXE 21081 29Jun1992 04:40PM
DEDICATE.COM 192 10Mar1992 09:31AM
DRIVER.LST 1556 01Apr1992 11:24PM
INSTALL.COM 13792 25Aug1992 01:31PM
INSTALL.EXE 59754 30Jun1992 08:29AM
IPXODI.CO@ 12252 20Nov1991 04:57PM
IPXSYNC.EXE 15664 01Jul1992 11:44AM
LITE$RUN.OVL 2400 11Sep1991 07:11PM
LSL.CO@ 6031 30Jan1992 04:05PM
NE1000.CO@ 7889 29Jul1991 09:37AM
NE1000.INS 97 11Sep1991 07:11PM
NE1500T.CO@ 8038 11Oct1991 05:09PM
NE1500T.INS 127 23Mar1992 08:44AM
NE2.CO@ 9283 04Nov1991 04:19PM
NE2000.CO@ 8181 03Jun1991 01:25PM
NE2000.INS 96 11Sep1991 07:11PM
NE2100.CO@ 8034 11Oct1991 05:10PM
NE2100.CO@ 8034 11Oct1991 05:10PM
NE2100.INS 126 23Mar1992 08:43AM
NET.EXE 35368 28May1992 04:05PM
NET.HL@ 17492 18May1992 03:41PM
NET.OVL 95685 16Jun1992 01:47PM
NETBIOS.EX@ 12653 18May1992 03:26PM
NLCACHEC.EX@ 10706 05May1992 12:46AM
NLCACHEM.EX@ 12362 05May1992 12:47AM
NLCACHEX.EX@ 13873 05May1992 12:47AM
NLCINST.EX@ 24542 02Jun1992 08:13AM
NLSNIPES.EXE 18042 11Sep1991 07:11PM
NWL11E.EXE 571623 01Nov1995 06:09PM
NWL11E.TXT 53590 08Oct1993 10:08AM
PCN2L.CO@ 8746 17Jul1991 03:40PM
README.TXT 53590 08Oct1993 10:10AM
SERVER.EXE 45411 01Jul1992 08:25AM
TASKID.CO@ 1681 19Dec1990 03:48PM
TBMI.CO@ 4615 10Jul1991 12:27AM
TBMI2.CO@ 5062 04Dec1991 02:46PM
TOKEN.CO@ 10242 14Jun1991 04:10PM
TRXNET.CO@ 7696 06Aug1991 10:48AM
TRXNET.INS 203 11Sep1991 07:11PM
UPATCH.EXE 19690 16Jan1992 09:35AM
UPGRADE.DOC 5603 05Oct1992 11:59AM
VIPX.38@ 7501 08Jul1992 10:55AM
WDPLUS.CO@ 10902 21Jun1991 02:11PM
WDPLUS.CO@ 10902 21Jun1991 02:11PM
WDPLUS.INS 219 11Sep1991 07:11PM
| Document Title: | Upgrade to NetWare Lite 1.1 for DOS and Win |
| Document ID: | 1203078 |
| Creation Date: | 02Nov1995 |
| Modified Date: | 02Nov1995 |
| Revision: | 1 |
| Novell Product Class: | NetWare |
The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts 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.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.