Networking Connectivity
Network Connectivity
MS-DOS Client Boot Disk to Connect With a Windows NT* 4.0 Server Using NetBEUI

Symptom(s):
Unable to create a DOS boot disk with a Xircom® network adapter.

Solution:
This document helps you create a DOS Boot Disk to connect a client computer to a Windows NT* 4.0 Server. The Xircom DOS/Windows 3.x Installation Disk contains the 16-bit Real Mode NDIS driver that is used in creating the boot disk. You can obtain this file from our Web site.

Known Issues

The use of the DOS boot disk is severely limited if your computer requires DOS-based Card and Socket Services to communicate with the computer's PCMCIA slots. The files used in DOS-based card and socket services are too large to reside on the disk. They must reside on the computer if you want to use them.

To use the Xircom adapter, you must modify the CONFIG.SYS file (on the floppy disk) to load the drivers, and you may need to modify the DOS-based Card and Socket Service startup files. The DOS-based Card and Socket Services are not generally included with computers, so if your computer requires DOS-based Card and Socket Services for proper operation of PC cards in DOS, you must obtain them from the computer manufacturer or the software developer.

Windows NT DOS Boot Disk

The System Administrator uses the Network Client Administrator function, included with Windows NT 4.0 Server, to create a network installation startup disk. This feature is available only with Windows NT Server. For additional information on using this feature, consult the NT 4.0 Server User's Guide or use Windows NT 4.0 Server Help.

NOTE: The file DSK3-1.EXE can be obtained from the Microsoft FTP site and used to create the DOS boot disk as well. The following description however, only covers the creation of this disk using Windows NT 4.0 Server.

In this example, we are using a Xircom CE3 adapter to connect a computer running DOS to an NT 4.0 server using the NetBEUI protocol.

From the NT 4.0 server, follow this procedure:

1. Click Start, point to Programs, and then click Administrative Tools.

2. In the Network Client Administrator, select Make Network Installation Startup Disk, and then click Continue.

NOTE: Make sure that your shared files are set correctly.

3. Select the Floppy Drive, and then select the Client and click Network Adapters.

4. Using the down arrow, select the Xircom Pocket Ethernet II adapter.

5. Enter the Computer Name, User Name, Domain, and Network Protocol (NetBEUI). This example uses the NetBEUI protocol. However, you can select a different protocol before you begin the disk creation process. (For example, if you wish to use the TCP/IP protocol see document KB1219).

The required files are created and copied to the floppy disk. These files must be modified (as outlined below) to allow the use of your Xircom adapter.

Here is a sample configuration using the Xircom CE3 card and the NetBEUI protocol:

CONFIG.SYS
REM (a REM is used to disable a line in this file)
REM (add the memory exclusion for the CE3 to the EMM386.EXE line)
REM (in this example it is D200-D7FF)
DEVICE=A:\NET\HIMEM.SYS
DEVICE=A:\NET\EMM386.EXE NOEMS X=D200-D7FF
DOS=HIGH,UMB
FILES=30
LASTDRIVE=Z
DEVICE=A:\NET\IFSHLP.SYS
AUTOEXEC.BAT
REM (a REM is used to disable a line in this file)
REM (no changes are required to this file)
PATH=A:\;A:\NET
A:\NET\NET START
A:\NET USE Z:\(server name)\Clients
ECHO Running Setup...
REM Disable the following line if you are doing anything
REM other than a Microsoft Windows NT 4.0 Setup
Z:\MSCLIENT\NETSETUP\SETUP.EXE /$

PROTOCOL.INI
;(a semicolon is used to disable a line in this file)
[network.setup]
VERSION=0x3110
NETCARD=ms$xirc,1,MS$XIRC,1
transport=ms$ndishlp,MS$NDISHLP
transport=ms$netbeui,MS$NETBEUI
lana0=ms$xirc,1,ms$netbeui
lana1=ms$xirc,1,ms$ndishlp

[ms$xirc]
;(This is the only section that can or should be)
;(modified in the Protocol.ini file.)
;(This section may not necessarily be named ms$xirc.)
;(Set the adapter resources and features as needed.)
;(With the latest Xircom drivers most-likely only the)
;(DriverName line is needed in this section. However, you can)
;(enable the resources and features needed below by removing)
;(the semi-colon and setting the desired values if necessary)
DRIVERNAME=XIRCOM$
;IOADDRESS = 0x320
;INT = 10
;MEM = 0xD2000
;NOCOM
;NOCHECK

