Microsoft KB Archive/65354

Minimum File Requirements for DOS Basic & Enhanced LAN Manager ID Number: Q65354

2.00 MS-DOS

The information listed below describes the minimum file requirements for DOS Basic and Enhanced LAN Manager.

= DOS BASIC LAN MANAGER =

It is assumed that you have set up your MS-DOS disk correctly, and that you have all of the required files for whatever operation you would like to perform in MS-DOS on the disk. The following is a list of the necessary and optional files:

Filename Comment ——– ——-

CHKNET.EXE

LANMAN.INI Optional. You can do without this file because it simply acts like a command file. If you delete this file you must know how to use the individual TSRs (terminate-and-stay-resident)/executables and in what order. To determine the order of the TSRs/executables, examine the LANMAN.INI file.

MINSES.EXE

NET.EXE Optional. Once again, if you delete this file, you will not be able to use the NET PAUSE and NET CONTINUE commands, and you must know how to use the TSRs/executables. The syntax can be best studied by looking at the LANMAN.INI file.

NET.MSG Optional. This file is not necessary if you can live without error messages. If this file is not present, for every command you enter, you will receive a “NET.MSG not found” error message. This file is used for issuing messages such as the following:

Command completed successfully. REDIR.EXE This file has three different versions of it: REDIR.320, REDIR.330, and REDIR.400, depending on what version of MS-DOS you are using.

NETBIND.EXE This file is necessary if you are using NDIS drivers.

SETNAME.EXE This file adds your computer name to the NetBIOS Name table, and also lists it (for example, NET NAME).

PRTSC.EXE This file captures the CTRL+ALT+PRINT SCREEN keystroke sequence and flushes the buffer. It chains onto INT 09H, 21H, and 28H, and the drivers (both MAC and transport) with the appropriate PROTOCOL.INI file. At this point, all you can do is start your redirector, but you cannot use any useful commands such as NET USE (disk, printer). However, you can execute commands such as NET PAUSE or NET CONTINUE because they are built into NET.EXE.

Add the files listed below for the commands shown:

Filename Command/Comment ——– —————

USE.EXE (NET USE)

PRINTQ.EXE (NET PRINT)(OPTIONAL) This file is only needed for print queue access and can be obtained via a server search path.

NETMOVE.EXE (NET MOVE)(OPTIONAL) This file is only needed for the NET MOVE function, and can be obtained via a server search path.

NETCOPY.EXE (NET COPY)(OPTIONAL) This file is only needed for the NET COPY function, and can be obtained via a server search path.

The last two utilities listed above (NETMOVE.EXE and NETCOPY.EXE) will work correctly with DOS Basic LAN Manager, even though they are not placed on a DOS Basic LAN Manager installation. Please note that if you are using the NETMOVE and NETCOPY commands in conjunction with a NET command (for example, NET MOVE), you must remember to make entries in LANMAN.INI for the NET commands that you are using. For example:

For the command NET MOVE, you must add the following lines to your LANMAN.INI file:

