Flashstart Configuration Process
Note: You must run the FlashWorks Install utility and edit the LOAD and
BIND statements on the server prior to running FlashStart.
Install the board and turn on the computer.
FlashStart replaces the boot loader with the Flash RPL loader by
hooking INT19 (the boot loader interrupt) during POST so that when
it's time for the boot loader to execute the Flash RPL loader
Note: Flash memory is located at D0000-D1FFFF. There is potential
for compatibility problems if the computer's BIOS does something
out of the ordinary with INT19.
The FlashStart program executes from Flash and displays a "Note
About FlashStart" screen followed by a screen with these choices:
FLASHSTART FOR NetWare*
SKIP FLASHSTART THIS TIME
DISABLE FLASHSTART PERMANENTLY
Note: If the FlashStart welcome screen doesn't display, run
SOFTSET to ensure that the flash chip is enabled and that the flash
chip's memory address does not conflict with another device. If
you have previously disabled FlashStart, run FLRESTOR to re-enable
FlashStart. See the FlashWorks Utilities Complete guide for
information on FLRESTOR.
If you select "FLASHSTART FOR NetWare" the next screen displays a
message that FlashStart will now attach to the server.
FlashStart then sends a multicast (802.2 frame type) over the
network to find the server where RPL.NLM is loaded.
The screen will display a Novell RPL Boot ROM sign-on and an Intel
EtherExpress 16 MLID sign-on message followed by:
RPL-ROM-ADR: 00AA00123456 is the Flash card Ethernet address.
RPL-ROM-IRQ: 5 is the IRQ for the Flash card.
RPL-ROM-PIO: 340 is the Base I/O address for the Flash card.
RPL-ROM-FFC: xx is the multicast retry count.
Note: If no server is found, the FFC number keeps incrementing
indefinitely. Verify that both 802.2 and 802.3 frame types have
been loaded and bound at the server by typing CONFIG at the server
console prompt. Also verify that RPL has been loaded and bound to
the 802.2 frame type. Verify that the files NWFLASH.SYS and
BOOTCONF.SYS exist in the SYS:LOGIN directory. If they do not, run
INSTALL again. Use SOFTSET to verify that the correct connector
type was selected. Boot from a floppy disk and verify that you can
log into the server. If not, check your cabling and hardware
The RPL server Novell then displays a NetWare RPL Generic Bootstrap
Loader sign-on message followed by:
Note: When this process works correctly, the screen message is
displayed for only a fraction of a second. If IPX has not been
bound to the driver with the 802.2 frame type, the following error
UNABLE TO CONNECT TO FILE SERVER; RPL HALTED.
Check the LOAD and BIND statements on the server.
Once the connection is made to the Flash/RPL server, the
BOOTCONF.SYS file in the LOGIN directory on the Flash/RPL is
executed. (The BOOTCONF.SYS was created or appended to during the
FlashWorks Install utility.)
Note: At this point, control is transferred from the code in the
Flash chip to the server.
RPL will execute the line: 0x00000001,00AA000B059F=NWFLASH.SYS
0x00000001 is the network number of the 802.3 segment where
FlashWorks Install was run.
00AA000B059F is the FlashStart Ethernet address. This address
is not the real address of the card but a special one used
during the FlashStart process.
NWFLASH.SYS is the remote boot image file created during the
FlashWorks Install/DOSGEN process.
Note: If this line doesn't exist, RPL will check for a NET$DOS
file to execute. If a NET$DOS exists and it's configured for a
non-EtherExpress card, you will get an error message since these
files are adapter/hardware specific. If a NET$DOS exists and it's
configured for an EtherExpress card, it will execute as a standard
RPL workstation. The remaining part of FlashStart will not be
executed and no drivers will be downloaded to the workstation.
The Autoexec.bat file in the NWFLASH.SYS image file contains one
line that calls the NWFLASH.BAT file (also located in the LOGIN
directory and created by the FlashWorks Install/DOSGEN process).
This batch file initiates the FlashStart login.
Note: If you are using FlashWorks 1.5 and the image file was
created using a MS DOS 6.2 formatted disk or if you are using
FlashWorks 1.0 and the image file was created using a MS DOS 6.0 or
greater formatted disk, you will receive an error message when the
NWFLASH.BAT runs that you are not running on DOS 3.x to 5.x (or
6.0). See document 6280 for information on installing FlashWorks
with DOS 6.x.
When NWFLASH logs in, the system login script is run followed by a
user login script. The user login script sets up necessary drive
mappings and executes the FLSTART.EXE program. (FLSTART.EXE is in
the FLASH directory on the server). The user login script is a
standard login script which can be viewed and edited with SYSCON.
NWFLASH user login script:
MAP INS S16:=SYS:PUBLIC
Note: If there is anything in the system login script that will
prevent a user login script from executing (e.g. an EXIT command),
FlashStart will fail and the message "Extended Error 5" will be
displayed or FlashStart will exit to a DOS prompt. To allow
FlashStart to download network drivers, either remove the EXIT
command or put this conditional statement before the EXIT command
in the system login script:
If %LOGIN_NAME=NWFLASH THEN BEGIN
MAP INS S16:=SYS:PUBLIC
The RPL process is now complete.
One of two screens will now be displayed on the FlashStart
If both IPX and ODI were installed during the FlashWorks Install, a
"Select Diver" screen will be displayed. After you select either
IPX or ODI, a "FlashStart in progress" screen is displayed. This
screen will show which files are being copied from the server to
the workstation and the directory to where they are copied.
G:\Flash\Software\IPX\IPX.COM -> C:\IPX.COM
G:\Flash\Software\IPX\NETX.COM -> C:\NETX.COM
If either IPX or ODI (one but not the other) was installed during
the FlashWorks Install, the Select Driver screen is not displayed
and you are taken straight to the FlashStart in progress screen.
There are several hidden things that happen during the display of
the FlashStart in progress screen.
- The original Autoexec.bat file is saved as - Autoexec.old
- A new Autoexec.bat is created to include: IRQTEST and the
driver lines (IPX, NETX, etc.) at the beginning of the file
and DEL IRQTEST.EXE and COPY AUTOEXEC.PRN AUTOEXEC.BAT at the
file of the file.
- A final version of the Autoexec file is also created
(Autoexec.prn). This is the original Autoexec.bat with the
driver lines at the beginning of the file.
- IRQTEST is copied to the workstation's root directory. This
program tests for free IRQs and sets the EtherExpress card to
the first free IRQ it finds.
|Original Autoexec.bat Renamed to autoexec.old)
||(Final version of Autoexec.bat)
||DEL IRQTEST.EXE Copy autexec.prn autoexe.bat
Note: "DEL IRQTEST.EXE" and "COPY AUTOEXEC.PRN AUTOEXEC.BAT"
assume the root directory to be the C: drive. If there is a
statement in the AUTOEXEC.BAT file that changes the current
directory to a subdirectory or a different drive letter, these two
lines won't be executed properly.
After this is completed, a "FlashStart has been successful screen"
is displayed. When you press a key the computer will reboot and
the AUTOEXEC.BATt file that was set up in the previous step is
If FlashStart is interrupted or it fails, you will not get the
FlashStart successful screen.
When you reboot the computer, FlashStart will display a FlashStart
not successful screen and offer some suggestions. After this
screen, a SOFTSET like manual configuration screen is displayed.
This gives you the opportunity to change the hardware configuration
of the EtherExpress card before trying FlashStart again.
This applies to: