October 1995
D-Link Corporation
Readme for the DE-224C Rev.1.0 boot ROM
========================================
Copyright (c) 1995 by D-Link Corporation. All rights reserved.
Product name : DE-224C Rev.1.0
Boot ROM size : 16K
Supported adapters : DE-220 family adapters
Functions :
With this Boot ROM insert on the DE-220 family adapters, it can act as remote
booting devices for your PCs or diskless workstation to connect to the
network.
Boot Server and Boot ROM cross reference table:
ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ»
º Boot Server and Boot ROM Table º
ÇÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÂÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄĶ
º Boot Server ³DRV ³DOS/OS2³ D-Link Boot ROM type º
ÇÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÅÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄĶ
º ³LANsmart ³ ³ ³ ³ º
º D-Link ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´IPX ³ ³ ³ º
º ³NetWare 2.2 (Bootsrv,vap) ³ ³ ³ ³ º
ºSuperBootÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³ ³ ³ º
º Program ³NetWare 3.1x (Bootsrv,nlm) ³ ³ ³ ³ º
º ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³ ³ ³ º
º ³NetWare 4.x (Bootsrv4.nlm) ³ ³ All ³ ³ º
ÇÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³ DOS ³ ³ º
º ³ ³NW 2.2 Server ³ ³version³ DE-224A ³ º
º ³ NCP ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³ ³ v1.03 ³ º
º ³802.3³NW 3.1x Server ³ ³ ³ ³ º
º ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³ ³ ³ º
º ³ ³NW 4.x Server ³ ³ ³ ³ º
º NetWare ÃÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄ´ ÃÄÄÄÄÄÄ¿ ³ º
º ³ ³NW 2.2 (RPL.vpl) ³ ³ ³ ³ ³DE-224Cº
º ³ RPL ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ODI ³ ³ ³ ³ v1.0 º
º ³802.2³NW 3.1x (RPL.nlm) ³ ³ ³DE-224³ ³ º
º ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³ ³ ³ ³ º
º ³ ³NW 4.x (RPL.nlm) ³ ³ ³ ³ ³ º
ÇÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÅÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÅÄÄÄÄÄÄÄ´ ³ ³ º
º ³ ³OS/2 ³ NOS ³ ³ ³ ³ ³ º
º ³ ÃÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³ ³ ³ ³ º
ºMicrosoft³ RPL ³v1.3 ³Lan Manager V2.1³ ³ ³ ³ ³ º
º ³ ÃÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³ ³ ³ ³ º
º ³ ³v1.3 ³Lan Manager V2.2³ ³ ³ ³ ³ º
ÇÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÅÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´NDIS³ All ³ ³ ³ º
º ³ ³OS/2 ³ NOS ³ ³DOS/OS2³ ³ ³ º
º ³ ÃÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³version³ ³ ³ º
º ³ ³v1.3 ³LanServer V2.0³ ³ ³ ³ ³ º
º ³ ÃÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³ ³ ³ ³ º
º IBM ³ RPL ³v2.1 ³LanServer V3.0³ ³ ³ ³ ³ º
º ³ ÃÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³ ³ ³ ³ º
º ³ ³v2.1T³LanServer V3.0³ ³ ³ ³ ³ º
º ³ ÃÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³ ³ ³ ³ º
º ³ ³v2.1 ³LanServer V4.0³ ³ ³ ³ ³ º
ÈÍÍÍÍÍÍÍÍÍÏÍÍÍÍÍÏÍÍÍÍÍÏÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÏÍÍÍÍÏÍÍÍÍÍÍÍÏÍÍÍÍÍÍÏÍÍÍÍÍÍÍÏÍÍÍÍÍÍͼ
Using DE-224C in Netware NCP environment:
=========================================
1. The philosophy of design
- Check if floppy drive A: has floppy diskette, then boot from drive A:
- If no floppy diskette in A:, check the user has hard disk or not.
If no hard disk, boot from network.
- With hard disk, the program will ask "Boot from network (Y/N) ?"
Yes, boot from the network.
No, boot from the hard disk.
2. Supported servers
1> D-Link SuperBoot Server
. Search for D-Link SuperBoot Server
2> Netware boot servers
. Search for Netware NCP server using Ethernet_802.3 frame type
(default)
3> Auto
. Search for D-Link SuperBoot Server
. Search for Netware NCP server using, Ethernet_802.3 frame type
NOTE: Novell Netware NCP support ETHERNET_802.3, ETHERNET_II frame type
Troubleshooting:
----------------
1. If remote boot function doesn't work, please ...
. Check the boot ROM has been plugged in correctly or not.
. Check the NIC's remote boot function is enabled or not.
. Select a ROM address that does NOT conflict with other devices.
. Select correct ROM size in the adapter's SETUP program.
. Cold start your system again (Turn off/on your PC again).
. If it still doesn't work, contact with your local dealers.
2. If find D-Link superboot system failure, Please ...
. Check the D-Link superboot server is enabled or not. please refer to
the superboot system manual.
. Check superboot system BOOT VOLUME and USER configurations.
. If it still doesn't work, contact with your local dealers.
3. If find Netware NCP boot server failure,
a) If error message is "Error initializing Network Interface Board."
please ....
. Check is this board conflict with other devices or not?
. Please execute adapter diagnostic program to verify.
. If it still doesn't work, contact with your local dealers.
b) If error message is "Error finding server", please ...
. Check whether the Netware boot server is on-line or not.
. Make sure adapter is working properly.
. Check the server is using the right frame type.
. If it still doesn't work, contact with your local dealers.
c) If error message is "Error opening boot disk image file." or
"Error reading boot disk image file.", please ...
. Check Netware BOOT VOLUME. Please use DOSGEN to generate a
boot volume (default is NET$DOS.SYS). Refer to Netware manual for
more details.
. Check BOOTCONF.SYS and NET$DOS.SYS files in \LOGIN directory.
. If you are using DOS v5.0, DR DOS v6.0 or above, execute
RPLFIX utility as follows,
> RPLFIX NET$DOS.SYS <CR>
Note: DOSGEN utility is in SYS:\SYSTEM subdirectory.
RPLFIX utility is provided by Novell.
d) If remote boot from server is still failure, please ...
. Check to see if boot volume has bootable function or not.
Using DE-224C in RPL environment:
=================================
1. The philosophy of design
The same with NCP Procedure of DE-224C
2. Supported servers are:
1> Netware RPL Server
. Boot from Netware RPL Server
2> IBM LAN Server 3.0
. Boot from IBM LAN Server 3.0
3> IBM LAN Server 4.0
. Boot from IBM LAN Server 4.0
4> MS LAN MAN Server
. Boot from MS LAN MAN Server
5> MS NT 3.5 Advance Server
. Boot from MS NT3.5 Advance Server
6> DEC Pathwork
. Boot from DEC Pathwork
7> The first available server
. The program will find the server in the network which responds
first.
Boot ROM Menu:
--------------
1. When Boot ROM activate and start, it will show the following message,
" D-Link .........." as to show D-link trade mark.
2. Then Boot ROM will check whether floppy drive A: have bootstrap or not.
If there is no bootstrap on drive A:, it will check whether hard disk
exist or not.
3. If hard disk exists, it will show the message,
" Do you want to boot from NETWORK (y/n) ? "
4. If you selected "y" , it will show the message,
" What server will been found , Please select a number which you want."
" If no key mapping, system will AUTO find server After 3 seconds "
" 1. D-Link Superboot "
" 2. Netware NCP "
" 3. RPL "
You can select one of the above three items,
If one choose "1": It will find D-link Superboot server, and boot from
it. If there was no Superboot server, it will find
Netware NCP server using Ethernet_802.3 frame type.
If one choose "2": It will find Netware NCP Server using Ethernet_802.3
frame type, and boot from it.
If one choose "3": It will find any RPL server, and boot from it,
where RPL server includes:
. Netware Server with RPL protocol
. IBM LAN Server 3.0
. IBM LAN Server 4.0
. MS LANMAN
. MS NT 3.5 Advance Server
Troubleshooting:
================
1. If remote boot function doesn't work, please ...
. Check the boot ROM has been plugged in correctly or not.
. Check the NIC's remote boot function is enabled or not.
. Select a ROM address that does NOT conflict with other devices.
. Select correct ROM size in the adapter's SETUP program.
. Cold start your system again (Turn off/on your PC again).
. If it still doesn't work, contact with your local dealers.
2. If find IBM LAN SERVER failure, please ...
. Check whether the LAN SERVER net started successfully or not.
. Check the LAN SERVER support remote boot function or not.
. Check the machine ID has been created.
. Check the RPL server has been created.
. Please refer to the IBM LAN SERVER manual.
. For IBM LAN Server 4.0, one must use IRQ9 for Boot ROM
3. If find NetWare RPL boot server failure, please ...
. Check whether the Netware server is on-line or not.
. Make sure adapter is working properly.
. Make sure the Netware server support RPL and IPX interface.
. Make sure the Netware server support ETHERNET_802.2 frame type.
. Load drivers as follows:
:LOAD xxx.LAN frame=ethernet_802.2
:LOAD RPL.NLM
:BIND IPX to xxx.LAN net=yyy
:BIND RPL to xxx.LAN
NOTE: Netware RPL only support ETHERNET_802.2 frame type
. If it still doesn't work, contact with your local dealers.
4. If remote boot from server failure, please
. Check the boot volume has bootable function or not.
5. If find MS LANMAN failure, please ...
. Check whether the LANMAN net started successfully or not.
. Make sure the LANMAN support remote boot function.
. Check the remoteboot configurations for new adapters have
been created correctly.
. Check the machine ID has been created.
. Check the IPL server has been created.
. Please refer to the MS LANMAN manual.
Note:
1. RPL (RIPL) : Remote Initialization Program Loader.
2. Netware RPL server, IBM LAN Server 3.0, IBM LAN Server 4.0,
and MS LAN MAN server all follow the RPL specifications.
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.