![[Intel Navigation Header]](/CONTENT/PIX/HEADER.GIF)
TokenExpress(TM) PRO Adapter: Troubleshooting Notes from Tech Support
Contents:
USING DOUBLESPACE
FlashStart won't work properly on computers using Doublespace with the
/move parameter.
PRODMI.EXE
Abstract:
This self-extracting archive contains DMI support files for the
TokenExpress PRO adapters. DMI files for the EtherExpress PRO/10+ ISA,
EtherExpress PRO/100 (PCI and EISA) and EtherExpress PRO/100B adapters,
are available on the disks that ship with the product. You can also
download the adapter's SW driver disk from Intel's on-line services.
FLSWKS.EXE
FlashWorks 1.62c: This archive contains a DOS text file of FlashWorks
documentation and the latest release of FlashWorks v1.61 (Software P/N
351926-001) with these updates:
INSTALL.EXE - installs correctly on NetWare 4.02 server when selecting
VLMs.
FLSCAN.EXE - correctly reports 486 based systems
FLSTART.EXE - works with foreign versions of Microsoft Windows (such as
Chinese and Korean).
Version 1.62c provides full support for the following adapters:
EtherExpress Flash Adapters
EtherExpress PRO Flash Adapters
EtherExpress Flash32 Adapters
TokenExpress PRO Flash Adapters
TPRODSK1.EXE
TokenExpress PRO adapters 1 of 2: TokenExpress PRO adapters,
Configuration Diskette. Software version 2.0. This archive contains
updates of README installation notes, TOKENSET with diagnostics and auto
driver install utility, and configuration files.
TPRODSK2.EXE
TokenExpress PRO adapters 2 of 2: TokenExpress PRO adapter, Drivers
Diskette. Software version 2.0 of the Intel TokenExpress PRO adapter
drivers. Includes new WFW and NT drivers.
UNDETECTABLE IRQS
TokenSet can reliably detect most IRQs used in a computer. The best way
to avoid IRQ conflicts is to load the device drivers for all other
adapters before running TokenSet. If you still have problems with the
computer after installing the adapter, make sure no other device uses
the same IRQ as your TokenExpress PRO adapter.
LOCALLY ADMINISTERED ADDRESSES FOR OS/2 AND WINDOWS FOR WORKGROUP USERS
OS/2 users
If you use LAPS to configure your adapter, don't set your locally
administered address in LAPS. Instead, add the following line under the
[tproeos2_nif] section your PROTOCOL.INI file:
NODEADDRESS="400000000012"
Where 400000000012 is an example of a 12-digit locally administered
address.
Note: If you configure your locally administered address during LAPS,
you need to delete the NETADDRESS= lines in the protocol sections of
your PROTOCOL.INI file. You'll also need to add the NODEADDRESS= line to
the [tproeos2_nif] section.
Windows for Workgroups users
If you want to set a locally administered address, add the following
line under the [tpro] section your PROTOCOL.INI file:
NODEADDRESS="400000000012"
Where 400000000012 is an example of a 12-digit locally administered
address.
CHANGING THE FLASH CHIP ADDRESS WHEN A MEMORY MANAGER IS RUNNING
When a memory manager is running, TokenSet indicates that all memory
addresses (except D000) are used, even if they're free. To change the
flash chip address, follow these steps:
1. Temporarily disable the memory manager. For example, add a REM
statement to the start of the memory manager command in your
CONFIG.SYS file. Then reboot.
2. Run TokenSet and select a flash chip address. Note the address.
3. Exclude the memory range that the flash chip uses and re-enable
the memory manager.
Memory overlap problems - 6283
The default flash chip address is D000-D3FFh. If you install the
adapter, turn on the computer, and see a blank screen or an error
message, the flash address probably conflicts with something else in the
computer. To resolve the conflict:
Determine what device is using the D000-D3FFh range and reconfigure
that device to use a different memory address.
Check your system setup and disable ROM shadowing at D000h.
Remove the adapter from this computer, install it in another computer
that doesn't have a conflict at D000-D3FFh, and use TokenSet to
configure it to use a different flash chip address. Then, reinstall the
adapter in the first computer.
INSTALLING MULTIPLE ADAPTERS OF VARIOUS TYPES
If you're installing multiple Intel flash adapters in one computer,
install and configure the adapters one at a time.
Also, if you plan to use FlashVirusProtect on the computer or have a
computer with a Plug and Play BIOS, disable the flash chip on all but
the last adapter you install. Otherwise, disable the flash chip on all
of the adapters.
INSTALLING IN 8086 OR 8088-BASED COMPUTERS
IRQ5 conflicts
Many 8086- or 8088-based computers use IRQ5 for the hard drive. IRQ5 is
the default interrupt for the TokenExpress PRO adapter. When installing
the adapter in these computers, use TokenSet to change the interrupt to
one other than IRQ5.
USING NETWARE 3.12 OR 4.01 WITH FLASHWORKS
If you use VLM's, make sure this line is in the CONFIG.SYS file:
LASTDRIVE=Z
Without this line, the FIRST NETWORK DRIVE=F command in the NET.CFG
file won't work.
INSTALLING FLASHVIRUSPROTECT FROM THE INTEL DISKETTE
You can install FlashVirusProtect on any workstation containing an
TokenExpress PRO adapter. Here's how:
1. Put a copy of the FlashWorks disk into a drive, switch to that
drive and, at the DOS prompt, type "SETUPFVP".
The batch file decompresses files from the diskette and copies them
to C:\VPROTECT.PC. It then starts the FlashVirusProtect
configuration program.
2. Specify the configuration you want (see the FlashWorks Installation
and User's Guide for details) and press F10.
3. Choose Yes to download the configuration to the flash adapter.
UPDATING FLASHVIRUSPROTECT
If an update of FlashVirusProtect fails, and FLUPDATE's View status
option displays
Failed: Insufficient flash memory
make sure you've turned off FlashStart on the adapter. Then run
FLUPDATE to reschedule the event.
USING FLASHVIRUSPROTECT WITHOUT A FLOPPY DRIVE
If you're running FlashVirusProtect and don't have a floppy drive, make
sure you configure FlashVirusProtect to scan only your hard drive.
UPDATING FLASH MEMORY
If a flash update fails, and FLUPDATE's View status option displays
Failed: Flash memory erase error.
run FLRESTOR /ERASE at the computer (make sure the flash image file
with a .FLS extension is in the same directory), then run FLUPDATE at
the server and reschedule the update. The flash image file (FLSIMG.EXE)
is available through Intel's online services.
IF TOKENSET WON'T RUN
When you start TokenSet, it checks to see if enough memory is available
to run. If there isn't enough memory, it displays an error message. If
this happens to you, remove TSRs or device drivers from memory before
running TokenSet. You might try booting from a clean boot diskette and
then running TokenSet.
A similiar situation can occur if you try to run TokenSet with adapter
drivers already loaded. In this case, TokenSet can cause the computer
to hang or cause drivers to lose connection. If this happens, remove
the TokenExpress PRO adapter drivers from memory before running
TokenSet.
SPECIAL CONFIGURATIONS
If you have a PCI/ISA Pentium computer without a Plug and Play BIOS,
your adapter*s flash program may be disabled during installation due to
ROM shadowing problems. To fix this, disable ROM shadowing for the flash
memory address in the computer*s BIOS.
If you have a computer with a Plug and Play BIOS and don't see the "Plug
and Play BIOS detected" dialog box during installation, you'll want to
upgrade the flash image. To do this, insert the FlashWorks disk into a
drive, switch to that drive and, at the DOS prompt, type "FLUP.BAT".
RPL LIMITATION
With our current release, the only Remote Program Load (RPL) supported
is NetWare ODI. TokenSet's Remote boot program screen still lists other
options, but they aren't yet supported.
Trademark information