move $* netmove $* /* Once again, please note that you will not get any help on this command because there is no help file available for this command in the DOS Basic LAN Manager. However, you still can use the command.

= ENHANCED LAN MANAGER =

Filename Command/Comment ——– —————

CHKNET.EXE

LANMAN.INI Optional. If you don’t use this file, you will have to enter all the workstation parameters in front of the netwksta line. Therefore, it is best to use this file.

MINSES.EXE

NET.EXE This file contains the LOGON, PAUSE, USE, PRINT, etc., commands, and thus is different than the DOS Basic LAN Manager version of this file.

NET.MSG This file should be placed in the NETPROG directory in your LANROOT directory. You must create the NETPROG directory in your LANROOT directory.

OSO001.MSG This file should be placed in the directory specified in the LANMAN.INI file. This information is hard-coded into NET.EXE, and that is exactly where it looks for these files. This file is not necessary if you can live without error messages such as “Cannot find NET.MSG/OSO001.MSG” (for more information, see the information listed above for NET.MSG).

NETWKSTA.EXE This file is MS-DOS version dependent. Please note that it comes from NETWKSTA.400, NETWKSTA.330, etc.

SETNAME.EXE See the description of SETNAME.EXE included above for DOS Basic LAN Manager.

NETBIND.EXE See the description of NETBIND.EXE included above for DOS Basic LAN Manager.

Add the usual drivers with the appropriate PROTOCOL.INI file.

For additional commands, add the following:

Filename Command/Comment ——– —————

NETMOVE.EXE (NET MOVE)(OPTIONAL) This file is only needed for the NET MOVE function, and can be obtained via a server search path.

NETCOPY.EXE (NET COPY)(OPTIONAL) This file is only needed for the NET COPY function, and can be obtained via a server search path.

PRINTQ.EXE (OPTIONAL)(NET PRINT) This file is only needed for print queue access, and can be obtained via a server search path.

PRTSC.EXE This file captures the CTRL+ALT+PRINT SCREEN keystroke sequence and flushes the buffer. It also chains onto INT 09H, 21H, and 28H.

USE.EXE (NET USE) This file is only needed for the FILE SYSTEM in which you require to do I/O over the network, and can be accessed by a server search path.

NETAPI.EXE (OPTIONAL) This file is only needed for API support.

ENCRYPT.EXE (OPTIONAL) This file is only needed for password encryption.

MSRV.EXE (OPTIONAL) This file is only need for the MESSENGER service.

NETPOPUP.EXE (OPTIONAL) This file is only needed for NETPOPUP support.

= EXAMPLE: BUILDING A LAN MANAGER 2.00 DOS ENHANCED 1.2 MB BOOT DISK =

This is the BARE MINIMUM file setup for a 3Com EtherLink II card with NetBEUI. This configuration takes up about 515K of disk space. If you have a different card, you must change the card driver file in the in your CONFIG.SYS file.

With this minimum configuration, you will get two errors with the first NET LOGON command (because it can’t find the message files to tell you that the command completed successfully). These errors can be ignored. Also, if the optional Assign statement at the end of your AUTOEXEC.BAT file is used, an error stating that the batch file can no longer be found will be issued. This error can also be ignored. In fact, you may be able to put this Assign statement in a logon script and work around this error.

If there is 700K left on this disk, you can add the following files to this bare-minimum setup for more functionality:

  Add HIMEM.SYS, EMM386.SYS, SMARTDRIVE.SYS, and RAMDRIVE.SYS if you have the memory to use these utilities.   Place the message files (NET.MSG and OSO001.MSG) in .DOS. If you do this, the two error messages will not be displayed when you enter the first NET LOGON command. These network errors occur because the message files can’t be found until you get a drive mapped to the server.   The bare-minimum setup does not let you autostart the messenger (MSRV.EXE), netpopup (NETPOPUP.EXE), and encrypt (ENCRYPT.EXE) services. You CAN start them later, after you have a drive mapped to a server share with the .DOS files, and then use the NET START SERVICE command. However, if you put the following files on the floppy disk, you can have these services start up automatically. Add the messenger, netpopup, and encrypt services into the .DOSdirectory. The service names need to be added to the wrkservices line in the LANMAN.INI file. Also, you need to create a .DOSdirectory for the messenger service to start. 

Floppy Disk Directories
Volume in drive A is DOS4BOOT Volume Serial Number is 2C6A-10E1 Directory of A:

LANMAN DOS  09-29-90 11:22a COMMAND COM 37557 04-07-89 12:00a CONFIG SYS 208 09-29-90 11:26a AUTOEXEC BAT 341 09-29-90 11:42a 4 file(s) 38106 bytes 707072 bytes free

Volume in drive A is DOS4BOOT Volume Serial Number is 2C6A-10E1 Directory of A:.DOS

.  09-29-90 11:22a ..  09-29-90 11:22a DRIVERS  09-29-90 11:24a NETPROG  09-29-90 11:22a LANMAN INI 2181 09-29-90 11:21a PROTOCOL INI 316 09-29-90 11:13a 6 file(s) 2497 bytes 707072 bytes free

Volume in drive A is DOS4BOOT Volume Serial Number is 2C6A-10E1 Directory of A:.DOS

.  09-29-90 11:24a ..  09-29-90 11:24a ELNKII DOS 10150 06-28-90 12:00a NETBEUI DOS 30326 06-28-90 12:00a PROTMAN DOS 10661 06-28-90 12:00a 5 file(s) 51137 bytes 707072 bytes free

Volume in drive A is DOS4BOOT Volume Serial Number is 2C6A-10E1 Directory of A:.DOS

.  09-29-90 11:22a .. <DIR> 09-29-90 11:22a CHKNET EXE 698 06-28-90 12:00a MINSES EXE 2438 06-28-90 12:00a NET EXE 218430 06-28-90 12:00a NETBIND EXE 15639 06-28-90 12:00a NETWKSTA EXE 98560 06-28-90 12:00a 7 file(s) 335765 bytes 707072 bytes free

AUTOEXEC.BAT
BUFFERS=20 FILES=20 LASTDRIVE=Z SHELL=COMMAND.COM /P /E:256

DEVICE=A:.DOS.DOS /i:A:.DOS DEVICE=A:.DOS.DOS DEVICE=A:.DOS.DOS PATH=F:;F:;

REM == LANMAN 2.0 == DO NOT MODIFY BETWEEN THESE LINES == LANMAN 2.0 == PATH=A:.DOS;%PATH%; NETBIND NET START WORKSTATION REM == LANMAN 2.0 == DO NOT MODIFY BETWEEN THESE LINES == LANMAN 2.0 ==

PROMPT $P$ G

NET LOGON scott * NET USE f: \psu

ASSIGN a=f >>>>>>>>>>COMMENT: THIS IS OPTIONAL

LANMAN.INI

 * ;** Microsoft LAN Manager ; ; Copyright? Microsoft Corp., 1990 ; ;***************************************************************; ;*****************************************************************; ;* NOTE ; ; THIS FILE IS USED BY THE ENHANCED VERSION OF DOS LANMAN WITH  ; API SUPPORT IF YOU HAVE INSTALLED THE BASIC VERSION OF DOS  ; LANMAN OR THE ENHANCED VERSION BUT WITHOUT API SUPPORT, THE  ; SYSTEM USES THE FILE LANMAN.INI IN THE NETPROG DIRECTORY  ; INSTEAD OF THIS ONE.  ;  ;****************************************************************

[networks]

netservices = chknet, minses

[workstation] wrkservices = charcount = 16 chartime = 250 charwait = 128 computername = Lan_Dude domain = DOMAIN himem = no keepapis = yes keepconn = 600 keepsearch = 600 lanroot = \PSU.DOS lim = no mailslots = yes maxcmds = 30 numbigbuf = 0 numcharbuf = 2 numdgrambuf = 14 nummailslots = 5 numresources = 15 numservers = 15 numservices = 10 numviewedservers = 50 numworkbuf = 10 othdomains = sizcharbuf = 128 sizworkbuf = 1024 sizbigbuf = 4096


 * The next lines help you to locate bits in the wrkheuristics entry. ; 1 2 3 ; 012345678901234567890123456789012 wrkheuristics = 111121101221200000000000000000000 wrknets = 0

[messenger] nummsgnames = 2 sizmessbuf = 256 logfile = messages.log

[netshell] username = scott

[services] chknet = netprog.exe minses = netprog.exe workstation = netprog.exe messenger = services.exe netpopup = services.exe encrypt = services.exe

PROTOCOL.INI
[PROTOCOL MANAGER] DRIVERNAME = PROTMAN$

[NETBEUI_XIF] drivername = netbeui$ BINDINGS = “ELNKII_NIF”

[ELNKII_NIF]


 * protocol.ini section for the 3Com EtherLink II Adapter Card

IOADDRESS = 0x300 INTERRUPT = 3 MAXTRANSMITS = 40 DRIVERNAME = ELNKII$ TRANSCEIVER = EXTERNAL