[protman]
drivername=PROTMAN$
PRIORITY=MS$NDISHLP

[MS$NDISHLP]
drivername=ndishlp$
BINDINGS=ms$xirc

[ms$netbeui]
drivername=netbeui$
SESSIONS=10
NCBS=12
BINDINGS=ms$xirc
LANABASE=0

SYSTEM.INI
;(a semicolon is used to disable a line in this file)
;(change the driver PE2NDIS.DOS to CE3NDIS.EXE)
[network]
filesharing=no
printsharing=no
autologon=yes
;(The computer name should reflect your environment)
computername=DOS
lanroot=A:\NET
username=Administrator
workgroup=WORKGROUP
reconnect=no
directhost=no
dospophotkey=N
lmlogon=0
logondomain=WORKGROUP
preferredredir=full
autostart=full
maxconnections=8

[network drivers]
;(add the NDIS driver for your adapter on a netcard line and)
;(disable the PE2NDIS.DOS line by adding a semi-colon)
;netcard=PE2NDIS.DOS
netcard=CE3NDIS.EXE
transport=ndishlp.sys,*netbeui
devdir=A:\NET
LoadRMDrivers=yes

[Password Lists]
*Shares=a:\net\Share000.PWL
_____________

Copy the Xircom NDIS2 driver (CE3NDIS.EXE in this example) from the Xircom DOS/Windows 3.x Installation disk, or from the extracted (downloaded) files, to the A:\NET directory. You can delete the PE2NDIS.DOS file if you are not using a PE2 adapter.

Note: A Xircom CE3 was used in the previous example. If you are using a different Xircom card, use the appropriate *NDIS.EXE file for your particular Xircom card in place of the CE3NDIS.EXE file. Xircom uses *NDIS.EXE drivers in place of *.DOS drivers when using a DOS Client Boot Disk to attach to Windows NT Server.

Relevant Information: Microsoft Windows NT* Workstation 4.0, Microsoft Windows NT* Server 4.0

This applies to:

Xircom® 10/100 Network PC Card Adapter (XE2000)
Xircom® 10/100 Network+Modem 56 PC Card Adapter (XEM5600)
Xircom® CardBus Ethernet 10/100 Adapter (CBE-10/100BTX)
Xircom® CardBus Ethernet 10/100+Modem 56 GlobalACCESS Adapter (CBEM56G-100)
Xircom® CardBus Ethernet II 10/100 Adapter (CBE2-100)
Xircom® CreditCard Ethernet 10 Adapter (CE3-10)
Xircom® CreditCard Ethernet 10/100 Adapter (CE3B-100BTX)
Xircom® CreditCard Ethernet 10/100+Modem 56 GlobalACCESS Adapter (CEM56-100)
Xircom® CreditCard Ethernet II Adapter (CE2, PS-CE2-10)
Xircom® CreditCard Ethernet+Modem 28.8 Adapter (CEM28, CEM-28)
Xircom® CreditCard Ethernet+Modem 33.6 Adapter (CEM33)
Xircom® CreditCard Ethernet+Modem 33.6 GlobalACCESS Adapter (CEM33i)
Xircom® CreditCard Ethernet+Modem II Adapter (CEM2)
Xircom® RealPort™ CardBus Ethernet 10/100 Adapter (RBE-100)
Xircom® RealPort™ CardBus Ethernet 10/100+Modem 56 GlobalACCESS Adapter (RBEM56G-100)
Xircom® RealPort™ Ethernet 10 Adapter (RE-10)
Xircom® RealPort™ Ethernet 10+Modem 56 GlobalACCESS Adapter (REM56G-10)
Xircom® RealPort™ Ethernet 10/100 Adapter (RE-100)
Xircom® RealPort™ Ethernet 10/100+Modem 56 GlobalACCESS Adapter (REM56G-100)
Xircom® RealPort2™ CardBus Ethernet 10/100 Adapter (R2BE-100)
Xircom® RealPort2™ CardBus Ethernet 10/100+Modem 56 GlobalACCESS Adapter (R2BEM56G)
Xircom® RealPort2™ Ethernet 10/100 Adapter (R2E-100BTX)



Solution ID: CS-003317 (1.0.2200626.3367859)
Last Modified: 24-Mar-2014
Date Created: 26-Dec-2002
Back to Top