PDA

View Full Version : Did I get a bad 3G nano?


mvalpreda
09-13-2007, 10:50 AM
Vista system, 4GB RAM, AMD 5000+, fully patched, iTunes 7.4.1

Just bought a 3G 8gb Nano last night and it's giving me fits. I plug in my 5G 30gb video and iTunes comes up fine and quickly. I plug in my 1G 4gb Nano and iTunes comes up fine and quickly. I plug in my 3G 8gb Nano and iTunes won't auto start, and when I manually start it, the app takes 2-4 minutes to start and the device takes another 2-5 minutes to show up as an available device. During this time explorer.exe is sucking up 30-50% CPU. I'm using the same cable to connect all 3 iPods.

I hear the connect/disconnect USB noise with the 3G Nano.

I think I got a bad one!

Sancroff
09-13-2007, 11:14 AM
I could be completely out to lunch but that sounds like Explorer is searching the entire contents of the Nano for something to autorun or autoplay or whatever it's called. But why would that only happen with the new iPod?

mvalpreda
09-13-2007, 05:08 PM
After uninstalling iTunes a few times and reinstalling it, works ok now.....go figure.

espanoliPod
09-13-2007, 09:14 PM
Vista system, 4GB RAM, AMD 5000+, fully patched, iTunes 7.4.1

Just bought a 3G 8gb Nano last night and it's giving me fits. I plug in my 5G 30gb video and iTunes comes up fine and quickly. I plug in my 1G 4gb Nano and iTunes comes up fine and quickly. I plug in my 3G 8gb Nano and iTunes won't auto start, and when I manually start it, the app takes 2-4 minutes to start and the device takes another 2-5 minutes to show up as an available device. During this time explorer.exe is sucking up 30-50% CPU. I'm using the same cable to connect all 3 iPods.

I hear the connect/disconnect USB noise with the 3G Nano.

I think I got a bad one!
wow, nice setup... your problem could be fixed with an upcoming firmware update from apple, so try holding off a few days and see if the update fixes it.

EDIT: whoops, didn't see that you got it fixed, i read your second post wrong, sorry about that. good that you got your problem fixed, though.