How to install the PCI adapter Boot Rom for Windows 95.
1. What you will need?
* A Windows NT 4.0 server with the Remoteboot Service installed and
configured. Earlier versions of NT do not support Windows 95 clients.
* A workstation running Windows 95 with connections to the NT server.
This workstation should have a CD-ROM drive. If not, the NT server
must have a CD-ROM drive installed and configured for sharing.
* Windows 95 on CD-ROM. Make sure the CD-ROM contains the NETSETUP.EXE
program. You must purchase the correct licensed copy of Windows 95 for
network installation.
* An Ethernet network adapter with boot PROM. You must be able to remoteboot
from the NT server with this boot PROM.
2. Installing the "Remoteboot Service" on the NT Server.
a. Choose the Control Panel under the NT Server, and then select the
network options.
b. Add the DLC and NetBEUI protocol in the protocols, and you also
need add the Remoteboot service in the services.
c. During the installation, you need to put the NTAS CD disk into the
CD-ROM.
3. Sharing the directory \RPLFILES in the NT Server.
Sharing the directory \WINNT\RPL\RPLFILES by using File Manger sharing.
4. Copy all the MS-DOS 6.22 ver files to \WINNT\RPL\RPLFILES\BINFILES\DOS622
For example:
a. Make the DOS 6.22 Boot floppy disk.
b. attrib -s -h a:\io.sys in the boot disk.
c. attrib -s -h a:\msdos.sys in the boot disk.
d. copy a:\io.sys \WINNT\RPL\RPLFILES\BINFILES\DOS622
e. copy a:\msdos.sys \WINNT\RPL\RPLFILES\BINFILES\DOS622
5. Creating DOS Remoteboot configuration for new adapter
a. Copy the NDIS2(FEAND.DOS) for the Adapter to the
"\WINNT\RPL\BBLOCK\NDIS" directory.
b. Create this directory \WINNT\RPL\BBLOCK\NETBEUI\FEAND and
then copy the W95BB.CNF, FEAND.CNF and PROTOCOL.INI files to the
directory.
c. In MS-DOS Prompt type " NET START RemoteBoot ".
d. Use RPLCMD utility to add a bblock record for new adapter.
e. Screen will display under line option and you following these do it.
Adapter Boot Config Profile Service Vendor Wksta [Quite] V
Add Del Enum:A
VendorName=004095 <Ether ID>
VendorComment=FEAND
Adapter Boot Config Profile Service Vendor Wksta [Quite] B
Add Del Enum:A
BootName=DOSMX
VendorName=004095
BbcFile=BBLOCK\NETBEUI\FEAND\FEAND.CNF
BootCommet=PCI Adapter <Name of this adapter>
WindowsSize=0
Adapter Boot Config Profile Service Vendor Wksta [Quite] C
Add Del Enum:A
ConfigName=DOS622MX
BootName=DOSMX
DirName=DOS
DirName2=DOS622
FitShared=FITS\DOS622.FIT
FitPersonal=FITS\DOS622P.FIT
ConfigComment=DOS 6.22 for FEAND PCI Adaper <Name of the Config>
DirName3=
DirName4=
Adapter Boot Config Profile Service Vendor Wksta [Quite] Q
f. Shutdown Windows NT server, and reboot it.
6. Login Administrator to NTAS server.
7. Starting Remoteboot service and Remoteboot Manager
a. In MS-DOS Prompt type "NET START Remoteboot"
b. In Network administrator, select Remoteboot Manager
1.Choose Remoteboot, New Profile, created a FEAND Profile Name
2.Add new workstation for FEAND Adapter and choose FEAND Profile
file.
* Above will run on CLIENT. *
c. Use Administrator enter WinNT
d. Choose start --> Programs --> Administrative Tool --> Remote Manager
e. Use Remoteboot item --> Covert Adapters
Installing Windows 95 for Windows 95 Clients
1. What you will need?
* Install Server-Based Setup (SBS) on a Window NT 4.0 server
* Install the first Windows 95 client
* Install subsequent clients
2. Installing SBS for Windows 95 Clients
a. On the Windows NT 4.0 server, create a shared directory (sbs) with
90 MB space available, assign read-ponly for regular user and full
access for administrator.
b. Put the Windows 95 compact disc in the client's CD-ROM drive. In Windows
Explorer, switch to the ADMIN\NETTOOLS\NETSETUP directory.
c. Double-click NETSETUP.EXE.
Note that you must run NETSETUP.EXE at a Windows 95 client. It will
encounter errors on a computer running Windows NT.
d. In the Server-Based Setup dialog box, click the Set Path button, and
then specify the path to the SBS server. Then click OK.
You can type a drive letter for a mapped drive, a network name for a
server the format is: \\server1\sharedir,
for example:
\\ntserver\sbs
e. Click Install. Server-Based Setup presents a series of dialog boxes so
that you can complete these actions:
* Specify an "install policy" for how users can install Windows 95 from
the server. If you support only remoteboot clients, choose the
"Server" option. If you support other SBS functions as well, choose
"User's choice." Do not choose "Local hard drive."
* Set the source path for Windows 95 files. This is the path to the
compact disc on the client.
* If asked, specify that you do NT remoteboot installation require
special settings. not want to create a default setup script. Setup
scripts for Windows
* Provide a CD Key number for product identification. Server-Based Setup
copies Windows 95 files to the SBS shared directory.
f. At the remoteboot server, put the compact disc or floppy disk
containing the Windows NT remoteboot for Windows 95 files into a drive.
Change to the drive and then change to the UPDATE\WIN95 or
CLIENTS\RPL\UPDATE\WIN95 directory.
g. Run win95srv.bat to update the Windows 95 files for remotebooting.
For example:
cd\clients\rpl\update\win95
win95srv.bat \\ntserver\sbs
h. At the remoteboot server, start Remoteboot Manager. From the Configure
menu, choose Check Configurations to activate the new configurations.
3. Installing the First Windows 95 Client
. Overview
Installing the first Windows 95 client requires booting that client
first to MS-DOS 6.2x, running Windows 95 Setup on the client, and then
copying selected files from the client's machine directory to the
remoteboot server. Once you have installed this first client, you can
easily install subsequent clients by using SBS to make a modified copy
of the original machine directory without having to run Windows 95 Setup
again. Your first Windows 95 clients must be using an ethernet network
adapter. Furthermore, the first client computer must have one or more
PCI slots for later use with the PCI network adapter.
Each remoteboot client has a "machine directory," a directory on a
server that contains client-specific configuration information and data.
For example, the machine directory contains the following:
* Appropriate initialization and configuration files (including
WIN.INI and SYSTEM.INI) SYSTEM.DAT and USER.DAT (the Registry)
* Files that define the Desktop, Start menu directories, and other
programs
* The spool directory for printing
* The swap file and TEMP directory
. Create "machine0" directory on the windows NT server.
. Boot the new client to MS-DOS 6.22.
. Use the "net use" command to map drive letters to the SBS server and
machine0 directory location, it will run on CLIENT.
For example:
net use f: \\ntserver\sbs
net use g: \\ntserver\machine0
. Change to the drive letter mapped to the SBS directory.
. Run the Windows 95 Setup program by typing
setup /t:temppath
where /t: is required and temppath is a path to a directory in which to
store temporary files during installation. For example, if G: is mapped
to the shared directory containing the client's machine directory, you
could type
f:
setup /t:g:\client.tmp /im /is
to store temporary files on that server.
* Do not delete the t:\temppath directory until you have completed
steps.
* If you are installing two Windows 95 clients simultaneously (for
example, to support clients with different network adapters), choose
separate temporary directories for each client.
. Make the following decisions during setup:
* In the Server-based Setup dialog box, choose "Set up Windows to run
from a network server" if asked.
* In the Startup Method dialog box, choose "Start Windows from the
network (remote boot server)."
* In the Machine Directory dialog box, when asked where to install
Windows 95, type the path of the machine directory (using the drive
letter specified in Step 4, for example, g:\client).
* In the Setup Options dialog box, choose Custom setup.
* In the Analyzing Your Computer dialog box, choose "No, I want to
modify the hardware list." Exclude as many hardware types and items
from autodetection as possible. If autodetection crashes, run Setup
again and exclude more items from autodetection. One problem could be
that your network adapter is on IRQ2 or IRQ3; this conflicts with
serial port detection with some network adapters.
* In the Select Components dialog box, clear "Communications" the
checkbox.
* add a network component from a floopy disk.
* In the Network Configuration check that your network adapter and
desired protocols are present and configured correctly. If there are
no network adapters shown, you must add and configure your network
adapter. If youadd your network adapter, you must confirm the resource
settings for theadapter. Select the adapter name in the Network
Configuration dialog box, click Properties, and then click the
Resources tab. Check that the settings displayed are correct (for
example, the interrupt level). Then, click OK to force the Setup
program to accept the settings; do not click Cancel. For details about
protocols on Windows 95 remoteboot clients, see "Supporting Other
Protocols", later in this chapter.
* In the Identification dialog box, make sure that the workgroup for
this client is the same as the workgroup or domain of the SBS server
and machine directory server.
. When the Windows 95 Setup program is done, reboot the client. The
client will not yet boot to Windows 95. You must complete more steps
first.
. At the remoteboot server (or a client running Remoteboot Manager
focused on the remoteboot server), start Remoteboot Manager.
. Create a profile for the Windows 95 client. In the Configuration box,
choose the Windows 95 configuration corresponding to the client's
network adapter type.
. If you are not sure which configuration to choose, check the profile
that is currently associated with this client for booting MS-DOS, and
use the equivalent Windows 95 profile.
. Edit the client's workstation record to assign the client to the
Windows 95 profile.
. Copy feand.dos to c:\machine0\client\suboot directory.
Copy feand3.sys and ndis.vxd files to c:\sbs\system directory.
* You can find these files from \BOOTROM\RPL\NTRPL\Win95 directory.
. Next, you can find the following files in the c:\machine0\client\suboot
directory
* AUTOEXEC.BAT
* CONFIG.SYS
* MSDOS.SYS
* PROTOCOL.INI
* FEAND.DOS
* SYSTEM.DAT
. Creates sample boot block records for Windows 95. The sequence commands
are:
c:\winnt\rpl>rplcmd
Adapter Boot Config Profile Service Vendor Wksta [Quite] B
Add Del Enum:A
BootName=W95XX
VendorName=004095
BbcFile=BBLOCK\NETBEUI\FEAND\W95BB.CNF
BootCommet=FEAND PCI Adapter FOR WIN95 <Name of this adapter>
WindowsSize=0
Adapter Boot Config Profile Service Vendor Wksta [Quite] C
Add Del Enum:A
ConfigName=W95FEAND
BootName=W95XX
DirName=DOS
DirName2=WIN95
FitShared=FITS\WIN95.FIT
FitPersonal=FITS\WIN95P.FIT
ConfigComment=WIN95 for FEAND PCI Adaper <Name of the Config>
DirName3=
DirName4=
Adapter Boot Config Profile Service Vendor Wksta [Quite] Q
. At the Remoteboot Server (or a client running Remoteboot Manager
focused on the remoteboot server), start Remoteboot Manager.
. Create a profile (WFEAND) for the Windows 95 client. In the
Configuration box, choose the Windows 95 configuration corresponding
to the client's network adapter type.
. If you are not sure which configuration to choose, check the profile
that is currently associated with this client for booting MS-DOS, and
use the equivalent Windows 95 profile.
. Edit the client's workstation record to assign the client to the
Windows 95 profile.(In the SBS server of the MACHINES.INI file.)
. At the remoteboot server (or a client with write access to the
remoteboot server's RPL directory), run the RPL\BIN\WIN95CLT.BAT program
by typing:
cd winnt\rpl\bin
win95clt mach_directory \\rpl_server profile_name
where
* mach_directory is the path to the client's machine directory.
* \\rpl_server is the name of the remoteboot server.
* profile_name is the name of the Windows 95 profile associated with
the client.
For example, you could type:
cd \winnt\rpl\bin
win95clt \\ntserver\machine0\client \\ntserver wfeand
. The WIN95CLT program copies client-specific Windows 95 real-mode (also
identified as MS-DOS 7.0) boot files from the client's machine directory
to the RPL\RPLFILES\PROFILES\<profile_name>\SUBOOT directory on the
remoteboot server.
. At the SBS server (or a client with write access to the SBS directory),
edit the MACHINES.INI file in the SBS directory. Add the following lines
for the new client:
[adapter id]
SYSDATPATH=g:\machine_dir
g=\\mach_server\mach_share
where:
* adapter id is the network adapter id, specified in the remoteboot
workstation record for this client.
* \machine_dir is the location of the client's machine directory on a
server. “g?is the drive letter assigned on the next line to the
shared directory where the client's machine directory is located.
* \\mach_server\mach_share identifies the drive letter assigned to the
shared directory where the machine directory resides. You must use
the same drive letter and share name established in Step 4.
For example, you might add the following lines to MACHINES.INI:
[00409500002b]
SYSDATPATH=g:\client
g=\\ntserver\machine0
. Power off the machine and remove the ethernet network adapter.
. Install the BootWare ROM on the PCI adapter.
. Configure the ROM to use the RPL boot protocol.
. Reboot the Windows 95 client.
. Start Remoteboot Manager on the server.
. Remember to log on to a user account that belongs to the Administrators
local group.
. Start the remoteboot client. The client does not actually boot, but it
does send a boot request to the server.
. In Remoteboot Manager on the server, from the View menu, choose
Refresh.
. In Remoteboot Manager, select the adapter record that has appeared
with the network adapter ID number in place of the client name. From the
Remoteboot menu, choose Convert Adapters.
. In the Wksta Name box, type a name for the client. The name can have no
more than 15 characters [with no spaces or backslashes (\)]. The
Remoteboot Service will create a Windows NT user account with this name,
not for the user but for the client itself.
. The client will now boot to Windows 95 and complete the Windows 95
setup.
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.