Removing Adapter Software from Windows* 95/98
Intel has developed a program that will remove this Intel® PRO/100 Mobile adapter driver and all associated information files and Registry entries from the Windows* 95/98 environment. This procedure may be necessary to prepare for driver upgrades or to remove a corrupted or failed installation. Download the REMOVE.EXE file archive.
Does the Intel® Mobile adapter support BNC or 10Base2 topology?
None of the Intel® PRO/100 mobile adapters support BNC connections.
Promiscuous Mode and Intel® Mobile Adapters
The NDIS 3 miniport drivers for the mobile adapters support promiscuous mode to the extent allowed by the NDIS 3 specification. Generally, there shouldn't be a problem using the NDIS 3 drivers in promiscuous mode, however the NDIS 3 specification doesn't specify bad packet error capturing. Novell cannot guarantee successful operation under LANalyzer* for Windows* since NDIS drivers are not certified by Novell. The PC Card miniport driver has been used with success. It is recommended that users update the VMLID.NLM to the 2/26/96 version, available on the LANalyzer for Windows 2.2, Diskette 3.
If using the PC Card with Novell's LANalyzer 2.1 at 10 Mbps, add the keywords; LINESPEED 10, NOEARLYRX and NOEARLYTX to the NET.CFG.
All Mobile adapter 16-bit DOS ODI drivers are certified by Novell for promiscuous and multicast modes. Intel has a 32-bit ODI driver and Client 32 installation files for the CardBus adapter. This driver does provide error capturing, although there is one limitation in it's support. Fragment errors are captured, but they are classified, counted and reported as undersized errors. Therefore, the total count for undersized errors includes the total of undersized and fragment errors.
Note: Bad packet error capturing is not a test required for Novell certification. If drivers are written to the ODI specification, they should be supported.
Does Intel make a point enabler DOS driver?
A point enabler is software designed to work with a specific PCMCIA device, and does not use card and socket services. All the drivers that ship with this Intel Mobile adapter include a point enabler.
Having problems installing and rebooting Windows 95 with the CardBus adapter?
Some issues were seen in Windows* 95 OEM Service Release 2 (OSR2) with earlier versions of the CardBus Windows 95 driver. Among these were GPFs, reboots going into safe mode, or inability to boot into Windows 95 when the adapter was installed. Obtain the latest Windows 95 driver for the CardBus adapter, M32ADISK.EXE.
Can other 16-bit PCMCIA devices be used at the same time as the CardBus adapter in Windows 95?
Using the latest release of the NDIS 3 driver for the CardBus adapter, (M32A.SYS dated 9-Sep-97), Windows* 95 Retail and OSR1 allow the use of a 16-bit PCMCIA device in the other slot. Previous versions of the NDIS 3 driver did not allow it. The only known limitations are with Toshiba* computers. The second PC Card slot is disabled when the computer is put into CardBus mode.
CardBus Adapter Detected as a "PCI Fast Ethernet DEC 21143/21142 Adapter."
The version of Windows* 95 OSR2 that shipped with this computer contains a generic .INF file that can be used to install several different DEC Ethernet controllers (C:\WINDOWS\INF\NETPCI.INF), including the DEC Ethernet Controllers used in the CardBus adapter. The CardBus driver uses subclass keys to differentiate between the Intel® adapter and other devices using this controller chipset. The NETPCI.INF file does not use these subclass keys and will install the generic driver each time one of these controllers is detected. The generic driver does not work with the Intel CardBus adapter.
Follow the steps below to fix the problem:
- Remove the "PCI Fast Ethernet..." listing from the Device Manager Network adapter section.
- In the WINDOWS\INF directory, delete DRVDATA.BIN, DRVIDX.BIN, NETCARDBUS.INF (if present) and rename NETPCI.INF to NETPCI.ORI (for original).
- Shutdown and re-start Windows 95.
CardBus adapter is not recognized by the laptop and/or does not fit into the PCMCIA.
First, if the adapter does not fit easily into the PCMCIA slot, the computer is not CardBus ready and you cannot use this adapter on that system. CardBus adapters are keyed differently and should not fit into slots that support only 16-bit cards. Contact your system's vendor for verification of CardBus functionality.
Secondly, if it does fit in the slot, verify with your vendor that the model is CardBus enabled. Sometimes manufacturers have shipped systems that physically support CardBus, but the BIOS needs to be updated to enable the CardBus capability.
Thirdly, some systems have BIOS or utilities that need to be run to set it to CardBus. For instance, Toshiba systems have a DOS utility called TSETUP or a Windows* GUI that sets their ToPIC 95 controller to a CardBus state.
Ordering an extra cable for my Mobile adapter*
This applies to: