| April 2002 | ||||||
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
| 1 | 2 | 3 | 4 | 5 | 6 | |
| 7 | 8 | 9 | 10 | 11 | 12 | 13 |
| 14 | 15 | 16 | 17 | 18 | 19 | 20 |
| 21 | 22 | 23 | 24 | 25 | 26 | 27 |
| 28 | 29 | 30 | ||||
| Mar May | ||||||
This site is no longer maintained.
My current weblog.
From 80211b News: D-Link announces June availability of its dual-radio a/b access point.
I'm not so sure that this really matters. Businesses should be buying products with more security features. Consumers can buy individual 802.11a and 802.11b access points for less money. Many APs use PC Card radios, making them just as "future proof" as a Mini-PCI chassis.
And I'm still waiting for an 802.11a Compact Flash card.
PPCW: Be aware of the iPAQ H3870 Bluetooth/Wireless Pack bug. Seems that Compaq's Bluetooth driver and the GPRS wireless pack do not co-exist.
Reiter on NTT's launch of 802.11b/a:
You can doubt today's financial models for public 802.11 networks. And you can doubt whether aggregators like Boingo will succeed. But you had better not doubt the eventual success of nationwide 802.11 hotspots. Frankly, this is a no-brainer.
What are the parameters for success?
My money is on GPRS, 1xRTT, and their successors. The pricing sucks now, but flat-rate is already happening. Speeds will improve. Coverage is already better than 802.11 can ever hope for. Hotspots won't go away, but their success will be narrow.
First Impressions with the Compact Framework
Hey, it works. Haven't crashed anything so far. The memory usage for a "does almost nothing" executable is much lower than it was with Embedded Visual Basic.
My Winsock.LocalIP problem still exists with System.Net.IPHostEntry, must be a problem with the underlying CE APIs.
Almost none of the APIs exclusive to CE are exposed. This is very disappointing, as Pocket PC for CE.NET isn't going to happen this year. I'm going to have to learn that PInvoke stuff if Pocket Blog is going to get a spell-checker...