Bootrom/BOOTROM.TXT Driver File Contents (davicom9102.zip)

Driver Package File Name: davicom9102.zip
File Size: 1.8 MB

[+******************************************************************+]
[                     DAVICOM Semiconductor Inc.                     ]
[                  PCI Fast Ethernet Adapter (DM9102)                ]
[                  RPL BootROM Code Installation Guide               ]
[                                                                    ]
[          (C) Copyright 1997-2000 DAVICOM Semiconductor Inc.        ]
[                         All Rights Reserved.                       ]
[====================================================================]
[                                                                    ]
[  Model Name     : DM9102                                           ]
[                                                                    ]
[  Driver Name    : RBOOT.ROM                                        ]
[                                                                    ]
[  Platform       : NetWare Server, NT Server                        ]
[                                                                    ]
[-******************************************************************-]

The DM9102 RPL BootROM supports 3 RPL boot modes (INT 19h/INT 18h
/Local).

        RPL Boot Menu :

         1. RPL Boot from INT 19h (Default)
         2. RPL Boot from INT 18h (BIOS LAN)
         3. RPL Boot from Local Drive

        Please enter RPL boot mode (1..3) :

(1) The RPL Boot from INT 19h is for the normal machine.
(2) The RPL Boot from INT 18h is for the new machine that
    the BIOS configuration supports Boot from LAN option.
(3) The RPL Boot from Local Drive will skip the RPL BootROM
    code and boot from local drive (A:, C:, ...).


The DM9102 RPL BootROM can remoteboot to MS-DOS from Novell Netware
Server or 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 RBOOT.ROM Code

        B. MS-DOS Remote Boot to Netware Server Installation

           B-1. AUTOEXEC.BAT Sample File
           B-2. CONFIG.SYS Sample File
           B-3. NET.CFG Sample File

        C. MS-DOS Remote Boot to NT Server Installation

           C-1. DOSBB.CNF Sample File for DM9102
           C-2. PROTOCOL.INI Sample File for DM9102

        D. Windows 95 Remote Boot to NT Server Installation (ONLY for NT 4.0)

           D-1. W95BB.CNF Sample File for DM9102
           D-2. MSDOS.SYS Sample File for DM9102
           D-3. CONFIG.SYS Sample File for DM9102
           D-4. AUTOEXEC.BAT Sample File for DM9102
           D-5. WIN.BAT Sample File for DM9102
           D-6. PROTOCOL.INI Sample File for DM9102
           D-7. MACHINES.INI Sample File for DM9102
           E-1. MSDOS.SYS Sample File for NE2000
           E-2. CONFIG.SYS Sample File for NE2000
           E-3. AUTOEXEC.BAT Sample File for NE2000
           E-4. WIN.BAT Sample File for NE2000
           E-5. PROTOCOL.INI Sample File for NE2000
           E-6. MACHINES.INI Sample File for NE2000


A. Generate RPL Boot ROM from RBOOT.ROM Code :
==============================================

   **********************************************************************
   * Hardware Requiremment:                                             *
   *                                                                    *
   *  1. A EPROM Programming Machine                                    *
   *  2. A M27C512 EPROM (or others model EPROM)                        *
   *  3. The DM9102 RPL BootROM Code (RBOOT.ROM)                        *
   **********************************************************************

   1. Use the EPROM Programming Machine to write RBOOT.ROM code
      to the addresses 0000h, 4000h, 8000h, C000h of the M27C512 EPROM.

   2. Please refer to the EPROM Programming Machine Operating Guide
      for details.


