PCMCIA card services

I am looking for a card service to run on my 486 laptop. At the moment in the diagnostic for the NIC it states that no card services are installed. The PCMCIA Controller is Intel 82365SL compatible. I have no idea what that means. I am just trying to get the laptop connected to my LAN for small programs, nothing big. Links lites to the dongle on the NIC are visible and a link lite to the hub is visible as well. When going to the card in the Device Manager it has the yellow circle with the exclamation point in it (!). Does anyone know what I can do to get this old monster connected to mt network? All settings are already in place such as IP, DNS, Subnet Masks and etc. PLease help! Thanks in advance.

The PC Card socket may have an IRQ conflict with another device in your system. By default, it uses IRQ 11. You can change it by following these steps:
[list=1][*] In Control Panel, double-click System, and then click the Device Manager tab.
 [*] Double-click PCMCIA Socket, double-click the PCMCIA controller, and then click the Resources tab.
 [*] Click the Use Automatic Settings check box to clear it, click Interrupt Request, and then click Change Settings.
 [*] In the Value box, click an available IRQ setting.
 [*] Click OK, and then click OK.
 [*] Shut down Windows 95 and then turn your computer off and back on.[/list=a]
If that doesn't solve the problem, what is the make/model of both your laptop and the NIC.

[This message has been edited by Vernon Frazee (edited 08-21-2000).]

Laptop is a 486 IBM Thinkpad.
Nic is Linksys Combo PCMCIA Ethernet Adapter. The problem seems to be with the NIC and not with the card service after closer inspection. It has the yellow circled exclamation (!) in the network adapters field under device manager. HELP ME!!!!

Did you try the above instrucions?

Have you tried installing the Windows 95 32-Bit PCMCIA Socket drivers? You can do so by following these steps:
[list=1][*] Double-click My Computer
 [*] Double-click Control Panel
 [*] Start the 32-bit PC Card (PCMCIA) wizard, and follow the instructions on the screen[/list=a]

Note: To use protected-mode network interface card (NIC) drivers with a PCMCIA NIC, the PCMCIA socket must be supported for protected-mode socket services. The IBM ThinkPad 720/720C PCMCIA socket uses the Stinger chip set. The Stinger chip set is not a supported PCMCIA socket chip set for Windows 95 protected-mode socket services. To use the PCMCIA socket on an IBM ThinkPad 720/720C, install the real-mode socket drivers using the manufacturer's instructions.

Related links
Microsoft KB: Enabling PCMCIA Support in Windows 95
Microsoft KB: Troubleshooting PCMCIA Cards in Windows 95

What do you mean by "Start the 32-bit PC Card (PCMCIA) wizard, and follow the instructions on the screen"? All I see is the PCMCIA icon in the control panel. If I am missing something please let me know.
[email protected]

Click the Start button, then Help, then the Find tab. Type in the word [b]wizard[b/]. (If more than one "wizard" word appears in the center frame, select the one that's all lower-case). Now click "Enabling 32-bit card support" in the bottom frame and then click the Display button. What I see here, on two different machines, is:
 
http://www.gate.net/~pweins/nowonder...s/pcmciawh.gif
 

Ok, did what you asked me to on the Enabling 32 bit support. When I went there all it did was pop up the properties for the card slots. The first slot was empty and the second displayed my NIC. The help said that if I saw the properties then it was already installed. What now?

Well Vernon, looks like I finally got it to work. I removed the PCMCIA service on the laptop and then did a reboot. I then did the detection of hardware and it detected the service. I then had to manually load the drivers for my NIC by way of floppy of course but I finally got it. Although painfully slow it will do the job it is needed for. Thank you for all your help!Please reply to this to let me know you got the message. THANKS AGAIN!

Hey hey, good to hear you finally got it up and running. That remove/reboot/redetect step is covered in that Microsoft Troubleshooting ... link above. Anyway, thanks for letting us know the problem's been solved. More often than not we never know.