NETWARE.TXT Driver File Contents (

                 Accton Technology Corporation
       Ethernet Remote Boot Rom for Netware Operation System

Accton adapters provide an empty socket for installing the
optional Boot ROM device. Once installed, the adapter is
able to load DOS from server. This is useful for using
the adapter in a diskless workstation. Two types of Boot
ROMs available. They are IPX boot rom and RPL boot rom.

 I)  : Ethernet Remote Reset Boot ROM (IPX Boot ROM)
         - Supports the NetWare IPX workstation

 II) : Generic Boot ROM (RPL Boot ROM)
         - Supports NetWare 3.x, 4.x and Microsoft
           LAN Manager 2.x

 III): Using RPL Boot Rom for ND7 and PNW
         - ND7 : Novell DOS version 7
         - PNW : Novell Personal Netware version 1.0

I):    Using the Ethernet Remote Boot ROM (IPX Boot ROM)

The Ethernet Remote Reset Boot ROM is for NetWare

1. Generate a DOS Image

To allow remote booting, you should first generate a DOS image.
See the corresponding section in your NetWare manuals for detailed


This program is provided and developed by Novell to fix the bug
that causes boot failure when using MS-DOS 5.0 or DR DOS 6.0 or their later
versions. Users of MS-DOS 5.0 or DR DOS 6.0 MUST run this program after
generating the DOS image. Failure to do so will result in boot failure.

3. Auto-detect adapter configuration

Once you power on the host PC, the Boot ROM will automatically
detect the configuration of the network adapter installed.
The parameters detected will vary according to the type of network
adapter. Corresponding values will be shown on screen.
See Figures 1 and 2 for sample screen displays. For related
information, see section on "List of Adapter Parameters
Automatically Detected by the Boot ROM".

4. Follow screen instructions to select the appropriate
        Ethernet_Type if necessary.

See section on Ethernet Type Selection for more information.

Note: The program automatically detects the adapter's
                parameter settings, including Frame type, RAM Test,
                RAM Size, IRQ value, I/O base address,
                data width, Ethernet-ID

Ethernet Type Selection
The  Boot ROM device is compatible with both Ethernet_II  and
IEEE 802.3 Ethernet.

1. Upon power on the program automatically detects the
        adapter's configuration, and will display it on the screen.

2. When prompted to select a "frame type" choose an
        appropriate one for your adapter if necessary.
        For example, pressing "1" selects "Ethernet_II," while
        pressing "2" selects "802.3"

Additional RPLODI.COM

When you are building the DOS Image file, note that the logging in sequence is
different from booting from disk for IPX Boot ROM. Run RPLODI after LSL.COM is
loaded. The following procedures are the same. They may be NWMLID, IPXODI and
NETX. For Generic Boot ROM, the booting sequences are the same.

II):   Using the Generic Boot ROM (RPL Boot ROM)

Accton's Generic Boot ROM can be used with the following programs:

        * NetWare v3.x or later
        * Microsoft's LAN Manager 2.1 or later

Each platform has its own software installation and setup routine.
The diskette that comes with the ROM kit has drivers for the different
network environments.

