(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:Upload of L11U01.ZIP
DOCUMENT ID#:FYI.P.10963
DATE:29DEC92
PRODUCT:NetWare Lite
PRODUCT VERSION:v1.1
SUPERSEDES:NA
SYMPTOM
NA
ISSUE/PROBLEM
Concerning the file L11U01.ZIP available on available on NetWire or NetWare Express. For NetWare Lite v1.1. Files included:
GETATRIB.PAT 1248 12-03-92 9:09a
CLOSEFIL.PAT 1084 12-01-92 10:30a
LPTSTAT.PAT 1255 11-16-92 2:06p
RECONFIX.PAT 2626 10-12-92 9:52a
CLPRINTR.PAT 1198 11-16-92 10:12a
INFORMATION ON SPECIFIC PATCHES
GETATRIB.PAT - NetWare lite Client get file attribute fix patch
Target: CLIENT.EXE
Checksums: 758, BB2, 59A, 351, BB2
Problem: When running the Quicken finance software and printing to a NetWare Lite captured printer, Quicken printing fails with the message "Can't print to LPT1."
Symptoms: Quicken printing fails with the message "Can't print to LPT1". This also fixes the problem with getting file attributes across the network. The problem was with OPENDEV.PAT.
CLOSEFIL.PAT - NetWare Lite v1.1 Server close file handles fix patch
Target: SERVER.EXE
Checksums: 2CC, 2B4, 20
Problem: When a client station has open files on a NetWare Lite server and the client reboots with the files still open, sometimes the files will not be closed when the client reconnects or when watchdog clears the station connection.
Symptoms: Files are left open on the server when a client reboots.
LPTSTAT.PAT - NetWare Lite v1.1 Server LPT printer status fix patch
Target: SERVER.EXE
Checksums: 5B7, CO1, 575, 307, C01
Problem: Print jobs in NetWare Lite are being sent to a printer that has been taken off line or powered off. The jobs are being lost.
Symptoms: Print jobs are being lost when the printer has been powered off or taken off line.
RECONFIX.PAT - NetWare Lite Client reconnect patch
Problem: The reconnection between server and client fails to occur when the NET CAPTURE or NET PRINT commands are issued by a client to a server that has just been rebooted. Subsequent NET CAPTURE or NET PRINT commands from the client station will work normally.
Symptoms: When using the NET CAPTURE or NET PRINT commands as the first commands from a client to a server that has just been rebooted, the error messages "Redirect device -- Too many open files." or "Write file -- Access denied." will be displayed and the command will fail.
CLPRINTR.PAT - NetWare Lite Client printer corruption fix patch
Target: CLIENT.EXE
Checksums: 6AC, 562, 5D4, 316, 562
Problem: Running certain applications on a client/server with a local printer will produce printer output that has been corrupted.
Symptoms: Printer output that has been captured through NetWare Lite will be corrupted.
SOLUTION
NA
FYI:No DOS ODI Drivers for DEC Ethernet LAN Boards
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:No DOS ODI Drivers for DEC Ethernet LAN Boards
DOCUMENT ID#:FYI.P.09062
DATE:11JUN92
PRODUCT:NetWare Lite
PRODUCT VERSION:v1.0
SUPERSEDES:FYI.P.07850
SYMPTOM
NA
ISSUE/PROBLEM
Are Open Data-Link Interface (ODI) drivers available for the following Digital Equipment Corporation (DEC) Ethernet LAN boards?
DE100, DE200, DE210, DE201, or DE202
The user wanted ODI drivers for NetWare Lite software.
SOLUTION
Yes. Refer to the following Novell Labs reports:
l-1057DE-100(NetWare v3.11 Only)
l-1058DE-101
l-1059DE-200
l-1060DE-201
l-1061DE-202
l-1062DE-210
ODI Drivers should be used with NetWare Lite. Using dedicated IPX drivers with NetWare Lite software is not officially supported by Novell.
If forced to use a dedicated IPX driver in NetWare Lite software, do the following:
1.Select the appropriate LAN driver during the installation.
2.Edit the STARTNET.BAT file so that it loads the desired IPX.COM (then SHARE, SERVER, CLIENT) instead of Link Support Layer (LSL), <odi mlid>, and IPXODI.
3.Also if it is necessary to load IPX with a different configuration, then change the NET.CFG file created during the install to reflect that change.