How to install the RTL8139 PCI adapter Boot Rom for Windows 95. 


 This document provides step-by-step instructions on how to remoteboot
 Windows 95 clients with PCI network adapters from a Windows NT server
 using the NT Remoteboot Service.



Your responsibilities

This article assumes that your are a network administrator or equivalent
and that you have prior experience installing and configuring the NT
Remoteboot Service. Furthermore, you should be familiar with installing
Windows 95 for a shared network installation using NETSETUP.EXE.

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. 



   
Installing the Remoteboot Service on the Server.

1.Choose Control Panel , Network , Add Service , Remoteboot Service , put NTAS CD 
  disk they will be installed Remoteboot Service.

2.You must use Protocols item of Network Panel add DLC and NetBEUI Protocol. 

3.You must use Service item of Network Panel add Remoteboot Service. When you add Remoteboot
  it will set the directory on \winNT\rpl then choose OK --> point the directory of winNT setup
  disk (\\i386) --> continue --> key in the \clients\rpl on the space bar due to point the 
  directory of Remoteboot Clients files.(There are in winNT setup disk.) System will copy a
  couple of files to you hard disk. When it done, check your Services item have a Remoteboot 
  Service on list or not ? If OK, re-boot your system.

  Note:
        To install RPL server before , you must have installed DLC and
  NetBEUI protocol in your NTAS.

4.Sharing RPLFILES files and to install MS-DOS Files for Remoteboot workstation.

 (a).Sharing \rpl\rplfiles to (use File manager sharing, click right key of mouse)

 (b).Copy all the MS-DOS 6.22 ver files to \\RPL\RPLFILES\BINFILES\DOS622

     copy c:\dos\*.* \\NTAS40\RPLFILES\BINFILES\DOS622
     attrib -s -h c:\io.sys         ---- Running under DOS not dos prompt
     attrib -s -h c:\msdos.sys      ---- Running under DOS not dos prompt
     copy c:\io.sys \\NTAS40\RPLFILES\BINFILES\DOS622
     copy c:\msdos.sys \\NTAS40\RPLFILES\BINFILES\DOS622
     attrib +s +h c:\io.sys              
     attrib +s +h c:\msdos.sys

   Note: 
	Make sure io.sys and msdos.sys must change attribute under \\binfiles\dos622

5.Creating DOS Remoteboot configuration for new adapter

 (a).copy the MS-DOS device driver (NDIS2) for the  RTL8139 PCI adapter RTSND.DOS to 
     the \systemroot\RPL\BBLOCK\NDIS directory  

 (b).Create this directory \systemroot\RPL\BBLOCK\NETBEUI\RTL8139 and copy RTL8139.CNF, W95bb.cnf ,
     PROTOCOL.INI files. (Realtek provided it in the \driver directory !)

 (c).use RPLCMD utility to add a bblock record for new adapter.
     In MS-DOS Prompt type. NET START RemoteBoot (enter)
     DOS will show ......successfully.

 (d).In MS-DOS Prompt type RPLCMD (enter) {setup Configuration}
     Screen will display under line option and you following these do it.

 
 (e). Created DOS profile of the rtl8139 PCI adapter

  Adapter Boot Config Profile Service Vendor Wksta [Quit]: V
        Add Del Enum: A
        VendorName=E04C39 ( You can use rset8139.exe to check Ethernet ID first third byte 
                            of your adapter on client )

        VendorComment=DOS of the  RTL8139 PCI Adapter.

        Adapter Boot Config Profile Service Vendor Wksta [Quit] B
        Add Del Enum:A
        BootName=DOSZ
        VendorName=E04C39
        BbcFile=BBLOCK\NETBEUI\RTL8139\RTL8139.CNF
        BootCommet=DOS of the rtl8139 PCI adapter
        WindowsSize=0

        Adapter Boot Config Profile Service Vendor Wksta [Quit]: C
        Add Del Enum:A
        ConfigName=DOS622Z
        BootName=DOSZ
        DirName=DOS
        DirName2=DOS622
        FitShared=FITS\DOS622.FIT
        FitPersonal=FITS\DOS622P.FIT
        ConfigComment=DOS 6.22 <Adapter name>
        DirName3=
        DirName4=

 
      Then " choose Q and QUIT "
 (f).Shutdown Windows NTAS 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 , Remoteboot Manager
     1. Choose Remoteboot , New Profile , created a RTL8139 Profile Name
   *i.e. Profile Name: " enter the name you want " "D8139"
     Configuration: " choose DOS622 RTL8139 "
     Choose OK
     2. close this windows

