(C)Copyright 1995-1997 SysKonnect,
a business unit of Schneider & Koch & Co. Datensysteme GmbH.
All rights reserved
==========================================================================
BOOTFP.TXT

Readme File for BOOTFP.ROM

	SK-NET FDDI PCI DLI Boot ROM Driver v4.00 Rev. D (970319)

March 19, 1997

==========================================================================


This file contains
(1) Overview
(2) Supported Adapters
(3) Required Files
(4) Installation Instructions
(5) Creating the Remote Boot Image File
(6) Disabling the Remote Boot ROM Software
(7) Troubleshooting

===========================================================================


(1) OVERVIEW
============

This README explains how to install the configurable Remote Boot ROM
Software file BOOTFP.ROM.

The BOOTFP.ROM file contains software that can be downloaded into the
on-board FPROM (Flash Programmable Read Only Memory) of the
SK-NET FDDI PCI adapter. The workstation in which the adapter is
installed can then be booted remotely from a NetWare file server.

The BOOTFP.ROM file can be configured with the Remote Boot ROM
Configuration utility SKROMCFG. However, a default configuration has been
selected for BOOTFP.ROM before delivery. See the README file
SKROMCFG.TXT that comes with SKROMCFG for further information on how to
configure the Remote Boot ROM Software before downloading it into the FPROM
of the adapter.
***


(2) SUPPORTED ADAPTERS
======================

The BOOTFP.ROM Remote Boot ROM Software supports the following
adapters of the SysKonnect FDDI network adapter family:

	SK-NET FDDI PCI
***


(3) REQUIRED FILES
==================

The following files are required for the SK-NET FDDI PCI adapter:

	BOOTFP.ROM	The Remote Boot ROM Software
	SKDIAGFP.EXE	The Diagnostics tool
or
	FLASHFP.EXE	The Flash Programmer tool
***


(4) INSTALLATION INSTRUCTIONS
=============================

Two different methods are available to download the Remote Boot ROM
Software file BOOTFP.ROM into the FPROM:

	a) Using the Diagnostics tool SKDIAGFP.EXE
or
	b) Using the Flash Programmer tool FLASHFP.EXE

Although it is more convenient to use the interactive Diagnostics tool
SKDIAGFP, the FPROM Programmer tool FLASHFP allows downloading
the Remote Boot ROM Software from a batch file or login script. Thus, if
many workstations with SK-NET FDDI PCI adapters are to be updated, the
update process can be automated with FLASHFP.

Both of the available methods are described below.

Note:	The Remote Boot ROM Software file BOOTFP.ROM can optionally
	be configured to meet your special needs with the Remote Boot ROM
	Configuration utility SKROMCFG.EXE. See the README that comes with
	SKROMCFG for further information on how to configure the Remote
	Boot ROM Software.

	Note that configuring BOOTFP.ROM with SKROMCFG must be done
	*before* BOOTFP.ROM is downloaded into the adapter's FPROM.


Using the Diagnostics Tool
--------------------------

The following describes how to download the Remote Boot ROM Software file
BOOTFP.ROM into the FPROM of the SK-NET FDDI PCI adapter by
using the Diagnostics tool SKDIAGFP.EXE. For further information on
SKDIAGFP, see the README that comes with this program.

Step 1:	Copy SKDIAGFP.EXE and BOOTFP.ROM to the current
	directory.

Step 2:	Start SKDIAGFP with the following command:

		SKDIAGFP [option(s)] <Enter>

	The following command line options are available:

		-b	PCI bus number
		-d	PCI device number
		-s	PCI device index number ("slot")
		-l	list all SK-NET FDDI PCI adapters

	Note:	If only one SK-NET FDDI PCI adapter is installed,
		SKDIAGFP will automatically use this adapter. If,
		however, more than one adapter is installed, the device
		index or bus/device number of the desired adapter must
		be specified.

		Use the "-l" option to get a list of all installed
		SK-NET FDDI PCI adapters in your system.

Step 3:	From the "Main menu" select "Flash PROM ...".

Step 4:	From the "Flash PROM" menu select "Load Flash PROM from File".

Step 5:	Enter BOOTFP.ROM for the name of the Remote Boot ROM Software
	file when prompted "Filename :" and press <Enter>.

	Note:	BOOTFP.ROM must be in the current directory. You
		cannot enter a path.

Step 6:	Press <Enter> when prompted "Do you really want to destroy Flash
	PROM contents ?".

	SKDIAGFP will now download the selected file into the
	adapter's FPROM.

Step 7:	When the FPROM download process is complete, you will be prompted
	"*** Press any key to continue ***". Press any key and <Esc> twice
	and then <Enter> when prompted "Terminate Program" to exit
	SKDIAGFP.

		------------------------------------------------
				IMPORTANT NOTE

		Some PCI systems do not automatically recognize
		the newly installed Remote Boot ROM Software. In
		this case, refer to the section
		"Troubleshooting" at the end of this file.
		------------------------------------------------

