Just starting the stumbler game with a d-link DWL-AB520 multimode on XP. It is a PCI bus card with an antenna hardwired on a coax cable about 3 feet long. I have a full size Ford van with a sunroof. A desktop system is mounted behind my seat, with a 17 inch LCD on the doghouse. The antenna goes out the sunroof, and I'm a stumblin' fool! The AB520 card connects to 802.11a and/or 802.11b networks automatically, so my logs show both a and b networks (actually, mine is the only 11a I've found, but I have not gone very far from home yet)
Theoretically, I should be able to stumble 11g networks, but I'm not sure how I would tell them apart. The only way I can see to tell 11a from 11b is the channel numbers.
It was a rough start, the driver that shipped made clicking the stumbler icon like russian roulette, blue screening 2 out of 3 times, was beginning to be a pain till I actually pulled over and checked the XP dump file. A3AB.sys right on top. d-link site has a new driver dated 31 March 2003, and it is much happier now, and the new utility program is much cooler. The old driver even took my wireless router down when I tried setting up the 152 bit WEP, d-link was even ready to give me an RMA on the router. One of these days I might even give them a call and tell them what the problem was really.
I have a DeLorme Earthmate GPS, which does not seem to work. Thought I saw something about adding support in an upcoming release, soon I hope!
16 April -- I may have spoken too soon on the driver fix. It seems that as long as I am already connected to some wireless network when I start netstumbler, everything works fine. But try to start while the driver is searching for a wireless node and BLAM! Or rather BSOD! Curious.
