Latest news about Driver Release 2.0
====================================
The following table displays the drivers available with this release
and suggests how to install them.
--------------------------------------------------------------
Network Driver types How to install the driver
-------------------- -------------------------
Novell
DOS ODI Client Let TokenSet do it for you
NetWare 3.x, 4.x View the instructions
NetWare Remote Boot in TokenSet, or run:
OS/2 NetWare Requester README
Microsoft
WfW 3.11 View the instructions
Windows NT 3.1, 3.5 in TokenSet, or run:
LAN Manager README
IBM
DLC, DLC w/ NetWare Let TokenSet do it for you
AS/400
OS/2 Workstation View the instructions
LAN Server 3.0 in TokenSet, or run:
README
Other
Banyan View the instructions
UNIX in TokenSet, or run:
README
--------------------------------------------------------------
NetWare* server, Windows NT*, and OS/2* users
---------------------------------------------
If you have a Plug and Play BIOS and are running OS/2, Windows NT,
or a NetWare server, make sure you DISABLE Plug and Play on your
adapter using TOKENSET. Having Plug and Play enabled on your
adapter may cause configuration problems because these environments
don't support Plug and Play.
DOS/ODI driver
--------------
If you're using the new DOS/ODI driver, TPROODI.COM, make sure
you install the new support files:
LSL.COM 10/11/94 v2.14
IPXODI.COM 10/31/94 v3.01
Older versions of these files may not work with the new driver.
IBM ValuePoint* users
---------------------
If you have an IBM ValuePoint Plug and Play computer, you may need
to run TokenSet (v2.11 or later) with the /RESTOREEPROM option.
At the DOS prompt, type:
TOKENSET /RESTOREEPROM
This should resolve any problems you may have had configuring
your adapter.
Updating flash memory
---------------------
If a flash update fails, and FLUPDATE's View status option
displays:
Failed: Flash memory erase error.
make sure the flash image file, TPRO.FLS, is in the same
directory and then run:
FLRESTOR /ERASE
At the server run FLUPDATE and reschedule the update. If you
still have problems, download the most recent image file from
the Intel BBS (in FLSIMG.EXE) and try this again.
FlashVirusProtect
-----------------
If you don't want to install FlashWorks or don't have a NetWare
server, you can still use FlashVirusProtect. Here's how:
Installing from the FlashWorks disk
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.
Using Doublespace*
------------------
FlashStart won't work properly on computers using Doublespace
with the /move parameter.
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
(EMM386.EXE) 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
-----------------------
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
----------------------------
If you’re installing multiple Intel adapters in one computer,
install and configure the adapters one at a time. Use a
different IRQ and I/O address for each and make sure no
adapters use the default I/O address of 300.
Disable the flash chip on all of the adapters. If you plan to
use FlashVirusProtect on the computer, enable the flash chip
on the last adapter you installed.
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.
PCI/ISA computers
-----------------
If you have a PCI/ISA 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, use your computer's
BIOS setup program to disable ROM shadowing for the flash memory
address.
Plug and Play computers
-----------------------
If you disabled Plug and Play on your adapter and later want
to re-enable it, use TokenSet and then be sure to cold boot
your computer.
This allows your computer's Plug and Play BIOS to find the
adapter and configure it automatically.
XT computers
------------
Intel PRO adapters don't support XT computers (8086's and 8088's).
Try contacting your computer vendor or reseller for a network
adapter that supports XT computers.
FlashWorks and VLMs
-------------------
If you use VLMs, 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.
RPL limitation
--------------
With our current release, the only Remote Program Load (RPL)
supported is NetWare ODI. TokenSet's Remote boot program screen
lists other options, but they aren't yet supported.
* Third-party trademarks are the property of their respective owners
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.