B. MS-DOS Remote Boot to Netware Server Installation :
======================================================

   **********************************************************************
   * Hardware Requiremment:                                             *
   *                                                                    *
   *  1. A Netware Server with the RemoteBoot Service                   *
   *  2. A Remote Boot Workstation with DM9102 PCI Adapter              *
   *  3. A Remote Boot Image Files Floppy Diskette                      *
   *  4. A DAVICOM DM9102 PCI Fast Ethernet Adapter with RPL BootROM    *
   **********************************************************************

   Installation Guide Topics:

      1. Install the RemoteBoot Service on the Netware Server
      2. Prepare a Remote Boot Image Files Floppy Diskette
      3. Generate the Remote Boot Image File (NET$DOS.SYS)
         to the Netware Server

   1. Install the RemoteBoot Service on the Netware Server

      (1) Startup the Netware Server.

      (2) At the Netware Server Console, load the server LAN driver
          with the frame type ETHERNET_802.2, and the other frame types
          that you want to load, then bind the IPX protocol with all
          frame types of the server LAN driver.

            NW50: LOAD DM9PCI SLOT=3 FRAME=ETHERNET_802.2 NAME=E1_802.2
            NW50: BIND IPX E1_802.2 NET=1111

      (3) Login one workstation to the Netware Server.

      (4) Insert the DM9102 Driver Diskette into the workstation floppy
          drive (A:).

      (5) Update the RPL.NLM file to the directory SYS:SYSTEM.

            F:\> COPY F:\SYSTEM\RPL.NLM F:\SYSTEM\RPL.NL_
            F:\> COPY A:\BOOTROM\NETWARE\RPL.NLM F:\SYSTEM

      (6) Update the RBOOT.RPL file to the directory SYS:LOGIN.

            F:\> COPY F:\LOGIN\RBOOT.RPL F:\LOGIN\RBOOT.RP_
            F:\> COPY A:\BOOTROM\NETWARE\RBOOT.RPL F:\LOGIN

      (7) Copy the RPLFIX.COM file to the directory SYS:LOGIN.

            F:\> COPY A:\BOOTROM\NETWARE\RPLFIX.COM F:\LOGIN

      (8) At the Netware Server Console, load RPL.NLM module and
          bind the RPL protocol with the frame type ETHERNET_802.2
          of the server LAN driver.

            NW50: LOAD RPL
            NW50: BIND RPL E1_802.2

      (9) Now the Netware Server Remoteboot Service is working.

   2. Prepare a Remote Boot Image Files Floppy Diskette

      (1) Startup a workstation with MS-DOS prompt from a local disk.

      (2) Insert a blank diskette into the floppy drive (A:),
          and label this diskette as "RPL RemoteBoot Image Diskette".

      (3) At the MS-DOS prompt, run the following command to format
          the blank diskette.

            C:\> FORMAT A:/S

      (4) Copy the following files to the RPL RemoteBoot Image Diskette.

            LSL.COM
            IPXODI.COM
            DM9PCI.COM
            VLM.EXE
            *.VLM       <== All needed VLM modules files
            HIMEM.SYS

      (5) Create the following files to the RPL RemoteBoot Image Diskette.
          (Please refer to the following sample files)

            AUTOEXEC.BAT
            CONFIG.SYS
            NET.CFG

   3. Generate the Remote Boot Image File (NET$DOS.SYS) to Netware Server

      (1)  Plug the DM9102 PCI adapter WITHOUT the DM9102 RPL
           BootROM into the workstation PCI slot.

      (2)  Insert the RPL RemoteBoot Image Diskette into the floppy
           drive (A:).

      (3)  Restart the workstation from the RPL RemoteBoot Image
           Diskette.

      (4)  Login the workstation to the Remote Boot Netware Server.

      (5)  Generate the Remote Boot Image File (NET$DOS.SYS) into
           the Remote Boot Netware Server by running the following
           command, and copy the AUTOEXEC.BAT file from the floppy
           diskette to the directory SYS:\, SYS:LOGIN and SYS:SYSTEM.

             A:\> F:
             F:\SYSTEM> CD \LOGIN
             F:\LOGIN> \SYSTEM\DOSGEN A:
             F:\LOGIN> RPLFIX NET$DOS.SYS
             F:\LOGIN> FLAG NET$DOS.SYS SH

             F:\LOGIN> COPY A:\AUTOEXEC.BAT F:\
             F:\LOGIN> COPY A:\AUTOEXEC.BAT F:\LOGIN
             F:\LOGIN> COPY A:\AUTOEXEC.BAT F:\SYSTEM
             F:\LOGIN> FLAG F:\AUTOEXEC.BAT SH
             F:\LOGIN> FLAG F:\LOGIN\AUTOEXEC.BAT SH
             F:\LOGIN> FLAG F:\SYSTEM\AUTOEXEC.BAT SH

      (6)  Logout the workstation from the Remote Boot Netware Server.

      (7)  Remove the RPL RemoteBoot Image Diskette from the floppy
           drive (A:).

      (8)  Power OFF the workstation.

      (9)  Plug the DM9102 RPL BootROM into the Boot ROM socket of
           the DM9102 PCI Adapter.

      (10) Plug the DM9102 PCI adapter WITH the DM9102 RPL BootROM
           into the Remote Boot Workstation PCI slot.

      (11) Restart the Remote Boot Workstation from the DM9102 RPL
           BootROM.

      (12) The Remote Boot Workstation will remoteboot to MS-DOS
           from the Remote Boot Netware Server and specify the
           Username (ADMIN) and Password to login the Remote Boot
           Netware Server by the RPL BootROM.


