• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 207
  • Last Modified:

Network boot disk on NT

I want to make Network Dos cleint boot disk!
When i go into the Network Client Adm, i make my boot disk but i dont have the right NIC, and NT dont want me to browse for new drivers for my NIC !!

I tried to replace the ***.DOS and edited protocol.ini on the boot disk, with the **.dos from the NIC manufacturer (3Com 905B) but i alway have an error message when i try to boot with my disk; cannot open protman.dos

is there a way Network Client administrator could be modified to suggest the right NIC in the list ??

Tx all
0
lavabo
Asked:
lavabo
1 Solution
 
LermitteCommented:
SUMMARY
=======
 
This article explains how to add an NDIS driver for Network Interface Cards
(NIC) that were not originally included in the Network Client Administrator.
This information applies to the Network Client version 3.0 for MS-DOS and
Windows Startup Disk.
 
Verify that the 3.5" HD disk to which the client files will be copied is a DOS
system disk and formatted under DOS. If the disk is formatted under NT, the copy
process will fail.
 
MORE INFORMATION
================
 
To configure this disk:
 
NOTE: The following example is for the Intel EtherExpressPro NIC; however, this
example can serve as a template for all NDIS compatible drivers.
 
1. Copy the Epro.dos driver to the A:\Net directory.
 
2. Modify the Net\Protocol.ini file and change the [EPRO$] section to
   "drivername=EPRO$".
 
   NOTE: The "drivername=" information is included on most manufacturers' disks
   in the sample Protocol.ini file that comes with the network card.
 
3. Modify the Net\System.ini file and change the [network drivers] section to
   "netcard=Epro.dos".
 
   NOTE: The file that the "netcard=" equals is also on the manufacturer's disk.
 
Additional drivers can be found on the Windows NT Server compact disc in the
Clients\Wdl\Update directory.
 
For more information, please see the following article in the Microsoft Knowledge
Base:
 
   ARTICLE-ID: Q128800
   TITLE : How to Provide Additional NDIS2 Drivers for Network Client 3.0
 
Sample Protocol.ini Entries
---------------------------
 
[network.setup]
version=0x3110
netcard=EPRO$,1,EPRO$,1
transport=ms$ndishlp,MS$NDISHLP
transport=ms$nwlink,MS$NWLINK
lana0=EPRO$,1,ms$nwlink
lana1=EPRO$,1,ms$ndishlp
 
[EPRO$]
drivername=EPRO$
; IRQ=3           <----------------- You may have to adjust this.
; IOADDRESS=0x330 <----------------- You may have to adjust this.
; IOCHRDY=Late
; TRANSCEIVER=Thin Net (BNC/COAX)
 
[protman]
drivername=PROTMAN$
PRIORITY=MS$NDISHLP
 
[MS$NDISHLP]
drivername=ndishlp$
BINDINGS=EPRO$
 
[ms$nwlink]
drivername=nwlink$
FRAME=Ethernet_802.2
BINDINGS=EPRO$
LANABASE=0
 
Sample System.ini Entries
-------------------------
 
[network]
filesharing=no
printsharing=no
autologon=yes
computername=TEST
lanroot=A:\NET
username=Administrator
workgroup=TESTDOM
reconnect=no
dospophotkey=N
lmlogon=0
logondomain=BOARD
preferredredir=full
autostart=full
maxconnections=8
 
[network drivers]
netcard=epro.dos     <----------- If the path is not set, specify the
                                   full directory (for example,
                                   c:\net\epro.dos).
 
transport=ndishlp.sys
devdir=A:\NET
LoadRMDrivers=yes
 
[Password Lists]
*Shares=a:\net\Share000.PWL

Mario
0
 
ghanaCommented:
I've already made a boot disk for the 3Com 3C905B. The first step is to create a boot floppy with a nic that is supported by the Network Client Administrator. That will copy all the necessary common files to the disk and you only have to modify the nic files.

The DOS driver file in your case is EL90X.DOS, so you need the following content in the PROTOCOL.INIfile:


[network.setup]
version=0x3110
netcard=NicInfo,1,NicInfo,1
transport=tcpip,TCPIP
lana0=NicInfo,1,tcpip


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

[NicInfo]
MAXTRANSMITS=40
; *** insert the filename of your driver without the extension
;     and followed by a '$' here. e.g.: if the driver filename
;     is el90x.dos, insert el90x$ here - (here El90x.dos)
DriverName=El90X$

[tcpip]
NBSessions=6
DefaultGateway0=
SubNetMask0=
IPAddress0=
DisableDHCP=0
DriverName=TCPIP$
BINDINGS=NicInfo
LANABASE=0

This example is for TCP/IP and DHCP. If you don't use DHCP in your network you have to set values for SubNetMask=, IPAddress=. And you have to set DisableDHCP=1.

Now you have to create the SYSTEM.INI file. You have to use a single computer name in your network (computername= ), you have to specify a valid user account in your domain (username= ) and you have to specify the name of your domain or workgroup (workgroup= ). And of course you have to modify the netcard= value to the DOS driver name:


[network]
filesharing=no
printsharing=no
autologon=yes
computername=testPC
lanroot=A:\NET
username=itworks
workgroup=domain
reconnect=no
dospophotkey=N
lmlogon=0
logondomain=Force
preferredredir=full
autostart=full
maxconnections=8

[network drivers]
; *** insert the exact filename of the DOS driver of the network
;     card in this field
netcard=El90x.dos
transport=tcpdrv.dos,nemm.dos
devdir=A:\NET
LoadRMDrivers=yes

[Password Lists]
*Shares=a:\Net\shares.pwl
INSTALL=A:\NET\INSTALL.PWL


Now finally copy the EL90X.DOS, SYSTEM.INI and PROTOCOL.INI to the a:\net directory (not the root a:\ !!!) and start up your computer.

If you have any further questions feel free to ask me again.
0
 
jvsteenCommented:
0

Featured Post

2018 Annual Membership Survey

Here at Experts Exchange, we strive to give members the best experience. Help us improve the site by taking this survey today! (Bonus: Be entered to win a great tech prize for participating!)

Tackle projects and never again get stuck behind a technical roadblock.
Join Now