*****************************************************************************
* *
* 32-BIT IO MODE PCI ETHERNET ADAPTER *
* *
* Remote Boot from Windows NT 4.0 Server for RPL Boot ROM *
* *
*****************************************************************************
Contents:
- Remote booting MS-DOS 6.22 from Windows NT Server 4.0
- Remote booting Windows 95 from Windows NT Server 4.0
Remote booting MS-DOS 6.22 from Windows NT Server 4.0
=====================================================
Installing the Remote Boot Service
----------------------------------
- At the NT server, double click the Network icon in the control panel.
Make sure that DLC and NETBEUI protocols have already been installed
in the server. The Remote Boot service requires DLC and NETBEUI.
- Add Remote Boot Service by choosing Service tab, click add button to
select Remote Boot Service to create c:\winnt\rpl directory.
(Windows NT Server compact disc is needed.) You will have to provide
the source path d:\i386 and d:\clients\rpl.
- Check that the \winnt\rpl\rplfiles directory is being shared on
the NT server. It should have the shared name RPLFILES.
Starting the Remote Boot Service
--------------------------------
Double click the Service icon in control panel. In the Services dialog
box, select the Remote Boot Service and click the Start button.
Installing MS-DOS for MS-DOS Clients
------------------------------------
Installing MS-DOS files for Remote Boot workstations :
- Put MS-DOS 6.22 diskette into floppy A. Go to Windows Explorer to
click Floppy A and select IO.SYS, MSDOS.SYS, COMMAND.COM and
HIMEM.SYS files. Copy and paste them to the directory named
C:\winnt\rpl\rplfiles\binfiles\dos622.
- Go to MS-DOS prompt on the NT server, type :
cd \winnt\rpl\rplfiles\binfiles\dos622
attrib -s -h io.sys
attrib -s -h msdos.sys
Starting Remote Boot Manager
----------------------------
On the NT server, log on as administrator and click Start\Program\
Administrator Tools(Common)\Remote Boot Manager to enter Remote Boot
Manager Window.
Checking the Remote Boot Installation
-------------------------------------
From the configure menu, choose check configurations and click Yes
button. From the configure menu, choose Fix Security and click Yes
button.
Creating Remote Boot Configurations for New Adapter
---------------------------------------------------
- Copy network NDIS2 dirver to C:\winnt\rpl\bblock\ndis directory.
You can in MS-DOS prompt under NT server, type :
copy a:\ndis\dos\pcind.dos C:\winnt\rpl\bblock\ndis
- Create C:\winnt\rpl\bblock\netbeui\PCIND directory and copy dosbb.cnf,
w95bb.cnf and protocol.ini files to PCIND directory from
C:\winnt\rpl\bblock\netbeui\NE2000.
You can in MS-DOS prompt under NT server, type :
cd C:\winnt\rpl\bblock\netbeui
md PCIND
cd PCIND
copy C:\winnt\rpl\bblock\netbeui\NE2000\*.*
- Edit dosbb.cnf, w95bb.cnf and protocol.ini to replace MS2000 with
PCIND. (uppercase)
- Create Remote Boot Configurations:
In MS-DOS prompt under NT server, run RPLCMD.EXE to add 'Boot',
'Config' and 'Vendor'. Note: You can delete the preexisting boot
record by typing b then d and provide the boot name and vendor name.
Example: Use RPLCMD utility to add a Boot Block for the new adapter.
C:\WINNT\RPL>RPLCMD
Adapter Boot Config Profile Service Vendor Wksta [Quit]: b
Add Del Enum: a
BootName=DOS-RTL8029
VendorName=0050BF <-- Adapter Vendor Node ID
BbcFile=BBLOCK\NETBEUI\PCIND\DOSBB.CNF
All other parameters are optional
BootComment=Generic RTL8029
WindowsSize=0
Adapter Boot Config Profile Service Vendor Wksta [Quit]: c
Add Del Enum: a
ConfigName=DOS-RTL8029AS
BootName=DOS-RTL8029
DirName=DOS
DirName2=DOS622
FitShared=fits\dos622.fit
FitPersonal=fits\dos622p.fit
All other parameters are optional
ConfigComment=DOS 6.22 & Generic RTL8029AS
DirName3=
DirName4=
Adapter Boot Config Profile Service Vendor Wksta [Quit]: v
Add Del Enum: a
VendorName=0050BF
VendorComment=Generic RTL8029AS
Press Q to Quit
Installing a Client
-------------------
Put Generic Boot ROM to the adapter boot rom socket.
Run SETUP.EXE program to enable the Boot ROM.
Adding "New Profiles", "New Workstations" and "Convert Adapter".
----------------------------------------------------------------
- From the Remote Boot menu in the Remote Boot Manager, choose "New Profile",
type the profile name ex. DOS-RTL8029AS and choose DOS 6.22 & Generic
RTL8029AS from the configuration box.
- If the remote boot station has started Boot ROM booting, choose "Refresh"
from the view menu in the Remote Boot Manager.
- Select record that has appeared with the network adapter Node ID number
in place of the workstation name, choose "Convert Adapter" from the remote
boot menu. In the Wksta Name box, type a name for the workstation and
choose Add.
The client will boot up to DOS from the NT server.
*The message "The workstation program NETWKSTA.EXE could not not be loaded
into the High Memory Area." will appear after client is successfully boot
up to DOS. It is a known bug.
If it does not work, please check the above Remote Boot Configurations "Boot",
"Config" again. And don't forget to check DOSBB.CNF and PROTOCOL.INI files
in the C:\winnt\rpl\bblock\netbeui\PCIND directory.
Example: DOSBB.CNF
; DOS on Generic RTL8029AS PCI Ethernet
BASE D0H
RPL BBLOCK\RPLBOOT.SYS
LDR BBLOCK\RPLSTART.COM ~
DAT BBLOCK\NETBEUI\PCIND\PROTOCOL.INI
DRV BBLOCK\RPLDISK.SYS ~ ~ ~
EXE BBLOCK\RPLPRO1.COM ~ 2 ~
EXE BBLOCK\I13.COM ~ ~ ~
EXE BBLOCK\RPLBIND2.EXE ~ ~
EXE BBLOCK\PROTMAN.EXE ~ ~
EXE BBLOCK\RPLBIND1.EXE ~ ~
;DRV BBLOCK\IPXNDIS.DOS ~ ~ ~
;DRV BBLOCK\TCPDRV.DOS /I:C:\LANMAN.DOS ~ ~
EXE BBLOCK\NETBEUI\NETBEUI.EXE ~ 10 ~
DRV BBLOCK\NDIS\PCIND.DOS ~ ~ ~
DRV BBLOCK\PROTMAN.DOS /I:C:\LANMAN.DOS ~ M
Example: PROTOCOL.INI
[protman]
drivername = protman$
dynamic = yes
priority = netbeui
[netbeui_xif]
drivername = netbeui$
bindings = PCIND_nif
names = 6
ncbs = 12
packets = 20
pipeline = 10
sessions = 6
stacksize = 512
lanabase = 0
[xnsnb_xif]
drivername = xnsnb$
bindings = PCIND_nif
load = xnsnb[cbr]
lanabase = 1
[xnstp_xif]
drivername = xnstp$
bindings = PCIND_nif
load = xnstp[ub]
lanabase = 1
[tcpip_xif]
drivername = TCPIP$
disabledhcp = (TCPIP_NO_DHCP)
ipaddress0 = (TCPIP_ADDRESS)
subnetmask0 = (TCPIP_SUBMASK)
defaultgateway0 = (TCPIP_GATEWAY)
tcpsegmentsize = 1450
tcpwindowsize = 1450
nbsessions = 6
load = tcptsr[c],tinyrfc[c],emsbfr[cr]
unload = "unloadt /notsr[dc]"
bindings = PCIND_nif
lanabase = 1
[ipx_xif]
drivername = ipx$
load = ipxmark[u],ipx[u]
unload = ipxrel[c]
bindings = PCIND_nif
lanabase = 1
[msdlc_xif]
drivername = msdlc$
bindings = PCIND_nif
load = msdlc[ub]
unload = msdlc[u]
[PCIND_nif]
drivername = PCIND$ ; <-- This must be uppercase.
-------------------------------------------------------------------------------
Remote booting Windows 95 from Windows NT Server 4.0
====================================================
You must complete the above remote booting MS-DOS and then use the following
procedures to install Remote booting Windows 95 from Windows NT 4.0 server.
Installing Windows 95 for Windows Clients
-----------------------------------------
In order to support Windows 95 Remote Boot clients, you must install
Server-Based Setup (SBS) on the NT server. You will need a Windows 95
installation compact disc (not floppies) and a Windows 95 client computer.
Installing SBS for Windows 95 Clients
-------------------------------------
- On the NT server, create sbsfiles and machines directories and make them
shared. The shared name of sbsfiles is sbsfiles. The shared name of machines
is machines.
- From a regular Windows 95 client computer to log on the NT server, run
the NETSETUP.EXE from the WIN95 CD-ROM ADMIN\NETTOOLS\NETSETUP directory.
- Set path to \\%ntserver%\sbsfiles (%ntserver% is your NT server name.)
and click 'Install' button, choose 'Server' and provide the source path,
don't create default setup script and provide CD-KEY.
- At the NT server, under clients\rpl\update\win95 directory in the WINNT
server CD-ROM, type win95srv.bat \\%ntserver%\sbsfiles to update the Windows
95 files for Remote Booting, 6 files(msbatch.inf, netdi.dll, suwin.exe,
netdl.dll suwin.dll) will be copied to that directory.
It is no need to do set machines or copy any files to machines directory.
Copying drivers
---------------
You can in MS-DOS prompt under NT server, type :
copy a:\win95\rtl8029.sys c:\sbsfiles\system
copy a:\win95\e32nd3.inf c:\sbsfiles\system
copy a:\win95\e32nd3.inf c:\sbsfiles\inf
copy a:\ndis\dos\pcind.dos c:\sbsfiles
copy a:\ndis\dos\pcind.dos c:\sbsfiles\system
Installing the first Windows 95 Client
--------------------------------------
- Reboot the remote boot workstation's Boot ROM to MS-DOS 6.22 from the
NT server.
Type:
net use f: \\%ntserver%\sbsfiles
net use g: \\%ntserver%\machines
f:
f:\setup /t:g:\client1.tmp
- Starting to setup up Windows 95.
- USE ALL THE DEFAULT CHOICES.
- Select "Set up Windows from a network server".
- Select "Start Windows from the network".
- Provide machine directory g:\client1 for installing windows 95.
- Select "Custom" setup and select "No, I want to modify the hardware list."
to avoid win95 searching for too many devices.
- Deselect CD-ROM drive, network adapter, PCMCIA socket, SCSI controller,
sound MIDI or video capture card. Seaching too many devices often caused
the system hang.
- Don't choose communication in the Select Component dialog box.
- In the Network configure dialog box, choose add adapter and select
"Have Disk". Set path to f:\system and select E32ND3.INF file.
System will find "32-Bit IO Mode PCI Ethernet Adapter".
Then, add Microsoft TCP/IP or others you need.
Enter the full pathname F:\SYSTEM of the E32ND3.INF file, then click OK
button from "Copying Files..." dialog box.
Enter the full pathname F:\ of the ASPI2HLP.SYS file, then click OK
button from "Windows 95 Setup" dialog box.
- Complete Windows 95 setup and turn off workstation.
Creating Remote Boot Configurations for the Windows 95 Client
-------------------------------------------------------------
- In MS-DOS prompt under NT server, run RPLCMD.EXE to add 'Boot',
'Config'. Note: You can delete the preexisting boot record
by typing b then d and provide the boot name and vendor name.
Example: Use RPLCMD utility to add a Boot Block for the new adapter.
C:\WINNT\RPL>RPLCMD
Adapter Boot Config Profile Service Vendor Wksta [Quit]: b
Add Del Enum: a
BootName=W95-RTL8029
VendorName=0050BF <-- Adapter Vendor Node ID
BbcFile=BBLOCK\NETBEUI\PCIND\W95BB.CNF
All other parameters are optional
BootComment=Generic RTL8029
WindowsSize=0
Adapter Boot Config Profile Service Vendor Wksta [Quit]: c
Add Del Enum: a
ConfigName=W95-RTL8029AS
BootName=W95-RTL8029
DirName=DOS
DirName2=WIN95
FitShared=fits\win95.fit
FitPersonal=fits\win95p.fit
All other parameters are optional
ConfigComment=WIN95 & Generic RTL8029AS
DirName3=
DirName4=
Press Q to Quit
- Go to Remote Boot Manager to add New Profile "WIN95-RTL8029AS", in the
configuration box choose "WIN95 & Generic RTL8029AS".
- Check if config.sys and autoexec.bat exist in the C:\machines\client1\suboot
directory. If not, please create them. The contents are described below.
Please add a line "net use g: \\%ntserver%\machines" in the WIN.BAT file.
Config.sys:
DEVICE=HIMEM.SYS
device=c:\ramdrive.sys 1440 /E
STACKS=16,512
Autoexec.bat:
@if not exist d:\winboot\nul mkdir d:\winboot
@copy c:\ d:\winboot
d:
cd \winboot
WIN.BAT
set comspec=d:\winboot\command.com
nwrpltrm
fixmem
snapshot /S /B:d
setmdir /m /r:d:\winboot
net start
net logon /savepw:no /y
net use F: \\%ntserver%\sbsfiles
net use g: \\%ntserver%\machines <-- Add this line
PATH=F:\;F:\COMMAND
setmdir
win.com
- Copy PCIND.DOS and PROTOCOL.INI into C:\machines\client1\suboot directory.
You can in MS-DOS prompt under NT server, type :
cd \machines\client1\suboot
copy a:\bootrom\suboot\protocol.ini
copy a:\ndis\dos\pcind.dos
- Now, you can find the following files in the C:\machines\client1\suboot.
* AUTOEXEC.BAT --- if system lost it, please copy from a:\bootrom\suboot
* CONFIG.SYS --- if system lost it, please copy from a:\bootrom\suboot
* MSDOS.SYS ---
* PROTOCOL.INI --- copied from a:\bootrom\suboot
* PCIND.DOS --- copied from a:\ndis\dos
* SYSTEM.DAT
* WIN.BAT
- Modify the mini registry file SYSTEM.DAT by using REGEDIT.EXE.
Note: REGEDIT must be run from the DOS command prompt. It will not work
as intended if you load it from a DOS session under Windows.
The easiest way to do this is to remoteboot from your first Windows 95
client, and, when the message "Starting Windows 95" appears, press the F8
function key. When the boot menu appears, select the Step-by-step
Confirmation option, answer Yes to each line except WIN.COM. When prompted
to start WIN.COM answer No. This will drop you to the DOS command prompt.
. Export system.dat miniregistry file as follows:
regedit /L:system.dat /E registry.txt
. Edit REGISTRY.TXT by searching and replacing all occurences of the new
PCI machine environment and driver name.
Example:
old register.txt new register.txt
"transport"="*netbeui,*nwlink,"-->"transport"="*netbeui,*nwlink,ndishlp.sys"
"netcard"=" " --> "netcard"="pcind.dos"
. After modifying REGISTRY.TXT you must update SYSTEM.DAT by importing
the new information.
regedit /L:system.dat /C registry.txt
. Remove the hidden, system, and read only attributes from SYSTEM.DAT by
entering:
attrib -r -s -h system.dat
. Copy new system.dat to c:\machines\client1\suboot directory.
- Go to C:\winnt\rpl\bin directory on the NT server, type
win95clt c:\machines\client1 \\%ntserver% win95-rtl8029as
Seven files including autoexec.bat and config.sys will be copied from
C:\machines\client1\suboot into C:\winnt\rpl\rplfiles\win95-rtl8029as.
- Use EDIT editor to modify the MACHINES.INI file in the sbsfiles directory.
Add the following lines in the MACHINES.INF file.
[0050BFXXXXXX]
SYSDATPATH=g:\client1
g=\\%ntserver%\machines
- Reboot the remote boot workstation's Boot ROM.
- In the Remote Boot Manager on the server, choose "Refresh" from the view
menu. Select record that has appeared with the network adapter Node ID
number in place of the workstation name, choose "Convert Adapter" from the
remote boot menu. In the Wksta Name box, type a name for the workstation
and choose Add and select WIN95-RTL8029AS profile.
The client will now boot into Windows 95 and complete the Windows 95 Setup
program.
Note:
- Don't plug in the hard disk during the whole process.
- If WIN.BAT excutes "net logon /savepw:no /y" and shows error message
'Error loading device driver NE2000.DOS.'
It means that "netcard"="ne2000.dos" in your SYSTEM.DAT file.
You must use REGEDIT to modify SYSTEM.DAT, or just rename PCIND.DOS
to NE2000.DOS in the C:\winnt\rpl\rplfiles\win95-rtl8029as directory.
- During the first time startup of Windows 95, error messages shown below
will appear, please skip it.
*System Error
'Windows cannot read from drive A:
If this is a network drive, make sure the network is working. If it is
a local drive, check the disk.'
Click Cancel button.
- The message 'Error loading Explorer.exe. You must reinstall Windows.'
appear, please install Windows again.
- If it does not work, please check the above Remote Boot Configurations
"Boot", "Config" again. And don't forget to check W95BB.CNF files in the
C:\winnt\rpl\bblock\netbeui\PCIND directory.
Example: W95BB.CNF
; Windows 95 on Generic RTL8029AS PCI Ethernet
BASE D0H
RPL BBLOCK\RPLBOOT.SYS
LDR BBLOCK\RPLSTART.COM ~
DAT BBLOCK\NETBEUI\PCIND\PROTOCOL.INI
DRV BBLOCK\RPLDISK.SYS ~ ~ ~
EXE BBLOCK\RPLPRO1.COM ~ 2 ~
EXE BBLOCK\RPLBIND2.EXE ~ ~
EXE BBLOCK\PROTMAN.EXE ~ ~
EXE BBLOCK\RPLBIND1.EXE ~ ~
;DRV BBLOCK\IPXNDIS.DOS ~ ~ ~
;DRV BBLOCK\TCPDRV.DOS /I:C:\LANMAN.DOS ~ ~
EXE BBLOCK\NETBEUI\NETBEUI.EXE ~ 10 ~
DRV BBLOCK\NDIS\PCIND.DOS ~ ~ ~
DRV BBLOCK\PROTMAN.DOS /I:C:\LANMAN.DOS ~ M
EXE BBLOCK\W95I13.COM ~ ~ ~
----
All trademarks or brand names mentioned are properties
of their respective companies.
Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.