802.11b

[Fish]

If you read the fine print on the www.cheezit.org.net.com you find a disclaimer that production CheezIt's are not intended as precision measuring devices. The only accurately calibrated CheezIt is held at the National Beaureu of Standards. Some other interesting standards held at this facility are:
Dogs Hind Leg (crookedness measurement)
Shit Load (dry measure)
Whole Nine Yards (completeness)
Witches Tit (cryogenics)

[CARPEDIEM]

I bought a CF 802.11 wireless card, brand Ambicom. It was pretty cool but i didn't give much use to it. The really cool stuff is that i got it to work on my Laptop by using a CF card to PC card adaptor that i got for free with my 128 simpletech CF card, i had to modify it a bit so it would fit but it worked perfectly. Bad thing is that the windows XP driver is still beta and it experiences micro-disconnections.

So basically if you own a laptop and a PocketPC i'd say go for it because a laptop with a wireless card is the way to go.

[Dan East]

I think I mentioned this in another thread, but I'll post it here to keep things consolidated. I tried what Carpe did, which was to use my CF 802.11b card in my laptop using an adaptor. I also modified my adaptor (tore the metal cover off the top) so the Type II CF card would work in that Type I adapter. However, I discovered (after the fact) that the Linksys CF card will only work with Windows CE. No other drivers are available for it.

The exact reply from their customer support:
The WCF11 is only supported under Windows CE. There are no drivers for it under Windows 2000.

So stay away from the Linksys card if you want something flexible that can be used with different hardware.

Dan East

[Fish]

Dan
Are you using the Linksys WAP too?

[Dan East]

Yes. I have had some problems with it as well. After using the wireless net for a bit (turning my Pocket PC on and off throughout the day, etc) the Pocket PC would stop communicating with the network. I soft reset my iPaq, removed / inserted the card, etc, to no avail. The only way I could get the connection going again was to power the WAP off and back on. That leads me to believe there is a firmware problem in the WAP. I haven't checked to see if any software updates are available yet. Regardless of what goes on with the clients, the WAP should never need to be rebooted.

Dan East

[Fish]

I wonder if it has a DHCP pool that gets used up. But you shouldn't have to reboot it.