8.Add new workstation for RTL8139 adapter and choose RTL8139 Profile file.
 (a). To config RTL8139 card "Node ID ( E0 4C 39 ** ** **)" and Running Boot ROM of 
     RTL8139 Card.  (use rset8139.exe to make sure that)
 (b) Use Rset8139.EXE to setup the Boot ROM enable and Size.
 (c). Re-boot and choose 3 ( Windows NTAS RPL Server )
   Note: System will count and wail NT system boot.

  * Above will run on CLIENT. *

 (d) Use administrator enter win NT 
 (e) choose start --> Programs --> Administrative Tool --> Remote Manager
 (f) You will see the Workstation Name......Description.........
     Choose the DOS of the rtl8139 ethernet adapter 
 (g) Use Remoteboot item --> Covert Adapters...
     Enter Wksta Name: " any name you want "
     Password: " your password "

     Note:
    1. If you cannot see any Workstation Name on your NT server. You can use Remoteboot
        item --> Set Focus ...
    2 If the new workstation Node ID is not match for your workstation , you can use 
        "Convert Adapters" in Remoteboot option.
9. Check the client is connected or not
    Your Login Name must belong to the memberships of Server Operators. You can check it 
    use User Manager to make sure that.




Installing Windows 95 for Windows 95 Clients

To support Windows 95 remoteboot clients, you must:

   * install Server-Based Setup (SBS) on a Window NT 4.0 server,
   * install the first Windows 95 client,
   * install subsequent clients.

Installing SBS for Windows 95 Clients

For greater technical detail about SBS servers, see the Microsoft Windows
95 Resource Kit. When you set up an SBS server you can use the server for
remoteboot and for other purposes described in the Microsoft Windows 95
Resource Kit.

You will need a Windows 95 installation compact disc (not floppies) and a
Windows 95 client computer.

To install an SBS server from windows 95 client to windows nt 4.0 server.

1. On the windows nt 4.0 server that will contain SBS files, create a shared 
directory (sbsfiles) with 90 MB space available. The shared directory can have 
any name. As you share the directory, assign read-only permission for regular 
users and full access for administrators. For example, use Server Manager to focus
 on the shared directory and set read-only permission for the Users group and full
permission for the Administrators group. In File Manager, use the Share As command 
from the Disk menu rather than the Permissions command from the Security menu.

 or in dos prompt type:

 mkdir c:\sbsfiles
 net share sbsfiles=c:\sbsfiles


2. Install one regular Windows 95 client on the network or use an existing
one. You will use this client to configure the SBS server.

3. Log on to the Windows 95 client using an account that has write access
to the shared directory on the SBS (windows nt 4.0) server.

4. Put the Windows 95 compact disc in the client's CD-ROM drive. In Windows
Explorer, switch to the ADMIN\NETTOOLS\NETSETUP directory.

5. 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.

6. 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
(format is: \\server1\sharedir,for example : \\ntas40\sbsfiles)

The button name becomes Change Path if a server was defined previously.

7. 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.

8. 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. 
Run win95srv.bat to update the Windows 95 files for remotebooting. For example:

 d:\
 cd \update\win95
or
 cd\clients\rpl\update\win95

 win95srv.bat <dest>

 where
 <dest> is the shared directory on the SBS server.

for example:

 win95srv.bat \\ntas40\sbsfiles

9. Follow this step only if you are updating from version 3.51 or earlier
of the Remoteboot Service. At the remoteboot server, start the Remoteboot
Service if it is not already started. Then run the rbootsrv.bat program to
update the remoteboot files and database for Windows 95 remotebooting. At
the server's command prompt, type

 d:
 cd \update\win95
or 
 cd\clients\rpl\update\win95

 rbootsrv.bat <SBS_path> <RPL_path> [\\servername]

for example:

 rbootsrv.bat \\ntas40\sbsfiles c:\winnt\rpl \\ntas40


