TransBIOS Startup Problems Under Windows 95
Here are some things to check if the TransBIOS network protocol does not start up properly under Windows 95.
If TransBIOS does not start up properly, then one or more of the following may occur during Windows startup:
Check for Incorrect TransBIOS Bindings
This problem is almost always caused by an incorrect network configuration. Specifically, the problem is caused by incorrectly "binding" TransBIOS to other devices besides the network adapter.
To check for incorrect bindings, proceed as follows:
Please check your bindings carefully, as correct bindings will almost always solve the problem.
Check the Hardware Driver Configuration
This problem might be caused by an incorrect configuration of the hardware driver.
For most hardware drivers, you need to enter the I/O port address and IRQ interrupt level into the driver configuration. If the driver's I/O port and IRQ level don't match the network board's actual I/O port and IRQ level, then this problem may occur. (Unfortunately, most Windows 95 hardware drivers don't show any error messages when you enter the I/O port or IRQ level incorrectly; they just don't work.)
To check the hardware driver configuration, proceed as follows:
If you are unsure of the configuration of your network board, you should examine the jumpers on the board or, in the case of jumperless boards, run the setup utility supplied with the board. Make absolutely certain that the I/O port and IRQ level match the settings in the driver's Resources page.
If your network board has a jumper for "turbo mode" or "bus timing" or "system compatibility", try changing the setting of that jumper.
Check for Conflicts in Device Manager
Other possible causes of the problem are: (1) a hardware conflict between the network board and other hardware in your computer; (2) installing the wrong hardware driver for your network board; or (3) installing more than one hardware driver for your board.
You can use the Windows 95 Device Manager to check for these problems. To run Device Manager, do the following:
Underneath "network adapters" you should see the hardware driver for your network board. If it isn't listed, then you need to install the hardware driver for your network board. (Starting from Control Panel, you can install the driver manually by clicking Network, then Add, then Adapter. Or, you can let Windows 95 identify the correct driver automatically by clicking Add New Hardware.)
Check to make sure that the hardware driver listed under "network adapters" is the correct driver for your network board. If it isn't, then remove the incorrect driver (click on the driver and then click Remove). Then, install the correct driver.
Check to make sure that there is only one driver installed for your network board. If there is more than one, then remove the extra ones.
Check if there is an "X" or an "!" showing next to the hardware driver. If there is, then Device Manager has detected a hardware conflict or malfunction. Double-clicking on the hardware driver may reveal additional information about the problem. The error indication might be caused by (a) a malfunctioning network adapter; (b) installing an incorrect driver; (c) setting the driver's I/O port or IRQ level incorrectly; or (d) setting the network adapter's I/O port or IRQ level to the same value used by other equipment in the computer. Whatever the problem is, you must correct it before Invisible LAN can function.
Double-click on the network hardware driver and then click Resources to view the hardware resources (I/O ports and IRQ level) that your driver is using. Check to make certain that these match the network board's actual I/O ports and IRQ level. Check to make sure they don't conflict with other hardware in the computer. Read the dialog box to see if there are any error messages. Check to make sure that an IRQ level is listed in the dialog box; if none is listed, it means that the IRQ level you selected conflicts with other equipment in the computer and must be changed.
Notices: Copyright 1997 by Invisible
Software, Inc. Invisible Software and InvisibleLAN are trademarks
of Invisible Software, Inc. Other trademarks are the property of
their respective holders.
This document was prepared on 12/01/97, and was believed to be accurate as of that date. Procedures, specifications, and compatibility may change without notice, and therefore this document may be out-of-date and/or inapplicable to current product versions. Invisible Software provides this document "AS IS" and without warranty of any kind. Under no circumstances shall this document be construed as creating or expanding any warranty of product performance.
Go back to Support FAQ.