View Single Post
  #10 (permalink)  
Old 20th Feb 2007, 8:46 pm
michiganjfrog michiganjfrog is offline
Senior Member
MPx Junkie
 
Join Date: Dec 2006
Posts: 423
Default Re: Glacier 2gb with usb problrms

Quote:
Originally Posted by iwik";p=&quot View Post
Yes i tend to agree.Its one of those sticky type problems.You only have to do a google re usb 2 probs to see.Will be very interested to see how your second Glacier goes.i have another computer which should be usable on USB 2 but wont respond to a usb 2 device.
Please let us know how it goes,im thinking of getting another one.
You said you had tried other cables,where did you source them from?.i wanted to buy a spare.
Les
The cables came from other players, such as the FMP. Ok, you wanted to know, this is how it goes:

When I first got the Glacier, I hooked it up to a friend's machine, using the USB cable supplied with the FMP I got from UXCell. I intended to transfer 2GB to the unit. After about 492mb of transfer (512MB I figure), it refused to continue the transfer, even after disconnecting and reconnecting the USB a few times. I gave up and decided to try this at home. Using another USB cable from another chipod, I managed to go beyond the 512mb barrier on my own computer (without doing anything special beforehand, such as reformatting). Although it gave me the USB 2.0 error a few times.

After some initial hiccups, it began to correctly transfer the files, but at 922 mb, it stopped with a volume error. After that, the green arrow indicating a USB peripheral in my system tray was no longer there, meaning the system no longer recognized the Glacier, although the Glacier thought it was still connected, since the black arrow was still in the middle of the connect SCREEN (instead of the zzzzz's). I dont know if it matters, but I had taken the battery out before this, so it was being powered by the USB port. Some mp3 players cant receive power from the USB port,but the glacier isnt known to be one of them.

The Windows error message that popped up was "Reconnect device... not recognized... explorer has problem". After closing the error window, the desktop refreshed itself for a second and windows saw the glacier again, automatically without my having to disconnect and reconnect. Then i stared transferring more files. A 20mb batch transferred okay. I intitiated another batch transfer of about 800MB, and this took about 20min, and succeeded. The player was filled to about 1.32GB. I tried filling the rest of the capacity, which took about 13:50s. It was only after it was full that I did a low level format, and confirmed it had 2GB.

Personally, I like the Glacier enough that if it has occasional problems transferring or conecting at usb 2.0 or staying connected, I think I can live with its communication quirks.
How often do you fill the player up, anyway? The list of players that can compete with it are small, and there's always some serious drawback to the competition (ie. it uses a 2.5mm jack, it costs twice as much, etc). To truly compete, they'd have to have a Nokia BL4c, a speaker, a min. 2.0" tft screen, reliable button design, 2gb onboard min. flash, be about the same price and preferably AMV for the simple fact that you can fit a lot more videos on 2gb with amv than avi (many people think you dont have to convert if its AVI because the ads tell you that, but they lie! You still have to convert to "special AVI for MP4" standard). You can get players with SD cards but the price of a 2gb card is close to the price of the player.

Out of curiousity, I tried the fresh new working battery in my old non working Glacier to see what would happen. I got as far as the movie screen, at which point the player gave me a low battery warning and shut off. I check the battery it ws 3.4v, and of course, played fine once installed back in the new glacier. After trying 3 Nokias in the old Glacier, I think I can pretty much confirm for certain the old Glacier gave up being able to either play or recharge a battery (it may work thru the USB port but thats not very practical for a portable player!).
Reply With Quote