B-1. AUTOEXEC.BAT Sample File :
===============================

      @ECHO OFF
      PROMPT $P$G
      LSL
      DM9PCI
      IPXODI
      VLM
      F:
      LOGIN ADMIN
      CD \LOGIN


B-2. CONFIG.SYS Sample File :
=============================

      DEVICE=HIMEM.SYS
      DOS=HIGH
      FILES=40
      BUFFERS=20
      LASTDRIVE=Z


B-3. NET.CFG Sample File :
==========================

      Link Support
           Buffers 8 1514

      Link Driver DM9PCI

              FRAME ETHERNET_802.2
              FRAME ETHERNET_802.3
              FRAME ETHERNET_II
              FRAME ETHERNET_SNAP

      NetWare DOS Requester
              FIRST NETWORK DRIVE = F
              NETWARE PROTOCOL = NDS BIND


C. 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 DM9102 PCI Adapter              *
   *  3. A DAVICOM DM9102 PCI Fast Ethernet Adapter with RPL BootROM    *
   **********************************************************************

   1. The network adapter driver and protocol must be installed
      successfully on the Remote Boot NT Server.

   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 A:\IO.SYS
            ATTRIB -R -S -H A:\MSDOS.SYS
            COPY A:\IO.SYS C:\WINNT35\RPL\RPLFILES\BINFILES\DOSxxx
            COPY A:\MSDOS.SYS C:\WINNT35\RPL\RPLFILES\BINFILES\DOSxxx

            ATTRIB +R +S +H A:\IO.SYS
            ATTRIB +R +S +H A:\MSDOS.SYS

      (2) Copy DM9102 NDIS2 Driver (DM9PCI.DOS) from Driver Diskette
          A:\LANTASTI to C:\WINNT\RPL\BBLOCK\NDIS directory.

            COPY A:\LANTASTI\DM9PCI.DOS C:\WINNT\RPL\BBLOCK\NDIS

      (3) Create C:\WINNT\RPL\BBLOCK\NETBEUI\DM9PCI subdirectory, and
          copy DOSBB.CNF and PROTOCOL.INI files from Driver Diskette
          A:\BOOTROM\NTSRV to C:\WINNT\RPL\BBLOCK\NETBEUI directory.

            COPY A:\BOOTROM\NTSRV\DOSBB.CNF C:\WINNT\RPL\BBLOCK\NETBEUI\DM9PCI
            COPY A:\BOOTROM\NTSRV\PROTOCOL.INI C:\WINNT\RPL\BBLOCK\NETBEUI\DM9PCI

      (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]: b
            Add Del Enum: a
            BootName=DM9102
            VendorName=00606E           <== Change to your Node Address
            BbcFile=BBLOCK\NETBEUI\DM9PCI\DOSBB.CNF
                    All other parameters are optional
            BootComment=DOS 6.22 for DAVICOM DM9102
            WindowsSize=0

            Adapter Boot Config Profile Service Vendor Wksta [Quit]: c
            Add Del Enum: a
            ConfigName=DM9102
            BootName=DM9102
            DirName=DOS
            DirName2=DOS622
            FitShared=fits\dos622.fit
            FitPersonal=fits\dos622p.fit
                    All other parameters are optional
            ConfigComment=DOS 6.22 for DAVICOM DM9102
            DirName3=
            DirName4=

            Adapter Boot Config Profile Service Vendor Wksta [Quit]: v
            Add Del Enum: a
            VendorName=00606E           <== Change to your Node Address
            VendorComment=DAVICOM Semiconductor, Inc.

      (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 DAVICOM
          DM9102" 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 DM9102 adapter with
      the DM9102 RPL BootROM into the Remote Boot Workstation PCI slot.

   7. Startup the Remote Boot Workstation, the RPL BootROM will try to
      remoteboot 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 DAVICOM DM9102" 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 DM9102 RPL BootROM, and
      specify Username and Password to logon the Remote Boot NT Server.


C-1. DOSBB.CNF Sample File for DM9102 :
=======================================

      ; DOS on DAVICOM PCI Fast Ethernet Adapter (DM9102)
      ; (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\dm9pci\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\dm9pci.DOS ~ ~ ~
      DRV BBLOCK\PROTMAN.DOS /I:C:\LANMAN.DOS ~ M


C-2. PROTOCOL.INI Sample File for DM9102 :
==========================================

      [protman]
        drivername = protman$
        dynamic = yes
        priority = netbeui

      [netbeui_xif]
        drivername = netbeui$
        bindings = dm9pci_nif
        names = 6
        ncbs = 12
        packets = 20
        pipeline = 10
        sessions = 6
        stacksize = 512
        lanabase = 0

      [xnsnb_xif]
        drivername = xnsnb$
        bindings = dm9pci_nif
        load = xnsnb[cbr]
        lanabase = 1

      [xnstp_xif]
        drivername = xnstp$
        bindings = dm9pci_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 = dm9pci_nif
        lanabase = 1

      [ipx_xif]
        drivername = ipx$
        load = ipxmark[u],ipx[u]
        unload = ipxrel[c]
        bindings = dm9pci_nif
        lanabase = 1

      [msdlc_xif]
        drivername = msdlc$
        bindings = dm9pci_nif
        load = msdlc[ub]
        unload = msdlc[u]

      [dm9pci_nif]
        drivername = DM9PCI$            <== MUST be "DM9PCI$", char sensitive


D. Windows 95 Remote Boot to NT Server Installation (ONLY for NT 4.0) :
=======================================================================

   ************************************************************************
   * 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                                *
   *  5. A Remote Boot Workstation with ISA (or PCI) RPL BootROM          *
   *  6. A NE2000 Compatible ISA Ethernet Adapter with RPL BootROM        *
   *  7. A DAVICOM DM9102 PCI Fast Ethernet Adapter with RPL BootROM      *
   ************************************************************************

   Installation Guide Topics:

      1. Install Server-Based Setup (SBS) on NT Server
      2. Install the First Windows 95 Client by using ISA adapter
      3. Install others Windows 95 Client by using PCI adapter

   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" user with
           "Change" permission and "Administrators" user 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.

      (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 (\\NT40SRV\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 First Windows 95 Client by using ISA adapter

      (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" user with "Change" permission and
           "Administrators" user with "Full Control" permission.

      (2)  At the NT Server, follow the following step to create
           the New Profile Configuration for MS-DOS and Windows 95
           Remote Boot.

           a) 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=ACCNE2
                VendorName=0000E8       <== Change to your Node Address
                BbcFile=BBLOCK\NETBEUI\NE2000\DOSBB.CNF
                        All other parameters are optional
                BootComment=DOS 6.22 NE2000 for Accton
                WindowsSize=0

                Adapter Boot Config Profile Service Vendor Wksta [Quit]: c
                Add Del Enum: a
                ConfigName=ACCNE2
                BootName=ACCNE2
                DirName=DOS
                DirName2=DOS622
                FitShared=fits\dos622.fit
                FitPersonal=fits\dos622p.fit
                        All other parameters are optional
                ConfigComment=DOS 6.22 NE2000 for Accton
                DirName3=
                DirName4=

                Adapter Boot Config Profile Service Vendor Wksta [Quit]: v
                Add Del Enum: a
                VendorName=0000E8       <== Change to your Node Address
                VendorComment=Accton

                C:\WINNT\RPL> RPLCMD
                Adapter Boot Config Profile Service Vendor Wksta [Quit]: b
                Add Del Enum: a
                BootName=WACCNE2
                VendorName=0000E8       <== Change to your Node Address
                BbcFile=BBLOCK\NETBEUI\NE2000\W95BB.CNF
                        All other parameters are optional
                BootComment=Windows 95 NE2000 for Accton
                WindowsSize=0

                Adapter Boot Config Profile Service Vendor Wksta [Quit]: c
                Add Del Enum: a
                ConfigName=WACCNE2
                BootName=WACCNE2
                DirName=DOS
                DirName2=WIN95
                FitShared=fits\win95.fit
                FitPersonal=fits\win95p.fit
                        All other parameters are optional
                ConfigComment=Windows 95 NE2000 for Accton
                DirName3=
                DirName4=

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

           c) Select "New Profile" from "Remoteboot" item of the "Remoteboot
              Manager - Local Machine" dialog box, select "DOS 6.22 NE2000
              for Accton" from "Configuration" field, then specify the New
              Profile Name to "Profile Name" field, click "OK" button to
              create new profile.

           d) Select "New Profile" from "Remoteboot" item of the "Remoteboot
              Manager - Local Machine" dialog box, select "Windows 95 NE2000
              for Accton" from "Configuration" field, then specify the New
              Profile Name to "Profile Name" field, click "OK" button to
              create new profile.

      (3)  Plug a NE2000 Compatible ISA Ethernet Adapter with RPL BootROM
           into the Remote Boot Workstation ISA slot.

      (4)  Startup the Remote Boot Workstation, configure the ISA adapter
           settings (IRQ=3, I/O Port=300h-31Fh) and enable the BootROM
           function.

           (P.S.: The NE2000 driver uses the default settings (IRQ=3,
                  I/O Port=300h-31Fh), if you use another settings,
                  you must MANUALLY edit \WINNT\RPL\BBLOCK\NETBEUI
                  \NE2000\PROTOCOL.INI file to modify the following
                  lines to force the driver access another settings)

                  [ms2000_nif]
                    drivername = ms2000$
                    interrupt=3
                    ioaddress=0x300

      (5)  Reboot the Remote Boot Workstation, the RPL BootROM will
           try to remoteboot from NT server.

      (6)  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 NE2000 for Accton" from "Wksta In Profile"
           item then specify the New Workstation Name, click "Add" button.

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

      (8)  At the Remote Boot Workstation, specify Username and Password
           to logon the NT Server.

           (P.S.: This user MUST be "Administrators" user.)

      (9)  At the Remote Boot Workstation, run the following to map drives
           to \\NT40SRV\WIN95SRV and \\NT40SRV\CLIENTS shared directories.

             C:\> NET USE F: \\NT40SRV\WIN95SRV
             C:\> NET USE G: \\NT40SRV\CLIENTS

      (10) 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

      (11) 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 -> select
              "Novell/Anthem" from "Manufacturers" item -> select
              "NE2000 Compatible" from "Network Adapters" item ->
              click "OK" button to add your network adapter, select
              "NE2000 Compatible" in the Network Configuration dialog box,
              click "Properties" button, click "Resources" tab to change
              the settings of I/O Port and IRQ (IRQ=3, I/O Port=300h-31Fh)
              to match with the hardware setting then click "OK" button.

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

      (12) After complete Windows 95 client installation, 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.
           (Please refer to the following sample files for NE2000)

             MSDOS.SYS
             CONFIG.SYS
             WIN.BAT

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

      (14) 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\WACCNE2\SUBOOT directory.

             WIN95CLT.BAT \WINNT\RPL\CLIENTS\CLIENT1 \\NT40SRV WACCNE2

      (15) At the NT Server, change the directory to the \WIN95SRC
           directory to edit the MACHINES.INI file and add the following
           lines for the new clients.

             [0000E8318587]
             SYSDATPATH=G:\CLIENT1
             G=\\NT40SRV\CLIENTS

      (16) Reboot the Remote Boot Workstation, the RPL BootROM will
           try to remoteboot from NT server.

      (17) 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 NE2000 for Accton" from "Wksta In Profile"
           item then specify the New Workstation Name, click "Add" button.

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

      (19) 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 First Windows 95 Client installation.

   3. Install others Windows 95 Client by using PCI adapter

      (1) At the NT Server, follow the following step to create
          the New Profile Configuration for Windows 95 Remote Boot.

          a) Copy DM9102 NDIS2 Driver (DM9PCI.DOS) from Driver Diskette
             A:\LANTASTI to C:\WINNT\RPL\BBLOCK\NDIS directory.

               COPY A:\LANTASTI\DM9PCI.DOS C:\WINNT\RPL\BBLOCK\NDIS

          b) Create C:\WINNT\RPL\BBLOCK\NETBEUI\DM9PCI subdirectory, and
             copy W95BB.CNF and PROTOCOL.INI files from Driver Diskette
             A:\BOOTROM\NTSRV to C:\WINNT\RPL\BBLOCK\NETBEUI directory.

               COPY A:\BOOTROM\NTSRV\W95BB.CNF C:\WINNT\RPL\BBLOCK\NETBEUI\DM9PCI
               COPY A:\BOOTROM\NTSRV\PROTOCOL.INI C:\WINNT\RPL\BBLOCK\NETBEUI\DM9PCI

          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=WDM9102
               VendorName=00606E        <== Change to your Node Address
               BbcFile=BBLOCK\NETBEUI\DM9PCI\W95BB.CNF
                       All other parameters are optional
               BootComment=Windows 95 for DAVICOM DM9102
               WindowsSize=0

               Adapter Boot Config Profile Service Vendor Wksta [Quit]: c
               Add Del Enum: a
               ConfigName=WDM9102
               BootName=WDM9102
               DirName=DOS
               DirName2=WIN95
               FitShared=fits\win95.fit
               FitPersonal=fits\win95p.fit
                       All other parameters are optional
               ConfigComment=Windows 95 for DAVICOM DM9102
               DirName3=
               DirName4=

               Adapter Boot Config Profile Service Vendor Wksta [Quit]: v
               Add Del Enum: a
               VendorName=00606E        <== Change to your Node Address
               VendorComment=DAVICOM Semiconductor, Inc.

           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
              DAVICOM DM9102" from "Configuration" field, then specify the
              New Profile Name to "Profile Name" field, click "OK" button
              to create new profile.

      (2)  At the NT Server, copy DM9102 NDIS2 Driver (DM9PCI.DOS) from
           DM9102 Driver Diskette A:\LANTASTI to C:\WIN95SRV, C:\WINNT
           \RPL\CLIENTS\CLIENT1 and C:\WINNT\RPL\RPLFILES\PROFILES\WACCNE2
           directories, and copy DM9102 NDIS3 Driver (DM9PCI.SYS) from
           A:\WIN95 to C:\WIN95SRV\SYSTEM directory,

             COPY A:\LANTASTI\DM9PCI.DOS C:\WIN95SRV
             COPY A:\LANTASTI\DM9PCI.DOS C:\WINNT\RPL\CLIENTS\CLIENT1
             COPY A:\LANTASTI\DM9PCI.DOS C:\WINNT\RPL\RPLFILES\PROFILES\WACCNE2
             COPY A:\WIN95\DM9PCI.SYS C:\WIN95SRV\SYSTEM

      (3)  Power OFF the Remote Boot Workstation, and plug DM9102
           PCI Fast Ethernet Adapter WITHOUT the RPL BootROM into
           the Remote Boot Workstation PCI slot. (DON'T remove
           the ISA Ethernet Adapter)

      (4)  Startup the Workstation and remoteboot to Windows 95
           using ISA Ethernet Adapter RPL Boot ROM.

      (5)  When Windows 95 startup, the new PCI Ethernet Controller
           will be found, select "Driver from disk provided by hardware
           manufacturer" from "New Hardware Found" dialog box.

      (6)  Insert DM9102 driver diskette into floppy drive (A:) and
           enter "A:\WIN95" to "Install from Disk" field, then click
           "OK" button to install DM9102 driver, sometimes Windows 95
           will prompt you "File Copying Problem" dialog box, just
           click "Skip File" button to continue driver installation.

      (7)  Restart the Remote Boot Workstation, after Windows 95 startup
           again, select "Start" -> "Settings" -> "Control Panel",
           double-click the "Network" and "System" items from "Control
           Panel" dialog box to verify the DM9102 PCI Adapter has been
           successfully added and the default protocols are bound to
           the DM9102 PCI Adapter and the DM9102 device driver is worked
           normally.

      (8)  Startup Windows 95 Workstation with CD-ROM drive, enter
           Username and Password to logon NT Server.

      (9)  Insert Microsoft Windows 95 Resource Kit into Windows 95
           CD-ROM drive.

      (10) In Windows 95 Explorer, switch to the ADMIN\NETTOOLS\NETSETUP
           directory of CD-ROM drive, double-click NETSETUP.EXE.

      (11) In the Server-Based Setup dailog box, click "Set Path" button,
           and specify the path to SBS Server (\\NT40SRV\WIN95SRV),
           then click "OK" button.

      (12) In the Server-Based Setup dailog box, click "Add" button,

      (13) In the Set Up Machine dailog box, choose "Set Up One Machine"
           and enter the following fields information, then click "OK"
           button to copy the subsequence Windows 95 Clients files
           from \\NT40SRV\CLIENTS\CLIENT1 directory to \\NT40SRV\CLIENTS
           \CLIENT2 directory.

             Computer name: CLIENT2
             Path to machine directory: \\NT40SRV\CLIENTS\CLIENT2
             Existing machine directory: \\NT40SRV\CLIENTS\CLIENT1

      (14) The NETSETUP.EXE does NOT copy the SUBOOT directory so
           you must MANUALLY copy the directory at the NT Server.

             MD C:\WINNT\RPL\CLIENTS\CLIENT2\SUBOOT
             CD C:\WINNT\RPL\CLIENTS\CLIENT2\SUBOOT
             XCOPY C:\WINNT\RPL\CLIENTS\CLIENT1\SUBOOT\*.* .

      (15) You must MANUALLY edit the following files in the SUBOOT
           directory, all files except SYSTEM.DAT are in ASCII format
           and can be edited using any Text Editor such as EDIT.COM.
           (Please refer to the following sample files for DM9102)

             PROTOCOL.INI
             MSDOS.SYS
             CONFIG.SYS
             AUTOEXEC.BAT
             WIN.BAT
             SYSTEM.DAT

      (16) 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.

           (P.S.: The SYSTEM.DAT MUST remove the "Read Only", "Hidden"
                  and "System" attributes.)

           **************
           * NOTICE !!! *
           **************
           The REGEDIT.EXE MUST be run from Windows 95 DOS Prompt Mode,
           CAN'T be run from a DOS Session under Windows 95 or MS-DOS
           Prompt. So we must reboot the Windows 95 Workstation to
           Windows 95 DOS Prompt Mode (NOT under Windows 95) and
           copy SYSTEM.DAT file from C:\WINNT\RPL\CLIENTS\CLIENT2\SUBOOT
           directory of NT Server to the Windows 95 Workstation,
           then run the following command at the Windows 95 Workstation.

           Edit REGISTRY.TXT file by searching and replacing "client1"
           with "client2", replacing "d:\\winboot" with "e:\\winboot"
           and replacing "ne2000.dos" with "dm9pci.dos".

           At the NT Server:

             COPY C:\WINNT\RPL\CLIENTS\CLIENT2\SUBOOT\SYSTEM.DAT A:\

           At the Windows 95 Workstation (At Windows 95 DOS Prompt Mode):

             COPY A:\SYSTEM.DAT C:\
             REGEDIT /L:SYSTEM.DAT /E REGISTRY.TXT
             EDIT REGISTRY.TXT
             REGEDIT /L:SYSTEM.DAT /C REGISTRY.TXT
             ATTRIB -R -S -H SYSTEM.DAT
             COPY C:\SYSTEM.DAT A:\

           At the NT Server:

             COPY A:\SYSTEM.DAT C:\WINNT\RPL\CLIENTS\CLIENT2\SUBOOT

      (17) 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 CLIENT2\SUBOOT directory
           to PROFILES\WDM9102\SUBOOT directory.

             WIN95CLT.BAT \WINNT\RPL\CLIENTS\CLIENT2 \\NT40SRV WDM9102

      (18) At the NT Server, change the directory to the \WIN95SRC
           directory to edit the MACHINES.INI file and add the following
           lines for the new clients.

             [00606E00E925]
             SYSDATPATH=G:\CLIENT2
             G=\\NT40SRV\CLIENTS

      (19) Power OFF the Remote Boot Workstation, remove the ISA Ethernet
           Adapter, plug the RPL BootROM into DM9102 PCI Fast Ethernet
           Adapter and plug DM9102 PCI Fast Ethernet Adapter into
           the Remote Boot Workstation PCI slot.

      (20) Reboot the Remote Boot Workstation, the RPL BootROM will
           try to remoteboot from the Remote Boot NT server.

      (21) 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 DAVICOM DM9102" from "Wksta In Profile"
           item then specify the New Workstation Name, click "Add" button.

      (22) 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.

      (23) Now the Remote Boot Workstation will remoteboot to Windows 95
           from the Remote Boot NT Server by using DM9102 RPL BootROM,
           and specify Username and Password to logon the Remote Boot
           NT Server.