Step 8:	Continue under the heading "Creating the Remote Boot Image File"
	below.


Using the Flash Programmer
--------------------------

The following describes how to download the Remote Boot ROM Software file
BOOTFP.ROM into the FPROM of the SK-NET FDDI PCI adapter by
using the Flash Programmer tool FLASHFP.EXE. For further information
on FLASHFP, see the README that comes with this program.

Note:	FLASHFP can be used to automatically update the FPROMs of
	SK-NET FDDI PCI adapters, e.g. when started from the login
	script on the file server. If you want to use this method, please
	note the following:

	1. The FPROM should only be loaded *once* with the new Remote Boot
	ROM Software, i.e. there should be some mechanism that avoids
	downloading the FPROM again with the same data (see the example
	below).

	2. If the DLI is already loaded when FLASHFP is started, you
	must...
	a) ...use a DLI with hardware driver v3.00 Rev. C or higher.
	b) ...specify the option "-r" for FLASHFP.
	Otherwise, the workstation will hang and the contents of the FPROM
	will be left unchanged.

Step 1:	Start FLASHFP with the following command:

		FLASHFP [option(s)] -pBOOTFP.ROM <Enter>

	The following command line options are available:

		-p	path to the file to be downloaded into the FPROM
		-r	remote option (must be used if DLI loaded)
		-n	do not produce any output (quiet mode)
		-s	PCI device index number

	Note:	If only one SK-NET FDDI PCI adapter is installed,
		SKDIAGFP will automatically use this adapter. If,
		however, more than one adapter is installed, the device
		index number of the desired adapter must be specified.

		------------------------------------------------
				IMPORTANT NOTE

		Some PCI systems do not automatically recognize
		the newly installed Remote Boot ROM Software. In
		this case, refer to the section
		"Troubleshooting" at the end of this file.
		------------------------------------------------

Step 2:	Continue under the heading "Creating the Remote Boot Image File"
	below.


The following gives an example on how to automatically update the FPROMs of
SK-NET FDDI PCI adapters. The example assumes that you have SUPERVISOR
rights on your NetWare file server.

	1. In the system login script, assign the adapter's physical
	station address to an environment variable, e.g.

		DOS SET PS="%P_STATION" << 4

	If the adapter's address is 00005A401234, then the above command
	sets the environment variable "PS" to the value "5A401234".

	2. Create a new directory, e.g. SYS:PUBLIC/FPROM and grant at least
	the rights "create" and "write" to the group EVERYONE. Map drive H:
	to this directory (e.g. in the system login script).

	3. Copy FLASHFP.EXE and BOOTFP.ROM to the new directory.

	4. Call a DOS batch file, similar to the following:

		h:
		cd \PUBLIC\FPROM
		IF EXIST %PS% GOTO DONE
		FLASHFP -r -pBOOTFP.ROM
		ECHO.>%PS%
		:DONE

	Note:	If you need more options for FLASHFP, add them to the
		command line in this example batch file.

The list of files in the SYS:PUBLIC/FPROM directory gives an overview of
which adapters' FPROMs have already been updated.
***


(5) CREATING THE REMOTE BOOT IMAGE FILE
=======================================

Before the machine can be booted remotely from a NetWare file server, a
Remote Boot Image file must be generated on the file server.

Step 1:	Copy all the files you will need to boot your machine onto a
	bootable system disk. Edit the CONFIG.SYS, AUTOEXEC.BAT and NET.CFG
	as required. Below is an example of how these files may look:


	AUTOEXEC.BAT	CONFIG.SYS		NET.CFG
      * uppsfp -o	himem.sys		Link Driver UPPSMLID
	lsl		emm386 x=cc00-ce00	  Frame FDDI_SNAP
     ** rplodi		buffers=20		  Protocol IPX 8137 FDDI_SNAP
	uppsmlid	files=50
	ipxodi		lastdrive=e
	netx
	f:

	 * The "-o" parameter must be included if the DLI driver is being
	   loaded remotely.

	** When booting remotely the Novell tool RPLODI must be loaded
	   before the UPPSMLID.


	Care must be taken to avoid using paths und sub-directories when
	creating the boot disk that will be used for the remote boot image
	file. The boot disk should be tested on a workstation with a floppy
	drive before the boot image file is created. The RPLODI will
	display an error message but it can be ignored at this time.

Step 2:	After the disk has been successfully tested, the remote boot image
	file can be generated using the Novell tool DOSGEN, for example

		E:\SYSTEM\DOSGEN.EXE A: F:\LOGIN\NET$DOS.SYS

	A remote boot image file will be generated using the files located
	on the disk in floppy drive A: and copied into the LOGIN directory
	of the Novell file server. The boot image default name is
	NET$DOS.SYS. For further information pertaining to the creation and
	use of Novell boot disk image files, please see the respective
	NetWare reference manuals.

	Note:	If DOS v5.0 or higher is being used, the boot disk image
		file must be patched with the program RPLFIX that is
		included with the NetWare package.

