As I don’t run a Windows workstation day to day, this issue was not readily apparent to me. It seems that the technology shift from AT Command strings to Ethernet involved with the 3G Protocol has caused quiet a stir with DUN users. Windows Mobile DUN discussions.
As you see further down in the responses, a staff member responds putting several questions to bed. He goes on to say that the 3G radios are designed to use Ethernet rather than AT commands for “radio” to “client” based communications. This puts the Linux users in the cold. Many devices are still in use that require the AT command set for control and communication.
Mentioned as well, as if it was an excuse, is that the newer radios don’t even support Serial AT commands. Maybe if the OS authors had continued to include the support for DUN, the hardware would have followed suite? Which came first, the chicken or the egg? It isn’t bad enough that they’ve pushed the use of Ethernet and 3G down Mobile users throat’s, the battery technology isn’t up to par, and the coverage area is minimal!
Thanks Winderz, I’ll stick w/ my Mac!
One Comment
Thanks for this info. I’ve been trying to get BT DUN working on my pda for several weeks w/ no luck. I just don’t understaqnd why microsoft would drop something as useful as DUN without having a clear migration path for users w/ 2 and 2.5 G hardware?
Thanks again,
Sammy
One Trackback
Very nice
just stopped by.