D-1. W95BB.CNF Sample File for DM9102 :
=======================================

      ; Windows 95 on DAVICOM PCI Fast Ethernet Adapter (DM9102)
      BASE D0H
      RPL BBLOCK\RPLBOOT.SYS
      LDR BBLOCK\RPLSTART.COM ~
      DAT BBLOCK\NETBEUI\dm9pci\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\dm9pci.DOS ~ ~ ~
      DRV BBLOCK\PROTMAN.DOS /I:C:\LANMAN.DOS ~ M
      EXE BBLOCK\W95I13.COM ~ ~ ~


D-2. MSDOS.SYS Sample File for DM9102 :
=======================================

      [Paths]
      WinDir=g:\client2
      WinBootDir=e:\winboot     <== According to RAMDRIVE.SYS assign
      HostWinBootDrv=C              Virtual Drive (D: or E:)

      [Options]
      BootMulti=1
      BootGUI=1
      Network=1
      LoadTop=0
      Logo=0


D-3. CONFIG.SYS Sample File for DM9102 :
========================================

      DEVICE=c:\HIMEM.SYS /testmem:off
      device=c:\ramdrive.sys 1440 /E
      devicehigh=c:\ifshlp.sys
      lastdrive=z
      STACKS=16,512


D-4. AUTOEXEC.BAT Sample File for DM9102 :
==========================================

      @if not exist e:\winboot\nul mkdir e:\winboot
      @copy c:\ e:\winboot
      e:
      cd \winboot


