I recently got myself a USB memory stick/MP3 player however when i try and access it under Windows XP it freezes windows explorer or whatever i am trying to use to access it (command prompt etc). When i insert it i get a it i get a "Safley Remove Hardware" icon in the taskbar and it opens up an explorer window showing the files on the device however the window quickly stops responding. And will only go away by ctrl+alt+del and end processing it or by removing the device. Somtimes i get a error message along the line of the device failed to do whatever because of an I/O error. Works fine on my other computer also with Windows XP, SP1. All drivers are the inbuild XP ones on both machines. The rest of the USB stuff on my comp is working fine i have tried disabeling the other usb controlers and only using the one with the mp3 player connected to it but it still doesn't work so i don't think its a power issue. Under Universial Serial Bus controllers in device manager I have: Standard Enhanced PCI to USB Host Controller Standard OpenHCD USB Host Controller Standard OpenHCD USB Host Controller USB Mass Storage Device USB Printing Support USB Root Hub USB Root Hub USB Root Hub I googled it and only from some stuff relating to having usb2.0 causing similar problems with windows 2000. I was going to disable the USB2.0 hub but i carn't find it in the list. I have 3 diffrent USB1 connections (with 2 ports each) which seem to relate to the diffrent "USB Root Hub" entries and 1 USB2.0 (also 2 ports) which doesn't appear in the list so i wounder if it could be related. unfortunatly i carn't test the 2.0 as i have no 2.0 devices. Motherboard: AOpen AK79G-Max nForce2 AMD SktA board http://www.auspcmarket.com.au/show_product_info.php?code=MB-AOAK79GMAX MP3 player: TEG MP304 http://www.auspcmarket.com.au/show_product_info.php?code=MU-USBKEY128B

I believe SP1 gives support for USB2.x http://support.microsoft.com/default.aspx?scid=kb;en-us;329632 http://support.microsoft.com/default.aspx?scid=kb;en-us;813139

I have since tried running it in Linux with the same kind of problems. I think ill repost this in the general hardware forums as it nolonger seems to just be windows screwing around.