Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Nomad 2 MG memory glitch?

1 view
Skip to first unread message

Aake Kinnunen

unread,
Jan 1, 2001, 8:37:03 AM1/1/01
to
I was just wondering if anybody else has this problem that I had yesterday.

I uploaded a full 128megs of mp3s to the player (64+64Smartmedia) and
previously I had one corrputed mp3-file (had to recode it, otherwise it
crashed the player) but I sorted it out. Now I got one "Corrupted"-file
which I erased and the next song had a timeskip. Player just informed me
"Skip" and jumped some 10-15 seconds forwards.

I then formatted the internal memory once more and downloaded the same file.
No problem this time. So, has anybody gotten the same problem or something
similiar?


Wolf

unread,
Jan 2, 2001, 7:03:34 PM1/2/01
to
I actually had the same exact problem except that it was two songs on my
external memory which crashed my nomad 2 MG. The solution was the same as
yours reformat and re-upload.

Matt Theisen

"Aake Kinnunen" <Sa...@walli.uwasa.fi> wrote in message
news:92q1nt$ifi$1...@news.creativelabs.com...

Aake Kinnunen

unread,
Jan 3, 2001, 10:58:16 AM1/3/01
to
> I actually had the same exact problem except that it was two songs on my
> external memory which crashed my nomad 2 MG. The solution was the same as
> yours reformat and re-upload.

My crash-mp3 was a corrupted one, Winamp played it correctly but it crashed
the whole player, weather in internal or external memory. Recoding it solved
the problem. I'll have to test the other songs I mentioned earlier, while
filling entire memory.

128mb card would be tausty =)


Kevin Schlomas

unread,
Jan 4, 2001, 2:40:17 AM1/4/01
to Sa...@walli.uwasa.fi
Sounds like the corrupted mp3's file pointers got trashed...

Your corrupted file probably freaked the mg's file management system (fms). It
didn't know were the corrupted file ended and the next file began. Reformatting
memory and reloading all your files would probably be the only way to fix the
the integrity of the file pointers.

An observation: I had loaded about 23 WMA's on my mg. I deleted the 3 WMA, then
loaded a different WMA to the mg. I noticed it had taken the 3rd spot rather
than appending to the end of the line. I guess the fms for the mg's memory saw a
free block of memory, with enough room, in the 3rd spot so it loaded the new WMA
there. I tried to rearrange the order of the WMA'S on the mg, but found I had to
load them all on in the order I wanted - from the beginning. Therefore I had to
delete all the WMA'S and reload them in the proper sequence. The point I'm
trying to make here is that the mg's fms is very basic and inflexible (at least
in the firmware/software versions I'm using, the latest version locks up my mg -
long story). Does the newest version of firmware/software allow changing the
order of the files (at least their playback order) once they're on the mg?

Kevin
_________________________________________________________

Michael Christie

unread,
Jan 4, 2001, 11:22:37 AM1/4/01
to
>Does the newest version of firmware/software allow changing the
> order of the files (at least their playback order) once they're on the mg?

Well, I was just about to say that if you try to change the playback order
on the MG then weird things will happen and that it basically doesn't work.
However, I realised that I never tried doing it with the newest firmware,
and guess what, it works perfectly now! I'm so pleased, it was getting a
right PITA when you wanted to add a song to the MG but wanted to put it at a
specific track number because you had to basically format the memory and
transfer everything again.

Anyway, I'm happy!

Michael Christie
Hey it compiles, let's ship it!


0 new messages