Re: Please, don't kill my WiFi!
- From: "Paul G. Tobey [eMVP]" <p space tobey no spam AT no instrument no spam DOT com>
- Date: Fri, 31 Aug 2007 15:29:40 -0700
Microsoft allows it to be fixed, is how I understand it. The OEM still has
substantial control over what they actually expose that the system supports,
if you see what I mean. Fingers crossed, of course.
If you rebind the adapter, it's *very* unlikely that you'll get a different
IP address; very unlikely. The DHCP server is going to keep you in a cache
for a while after you go away (in fact, it probably won't even know that
you've gone away, as there's no ongoing communication between client and
DHCP server, until the lease is getting old). So, when the same Ethernet
address comes in and asks the DHCP server for another IP, it's virtually
certain that it will get the same one as last time. I'm constantly
rebooting our devices while under development and they will *forever* get
the same IP from our DHCP server, unless the server runs out of DHCP
addresses to assign and a new Enet address comes in and wants an IP...
Paul T.
"John" <John@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:7446D188-8A3F-4A76-B322-A2265F05AFD8@xxxxxxxxxxxxxxxx
If you're doing option #3, you'll have a significant amount of work to do
when Windows Mobile is based on Windows CE 6, presumably in the next
version
after WM6. You won't be able to do any UI stuff from inside the driver
because it will be in kernel mode. No other problems that come
immediately
to mind, though.
Yes, I know about CE 6 changes.
But, hopefully I will not need to port this solution to WM 7 because you
said
that the problem was solved in WM 6.
Anyway, my goal is to use my old WM 2005 Pocket PC as a WiFi bridge.
If it will work, then I will be able to use it for years to come and will
not need an upgrade.
I like solution #2. As long as AS isn't persistent about unbinding the
adapter over and over, this scheme requires no low-level access to
anything,
uses all documented interfaces, and should work.
Yes. CSPNET.DLL does unbind when you plug in AS, after
the adapter is enabled (this explains why WiFi actually works for a second
after setup, then breaks, as I explained in my ninitial post),
after suspend/resume cycle, may be some other occasions, which I haven't
seen yet.
So, the message box certainly should have an option "Don't show it
anymore",
otherwise it is too annoying.
But, method #2 re-binds adapters few seconds after they are unbound,
so all active connections will be broken, DHCP lease will have to be
re-established, you may get a different IP address, etc.
So, I will stick with a driver approach.
John
.
- Next by Date: Re: ActiveSync 4.5 can't find ipaq device
- Next by thread: Re: ActiveSync 4.5 can't find ipaq device
- Index(es):
Relevant Pages
|
|
