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

 
Output of file : 1012655.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: Assisting Floppy Based Clients
DOCUMENT ID#: FYI.P.6017
DATE: 01OCT92
PRODUCT: NetWare Lite
PRODUCT VERSION: All versions
SUPERSEDES: NA
LITE FAX DOC #: 2655

SYMPTOM

NA

ISSUE/PROBLEM

Assisting Floppy Based Clients

If there are workstations on the network that do not have hard disks,
Novell suggests that NetWork Directories be set up to help those
workstations. A DOS shared Network Directory should be created so that
workstations with no hard disks can load DOS commands from the network.
A Network Directory sharing IBM DOS v3.10 (named IBM_DOS_310 perhaps)
would be useful for those CLIENTs with only floppy drives to get to their
version of DOS. In conjunction with this, the DOS environment variable
COMSPEC should be set to allow you to load COMMAND.COM from across the
network.

For example, the following lines could be included in an AUTOEXEC.BAT or
STARTNET.BAT file:

NET MAP F: IBM_DOS_310
SET COMSPEC=F:\COMMAND.COM

In addition, workstations that only have floppy drives can be assisted by
creating a Network Directory where the NetWare Lite utility (NET.EXE,
NET.OVL, NET.HLP and LITE$RUN.OVL) can be loaded; instead of always
loading them from the floppy. Novell suggests that a Network Directory
called NWLITE be created. This directory should be a SERVERs C:\NWLITE
directory. Novell also suggests that this Network Directory be given
default rights of READ and not the default of ALL.

All floppy-only CLIENTs should map a drive to this resource and add the
drive to their DOS path. This will allow the loading of the NET utility
from across the network, which is a much better solution than loading
from floppy.

For example, the following lines could be included in an AUTOEXEC.BAT or
STARTNET.BAT file:

NET MAP M: NWLITE
PATH=M:.;%PATH%

If you want to run the CLIENT from a floppy drive and have that diskette
be the boot diskette, the following configuration is suggested. (Where

ever NE2000.COM appears, replace it with the appropriate driver name you
are using. Also, the drive letters L: and M: are simply used as
examples; you may use any other valid driver letters. Drive M: is mapped
to the Network Directory NWLITE as described above. Similarly, Drive L:
is mapped to the Network Directory IBM_DOS_310 as described above.)

1. Create a bootable diskette using the FORMAT A: /S command.

2. Copy the following NetWare Lite files to the diskette:

LSL.COM
NE2000.COM
IPXODI.COM
CLIENT.EXE
NET.EXE
NET.CFG

3. Create an AUTOEXEC.BAT with the following lines added to it:

LSL
NE2000
IPXODI A
CLIENT
NET LOGIN
NET MAP L: IBM_DOS_310
NET MAP M: NWLITE
PATH=L:\;M:\;%PATH%
SET COMSPEC=L:\COMMAND.COM

4. Create an CONFIG.SYS with the following line added to it:

LASTDRIVE=M

For those Network Directories that contain applications
(executables), the drives used to map to these applications should
be included in the DOS environment variable PATH. For example, the
following lines could also be included in an AUTOEXEC.BAT or
STARTNET.BAT file:

NET MAP G: TURBOC
NET MAP H: WORDPERFECT
NET MAP I: GAMES
SET PATH=G:\BIN;H:.;I:\TETRIS;%PATH

SOLUTION

NA


  3 Responses to “Category : Network Files
Archive   : NOVELFAX.ZIP
Filename : 1012655.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/