D-5. WIN.BAT Sample File for DM9102 :
=====================================

      @echo off
      set comspec=e:\winboot\command.com
      nwrpltrm
      fixmem
      snapshot /S /B:d
      setmdir /m /r:e:\winboot
      net start
      net logon client2 /savepw:no  /y
      net use F: \\NT40SRV\WIN95SRV
      net use G: \\NT40SRV\CLIENTS
      PATH=F:\;F:\COMMAND;g:\client2\system;
      setmdir
      set comspec=e:\winboot\command.com
      win.com


D-6. PROTOCOL.INI Sample File for DM9102 :
==========================================

      [NETBEUI$]
      DriverName=NETBEUI$
      Lanabase=0
      sessions=10
      ncbs=12
      Bindings=DM9PCI$

      [nwlink$]
      DriverName=nwlink$
      Frame_Type=4
      cachesize=0
      Bindings=DM9PCI$

      [DM9PCI$]
      DriverName=DM9PCI$

      [protman$]
      priority=ndishlp$
      DriverName=protman$

      [ndishlp$]
      DriverName=ndishlp$
      Bindings=DM9PCI$

      [data]
      version=v4.00.950
      netcards=DM9PCI$,PCI\VEN_1282&DEV_9102


D-7. MACHINES.INI Sample File for DM9102 :
==========================================

      ;Windows 95 MACHINES.INI
      ;[node address]
      ;SYSDATPATH=x:\<home directory>
      ;x=\\server\share

      [0000E8318587]
      SYSDATPATH=g:\client1
      g:=\\nt40srv\clients

      [00606E00E925]
      SYSDATPATH=g:\client2
      g:=\\nt40srv\clients


