Kudos. You guys made a tremendous 8.04 deadline job. You even added suspense ;-) This report may be incomplete, but I wanted to thank for the impressive improvement regarding general ease of use. The only problem I see is RT2500 download data rate. Shall we tell them? http://www.bluenext.co.uk/wifi-adapter/bn-wd54g-wireless-usb-adapter.html Now VISTA Supported, you can plug and play in Windows VISTAtm without install driver! New Mac and Linux driver is avaliable* * Mac and Linux driver is not offically supported by us. I installed 8.04 CR, near to what 8.04 LTS will be, on two computers. For the first time, my two ex-infamous Ralink-based wifi interfaces ran out of the box (well, I didn't put them back in it and they escaped, you know what I mean). Up to 8.04 beta included, I had to install serialmonkey for both. Specifically : USB 148F:2573 mod=rt73usb case=BlueNEXT BN-WD54G PCMCIA "RT2500 802.11g Cardbus/mini-PCI" mod=rt2500pci case=Comtrend GN-WMKG Both bought cheap on Ebay and are now nicely hot pluggable. Switch is USR5462 configured with WPA & TKIP. Channel 1 as I had had recongition problems of 12 before. I've run 1500 bytes pings for hours (ping 192.168.0.1 -s 1500). Not a single packet loss when running a sigle interface alone in an idle machine. Up to 5 hours for the RT73, probably 9 but I lost the stats, I explain why... Remarks are: - Internet download data rate is OK on RT73 (350 KiB/s) but slow on RT2500 (20-40 KiB/s) but I made decent Web browsing. CPU rate difference (800/400 MHz) cannot be the reason. To be checked. - The pings didn't run simultaneously on both machines. Once one got replies, the other stopped and they alternated. The computers were very near one another though. Fixed by moving one interface away. - The computer running RT73 freezes (behind a power&screensaved display) after a long time of inactivity (but PING). This is why I can't be sure of 9 lossfree hours. I suspect the hanging is not RT73 related, though, more probably to the screen. I would come back here if it was. - The 2500's second LED is off whereas serialmonkey switches it on and blinking when packets flow (seeing it off meant it wasn't working, as when just plugged in). Annoying but I would trade just this for the rest. - I wonder why it is/was hard to port excellent serialmonkey's sources to here, but they probably know much better than I. RT73: ----- --- 192.168.0.1 ping statistics --- 17303 packets transmitted, 17295 received, 0% packet loss, time 17302100ms = 5 hours rtt min/avg/max/mdev = 1.419/4.741/874.366/41.046 ms (64-bytes only pings, up to 9 hours 1500-bytes sessions ran smoothly but were interrupted by crash) rest is 1500-bytes 8801 packets transmitted, 8799 received, 0% packet loss, time 8800036ms rtt min/avg/max/mdev = 8.067/26.500/2091.843/151.196 ms, pipe 3 RT2500, all 1500-bytes ---------------------- --- 192.168.0.1 ping statistics --- 1315 packets transmitted, 1312 received, 0% packet loss, time 1314069ms rtt min/avg/max/mdev = 152.395/201.203/289.634/23.264 ms 2582 packets transmitted, 2308 received, 10% packet loss, time 2585980ms rtt min/avg/max/mdev = 143.066/271.846/6339.902/386.283 ms, pipe 4 (during Firefox activity 2149 packets transmitted, 2144 received, 0% packet loss, time 2147901ms rtt min/avg/max/mdev = 142.910/202.812/956.557/32.999 ms 8536 packets transmitted, 8519 received, 0% packet loss, time 8634489ms rtt min/avg/max/mdev = 147.349/304.278/10243.521/814.358 ms, pipe 6