[+******************************************************************+]
[ ]
[ 8139 PCI Fast Ethernet Adapter ]
[ RPL BootROM Code Installation Guide ]
[ ]
[====================================================================]
[ ]
[ Model Name : 8139 ]
[ ]
[ Driver Name : RPLBOOT.ROM ]
[ ]
[ Platform : NT Server ]
[ ]
[ User Guide Version : v1.1 ]
[ ]
[-******************************************************************-]
The 8139 RPL BootROM can remoteboot to MS-DOS from Microsoft
Windows NT 3.5 Server or above, and remoteboot to Windows 95
from Microsoft Windows NT 4.0 Server.
**************
* NOTICE !!! *
**************
The Remote Boot NT Server CANNOT use Microsoft Windows NT
Workstation version.
Topics :
========
A. Generate a RPL BootROM from the RPlBOOT.ROM Code
B. MS-DOS Remote Boot to NT Server Installation
B-1. DOSBB.CNF Sample File for 8139
B-2. PROTOCOL.INI Sample File for 8139
C. Windows 95 Remote Boot to NT Server Installation (ONLY for NT 4.0)
C-1. W95BB.CNF Sample File for 8139
C-2. CONFIG.SYS Sample File for 8139
C-3. AUTOEXEC.BAT Sample File for 8139
C-4. MACHINES.INI Sample File for 8139
A. Generate RPL Boot ROM from RPLBOOT.ROM Code :
==============================================
**********************************************************************
* Hardware Requiremment: *
* *
* 1. A EPROM Programming Machine *
* 2. A M27C512 EPROM (or others model EPROM) *
* 3. The 8139 RPL BootROM Code (RPLBOOT.ROM) *
**********************************************************************
1. Use the EPROM Programming Machine to write RPLBOOT.ROM code
to the M27C512 EPROM.
2. Please refer to the EPROM Programming Machine Operating Guide
for details.
B. MS-DOS Remote Boot to NT Server Installation :
=================================================
**********************************************************************
* Hardware Requiremment: *
* *
* 1. A Windows NT 4.0 Server with the RemotBoot Service *
* 2. A Remote Boot Workstation with 8139 PCI Adapter *
* 3. A 8139 PCI Fast Ethernet Adapter with RPL BootROM *
**********************************************************************
1. The network adapter of the Remote Boot NT Server must be
working properly.
2. At the NT Server, select "My Computer" -> "Control Panel"
-> "Network", select "Protocols" to add "DLC Protocol",
select "Services" to add "RemoteBoot Service", then reboot
the NT Server to take effect the new configuration.
3. At the NT Server, select "My Computer" -> "Control Panel"
-> "Services", select "RemoteBoot Service", then click "Start"
button to startup the Remote Boot Service.
4. Please check the \WINNT\RPL\RPLFILES directory has been shared
as "RPLFILES" for "Everyone" with "Full Control" Permission.
5. Follow the following step to create the New Profile Configuration
for MS-DOS Remote Boot.
(1) Go to MSDOS prompt, Copy DOS files to the NT Server.
(IMPORTANT !! The IO.SYS and MSDOS.SYS files in the
C:\WINNT\RPL\RPLFILES\BINFILES\DOSxxx subdirectory MUST
remove the "Read Only", "Hidden" and "System" attributes.)
COPY A:\DOS\*.* C:\WINNT\RPL\RPLFILES\BINFILES\DOSxxx (xxx: DOS VERSION)
ATTRIB -R -S -H IO.SYS
ATTRIB -R -S -H MSDOS.SYS
(2) Copy 8139 NDIS2 Driver (SILANND.DOS) offered by us along with the RPLBOOT.ROM.
A:\BOOTROM to C:\WINNT\RPL\BBLOCK\NDIS directory.
COPY A:\BOOTROM\SILANND.DOS C:\WINNT\RPL\BBLOCK\NDIS
(3) Create C:\WINNT\RPL\BBLOCK\NETBEUI\8139 subdirectory, and
copy DOSBB.CNF and PROTOCOL.INI files from Driver Diskette
A:\BOOTROM\NTSRV to C:\WINNT\RPL\BBLOCK\NETBEUI\8139 directory.
COPY A:\BOOTROM\NTSRV\DOSBB.CNF C:\WINNT\RPL\BBLOCK\NETBEUI\8139
COPY A:\BOOTROM\NTSRV\PROTOCOL.INI C:\WINNT\RPL\BBLOCK\NETBEUI\8139
(4) Run RPLCMD.EXE command to add the New Boot Name, the New
Configuration Name and the New Vendor Name for the New Adapter
Profile.
C:\WINNT\RPL> RPLCMD
Adapter Boot Config Profile Service Vendor Wksta [Quit]: v
Add Del Enum: a
VendorName=00E020 <== Change to your Node Address
VendorComment=Rsltek.
Adapter Boot Config Profile Service Vendor Wksta [Quit]: b
Add Del Enum: a
BootName=8139DOSB
VendorName=00E020 <== Change to your Node Address
BbcFile=BBLOCK\NETBEUI\8139\DOSBB.CNF
All other parameters are optional
BootComment=8139 for DOS 6.22
WindowsSize=0
Adapter Boot Config Profile Service Vendor Wksta [Quit]: c
Add Del Enum: a
ConfigName=8139DOSC
BootName=8139CDOSB
DirName=DOS
DirName2=DOS622
FitShared=fits\dos622.fit
FitPersonal=fits\dos622p.fit
All other parameters are optional
ConfigComment=DOS 6.22 for 8139
DirName3=
DirName4=
Adapter Boot Config Profile Service Vendor Wksta [Quit]: q
(5) At the NT Server, select "Start" -> "Programs" -> "Administrative
Tools (Common)" -> "Remoteboot Manager", select "Check Configurations"
from "Configure" item of the "Remoteboot Manager - Local Machine"
dialog box to take effect new configurations.
(6) Select "New Profile" from "Remoteboot" item of the "Remoteboot
Manager - Local Machine" dialog box , select "DOS 6.22 for 8139
" from "Configuration" field, then specify the New Profile
Name to "Profile Name" field, click "OK" button to create new profile.
6. After create the New Profile Name, plug the 8139 adapter with
the 8139 RPL BootROM into the Remote Boot Workstation PCI slot.
7. Startup the Remote Boot Workstation, the RPL BootROM will try to
remoteboot MS-DOS from the Remote Boot NT server.
8. At the NT Server, select "Start" -> "Programs" -> "Administrative
Tools (Common)" -> "Remoteboot Manager", select "Refresh" from
"View" item, the Remote Boot Client MAC Address will display into
the "Remoteboot Manager - Local Machine" dialog box, select the
MAC Address and select "Convert Adapters" from "Remoteboot" item
select "DOS 6.22 for 8139" from "Wksta In Profile" item
then specify the New Workstation Name, click "Add" button.
9. Now the Remote Boot Workstation will remoteboot to MS-DOS prompt
from the Remote Boot NT Server by using 8139 RPL BootROM, and
specify Username and Password to logon the Remote Boot NT Server.
B-1. DOSBB.CNF Sample File for 8139:
=======================================
; DOS on 8139 PCI Fast Ethernet Adapter
; (NOTICE !!! Execute the command from the Last Line to the First Line)
BASE D0H
RPL BBLOCK\RPLBOOT.SYS
LDR BBLOCK\RPLSTART.COM ~
DAT BBLOCK\NETBEUI\8139\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\silannd.DOS ~ ~ ~
DRV BBLOCK\PROTMAN.DOS /I:C:\LANMAN.DOS ~ M
B-2. PROTOCOL.INI Sample File for 8139:
==========================================
[protman]
drivername = protman$
dynamic = yes
priority = netbeui
[netbeui_xif]
drivername = netbeui$
bindings = 8139_nif
names = 6
ncbs = 12
packets = 20
pipeline = 10
sessions = 6
stacksize = 512
lanabase = 0
[xnsnb_xif]
drivername = xnsnb$
bindings = 8139_nif
load = xnsnb[cbr]
lanabase = 1
[xnstp_xif]
drivername = xnstp$
bindings = 8139_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 = 8139_nif
lanabase = 1
[ipx_xif]
drivername = ipx$
load = ipxmark[u],ipx[u]
unload = ipxrel[c]
bindings = 8139_nif
lanabase = 1
[msdlc_xif]
drivername = msdlc$
bindings = 8139_nif
load = msdlc[ub]
unload = msdlc[u]
[8139_nif]
drivername = SILANND$ <== MUST be "SILANND$", char sensitive
C. Windows 95 Remote Boot to NT Server Installation (ONLY for NT 4.0) :
=======================================================================
(NOTICE !!! You MUST first install the MS-DOS remote boot client for NT
Server before install the Windows 95 Remote Boot Client for NT Server)
************************************************************************
* Hardware Requiremment: *
* *
* 1. A Windows NT 4.0 Server with RemotBoot Service with CD-ROM drive *
* 2. A Workstation running Windows 95 with CD-ROM drive *
* 3. Microsoft Windows NT Server 4.0 Resource Kit *
* 4. Microsoft Windows 95 Resource Kit with NETSETUP.EXE Utility *
* 5. A Remote Boot Workstation with floppy drive *
* 6. A 8139 PCI Fast Ethernet Adapter with RPL BootROM *
************************************************************************
Installation Guide Topics:
1. Install Server-Based Setup (SBS) on NT Server
2. Install the Windows 95 Remote Boot Client for NT Server
1. Install Server-Based Setup (SBS) on NT Server
(1) Startup Windows NT 4.0 Remote Boot Server.
(2) At the NT Server, create \WIN95SRV directory for SBS Server,
and share \WIN95SRV as "WIN95SRV" for "RPLUSER" and
"Administrators" users with "Full Control" permission.
(3) At the NT Server, select "Start" -> "Programs" ->
"Administrative Tools (Common)" -> "User Manager for Domains",
select "New User" from "User" item of the "User Manager -
DOMAIN" dialog box, specify Username and Password for Windows 95
workstation, click "Groups" button -> select "Administrators"
-> click "Add" button -> click "OK" button to add
Administrators Permission, click "Add" button to completely
create new user, click "Close" button to quit new user dialog
box.
(4) Startup Windows 95 Workstation with CD-ROM drive, enter
Username and Password to logon NT Server.
(P.S.: This user MUST be "Administrators" user.)
(5) Insert Microsoft Windows 95 Resource Kit into Windows 95
CD-ROM drive.
(6) In Windows 95 Explorer, switch to the ADMIN\NETTOOLS\NETSETUP
directory of CD-ROM drive, double-click NETSETUP.EXE.
(7) In the Server-Based Setup dailog box, click "Set Path" button,
and specify the path to SBS Server (\\NTSERVER\WIN95SRV),
then click "OK" button.
(8) Click "Install" button, choose "Server" option from "Install
Policy" dialog box, check the Source Directory and Destination
Directory, click "OK" button.
(9) Click "Don't Create Default" button from "Create Default"
dialog box.
(10) Enter Windows 95 CD Key Number to "CD Key" dialog box, click
"OK" button to install the SBS files to NT Server.
(11) After completely install the SBS files to NT Server,
insert Microsoft Windows NT Server 4.0 Resource Kit into
Windows NT Server CD-ROM drive.
(12) At the NT Server, go to MSDOS prompt, change the directory
to the \CLIENTS\RPL\UPDATE\WIN95 directory of CD-ROM drive,
and run the following command to update the Windows 95
SBS files for Remote Booting.
D:\CLIENTS\RPL\UPDATE\WIN95> WIN95SRV.BAT C:\WIN95SRV
2. Install the Windows 95 Remote Boot Client for NT Server
(1) At the NT Server, create \WINNT\RPL\CLIENTS directory for
Windows 95 Remote Boot Clients and share \WINNT\RPL\CLIENTS
as "CLIENTS" for "RPLUSER" and "Administrators" users with
"Full Control" permission.
(2) At the NT Server, follow the following step to create
the New Profile Configuration for Windows 95 Remote Boot.
a) Copy the 8139 NDIS2/3 driver (SILANND.DOS and SL95.SYS)
from Driver Diskette A:\BOOTROM to C:\WIN95SRV directory.
COPY A:\BOOTROM\SILANND.DOS C:\WIN95SRV
COPY A:\BOOTROM\SL95.SYS C:\WIN95SRV\SYSTEM
b) Copy W95BB.CNF file from Driver Diskette A:\BOOTROM\NTSRV
to C:\WINNT\RPL\BBLOCK\NETBEUI\8139 directory.
COPY A:\BOOTROM\NTSRV\W95BB.CNF C:\WINNT\RPL\BBLOCK\NETBEUI\8139
c) Run RPLCMD.EXE command to add the New Boot Name, the New
Configuration Name and the New Vendor Name for the New Adapter
Profile.
C:\WINNT\RPL> RPLCMD
Adapter Boot Config Profile Service Vendor Wksta [Quit]: b
Add Del Enum: a
BootName=8139W95B
VendorName=00E020 <== Change to your Node Address
BbcFile=BBLOCK\NETBEUI\8139\W95BB.CNF
All other parameters are optional
BootComment=8139 for Windows 95
WindowsSize=0
Adapter Boot Config Profile Service Vendor Wksta [Quit]: c
Add Del Enum: a
ConfigName=8139W95C
BootName=8139W95B
DirName=DOS
DirName2=WIN95
FitShared=fits\win95.fit
FitPersonal=fits\win95p.fit
All other parameters are optional
ConfigComment=Windows 95 for 8139
DirName3=
DirName4=
d) At the NT Server, select "Start" -> "Programs" ->
"Administrative Tools (Common)" -> "Remoteboot Manager", select
"Check Configurations" from "Configure" item of the "Remoteboot
Manager - Local Machine" dialog box to take effect new
configurations.
e) Select "New Profile" from "Remoteboot" item of the "Remoteboot
Manager - Local Machine" dialog box, select "Windows 95 for
8139" from "Configuration" field, then specify
the New Profile Name to "Profile Name" field, click "OK" button
to create new profile.
(3) Plug 8139 PCI Fast Ethernet adapter with RPL BootROM into
the Remote Boot Workstation.
<<< NOTICE !! >>>
Please make sure the Remote Boot Workstation WITH the floppy
drive (Drive A:) but WITHOUT the hard disk drive.
(4) Startup the Remote Boot Workstation, the RPL BootROM will
try to remoteboot MS-DOS from NT server.
(5) At the NT Server, select "Start" -> "Programs" -> "Administrative
Tools (Common)" -> "Remoteboot Manager", select "Refresh" from
"View" item, the Remote Boot Client MAC Address will display
into the "Remoteboot Manager - Local Machine" dialog box, select
the MAC Address and select "Convert Adapters" from "Remoteboot"
item select "DOS 6.22 for 8139" from "Wksta In Profile"
item then specify the New Workstation Name, click "Add" button.
(6) At the NT Server, select "Start" -> "Programs" ->
"Administrative Tools (Common)" -> "User Manager for Domains",
double-click the New Remote Boot Username from the "User Manager
- DOMAIN" dialog box, click "Groups" button -> select
"Administrators" -> click "Add" button -> click "OK" button
-> click "OK" button to add Administrators Permission for
the Remote Boot Workstation.
(7) At the Remote Boot Workstation, specify Username and Password
to logon the NT Server.
(P.S.: This user MUST be "Administrators" user.)
(8) At the Remote Boot Workstation, run the following to map drives
to \\NTSERVER\WIN95SRV and \\NTSERVER\CLIENTS shared directories.
C:\> NET USE F: \\NTSERVER\WIN95SRV
C:\> NET USE G: \\NTSERVER\CLIENTS
(9) Change the drive to F: and run the following command to install
the First Windows 95 Remot Boot Client.
C:\> F:
F:\> setup /t:g:\client1.tmp
(10) Make the following decisions during setup :
a) In the Server-Based Setup dialog box, choose "Set up
Windows to run from a network server".
b) In the Startup Method dialog box, choose "Start Windows
from the network (remote boot server)".
c) In the Machine Directory dialog box, enter "G:\CLIENT1"
into the Machine Directory field.
d) In the Setup Options dialog box, choose "Custom" Setup.
e) In the User Information dialog box, specify the User Name
and Company Name informations.
f) In the Analyzing Your Computer dialog box, choose
"No, I want to modify the hardware list", exclude as many
hardware types and items from auto-detection as possible.
(Try to exclude all items except Display and Keyboard items)
g) In the Select Components dialog box, remove "Communications"
component.
h) In the Network Configuration dialog box, click "Add" button
-> select "Adapter" -> click "Add" button -> click "Have Disk"
button -> insert 8139 driver diskette into floppy and type
"A:\BOOTROM" for driver path to install Windows 95 NDIS3 driver
for remoteboot Windows 95 client.
i) In the Network Configuration dialog box, select "Client for
Microsoft Networks", click "Properties" button, choose
"Quick logon" from "Network logon options" field and click
"OK" button.
j) In the Network Configuration dialog box, select "Windows Logon"
from "Primary Network Logon" field.
k) In the Identification dialog box, specify the Computer
Name and Workgroup Name and make sure the Workgroup Name
is the same as the Domain Name of the Remote Boot NT server.
l) In the Computer Settings dialog box, check the all hardware
devices information are correct, click "Next" button to
continue the installation.
m) Following the screen prompt to complete Windows 95 client
pre-installation.
(11) At the NT Server, select "Start" -> "Programs" ->
"Administrative Tools (Common)" -> "Remoteboot Manager",
DELETE the Workstation Name of the Remote Boot Workstation
from the "Remoteboot Manager - Local Machine" dialog box.
(12) At the NT Server, you must MANUALLY edit the following files
in the \WINNT\RPL\CLIENTS\CLIENT1\SUBOOT directory.
All files are in ASCII format and can be edited using any
Text Editor such as EDIT.COM.
AUTOEXEC.BAT --- if system lost it , Rsltek provided it. \suboot directory
CONFIG.SYS --- if system lost it , Rsltek provided it. \suboot directory
MSDOS.SYS ---
PROTOCOL.INI --- \suboot directory
SILANND.DOS --- \BOOTROM directory
SYSTEM.DAT
(13) To edit the mini registry file SYSTEM.DAT use REGEDIT.EXE to export
its contents to text file, edit the text file, then import the text
file back into SYSTEM.DAT. See the example below.
regedit /L:system.dat /E registry.txt
edit registry.txt
regedit /L:system.dat /C registry.txt
(14) Please note that 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 95. 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.
(15) Export system.dat miniregistry file as follows:
regedit /L:system.dat /E registry.txt
(16) Edit REGISTRY.TXT by searching and replacing all occurences of the
new PCI machine environment and driver name .
For example:
old register.txt new register,txt
"transport"="*netbeui,*nwlink," --> "transport"="*netbeui,*nwlink,ndishlp.sys"
"netcard"=" " --> "netcard"="silannd.dos"
(17) After modifying REGISTRY.TXT you must update SYSTEM.DAT by importing
the new information.
regedit /L:system.dat /C registry.txt
(18) Remove the hidden, system, and read only attributes from SYSTEM.DAT
by entering:
attrib -r -s -h system.dat
(19) copy new system.dat to \WINNT\RPL\CLIENTS\CLIENT1\SUBOOT directory.
(20) At the NT Server, go to MSDOS prompt, change the directory
to the \WINNT\RPL\BIN directory and run the following command
to copy some remoteboot files from CLIENT1\SUBOOT directory
to PROFILES\8139W95C\SUBOOT directory.
WIN95CLT.BAT \WINNT\RPL\CLIENTS\CLIENT1 \\NTSERVER 8139W95C
<<< NOTICE !! >>>
Here, please make sure the 8139 NDIS2 driver (SILANND.DOS)
has been copied into the \WIN95SRV, \WINNT\RPL\BBLOCK\NDIS,
\WINNT\RPL\RPLFILES\PROFILES\8139W95C\SUBOOT, \WINNT\RPL\CLIENTS
\CLIENT1\SUBOOT directories and the 8139 NDIS3 driver
(SL95.SYS) has been copied into the \WIN95SRV\SYSTEM directory.
(21) At the NT Server, change the directory to the \WIN95SRV
directory to edit the MACHINES.INI file and add the following
lines for the new clients.
[00E020102125] <== Must match with your node address
SYSDATPATH=G:\CLIENT1
G=\\NTSERVER\CLIENTS
(22) Restart the Remote Boot Workstation, the RPL BootROM will
try to remoteboot Windows 95 from NT server to continue
the Windows 95 client installation.
(23) At the NT Server, select "Start" -> "Programs" -> "Administrative
Tools (Common)" -> "Remoteboot Manager", select "Refresh" from
"View" item, the Remote Boot Client MAC Address will display
into the "Remoteboot Manager - Local Machine" dialog box, select
the MAC Address and select "Convert Adapters" from "Remoteboot"
item select "Windows 95 for 8139" from "Wksta In Profile"
item then specify the New Workstation Name, click "Add" button.
(24) At the NT Server, select "Start" -> "Programs" -> "Administrative
Tools (Common)" -> "User Manager for Domains", double-click
the New Remote Boot Username from the "User Manager - DOMAIN"
dialog box, click "Groups" button -> select "Administrators"
-> click "Add" button -> click "OK" button -> click "OK" button
to add Administrators Permission for the Remote Boot Workstation.
(25) At the Remote Boot Workstation, specify Username and Password
to logon the NT Server, the client will now boot to
Windows 95 and continue to setup Windows 95 configuration,
sometimes it will occur some errors and prompt you to
reboot your system, just do it, and after startup Windows 95
again, Windows 95 setup will prompt you to specify the Time Zone
information and configure printer device, then prompt you
Windows 95 setup program finished and restart your computer
to complete the Windows 95 client installation.
C-1. W95BB.CNF Sample File for 8139:
=======================================
; Windows 95 on 8139 Fast Ethernet Adapter
BASE D0H
RPL BBLOCK\RPLBOOT.SYS
LDR BBLOCK\RPLSTART.COM ~
DAT BBLOCK\NETBEUI\8139\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\SILANND.DOS ~ ~ ~
DRV BBLOCK\PROTMAN.DOS /I:C:\LANMAN.DOS ~ M
EXE BBLOCK\W95I13.COM ~ ~ ~
C-2. CONFIG.SYS Sample File for 8139 :
========================================
DEVICE=HIMEM.SYS
device=c:\ramdrive.sys 1440 /E
STACKS=16,512
C-3. AUTOEXEC.BAT Sample File for 8139 :
==========================================
@if not exist d:\winboot\nul mkdir d:\winboot
@copy c:\ d:\winboot
d:
cd \winboot
C-4. MACHINES.INI Sample File for 8139 :
==========================================
;Windows 95 MACHINES.INI
;[node address]
;SYSDATPATH=x:\<home directory>
;x=\\server\share
[00E020102125] <== Must match with your node address
SYSDATPATH=g:\client1
g:=\\NTSERVER\clients
<<< End of file >>>
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.