E-1. MSDOS.SYS Sample File for NE2000 :
=======================================

      [Paths]
      WinDir=g:\client1
      WinBootDir=d:\winboot
      HostWinBootDrv=C

      [Options]
      BootMulti=1
      BootGUI=1
      Network=1
      LoadTop=0
      Logo=0


E-2. CONFIG.SYS Sample File for NE2000 :
========================================

      DEVICE=c:\HIMEM.SYS /testmem:off
      device=c:\ramdrive.sys 1440 /E
      devicehigh=c:\ifshlp.sys
      lastdrive=z
      STACKS=16,512


E-3. AUTOEXEC.BAT Sample File for NE2000 :
==========================================

      @if not exist D:\winboot\nul mkdir D:\winboot
      @copy c:\ D:\winboot
      d:
      cd \winboot


E-4. WIN.BAT Sample File for NE2000 :
=====================================

      @echo off
      set comspec=d:\winboot\command.com
      nwrpltrm
      fixmem
      snapshot /S /B:d
      setmdir /m /r:d:\winboot
      net start
      net logon client1 /savepw:no  /y
      net use F: \\NT40SRV\WIN95SRV
      net use G: \\NT40SRV\CLIENTS
      PATH=F:\;F:\COMMAND;g:\client1\system;
      setmdir
      set comspec=d:\winboot\command.com
      win.com


E-5. PROTOCOL.INI Sample File for NE2000 :
==========================================

      [NETBEUI$]
      DriverName=NETBEUI$
      Lanabase=0
      sessions=10
      ncbs=12
      Bindings=MS2000$

      [nwlink$]
      DriverName=nwlink$
      Frame_Type=4
      cachesize=0
      Bindings=MS2000$

      [MS2000$]
      DriverName=MS2000$
      Interrupt=3
      IOBase=0x300

      [protman$]
      priority=ndishlp$
      DriverName=protman$

      [ndishlp$]
      DriverName=ndishlp$
      Bindings=MS2000$

      [data]
      version=v4.00.950
      netcards=MS2000$,*PNP80D6


E-6. MACHINES.INI Sample File for NE2000 :
==========================================

      ;Windows 95 MACHINES.INI
      ;[node address]
      ;SYSDATPATH=x:\<home directory>
      ;x=\\server\share

      [0000E8318587]
      SYSDATPATH=g:\client1
      g:=\\nt40srv\clients



<<< End of file >>>

server: web1, load: 0.97