I found in this blog about New Intel Drivers that fixed often WiFi disconnections suffered by R2H owners. Well, I was having the same issue in my Q1 and after installing them the issue disappeared.

--
Posted By CTitanic to ULTRA MOBILE PC TIPS at 12/30/2006 08:41:00 AM

Anyone tried this on their Q1 yet? Any improvements?

Spit:

Anyone tried this on their Q1 yet? Any improvements?

Did you read what I said?

FWIW, I updated these drivers for all the Intel hardware that there were new drivers for (i.e. not graphics and CPU) on my TabletKiosk eo i7210 today and have not noticed any negative side effects...yet.  I can't say I've definitely observed any improvements, however.  Some things do seem snappier, but I have no measurements to back up the feelings.

What WiFi issues were you having with the Q1, Ctie? I'm a USB modem type myself. EV-DO on Verizon rocks! I've never lost that connection.

Can you describe the problem a little clearer?

Don't Panic!:

What WiFi issues were you having with the Q1, Ctie? I'm a USB modem type myself. EV-DO on Verizon rocks! I've never lost that connection.

Can you describe the problem a little clearer?

My wifi was getting disconnected even when the signal strength was excelent. It was not often, it was about 1 to times in every 3 to 4 hours. Now with these new drivers still getting disconnected but not that often. According to some pages this happens due to a feature of Zero Configuration that tries to scan for new networks with better signal to reconnect your device to those with better quality.

ctitanic:

Don't Panic!:

What WiFi issues were you having with the Q1, Ctie? I'm a USB modem type myself. EV-DO on Verizon rocks! I've never lost that connection.

Can you describe the problem a little clearer?

My wifi was getting disconnected even when the signal strength was excelent. It was not often, it was about 1 to times in every 3 to 4 hours. Now with these new drivers still getting disconnected but not that often. According to some pages this happens due to a feature of Zero Configuration that tries to scan for new networks with better signal to reconnect your device to those with better quality.

I used to have this problem with one of my desktop machines years ago, though it wouldn't go 10 mins without a disconnection. I disabled Wireless Zero Configuration altogether, and the problem disappeared. It's now the first thing I look at when experiencing disconnection problems :)

ctitanic:

... According to some pages this happens due to a feature of Zero Configuration that tries to scan for new networks with better signal to reconnect your device to those with better quality.

From reading around, I believe it is the Wireless Zero Configuration (WZC) service that's periodically checking for better connections.  Apparently, if you are afflicted with this issues, the recommendation is to disable the Wireless Zero Configuration service and use the configuration software provided by the wireless NIC vendor to configure your wireless card instead, that is if you have this software.  Most cards come with some.

In fact, if I disable WZC on my TabletKiosk i7210 and use the Winbond configuration tool that came with the eo, I don't experience the the periodic disconnects at all.

But what I found interesting is that if I do use WZC I only experience periodic disconnects when

(a) the eo on it's docking cradle   AND
(b) the LAN that's in the cradle is enabled  AND
(c) the LAN cable is plugged in AND
(d) after WZC service is started the LAN adapter is enabled before the wireless adapter is enabled.  This can happen if I boot the eo on the cradle and the cradle LAN is enabled first, or if I disable both adapters, restart WZC service, then start the cradle LAN and then the wireless adapter

then I see disconnects almost exactly every 10 minutes with 5-30 seconds between reconnects.  So it seems as if WZC is doing a scan on the wireless NIC every 10 minutes (temporarily dropping the connection), but only when it sees that the LAN (on the cradle) is the "primary" (i.e. first) network interface.  If the wireless NIC was started first, it must think it's the "primary" and not do any scans.

How this relates to the problems on the R2H and Q1, I don't know.  But I thought it was pretty interesting.


________________
A longer writeup of my experiments can be found here.