Step 3:	Set the attributes of the remote boot image file to "shareable":

		FLAG F:\LOGIN\NET$DOS.SYS S

Step 4:	Copy the file AUTOEXEC.BAT in the server's LOGIN directory.

Step 5:	Remove all floppy disks from the workstation's floppy disk drives
	and boot the workstation (press <Ctrl-Alt-Del>).

Step 6:	After a few seconds, the following startup message will appear:

	+----------------------------------------------------------------+
	|Press F1 to boot from network, F2 to boot from floppy/hard disk.|
	|								 |
	|Remaining seconds before auto-boot from network: 20		 |
	+----------------------------------------------------------------+

	Note:	If you have selected a custom configuration with the
		SKROMCFG tool, the startup message and/or startup behavior
		might be different.


The above prompt will be displayed with the following configurations:

	Configuration:			  |	Prompt
	----------------------------------+--------------------------------
	no floppy or harddisk		  |	NO
	(Diskless Workstation)		  |	(always boots from network)
					  |
	bootable floppy in		  |	NO
	drive A:			  |	(boots from disk A:)
					  |
	bootable harddisk		  |	YES
	(no bootdisk in A:)		  |	(boots from network, or
					  |	from harddisk)
					  |
	no bootable floppy		  |	NO
	in drive A:			  |	(Attempt to boot from drive A:)
					  |
***


(6) DISABLING THE REMOTE BOOT ROM SOFTWARE
==========================================

If you want to disable the Remote Boot ROM Software on your
SK-NET FDDI PCI adapter, you can use either the Diagnostics tool
SKDIAGFP.EXE or the Flash Programmer tool FLASHFP.EXE.

If you are using the Diagnostics tool SKDIAGFP, start the tool as
described in section "Installation Instructions - Using the Diagnostics
Tool" following steps 1 and 2. Then follow these steps:

Step 3:	From the "Main menu" select "Flash PROM ...".

Step 4:	From the "Flash PROM" menu select "Clear Flash PROM".

Step 6:	Press <Enter> when prompted "Do you really want to destroy Flash
	PROM contents ?".

	SKDIAGFP will now clear the adapter's FPROM.

Step 7:	When the FPROM clearing process is complete, you will be
	prompted "*** Press any key to continue ***". Press any key and
	<Esc> twice and then <Enter> when prompted "Terminate Program"
	to exit SKDIAGFP.

If you are using the Flash Programmer tool FLASHFP, enter the
following command:

	FLASHFP [option(s)] -e <Enter>

	Note: Other command line options might be required in order to
	specify the adapter and/or its configuration as described in
	section "Installation Instructions - Using the Flash
	Programmer".

		------------------------------------------------
				IMPORTANT NOTE

		Some PCI systems do not automatically recognize
		that the Remote Boot ROM Software has been
		removed and may therefore hang when rebooted.
		In this case, refer to the section
		"Troubleshooting" below.
		------------------------------------------------
***


(7) TROUBLESHOOTING
===================

Some PCI systems (e.g. COMPAQ) do not automatically recognize that the
content of the SK-NET FDDI PCI adapter's FPROM has been changed, i.e.
software has been added or removed as described in the previous sections.
The system may then show undesired behaviour, e.g. when rebooted:

	* software in the FPROM is not executed

	* system hangs

	* screen remains black

In any of the above cases, follow the instructions below.

Step 1:	Turn off system power and remove the SK-NET FDDI PCI adapter.

Step 2:	Turn on system power and boot the system. You might want to enter
	the system setup program during boot, if supported.

	If you have received any additional setup or configuration program
	with your system, run this program to make sure the system
	recognizes that the SK-NET FDDI PCI adapter has been removed.

	For instance, if your system also has an EISA bus, run the EISA
	configuration program.

Step 3:	Turn off system power and reinstall the SK-NET FDDI PCI
	adapter.

Step 4:	Turn on system power and boot the system.

	As in step 2, run any setup or configuration program again if
	required.


Black Screen
------------

The following steps are required only if your screen remained black during
system boot before you removed the SK-NET FDDI PCI adapter from your
system. In this case, the start address of the adapter's FPROM must be
configured such that it does not conflict with the VGA BIOS ROM address.

Step 1:	In the setup or configuration program (e.g. the EISA configuration
	program) select the SK-NET FDDI PCI adapter.

Step 2:	Select the "Memory Address" field and choose any FPROM start
	address above or equal to C8000h (the C0000h..C7FFFh range cannot
	be used because it is used by the VGA BIOS).

If the above steps cannot be executed on your system for some reason, it
may also help to lock the memory address of the VGA BIOS ROM, if possible.

*** End of information file ***