Intel Cardbus II tight fit in socket

[jlittle]

I am using a Mitac 7020 (one of the recommended notebooks for Intel's IPD program, manufacture date July 2000)with the Cardbus II. The adapter slides in OK and is recognized by Windows as documented in the manual. The notebook manual also says the machine is Cardbus compliant. However ejecting the card is next to impossible. Is this normal for this card or is there something wrong with the sockets or the card? Other cards eject normally.

Also, where can I get DOS drivers for this card?

Thanks for your help
John Little

[Intel(R) Customer Support Joe M.]

John:

I have the same NIC and it fits snugly into my laptop. I have other PCMCIA
adapters that release with less force and some that are on par. I have been
using it since I got it with the laptop (about 6 months) with no incident. I
insert and remove the adapter on the average of at least once a day. Are you
seeing any wear on the slots or the adapter?

Regards,

============================
Joe M.
MCSE, CCNA
Internet Support Engineer
Networking Products
Intel(R) Customer Support
http://support.intel.com
sup...@mailbox.intel.com

* Other names and brands may be claimed as the property of others.

"jlittle" <jli...@computercentral-1.com> wrote in message
news:eea2e...@WebX.9CDEEn2n...

[jlittle]

Hi Joe,
I'm not seeing any wear on the card but it is only a few weeks old. I have only taken it in and out a few times. I literally have to take the eraser end of a pencil and push the eject button to push it out. In comparing it to another card today I noticed that the slot on the left hand side on the connector end of the card is shallower than the other cards i.e. the part that slides into the pcmcia socket is thicker which would explain why it is so tight. As terrible as this sounds could that be thinned out by using some fine sandpaper or steel wool? I'm thinking that the Mitac notebooks are maybe just tight there. Please let me know what you think.

Regards,
John

[Intel(R) Customer Support Joe M.]

John:

I have to warn you straight off, doing such a thing is not supported by
Intel. If you do it and something goes wrong, you are pretty much on your
own. That being said, I see no great reason that you could not reduce the
width of that piece, as long as you thin from the center out. Removing from
the outside will do no good and possibly cause problems. The main purpose of
those small pieces is to keep you from putting the adapter in upside down,
and keep the adapter from dropping too low and possibly bending pins in the
socket. Personally I think you would be better off with a fine grained
sandpaper. Do all Intel(R) CardBus II adapters fit this tightly. When
ejecting my NIC, I have to grab the opposite of the laptop. If I don't the
laptop and port replicator go sliding across the desk. Personally, I prefer
it to be tight like this, I am assured that the NIC is solidly in the
computer and most likely making good contact. But that's just my opinion.

Regards,

============================
Joe M.
MCSE, CCNA
Internet Support Engineer
Networking Products
Intel(R) Customer Support
http://support.intel.com
sup...@mailbox.intel.com

* Other names and brands may be claimed as the property of others.

"jlittle" <jli...@computercentral-1.com> wrote in message

news:eea2...@WebX.9CDEEn2n...

[jlittle]

Hi Joe,

Your warning is taken to heart. I had already thought about that but it is better to hear it from you.

Back to the tight fit, since this conversation has been going on, while ejecting the card something apparently bent on the eject button and now the eject button does not pop all of the way out. While the card still seats properly, this prevents getting the full range of motion to push the card out where it can be gripped. In other words it moves the card enough to disconnect it from the pins but not out of the socket enough to grasp it. I'm still thinking that Mitac just uses a tight socket since yours is tight but apparently it will come out ok. I'm discussing this with Mitac as well.

Please let me know any other thoughts or suggestions.

Best Regards,
John

[Intel(R) Customer Support Joe M.]

John:

I don't really have much else to add. I am going to work with the people
here to see if there is anything else that can be done. Since this is a
manufacturing thing, it is not something that is going to change overnight.
If you find out anything interesting from Mitac, please let me know.

Regards,

============================
Joe M.
MCSE, CCNA
Internet Support Engineer
Networking Products
Intel(R) Customer Support
http://support.intel.com
sup...@mailbox.intel.com

* Other names and brands may be claimed as the property of others.

"jlittle" <jli...@computercentral-1.com> wrote in message
news:eea2...@WebX.9CDEEn2n...

[jlittle]

Joe,

I wanted to let you know the outcome of all of this. I wound up sending my notebook back to Mitac to check out the cardbus issue and a couple of other things that didn't seem quite right.

I now have it back. The adapter fits tight as you mentioned in your post to me but it does go ahead and pop out now. They did put a new cardbus socket in the machine as well as a few other things so I'm going to call it a Mitac problem.

Now back to work on booting the DOS drivers for this card! I worked on it some before I sent it in but I don't remember exactly where I was except that it seemed to be hanging at the boot when trying to load the drivers.

Best Regards,
John Little
MCP, A+

[Intel(R) Internet Support(John C.)]

John:

Thanks for your reply and progress report.

I know the following configuration files will work with the Intel(R) PRO/100
Cardbus II Network Adapters. Keep in mind, you may need to alter your
cbcombo load line in the autoexec.bat file to match your system.

This, along with the following two url's will help:

http://support.intel.com/support/network/adapter/pro100/6495.htm

and

http://support.intel.com/support/network/adapter/pro100/24332.htm

and

http://service1.symantec.com/SUPPORT/ghost.nsf/c92aa8e61de62ad08825694a0011c
f3b?OpenView&Start=1&Count=100&Expand=2#2

====================
Autoexec.bat

path=a:\net
lh a:\net\cbcombo memory=e000
a:\net\net initialize
a:\net\netbind.com
a:\net\umb.com
a:\net\tcptsr.exe
a:\net\tinyrfc.exe
a:\net\nmtsr.exe
a:\net\emsbfr.exe
a:\net\net start
net use z: \\ORSCHUCK001\CLIENTS
echo Running Setup...
z:\msclient\netsetup\setup.exe /$

Config.sys

DEVICE=A:\NET\HIMEM.SYS
DEVICE=A:\NET\EMM386.EXE NOEMS x=e000-e400
DOS=HIGH,UMB
files=30
device=a:\net\ifshlp.sys
lastdrive=z

Protocol.ini

[network.setup]
version=0x3110
netcard=ms$ee16,1,MS$EE16,1
transport=tcpip,TCPIP
lana0=ms$ee16,1,tcpip

[ms$ee16]
drivername=e100b$
; IRQ=3
; IOADDRESS=0x310
; IOCHRDY=Late
; TRANSCEIVER=Thin Net (BNC/COAX)

[protman]
drivername=PROTMAN$
PRIORITY=MS$NDISHLP

[tcpip]
NBSessions=6
DefaultGateway0=
SubNetMask0=
IPAddress0=
DisableDHCP=0
DriverName=TCPIP$
BINDINGS=ms$ee16
LANABASE=0

System.ini

[network]
filesharing=no
printsharing=no
autologon=yes
computername=JAC-test4301
lanroot=A:\NET
username=jacooper
workgroup=orrd02
reconnect=no
dospophotkey=N
lmlogon=0
logondomain=mad1
preferredredir=full
autostart=full
maxconnections=8

[network drivers]
netcard=e100b.dos
transport=tcpdrv.dos,nemm.dos
devdir=A:\NET
LoadRMDrivers=yes

[Password Lists]
*Shares=a:\net\Share000.PWL
JACOOPER=A:\NET\JACOOPER.PWL

===============

It is important to us that we know if we are answering and solving your
technical support issues. Please let us know how you come out and what you
find.

--
====================
John C.
Intel(R) Internet Support

*Other names and brands may be claimed as the property of others.

For the very best in online technical support, please see:

http://support.intel.com/

====================

"jlittle" <jli...@computercentral-1.com> wrote in message
news:eea2...@WebX.9CDEEn2n...