Generic Boot ROM Installation for NetWare v3.x
1. Install the NetWare Server RPL software.
2. Prepare a blank diskette for the remote reset image.
3. Create the server image boot file.
4. Boot your workstation.

        Installing the NetWare Server RPL Software
        a. "Load" a server LAN driver and be sure to specify the
            frame type that your workstation is going to use.
        b. "Bind" IPX to each of the different frame types
            (ETHERNET_802.2, ETHERNET_802.3, ETHERNET_II,
            ETHERNET_SNAP) that you require.
        c. "Load" RPL.NLM
        d. "Bind" RPL to the LAN driver and appropriate frame type

  Preparing a blank diskette for the remote boot image
  a. Label a blank diskette "Remote Image"
  b. From your root directory, type
     format a: /s
  c. Files needed on the remote image include the

          * For an IPX workstation, you will need the
                 IPX.COM (generated using Accton's driver or NE2000),
                 and the NETX.COM files
          * For the DOS ODI workstation with NetWare v3.x:
          NWMLID.COM (or NE2000.COM)
          NETX.COM (or EMSNETX.EXE)
          * For the DOSODI workstation with NetWare v4.x:
          NWMLID.COM (or NE2000.COM)
          * Other files necessary are:
          AUTOEXEC.BAT  (user defined)
          CONFIG.SYS (user defined) and
          other file you may deem necessary
          All NetWare VLM files for workstation NET.CFG

  Creating the server image boot file
  Refer to the sections entitled "Customizing Remote Boot Files"
  and "Creating the BOOTCONF.SYS Boot Files" in your NetWare
  documentation for details. A brief procedure follows:

  1. Log onto the network as "supervisor"  for the NetWare
          v3.x server; or as "admin" for the NetWare v4.x server.
  2. Map to your network server. Type: MAP F:=SYS:LOGIN
  3. Insert the Remote Reset Image diskette in the drive A
          of the workstation.
  4. Change to F: and type:
  5. Using DOSGEN create the file "NET$DOS.SYS":


  6. Flag the NET$DOS.SYS as sharable and run RPLFIX if you're
          using MS-DOS 5.0 or the later versions.

III):  Using RPL Boot Rom for ND7 and PNW
       ND7 : Novell DOS version 7
       PNW : Novell Personal Netware version 1.0

A..Installing the Server:

1. To set up a PERSONAL NetWare Server to allow diskless workstations
(as Accton LanStation-486) to use it as an RPL server, first perform a
standard installation of Novell DOS 7 or Personal NetWare.  From this point,
there is no difference between DOS 7 and PERSONAL NetWare with regard
to the configuration of the server system.

2. Run SETUP and instruct the system to share its resources.  This
will initiate the use of the PERSONAL NetWare Server software.

3. You will also need to define the network board you will be using
and the configuration of the board.  Ensure that the network board is
configured to use the ETHERNET_802.2 frame type if it is an Ethernet

4. After the network parameters have been defined, restart the
system.  When the system boots back up, it will automatically run the
PERSONAL NetWare SETUP to configure each Workgroup for your newly
created Server.  Complete all the configuration of the server.

5. The next step allows the disk boot image files to be created
with the minimum of files.  As part of the boot process, a shared
directory called LOGIN must exist.  This resource is required by the
RPL boot load process to get the Boot image files from.

6. You must also have access to the network utilities.  The best
way to achieve this is to rename the C:\NWCLIENT directory to C:\LOGIN
and change the references to NWCLIENT in the AUTOEXEC.BAT and
STARTNET.BAT files accordingly.

7. You will also need to add RPL.COM and NEARSERV.COM commands to
the STARTNET.BAT file. These two files are responsible for responding
to requests from diskless workstations.  RPL.COM will transmit the
primary loader utility to the workstation, the *.RPL file.  The loader
will then download the boot image file.  NEARSERV.COM enables the
server machine to respond to the GET NEAREST SERVER requests from the

8. Next, create the shared directory called LOGIN and point it to
the C:\LOGIN directory marked READ ONLY. Then copy the files from
C:\LOGIN\RPL into the C:\LOGIN directory.

   You will should now have a STARTNET.BAT file that looks like the following:

                @ECHO OFF
                CD C:\LOGIN
                LH LSL
                LH <Network Card Driver Name> as NWMLID.COM
                LH IPXODI
                LH RPL
                LH SERVER
                LH NEARSERV
                CD \
                NET LOGIN

At this point, you should have the server configured to operate as
a PERSONAL NetWare server that is able to respond to RPL requests and
is also usable as a workstation.

B..Creating the Boot Disk Image File

The next step is build the image files that the diskless workstations
will use.  Multiple image files can be created (see RPLDOC.TXT file).

