What can cause a PMCMIA slot not to accept a wireless g card, but will accept a b?
What happens is that I load the software as directed, turn off the laptop, insert the card, and restart. Everything comes up ok...the computer recognizes the new hardware and begins installing the drivers and it just locks up...every time.
I've tried everything I can think of:
1. updated bios and drivers for my laptop
2. removed startup group from loading in msconfig
3. disabled onboard nic
4. tried installing in safe mode
5. tried disabling other items (modem, com & lpt ports, ir, 1394)
I have a Cisto Aironet 350 that I use at work and it loads just fine (802.11b), it's the g cards that I can't load (tried Netgear, D-Link, Linksys...all same issue) And yes, I've uninstall the Cisco card before I tried the others.
Anyone have any suggestions?
Oh...by the way it's a Compaq EVO N1020V 2.4 Ghz, 768 Mb RAM, 40 GB HD, XP Pro w/SP1
Thanks,
Drew
yep...called Compaq. They made sure that had all my drivers and updates, then turned me over to the 3rd party vender. I've spoken with all 3 of them as well (Netgear, D-Link, and Linksys)...D-Link won't talk to me any more, and Netgear and Linksys say to try it in another laptop to see if it's the card. I've got a Toshiba 1805-S273 and they all work fine in it, so they turn me back to Compaq.
I just came through (kind of) a similar problem. It worked exactly that way, except that B cards don't work either and it's an old Thinkpad instead of a newer Compaq.
Turned out that the problem was caused by the card not being able to acquire an IRQ. You might open up Device Manager and check that out.
I know that once it's installed you can go throught the device manager and see what IRQs are being used, check for conflicts, etc., but if the device it's there how do you know what IRQ it's trying to aquire?
Thanks
I haven't figured that out, personally. This whole thing should be in the Wireless section. There's a guy named kwebb there who is a pro. I'd go ask him to step in on the matter. I'd like to know if there's a solution, too, but I suspect that there is a BIOS incompatibility at the root. It's just a guess, though.
Well...this was the answer that I finally got from Compaq, after I mentioned a TechNet issue that I found on Microsoft's site concerning a TI PCI-14xx cardbus controller and ACPI:
We are sorry to inform you that we have noticed that some of the PCMCIA card does not work o Evo 1020v model. The reason for this is the TI4410 combined Cardbus controller and the 1394 controller. The power management option can not be changed in the BIOS setup. However few third party PCMCIA cards may work with the Evo N1020v Notebook but you need to contact the vendor of the card to check for its compatibility with the Evo 1020v Notebook.
This came right after I had ask if this could revelant to the same issue that I was having. I think they used my question on revelance to answer my question.
(lot of help they were).
Dude, if that was not in the contract/terms of purchase when you bought your evo (by "that" i mean, 'We are sorry to inform you that we have noticed that some of the PCMCIA card does not work o Evo 1020v model. The reason for this is the TI4410 combined Cardbus controller and the 1394 controller. The power management option can not be changed in the BIOS setup. However few third party PCMCIA cards may work with the Evo N1020v Notebook but you need to contact the vendor of the card to check for its compatibility with the Evo 1020v Notebook.') - then you must just put your foot down.
You need to tell them that they can either replace your notebook with one that does work, give you a refund, or find you a wireless card that suits your specifications and swap it for the one that you have. It is your right to do that, and you just need to be firm and blunt about it (but not rude). Just demand to speak to a manager or someone with authority and tell them that you are not going to be pushed around, and if THEY do NOT rectify the matter, that you will escalate it. Don't let them push you around.
RaPTuRe
Who's General Failure and why's he reading my disk?
I have to agree. IF this was a known issue at the time that you bought the unit and it was not disclosed where you could see it, then you've got a case.
