PDA

View Full Version : NX70V runs slooooow when CF is in place.


Apurva
12-21-2003, 12:04 PM
Hi all. I recently purchased the WL100, so I had to change my CF storage driver (I read that the EUWare drivers wouldn't allow me to use the WL100). I followed the instructions on the first post of the sticky thread, and installed the hacked data drivers from Peleca's website. Everything works now (I can listen to MP3's, AND use the WL100). However, when the storage card is in place, my NX70V runs VERY slowly. About half the speed, actually. This is regardless of whether or not I'm listening to MP3's. And its not just stuff that reuquires the CF card. Pretty much every program is very slow. Even the graffiti area gets sluggish at times.

This all goes away when I remove the card. I did a few searches (spent about an hour total) and haven't found anything mentioning this. Hoping someone has an explanation, or even better, a solution? Thanks in advance.

Oh, if it matters, I use a Memorex 128MB SD card. And for some reason, the CFUtility cannot recognize my card, but it works just the same (When I get to the CFUtility scree, I get N/C or something like that, even when the card is installed).

-Apurva

cliener
12-28-2003, 03:24 PM
Only suggestion I can make is to try a different card? See if your results are different. If not then something may be wrong with your clie? Just a suggestion but it looks like I am the only reply on this so far. :)

yr3698
12-28-2003, 09:15 PM
Woa, wait a min. How are you using a 128mb SD card. Im guessing you meant MS card.

Apurva
12-30-2003, 05:25 AM
Thanks for the replies guys. I bought a new CF card-Sandisk 512MB CF card, and it runs much faster now. There is still a small but noticable speed hit however. But is small enough with this card that I can live with it.

And yes, I meant MS, not SD, in my earlier post. :)

-Apurva

tprime76
01-01-2004, 08:00 PM
Did you install the audio libraries from the UX? While it did improve the quality of the MP3 playback, it did slow my NX70 down as well. I took the lazy man's way out... I just overclocked instead of trying to figure out WHY the problem was occurring.