|The Complete Win95 Install Troubleshooting Guide|
Select the topic you need help with
|0.||BEFORE YOU START|
|1.||PREVIOUS VERSIONS and BETA REMOVAL|
|* Model 100/200/300, Ethernet 8/16|
|* ISA NE2000 Compatible|
|3.||ADDING THE PROTOCOL, CLIENT & SERVICE|
|4.||CONFIRMING NETWORK SETUP|
|6.||STARTUP ERROR MESSAGES AFTER INSTALL|
BEFORE YOU START
To use InvisibleLAN with Windows 95 REQUIRES InvisibleLAN version 4.0. If you do not have InvisibleLAN version 4.0, please obtain an upgrade before attempting to run Windows 95 on the network.
We recommend making a backup copy of your InvisibleLAN disks and placing the originals in a safe location.
You also MUST have your original Windows 95 CD-ROM or floppy disks. Windows 95 will ask you for the floppy disks or CD-ROM during the install.
1. PREVIOUS VERSIONS and BETA REMOVAL
If you previously had an Invisible Network (usually in a NET30 directory), run NETDIAG from a DOS prompt and make a note of the current IRQ and I/O settings of the network card. Next, determine your software type by typing DIR *.OPT in the C:\NET30 directory.
If NETAI.OPT is listed, there will also be a SERIAL.DAT file. Copy SERIAL.DAT to a floppy disk for later use. Remove ALL references from CONFIG.SYS (CACHE30.SYS, N30DEV.SYS) and AUTOEXEC.BAT (NETGO, NET30 or NET30.EXE, and C:\NET30 from the PATH) that were used with our previous networks. These are no longer needed with Win95.
If you were previously running Win95 with our BETA version it MUST ALSO BE REMOVED before proceeding. See page 7 of the "INVISIBLE LAN for Windows 95" book.
2. NETWORK CARDS
If you are using an Invisible LAN network card, you can use Adapter Dependent software, otherwise, you must use Adapter Independent software which requires a SERIAL.DAT serial number file. If your 4.0 Disks are not labeled "Adapter Independent" (SERIAL.DAT file included) or "Adapter Independent Upgrade" (for use with an existing SERIAL.DAT file), you have AD which requires an Invisible LAN network card.
The InvisibleLAN Model 100, Model 200, Model 300, Ethernet-8, and Ethernet-16 network cards are older, proprietary design cards. These cards do not have NDIS-3 drivers available, and are not Windows 95 compatible.
BEFORE installing a new ISA (standard NE2000 compatible) network card, determine how to configure it's IRQ and I/O address, (jumper, jumperless or plug & play) then determine it's current settings. Most cards are software configurable and require a DOS setup program after installation. To do this, turn off your computer, install the card and restart. AS SOON AS "STARTING WINDOWS 95" is displayed, PUSH the F8 key. This will bring up a menu that allows you to start in "COMMAND PROMPT ONLY" (usually option #6). Run the card's diagnostic program (part of it's SETUP program) to verify that it is working properly and it's current IRQ and I/O settings.
NOTE: Invisible Ethernet 2000 Plug & Play (PXA & PXC) cards are shipped in non-plug & play mode but can be reconfigured by running SETUPP.EXE. This is recomended when running Windows 95 on a Plug & Play enabled motherboard.
For PCMCIA cards, follow your laptop manufacturers recommendations for setup and configuration of your PCMCIA slot. Most notebooks require only the standard Windows 95 drivers for initialization of the slot, while others may require special drivers in your CONFIG.SYS or AUTOEXEC.BAT files. Your notebook MUST be able to recognize that an active device is plugged into the PCMCIA slot before any driver will work for the PCMCIA slot. You can verify the PCMCIA device has been initialized by examining the PC Card Icon in the control panel, or by removing the Ethernet card while in Windows 95 and checking for an Audio or Visual indication that the status of the port has changed.
Once your system has recognized the presence of the network card, Windows 95 may load a default driver for that card and proceed to initialize it. Other cards may require a driver that is supplied by the card manufacturer. Some InvisibleLAN supplied cards require such a driver, and are included on the driver disk in a directory labeled WIN95. Check with your Ethernet cards manual for a complete description and location of the card drivers.
Once the driver is loaded for the card, it is susceptible to the same resource conflicts as other types of cards. Go to the Control Panel, System icon, Device Manager Tab and examine the Network Adapters entry. Verify a valid entry for the network adapter card installed in your system.
If you do not see a network adapter, your PCMCIA card has not be properly recognized and initialized by Windows 95. Try rebooting your notebook without the card inserted, and while at the Windows 95 desktop insert the card. You should get and audio or visual indication that a card has been inserted as described above.
If you see your Network Card listed and it DOES NOT have a X or ! next to it, then your card is working correctly. If it does, then there is a error with the card, its settings, or the drivers. You should verify that the IRQ and I/O base Windows has assigned is not conflicting with another device. (These can be checked and changed from Control Panel, System, Device Manager Tab, Network Adapters, select your adapter, click properties, resources tab. Next remove the checkmark from Use automatic Settings and select a different I/O and IRQ that has no conflicts). If the problem persists, remove the adapter entry from the system list, and use the Windows 95 Add New Hardware wizard to re-identify the adapter. You can also verify the adapter is working correctly by testing the card with InvisibleLan for DOS (this may require the use of a direct enabler such as CARDGO).
NOTE: PCI cards do not require a setup program but are dependent on your computer's BIOS for proper IRQ and I/O settings. Consult your computer manual or dealer for setup procedures.
With the network card installed and it's IRQ and I/O recorded, START WINDOWS 95 and go to the NETWORK, CONFIGURATION menu: (START, SETTINGS, CONTROL PANEL, NETWORK)
If your network card was previously installed or auto-detected by Win95, you may already have an adapter (and protocols) listed here. (WIN95 will auto-detect Invisible LAN PCI Network cards, and load the required DEC drivers) If the NETWORK, CONFIGURATION menu is empty, Select ADD, ADAPTER, ADD, and select the proper manufacturer and model of your card. Invisible LAN ISA (standard) Network cards use the Novell/Anthem-NE2000 Compatible drivers. Consult Microsoft if you do not have this option.
When the network card drivers are loaded, Win95 will also load
Client for Microsoft Networks and Client for Netware Networks
plus additional protocols. Unless you are planning on a multi
network configuration, REMOVE EVERYTHING EXCEPT the network
adapter card (NE2000 Compatible).
(You should now have only the NE2000 Compatible or your network card listed)
NOTE: If your network card uses the DEC driver (such as the Invisible PCI 10MB and 100MB), highlight the card and click on Properties, then click Advanced. Click on Connection Type for 32 bit driver and enter the proper value on right (do NOT use AutoSense).
3. ADD The PROTOCOL, CLIENT & SERVICE
Click ADD, PROTOCOL, ADD, HAVE DISK, select your floppy drive
and install TransBIOS for Ethernet (or TOKEN RING) from Invisible
LAN 4.0 disk number 1.
(You should now have only NE2000 Compatible plus TransBIOS For Ethernet listed)
Click ADD, CLIENT, ADD, HAVE DISK, select your floppy drive
and install Client for Invisible LAN from Invisible LAN 4.0 disk
(You should now have Client for Invisible LAN, NE2000 Compatible and TransBIOS For Ethernet listed)
If this computer is going to share files or printers:
Click ADD, SERVICE, ADD, HAVE DISK, select your floppy drive and install File and Printer Sharing for Invisible LAN from Invisible LAN 4.0 disk number 1.
(You should now have 4 items listed, Client for Invisible LAN, NE2000 Compatible, TransBIOS For Ethernet and File and Printer Sharing for Invisible LAN)
NOTE: The button on this menu labeled "File & Print Sharing" will load the Microsoft Network AND DISABLE THE INVISIBLE NETWORK requiring reinstallation.
4. CONFIRM NETWORK SETUP
Click Okay on bottom left of menu and Win95 may take you to the network card RESOURCES MENU displaying the Interrupt Request (IRQ) and Input/Output Range (I/O address). Confirm that these settings match those of your network card. If they do not, Click on the "Use Automatic Settings" Box (to turn it off) then double-click each item to change it's configuration.
Click OK to accept the settings and your Win95 CD Rom or Floppy disks will be requested.
If asked for the CD Rom, be sure to specify the \Win95 subdirectory, and leave the Invisible LAN disk 1 in your Floppy drive.
5. NETWORK ACCESS
The Network Neighborhood icon on your desk top is used to access all servers on your network. If you are able to "see" the other network SERVER machines in Network Neighborhood, then the InvisibleLAN install is complete.
You can map to other InvisibleLAN machines by following these steps:
See the "INVISIBLE LAN for Windows 95" book for complete instructions on drive and Printer mappings, as well as Shortname and Security information.
6. STARTUP ERROR MESSAGES AFTER INSTALL
If Win95 Starts with the message "Licensed Number of Users Exceeded" you are using AI software and will need to record your serial number from your new version 4.0 disks (Adapter Independent) or from a previous install, saved on a floppy disk from step 1 (Adapter Independent Upgrade).
To do this, you must have Win95 running and "Shell" out to a DOS prompt. (START, PROGRAMS, DOS PROMPT) Place your AI disk 1 in a floppy drive and type A:\SETUP_AI (or B:\SETUP_AI) a batch file will run and ask you for the location of your SERIAL.DAT file. This will be stored in the Win95 registry and you can restart your computer.
7. OTHER PROBLEMS
If your Windows 95 machine boots without any error messages, but you are unable to find your other network SERVER machines in Network neighborhood, check the following:
1. Verify the IRQ shown from the System icon in Control Panel for your network adapter is the same as the physical address of the network card. If you are unsure of the physical address of the network card, you can restart the machine in MS-DOS mode and run our NETDIAG program which will display the physical IRQ and I/O base. (NETDIAG can be found in a previous installations NET30 directory, or on the QSTART v4.0 disk.
2. Make sure you are cabled into your network. If you using RJ45 cabling, you can run NETDIAG on your machine and watch your HUB for data activity on your machine. For other situations, it is recommended to restart your computer in DOS mode and to run NETDIAG to determine if a connection with the network can be made.
3. If you can see your network in DOS, but not from Windows 95 try rechecking #1 from above. Also, try forcing the media type of your network card if your card supports more than one cable type. This can be done from the network icon in the Control Panel. Double click on your network adapter, go to the Advanced Tab, and look for "Connection Type for 32 bit driver". Enter the proper value on right. (do not use AutoSense).
If when booting Windows 95 the "splash" screen appears as normal, then the system halts, check the following:
1. Make sure the NET30 command and any other network related commands are removed from CONFIG.SYS and AUTOEXEC.BAT.
2. Reboot in safe mode, then examine the network icon in the Control Panel of Windows 95. Try adding in the Microsoft network client with NETBEUI protocol and Netware network client with IPX/SPX protocol.
Notices: Copyright 1997 by Invisible
Software, Inc. Invisible Software and Invisible LAN are
trademarks of Invisible Software, Inc. Other trademarks are the
property of their respective holders.
This document was prepared on 02/06/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.