where

   * <SBS_path> is the path to the installed SBS server's Windows 95 files.
   * <RPL_path> is the path to the remoteboot directory.
   * \\servername is the name of the remoteboot server; you can omit this
     if you are typing at the remoteboot server.


10. At the remoteboot server, start Remoteboot Manager. From the Configure
menu, choose Check Configurations to activate the new configurations.

Installing the First Windows 95 Client

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

  Machine directories can reside on the remoteboot server, on the SBS
server, or on any designated server on the network. You may want to spread
the load of machine directories across servers. The only qualifications for
a machine directory server are sufficient disk space and running the
NetBEUI protocol. To create a location for machine directories, simply make
a shared directory on a server and share it with a name that does not
contain spaces. For example, on a computer running Windows NT Server that
will contain machine directories, type:

 mkdir c:\machine0
 net share machine0=c:\machine0

 Note:

The machine directories may not be subdirectories of the SBS directory.

Assign permissions to a machine directory so that only the users or
administrators who will use the client have read and write permissions in
the directory. If the machine directory is on an NTFS partition, assign
permissions directly to the machine directories. If the machine directory
is on an FAT partition, assign permissions to the shared directory
containing the machine directories.

To install the first Windows 95 client:

1. Boot the new client to MS-DOS 6.2x

You will need to run Windows 95 Setup while the client is booted from the
Remoteboot Service, rather than when the client is booted from a floppy
disk or hard drive.

2. Use the net logon command to log on using an account that has read
access to the SBS server and write access to the shared directory that will
contain this client's machine directory. A good example is the account of
someone who will use this client, as they will need this access anyway.

3. Synchronize the time and date settings of the client, the SBS server,
and the remoteboot server. Differing settings can interfere with Windows 95
Setup.

4. Use the net use command to map drive letters to the SBS server and
machine directory location. Determine the highest drive letter in use on
the computer. C: is a virtual hard drive mapped to parts of the remoteboot
server. Each local hard drive partition (if any) takes another drive letter
after C: (for example, D: and E: for two partitions). One more drive letter
is reserved for use as a RAM drive during the Windows 95 boot process.
Drive letters after that are available for use.

For example, if you have a local hard drive with one partition, C: will be
mapped to the remoteboot server; D: will be the local hard drive; E: is
reserved for use as a RAM drive; and, F: and higher are available for use.
You would type:

format is:

 net use f: \\sbs_server\win95_share
 net use g: \\mach_server\mach_share

for example:

 net use f: \\ntas40\sbsfiles
 net use g: \\ntas40\machine0

5. Change to the drive letter mapped to the SBS directory.

6. 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:\client3.tmp

to store temporary files on that server.

7. Do not delete the t:\temppath directory until you have completed Step
8. Also, 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.

9. 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:\client3).
   * 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 you
     add your network adapter, you must confirm the resource settings for the
     adapter. 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.

10. 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.

11. At the remoteboot server (or a client running Remoteboot Manager
focused on the remoteboot server), start Remoteboot Manager.

12. 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.

13. 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.

14. Edit the client's workstation record to assign the client to the
Windows 95 profile.

15. You must also copy \suboot\protocol.ini and \driver\rtsnd.dos NDIS driver to 
    c:\machine0\client3\suboot directory.
    copy \driver\rtl8139.sys file to c:\sbsfiles\system directory.

note:
      if you lost rtl8139.sys file that win95 system will show the message 
      "you can now safely turn off your computer.if you want to restart your computer"

16. Next, you must manually edit the following files found in the C:\machine0\client3\SUBOOT
directory

   * AUTOEXEC.BAT   ---  if system lost it , realtek provided it. \suboot directory 
   * CONFIG.SYS     ---	 if system lost it , realtek provided it. \suboot directory 	
   * MSDOS.SYS      ---  
   * PROTOCOL.INI   ---  Realtek  \suboot directory
   * RTSND.DOS      ---  Realtek  \driver directory
   * SYSTEM.DAT


17. 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

18. 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.


19. Export system.dat miniregistry file as follows:

 regedit /L:system.dat /E registry.txt

20. 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"="rtsnd.dos"



21. After modifying REGISTRY.TXT you must update SYSTEM.DAT by importing
the new information.

 regedit /L:system.dat /C registry.txt

