![]() |
|
|
#2 (permalink) |
|
Posts: n/a
|
No Luck
I have been working with a Buffalo WLI-PCM-L11G, a Compaq M700 in a win2K server and also in Win98 the Card works great with the OS's but netstumbler can't see the card. I bought the buffalo card specifically to use with netstumbler so needless to say it has been a big disappointment. I have been considering ME any thoughts??
Thanks w00dy |
|
|
|
#4 (permalink) |
|
Posts: n/a
|
Buffalo cards
I've had no luck either. Same card, latest drivers. I borrowed a Cabletron/Enterasys card (identical guts) and it works great. Had to use their driver however, the Win2k driver did not work.
Maybe Buffalo will put out a newer driver soon that will work. |
|
|
|
#5 (permalink) |
|
Posts: n/a
|
Drivers
Do you have a link to the drivers you used?? We may be able to use those drivers with our cards. If you get me the link I will give it a try.
BTW I attempted to upgrade to XP-Pro it failed to load on my POS Compaq M700 (Compaq support was totaly useless). I don't know which is the bigger hunk of junk Compaq or MSXP!! W00dy |
|
|
|
#7 (permalink) |
|
Posts: n/a
|
XP & gold drivers
Well the long and the short of it is that I have attempted to use the Buffalo card under XP ( it auto installed the Bullalo drivers )the OS works great but still no Netstumbler. I have obtained the latest Gold drivers and was unable to get the OS to see the card using them. I can't help but wonder if my Compaq is part of the problem but I can't really see how if the OS is able to use the card. My next move is to try to use the card with another laptop. Has anyone tried an NEC or an HP laptop?? All other WLAN PCMCIA cards I have are the wrong chipset. Any other suggestions are welcome. Its killing me not be be able to use this PROGRAM!!!!
Thanks for your suggestions. W00dy |
|
|
|
#8 (permalink) |
|
Posts: n/a
|
Hmmmm....
Did you get the new XP driver for the card - signal strength etc. listed in the notification icon area when first connected, all the XP eye candy? Have a look at this thread on < a href="http://www.ackers.org.uk/cgi/ikonboard/ikonboard.cgi?s=3bf638e82180ffff;act=ST;f=4;t=7" target="blank"> Ackers.org.uk </a>.
|
|
|
|
#10 (permalink) |
|
Posts: n/a
|
Great Post Guruchill
Thanks for the tip the link didn't work but it got me looking at the site. I found your posts and the XP goodies.
I am still working on getting the Stumbler to work with my gear, not inteligent enough to have success too stupid to quit. I am going to try another laptop today. Any other suggestions are welcome. W00dy |
|
|
|
#11 (permalink) |
|
Posts: n/a
|
Still going
I attempted to make Netstumbler work in a NEC laptop under 95 and a HP under 2000 with my Buffalo card. While the OS functioned flawlessly with the Buffalo Card Netstumbler still failed to see the card.
At this point I think its a Buffalo firmware/Netstumbler issue and don't see how to resolve it short of a new firmware release or a new version of Netstumbler. Still working on it. W00dy |
|
|
|
#12 (permalink) |
|
Posts: n/a
|
Duh
I bought a Buffalo card before finding this forum so I'm also in the land of "no wireless card found" with my Armada E500 and Win98. I'll leave other people to work on the firmware theory but I pulled out my copy of regmon from http://www.sysinternals.com and saw that Netstumbler is enumerating certain keys to do with available ports (COM, LPT, etc) and gives me a "not found" on some enumeration attempts.
I'm wondering if it may be that the Buffalo drivers don't put a registry entry in that Netstumbler is depending on!?!? If we could get some people who can get it to work compare/contrast their regmon logs with those who can't get it to work to see if this may possibly be the issue. Cheers r0ach |
|