Just was adding one song and it looked like it was running fdisk, when I came back this error was up. Going to try it again to see if it persists before emailing bugs@...

...running developer 9c with correct emplode, etc.

(O|||||O)

Update: Worked fine after the next sync... Not going to report it.

(Might have been because that file was open (and paused) in WinAmp, didn't notice until after the error, so it might have been a sharing error.)

(O|||||O)

It was actually a 'file not found' error. This could be a badly reported file in use error but that is unlikely.

emplode should probably cope better with this by recording the fact that the file was missing (or in use) and just carry on.

--
Mike Crowe
I may not be speaking on behalf of empeg above :-)

It was actually a 'file not found' error. This could be a badly reported file in use error but that is unlikely.

Do you think it would be possible for you to post your "errors.h" file for the player? :) It would be cool to have been able to look at that error code and see a FILE_NOT_FOUND #define or something... Granted half the time it might not help, but it still would be kinda useful to those of us who know how to use it. :)

(O|||||O)

I think I'm correct in saying that any 0x8xxxxxxx errors are windows errors, and the error numbers will be somewhere in the Win32 api header files. The 0xffffxxxx ones are generally ours.

Hugo

I think I'm correct in saying that any 0x8xxxxxxx errors are windows errors, and the error numbers will be somewhere in the Win32 api header files. The 0xffffxxxx ones are generally ours.

Anything starting with 0x8 is an HRESULT which is a Windows/COM thing. Facility 7 (i.e. 0x8007) is a Windows API error so you can find out the real error message by taking the bottom four digits, converting them to decimal and looking them up in winerror.h if you have Visual C++ installed.

Anything starting with 0xf is probably one of ours. It may be a Linux error which you can decipher by two's complimenting it, converting to decimal and looking it up in /usr/include/asm/errno.h on a Linux box.

There are a few oddballs which don't fit this pattern.

Of course simple errors like the one described here should be dealt with more elegantly by emplode.

--
Mike Crowe
I may not be speaking on behalf of empeg above :-)

(Might have been because that file was open (and paused) in WinAmp, didn't notice until after the error, so it might have been a sharing error.)

I've been able to synch songs whilst playing them in WinAmp, so that might not be it.

In general, I've been impressed with WinAmp's ability to allow other things to open and read the file simultaneously. Winamp makes sure to open the file for reading only, and as long as the other app doesn't ask for a "write", the two programs can double-team the file quite nicely.

Depending on your system, it could be something more like WinAmp's playback or vis was grabbing too many cycles (or perhaps too many interrupts since the USB port is interrupt-driven)? Dunno much about this stuff, just shooting in the dark here.

Anyone else have more info on this?

Tony Fabris
Empeg #144

Depending on your system, it could be something more like WinAmp's playback or vis was grabbing too many cycles (or perhaps too many interrupts since the USB port is interrupt-driven)? Dunno much about this stuff, just shooting in the dark here.

Actually, once they mentioned the "File not Found" error, I thought about it and I had remembered I was moving files around on my drives, and that was one of them, so the error makes complete sense. I didn't notice it was a WinAPI error. If I had, I would have looked it up, as I'm well versed in the Winblows API.

Silly me. :)

(O|||||O)