22. Remove the hidden, system, and read only attributes from SYSTEM.DAT by
entering:

 attrib -r -s -h system.dat

23.copy new system.dat to c:\machine0\client3\suboot directory.


24.For example, the following sequence of commands creates sample boot block
records for Windows 95:

 C:\winnt\rpl> rplcmd

 Adapter Boot Config Profile Service Vendor Wksta [Quit]: b

 Add Del Enum: a

 BootName=W95ZZ

 VendorName=E04C39

 BbcFile=BBLOCK\NETBEUI\rtl8139\W95BB.CNF

 All other parameters are optional

 BootComment=Name of this adapter

 WindowSize=0

 
Note

In this example, and in those that follow, the value E04C39 represents the
"vendor name" or network adapter prefix. Replace this with the first six
digits of the network adapter type's adapter identification number.

If you want to use a new remoteboot-compatible network adapter that is not
already supported by Windows NT Server, you must manually create a new boot
block, boot block record(s), and a configuration record corresponding to
the new adapter. This allows the Remoteboot Service and Remoteboot Manager
to recognize the new adapter type.


To create a Windows 95 configuration for the PCI adapter:

The following procedure should be done at the NT remoteboot server


1. Use the rplcmd utility to add a boot block record for the new adapter.

2. For example, the following sequence of commands creates a sample boot
block record for the RTL8139 PCI Ethernet adapter:

 \winnt\rpl> rplcmd

 
Adapter Boot Config Profile Service Vendor Wksta [Quit]: c

 Add Del Enum: a

 ConfigName=W95_8139

 BootName=W95ZZ


 DirName=DOS

 DirName2=WIN95

 FitShared=fits\win95.FIT

 FitPersonal=fits\win95p.FIT

 All other parameters are optional

 ConfigComment=Windows 95 <RTL8139 PCI Ethernet adapters>

 DirName3=

 DirName4=


 
3. Quit RPLCMD by pressing Q at the command line options.

4. At the remoteboot server (or a client running Remoteboot Manager focused
on the remoteboot server), start Remoteboot Manager.

5. Create a profile( W8139 ) for the Windows 95 client. In the Configuration box,
choose the Windows 95 configuration corresponding to the client's network
adapter type.

6. 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.

7. Edit the client's workstation record to assign the client to the
Windows 95 profile.(In the SBS server of the MACHINE.INI file.)

8. 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 <systemroot>\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 <Enter>
 win95clt \\ntas40\machine0\client3 \\ntas40 w8139

note: if client files are aleady present ,delete \systemroot\rpl\rplfiles\W8139\suboot
      and retry.

9. 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.

10. 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:

 [E04C39000001]
 SYSDATPATH=g:\client3
 g=\\ntas40\machine0

11. Power off the machine and remove the ethernet network adapter.

12. Install the BootWare ROM on the PCI adapter.

13. Configure the ROM to use the RPL boot protocol.

14. Reboot the Windows 95 client.

15. Start Remoteboot Manager on the server.

16. Remember to log on to a user account that belongs to the Administrators
local group.

17. Start the remoteboot client. The client does not actually boot, but it
does send a boot request to the server.

18. In Remoteboot Manager on the server, from the View menu, choose
Refresh.

19. 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.

20. 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.

21. If the server's RPL directory is on an FAT file system, use standard
MS-DOS 8.3 format (eight characters, with an optional period and three more
characters).

22. In the Description box, type a comment that describes the client. The
box already contains a comment provided by the network adapter itself.

23. Choose a configuration type:

?Shared if this client can share its profile with other clients.

?Personal if this client must use a personal copy of a profile so that you
can customize the environment for the client.

?In the Wksta In Profile box, choose a profile for this client. Profiles
that are unsuitable for this type of adapter (determined by the first six
digits of the network adapter ID number) are marked with a red X. If none
of the profiles is suitable, see "Setting Up and Starting the Remoteboot
Service," earlier in this chapter for instructions on creating profiles.

?In the TCP/IP Configuration box, enter appropriate addresses only if the
client will use TCP/IP and will not use DHCP for automatic address
handling.

?Choose the Add button.

24. The client will now boot to Windows 95 and complete the Windows 95
setup.

---------------------------------------------------------------------------






If you have any questions or problems, please contact leo@realtek.com.tw
