Remote Booting With DOS/Win Client 32

(Last modified: 07Feb2002)

This document (10018195) is provided subject to the disclaimer at the end of this document.


Clients for DOS/WIN 3.x


Remote Booting With DOS/Win Client 32

Needs to configure a remote boot of WIN 3.11 with the DOS/WIN Client 32.  However, the current version of DOS/WIN Client 32 does not support remote booting:   


This is a work-around rather than a solution. For this work-around to work all workstations must have a minimum of 16MB of RAM. The idea is to create a boot image using VLMs (which does support remote booting). One of the things that the boot image does is to create a 9MB RAM Drive (Drive C: ) on the workstation to simulate a hard disk. During the boot-up process the files contained in the boot image and files placed in the login directory are copied to the C: Drive (which is the RAM Drive). Once the machine has booted, the C: Drive now has all the software components necessary to run the Client 32. The VLMs are unloaded and the Client32.NLM is loaded, freeing a huge amount of conventional memory.

 Setup a diskette with the following files and boot files:

     device=emm386.exe noems
     device=ramdrive.sys 9000 512 256 /e

     @ECHO OFF
     copy *.* c:\>NUL
     set comspec=C:\COMMAND.COM

     VLM /U
     REN net.cfg > NUL
     REN net.two net.cfg > NUL
     Load Client32.NLM

     Dir A:

      Volume in drive A has no label
      Volume Serial Number is 1915-11F2
      Directory of A:\

     COMMAND COM 54,619 09-30-93 6:20a COMMAND.COM
     HIMEM SYS 29,136 09-30-93 6:20a HIMEM.SYS
     EMM386 EXE 120,926 05-31-94 6:22a EMM386.EXE
     NET CFG 3,675 05-21-96 11:54a NET.CFG
     AUTOEXEC BAT 72 05-17-96 4:23p AUTOEXEC.BAT
     NIOS EXE 239,117 04-18-96 3:26p NIOS.EXE
     LSLC32 NLM 18,571 02-27-96 10:31a LSLC32.NLM
     CMSM NLM 57,120 03-28-96 2:41p CMSM.NLM
     ETHERTSM NLM 14,411 03-11-96 3:40p ETHERTSM.NLM
     3C59X LAN 26,863 02-02-96 3:12p 3C59X.LAN
     IPX NLM 113,726 03-19-96 9:09a IPX.NLM
     VLM EXE 37,651 06-16-95 12:39p VLM.EXE
     NBIHW CFG 0 05-17-96 12:12p NBIHW.CFG
     STARTNET BAT 166 05-21-96 11:55a STARTNET.BAT
     RAMDRIVE SYS 5,873 03-10-93 6:00a RAMDRIVE.SYS
     CONFIG SYS 109 05-17-96 4:20p CONFIG.SYS
     NET TWO 3,675 05-20-96 4:18p NET.TWO
     CONN VLM 10,850 06-16-95 12:40p CONN.VLM
     IPXNCP VLM 10,116 06-16-95 12:40p IPXNCP.VLM
     TRAN VLM 1,562 06-16-95 12:40p TRAN.VLM
     SECURITY VLM 8,011 06-16-95 12:40p SECURITY.VLM
     BIND VLM 4,713 06-16-95 12:40p BIND.VLM
     NWP VLM 6,661 06-16-95 12:40p NWP.VLM
     FIO VLM 18,250 06-16-95 12:41p FIO.VLM
     GENERAL VLM 4,958 06-16-95 12:41p GENERAL.VLM
     REDIR VLM 14,842 06-16-95 12:40p REDIR.VLM
     PRINT VLM 8,005 06-16-95 12:40p PRINT.VLM
     NETX VLM 17,230 06-16-95 12:41p NETX.VLM

     1) Note that in the config.sys file - the RAMDRIVE is 9MB.
     2) This requires machine to have at least 16MB of RAM.
     3) There are two "net.cfg" files; the first one is the net.cfg file used by the VLMs during remote
     boot. This one has "Packet Burst = 0" to avoid the FIO.VLM error.
     4) There second "net.cfg" - "net.two" has "Packet Burst = 1" - this is used by the Client32.
     5)Place the Client32.NLM and its message files in the F:\Login Directory



Document Title: Remote Booting With DOS/Win Client 32
Document ID: 10018195
Solution ID: 1.0.33044120.2349387
Creation Date: 05Oct1999
Modified Date: 07Feb2002
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.