Creating DOS Basic LAN Manager Bootable Floppy Disk

ID Number: Q63784

2.00

MS-DOS

Question:

Can DOS Basic LAN Manager be run off a system that only has floppy

disk drives in it?

Response:

Yes, it is possible to build a boot floppy disk for DOS Basic LAN

Manager on even a 360K floppy disk.

The following steps can be used to produce a bootable floppy disk:

1. Create a directory on the server with all of the DOS Basic LAN

Manager NETPROG files in it (NETCOPY and NETMOVE from the DOS LAN

Manager Enhanced may also be put into this directory). In the

example listed below, this is accessed via the share point named

\\SERVER\PUBLIC in the subdirectory named DOS\LANMAN\BASIC.

2. Create a directory on the server with all of the MS-DOS version

4.01 files in it. In the example included below, this is accessed

via the share point named \\SERVER\PUBLIC, in the subdirectory

named DOS\DOS_4.01.

3. Format a disk on a working MS-DOS system (this places IO.SYS,

MSDOS.SYS and COMMAND.COM) on the floppy disk.

4. It is recommended that you place all the additional files listed

below in the root directory if you are using a 360K floppy disk.

Subdirectories do require some extra disk space, and there is not

a great deal of extra space on a 360K floppy disk.

5. Create the CONFIG.SYS file as listed below. In the example listed

below, 3Com 3C503 EtherLink II cards are used.

6. Create the AUTOEXEC.BAT file as listed below. Be sure that you set

up the COMSPEC and PATH variables correctly.

As in the example listed below, it is assumed that you have both a

mouse and the high-memory manager. There is some space left over on

the floppy disk, so you can customize it further.

MS-DOS Version 4.01 Boot Disk

-----------------------------

IO SYS 33337 4-07-89 12:00a

MSDOS SYS 37376 4-07-89 12:00a

AUTOEXEC BAT 855 6-08-90 7:47p

COMMAND COM 37557 4-07-89 12:00a

CONFIG SYS 484 6-30-90 8:36p

MOUSE SYS 26514 9-01-89 12:00a

CHKNET EXE 698 6-28-90 12:00a

ELNKII DOS 10150 6-28-90 12:00a

HIMEM SYS 11304 4-06-90 10:24a

LANMAN INI 216 6-30-90 8:40p

MINSES EXE 2438 6-28-90 12:00a

NET EXE 10598 6-28-90 12:00a

NETBEUI DOS 30326 6-28-90 12:00a

NETBIND EXE 15639 6-28-90 12:00a

PROTCHK EXE 30581 6-28-90 12:00a

PROTMAN DOS 10661 6-28-90 12:00a

PROTOCOL INI 290 6-30-90 8:46p

REDIR EXE 28084 6-28-90 12:00a

SETNAME EXE 44189 6-28-90 12:00a

USE EXE 10449 6-28-90 12:00a

CONFIG.SYS File

---------------

rem Config.sys

rem

rem Device Drivers

rem

device=a:\himem.sys

REM LANMAN 2.0 === DO NOT MODIFY BETWEEN THESE LINES ===== LANMAN 2.00

DEVICE=a:\PROTMAN.DOS /i:a:\

DEVICE=a:\ELNKII.DOS

DEVICE=a:\NETBEUI.DOS

REM LANMAN 2.0 === DO NOT MODIFY BETWEEN THESE LINES ===== LANMAN 2.00

device=a:\mouse.sys

rem

rem Configuration Parameters

rem

buffers=10,2

files=30

fcbs=4,0

stacks=0,0

lastdrive=z

rem

rem Shell

rem

shell=a:\command.com /p /e:800

AUTOEXEC.BAT File

-----------------

@echo off

rem

rem AutoExec.bat

rem

verify on

@REM LANMAN 2.0 === DO NOT MODIFY BETWEEN THESE LINES ===== LANMAN 2.00

a:\NETBIND

NET START WORKSTATION NAME

@REM LANMAN 2.0 === DO NOT MODIFY BETWEEN THESE LINES ===== LANMAN 2.00

net use f: \\server\public >NUL:

set comspec=f:\dos\dos_4.01\command.com

set path=f:\dos\lanman\basic;f:\dos\dos_4.01;

prompt $p$g

ver