1. The first step in creating this file is to create a bootable
floppy diskette by formatting a diskette with the /s option, to
transfer over the system files.  On this diskette, copy the following

                <Workstation Driver>.COM as NWMLID.COM

  These files can be found in the \LOGIN subdirectory of the server
you have created earlier.  You will also need to copy any of the DOS
files you will need during the boot up sequence, such as EMM386.EXE,

2. Create a suitable CONFIG.SYS file for the Boot Diskette.  This
file could appear as follows:

                DEVICE=a:\EMM386.EXE DPMI=OFF FRAME=NONE
                SHELL=A:\COMMAND.COM A:\ /E:512 /P

3. Now create a suitable AUTOEXEC.BAT, such as the following:

                @ECHO Off
                PATH A:\
                VERIFY OFF
                PROMPT [Novell DOS] $P$G
                HILOAD LSL
                HILOAD NWMLID
                HILOAD IPXODI

4. You will also now need to modify the NET.CFG file to reflect the
I/O port configuration of the board, the Interrupt line of the board,
and the FIRST NETWORK DRIVE.  If the workstation is to have a floppy
disk drive, then this parameter will be the C: drive.  If there is no
floppy disk drive, then this parameter will be the A: drive.


                Link driver NWMLID
                     FRAME Ethernet_802.2

                NetWare DOS Requester
                FIRST NETWORK DRIVE = C
                NETWARE PROTOCOL = PNW
                SHOW DOTS = ON
                USE DEFAULTS = ON
                VLM = AUTO.VLM

5. After this diskette has been created, try to boot it on a system
connected to the PERSONAL NetWare Server to ensure that it functions
correctly.  When the system boots correctly, then go to the \LOGIN
subdirectory on the server and type the following command:

                DOSGEN A:

   This command generates the Boot image file NET$DOS.SYS, which is
used to boot up the diskless workstation.  You also need to copy the
AUTOEXEC.BAT file from the diskette into the \LOGIN subdirectory;
because when the VLM loads, the disk image file is no longer visible
to the workstation, which now points at the \LOGIN subdirectory.

6. You then need to edit the C:\LOGIN\AUTOEXEC.BAT file to make it
read as follows:

                @ECHO Off
                PATH A:\
                VERIFY OFF
                PROMPT [Novell DOS] $P$G
                HILOAD LSL
                HILOAD NWMLID
                HILOAD IPXODI
                NET LOGIN SUPERVISOR
                NET MAP Z:=LOGIN
                Z:NET MAP C:=SERVER_DRVC

7. The final step is to create a BOOTCONF.SYS file that lists list
all the workstation nodes on the network that must boot from the
server.  This file is required, because it instructs the server to
respond to requests from the workstations.  Without an entry in this
file, the following error message will be shown on the workstation.


                RBOOT-RPL-100: Unable to CONNECT to File Server: RPL Halted

        Format the BOOTCONF.SYS file as shown:

                Ox<Network Card Node Address>=NET$DOS.SYS,GNS
                Ox<Network Card Node Address>=NET$DOS.SYS,GNS
                Ox<Network Card Node Address>=NET$DOS.SYS,GNS


  Note: The network card address can be found by booting the system
with the diskette, running NET INFO, and using the hexadecimal number
shown next to the machine address.

8.Reboot the PERSONAL NetWare server and load the network
software.  Now, by rebooting, the workstation should connect to the
server, download the NET$DOS.SYS file, load DOS, login to the server,
and map drives.

Quick Troubleshooter Tips

1. Make sure all systems are using the correct frame types.

2. Make sure the workstation has the correct entry in the

3. Make sure the diskette used to create the Boot Image files
   correctly boots.

4. Make sure all the required files are loaded on the Server.

5. Read the RPLDOC.TXT file copied during the INSTALL.


Download Driver Pack

How To Update Drivers Manually

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.

server: web3, load: 0.55