OK, so I have been using build 5600 for a couple weeks now, on a variety of computers.Ã‚Â
My desktop has been rock-solid.Ã‚Â My old tablet PC runs way too damned slow (not surprising – it was one of the first Tablets made), and my IBM ThinkPad T42p runs extremely well.Ã‚Â I actually was surprised to open the Windows Sidebar today and find I haven’t rebooted this machine in 6 days.
That may not sound like a long time to you – but I install a TON of software for testing purposes.Ã‚Â I also write code on this machine (and believe me, my code normally crashes something!).Ã‚Â I usually reboot at least once a day – sometimes many times a day.
I do have one major problem with this build (and it may have existed in earlier builds as well) – Wireless Networking often gets “confused”.Ã‚Â It will associate with an Access Point but will get an IP address of 192.168.0.1 – regardless of what I have set on the AP for DHCP.
This happens, I think, because I have multiple Access Points, all using the same SSID, but each has it’s own security settings – one is 64 bit WEP, one is WPA/TKIP and one is 128 bit WEP.Ã‚Â All with unique keys.
Why do I have things set up this way?Ã‚Â It doesn’t matter, does it?Ã‚Â Shouldn’t it still just work?Ã‚Â XP did.Ã‚Â Apple does.
Microsoft, if you need help replicating this, feel free to contact me.Ã‚Â One key – you need to put the computer in standby (or let it “go to sleep” while connected to one AP, then “wake it up” when you are closer to another.Ã‚Â It gets confused.
My real issue with this problem is that once you get that ip address of 192.168.0.1 the only way I can find to get it to change (ipconfig /renew, or /release do not work) is to delete the physical adapter from the Device Manager and then reinstall the driver.