I was uploading a batch of songs the other day to my RIO car 10gig, and the emplode program froze. I tried again, same thing, emplode froze. So, I decided to send the same file to my 20 gig, and the same problem. BTW, I am using 1.03. The file is encoded using Audiocatalyst (the same program I have always used). So, I reencoded the same song to get a different mp3, and it uploaded fine to both units. The file size is 8,036,052 bytes for both files. Both files play fine on winamp. So, it is obvious that either emplode or the unit(s) did not like this "corupt" file, but any ideas or has anyone experienced the same problem before. Thanks!

It could possibly be a problem with your local machine, for example a problem with the local hard disk on a sector that the "bad" file is sitting on. Have you checked that?

Also, it might be something in the file's tag data. You might want to compare the tag data between the "good" and the "bad" files. There was once a known bug where extra-long ID3V2 comment fields would screw up emplode.

Another possibility is the file name or path name might contain illegal characters.

Way back (about a year ago) I had a file like this, with valid headers that caused emplode to hang during upload. I sent the file to the guys in Cambridge and they fixed the problem in the next build.

So it is possible for something like this to happen.

Thanks for your replies. Everything seems to be okay with my computer, id3 tag was fine etc... I guess I will have to blame this one on a simple fluke.