首先说明一下,microsoft network client v3.0 for ms-dos 用的是
符合Microsoft公司NDIS 2.0 标准的以.DOS为扩展名的网卡驱动程序。
而FTP等工具用的是符合FTP公司Packet Driver标准的开放源码的驱动程
序,以.COM或.EXE为扩展名。
也就是说你的pcntpk.com是Packet Driver(包驱动程序),不能用在
MS client上。只能用在FTP等工具上。MS Client的网卡驱动是以.DOS为
扩展名的。
BTW: intel pro/100B packet driver的加载命令应该是 e100bpkt 0x60 16
我是在 e100bpkt.txt 里看到这个用法的。别的网卡的packet driver可以
看相应的txt说明文件(下载packet driver时带的)。或者用/?看命令行参数。
如加载AMD PCnet packet driver的命令行是 pcntpk int=0x60
下面以我做的网络启动盘(见:一张软盘启动M$CLIENT网络)为例,
说说MS Client禁用DHCP获取IP和配置IP地址的两种方法:
第一种方法,修改a:\net\amdpcnet\protocol.ini (amdpcnet是vmware虚拟网卡驱动的配置目录)
修改里的一行为 DisableDHCP=1 即可禁用DHCP获取IP
修改相应的IPAddress0和SubNetMask0设置IP地址和子网掩码
第二种方法,运行n:\net\setup.exe修改配置
启动时选择网卡(用vmware则选AMD PCnet Family)
询问“Start Network?”时,选NO!
执行 n:\net\setup.exe
提示插入软盘时,按回车
选择Change Network Configuration,按回车进入
选择Change Settings,不要按回车!!!
按Tab键使光标跳到上面选择框(注:很多人不知道光标可以跳上去)
选择Microsoft TCP/IP,按回车进入
把Disable Automatic Configuration改为1即可禁用DHCP获取IP
把IP Address和IP Subnet Mask改为你想要的IP地址和子网掩码
选择The listed options are correct确认设置正确
直到提示插入软盘时按F3退出Setup!!
如果只想临时改变配置,在N:\NET目录下执行STARTNET.BAT
即可启动网络。如想永远改变配置,请把N:\NET目录的
SYSTEM.INI和PROTOCOL.INI文件拷贝到A:\NET下与网卡类型
相对应的子目录(如:a:\net\amdpcnet目录)。
另外,Setup.exe还可以改变工作组名、计算机名或登录域等设置。请读者自己摸索。
注意:因为我做的网络启动盘用了内存虚拟盘,所以改变配置后记得按上面所说的,
把system.ini和protocol.ini拷回A盘!
如果你想自己安装MS Client,当手动输入网卡驱动位置时,记得是NDIS驱动的位置!!
MS Client不认packet驱动的!
First of all, Microsoft Network Client v3.0 for MS-DOS uses a network card driver with the extension .DOS that complies with Microsoft's NDIS 2.0 standard. The FTP and other tools use an open-source driver that complies with the Packet Driver standard of FTP, with the extension .COM or .EXE.
That is to say, your pcntpk.com is Packet Driver, which cannot be used on the MS client. It can only be used on tools like FTP. The network card driver for the MS Client has the extension .DOS.
BTW: The loading command for the intel pro/100B packet driver should be e100bpkt 0x60 16. I saw this usage in e100bpkt.txt. For other network cards' packet drivers, you can refer to the corresponding txt instruction files (brought when downloading packet driver) or use /? to view the command-line parameters. For example, the command line to load the AMD PCnet packet driver is pcntpk int=0x60.
The following takes the network boot disk I made (see: Booting M$ CLIENT Network with a Floppy Disk) as an example to talk about two methods for the MS Client to disable DHCP to obtain IP and configure IP address:
The first method: Modify a:\net\amdpcnet\protocol.ini (amdpcnet is the configuration directory of the vmware virtual network card driver). Modify a line in to DisableDHCP=1 to disable DHCP to obtain IP. Modify the corresponding IPAddress0 and SubNetMask0 to set the IP address and subnet mask.
The second method: Run n:\net\setup.exe to modify the configuration. When starting, select the network card (if using vmware, select AMD PCnet Family). When asked "Start Network?", select NO! Execute n:\net\setup.exe. When prompted to insert the floppy disk, press Enter. Select Change Network Configuration, press Enter to enter. Select Change Settings, do not press Enter!!! Press the Tab key to make the cursor jump to the above selection box (Note: Many people don't know that the cursor can jump up). Select Microsoft TCP/IP, press Enter to enter. Change Disable Automatic Configuration to 1 to disable DHCP to obtain IP. Change IP Address and IP Subnet Mask to the IP address and subnet mask you want. Select The listed options are correct to confirm that the settings are correct. Until prompted to insert the floppy disk, press F3 to exit Setup!!
If you only want to temporarily change the configuration, execute STARTNET.BAT in the N:\NET directory to start the network. If you want to permanently change the configuration, copy the SYSTEM.INI and PROTOCOL.INI files in the N:\NET directory to the corresponding subdirectory in the A:\NET directory (such as: a:\net\amdpcnet directory).
In addition, Setup.exe can also change the workgroup name, computer name or logon domain, etc. Please let the readers explore by themselves.
Note: Because the network boot disk I made uses a memory virtual disk, remember to copy system.ini and protocol.ini back to the A disk as mentioned above after changing the configuration!!
If you want to install the MS Client by yourself, when manually entering the network card driver location, remember it is the location of the NDIS driver! The MS Client does not recognize the packet driver!!