Softset Problems And Solutions
- Use the lastest SoftSet
Use the latest version of SOFTSET.EXE (v2.03), or use SOFTSET2.EXE.
SOFTSET.EXE is found on the latest Intel drivers diskette (S/W p/n
308629-004 or later). SOFTSET2.EXE is available through Intel's
online services in the self-extracting archive SOFT.EXE.
SOFTSET2.EXE supports the EtherExpress 16 and the EtherExpress
PRO/10 LAN adapters.
Running SoftSet v2.02 or earlier in a faster 386 or 486 computer could
result in an unprogrammed eeprom. Make sure you are using SOFTSET
v2.03 or SOFTSET2.
If you experience problems running SoftSet, the following procedures are
recommended:
- Copy SOFTSET.EXE v2.03 or SoftSet2 to your local hard drive and
run it.
- Boot the PC with no AUTOEXEC.BAT or CONFIG.SYS file. The
easiest way to do this with DOS 5.0 or earlier is to rename the
AUTOEXEC.BAT and CONFIG.SYS files. Power the PC off, then on
again. You will be prompted for the date and time. With DOS 6.0
or later, press F5 when loading MS-DOS during boot-up.
- Run SOFTSET or SoftSet2 from the C:\ prompt.
- SoftSet hangs after pressing spacebar on the welcome screen.
- Run SoftSet or SoftSet2 from your local hard drive. Follow the
procedures listed in #1 above to ensure that SoftSet runs
successfully.
- If you are running both Windows for Workgroups 3.11 and SoftSet and
the initial Windows* screen hangs, you have probably set the I/O
Channel Ready setting to Early. When the EtherExpress board is in
"early" mode it cannot communicate in a 16-bit slot in most
machines. To resolve this problem, there are two options:
- Obtain E16LATE.EXE which is available through Intel's online services,
which can reprogram the EEPROM to late.
- If you are unable to download from Intel's online services:
- Put the EtherExpress card in an 8-bit slot.
- Run SoftSet or SoftSet2 and select Yes to Force 8-bit mode
under manual setup. Change the IRQ to a setting below 9.
- Edit the PROTOCOL.INI in the Windows* directory to read
IOCHRDY=NEVER.
- Reboot the machine and run Windows. Select Network Setup
from the Network group. Select Drivers, Setup, and then
Advanced. Change the I/O Channel Ready setting to Late.
Save and exit Windows.
- Return the EtherExpress card to a 16-bit slot.
- "ERROR: SoftSet has detected a possible conflict at I/O address xxxh
that could damage your EtherExpress board. Move your EtherExpress board to
adifferent computer, or remove the conflicting board at I/O address xxxh."
Another adapter in the computer or a built-in device on the
motherboard (like VGA) may be using the same I/O address or IRQ as
the EtherExpress 16 adapter. Each adapter (device) in a computer
must have a unique I/O address and IRQ. The factory defaults for
the EtherExpress 16 adapter are I/O address 300 and IRQ 3.
To fix this problem:
- Remove the conflicting adapter.
- Run SoftSet v2.03 or SoftSet2 and change the I/O address on the
EtherExpress adapter.
- Return the conflicting adapter to the computer.
OR
- Place the EtherExpress adapter in another computer.
- Run SoftSet v2.03 or SoftSet2. Change the I/O address and IRQ to
something other than 300 and 3.
- Return the EtherExpress adapter to the computer.
- The Correct Connector Types Are Not Displayed In SoftSet.
Reset the eeprom to display the correct connector types:
If you are using SoftSet use these parameters:
SOFTSET /lisa | Forces the connector type to RJ45 and DIX. Do not use if you have a BNC connector or all 3 connectors (combo adapter). |
SOFTSET /bart | Forces the connector type to BNC and DIX. Do not use if you have a RJ45 connector or all 3 connectors (combo adapter). |
SOFTSET /combo | Forces the connector type to RJ45, BNC and DIX. Do not use on adapters with only 2 connector types. |
If you are using SoftSet2, use ISS1.EXE with these parameters:
ISS1 /lisa | Forces the connector type to RJ45 and DIX. Do not use if you have a BNC connector or all 3 connectors (combo adapter). |
ISS1 /bart | Forces the connector type to BNC and DIX. Do not use if you have a RJ45 connector or all 3 connectors (combo adapter). |
ISS1 /combo | Forces the connector type to RJ45, BNC and DIX. Do not use on adapters with only 2 connector types. |
NOTE: These switches only reset the eeprom to display the correct
connector types.
- FLASH/Boot ROM test fails in SOFTSET On-Board Diagnostics.
If there is not a FLASH/Boot ROM chip on the board and the
diagnostic test fails, run manual setup. Change the FLASH/Boot
ROM Address to "FLASH/Boot ROM disabled."
- Known Conditions That May Return an Unprogrammed EEPROM Message.
- Running SoftSet v2.02 or earlier in a faster 386 or 486 computer
could result in an unprogrammed eeprom. This is due to a timing
problem when reading and writing to the eeprom.
- SoftSet and SoftSet2 are DOS programs; you cannot run SoftSet or
SoftSet2 under OS/2! You could corrupt the EEPROM on the
EtherExpress adapter by running SOFTSET or SoftSet2 on an OS/2
machine, even if you run SoftSet or SoftSet2 in the DOS
compatibility box. Boot the machine with a DOS disk or setup the
EtherExpress adapter in a DOS PC then move it to the OS/2 machine.
Early versions of SoftSet (prior to v1.08) did not check for OS/2.
Newer versions display an error message if SoftSet finds OS/2 as
the operating system.
- Do not run SoftSet or SoftSet2 if network drivers are loaded.
SoftSet v2.03 displays an error message telling you to unload the
network drivers and rerun SoftSet.
Earlier versions of SoftSet (prior to v1.12) did not check for
network drivers and could result in SoftSet returning an
unprogrammed eeprom message. In many cases, you can unload the
network drivers and run SoftSet v2.03 successfully.
- NEC tested an EtherExpress 16 adapter containing an 8100 boot rom
with an NEC IMAGE 433 machine. SOFTSET.EXE or SoftSet2 would not
allow the user to set up the EtherExpress adapter and gave an
unprogrammed EEPROM error. This problem is caused by the 1.0026
BIOS in the NEC IMAGE 433 machines. Upgrading these machines with
the 1.0036 BIOS will solve the problem. Download the new BIOS from
the NEC BBS, then follow the upgrade instructions in the NEC
manual.
- Early versions of SoftSet (prior to v1.09) returned an Unprogrammed
EEPROM message if there was an I/O conflict. Later versions of
SoftSet or SoftSet2 return the correct message, indicating an I/O
conflict. In most cases you can successfully get into SoftSet or
SoftSet2 by eliminating the conflict. Use the latest SoftSet or
SoftSet2 and follow the procedures listed in #3 above to change the
I/O.
PLEASE NOTE:
This product is no longer being manufactured by Intel. THESE DOCUMENTS ARE PROVIDED FOR HISTORICAL
REFERENCE PURPOSES ONLY AND ARE SUBJECT TO THE TERMS SET FORTH IN THE "LEGAL" INFORMATION" LINK BELOW.
For information on currently available Intel products, please see
www.intel.com and/or developer.intel.com
|