Here's a rather... odd one. Using either EAC or CDex with lame.exe (version 3.90.3) and wapet.exe to encode MP3 files with APEv2 tags, sometimes... wapet.exe will just up and disappear in the middle of a ripping & encoding session. Thinking it may be a problem with EAC, I tried CDex, but it happens there as well. First, I was using the command line of

%d -t "Artist=%a" -t "Title=%t" -t "Album=%g" -t "Year=%y" -t "Track=%n" -t "Genre=%m" -t "Encoded by=My name here" lame.exe --alt-preset extreme -c --space-id3v1 %s %d

Which worked fine for several albums worth, over the period of two or three days. But then, like I said, wapet.exe just started... disappearing. Each time, I'd have to copy the file back. So then I changed the command line to

%d -t "Artist=%a" -t "Title=%t" -t "Album=%g" -t "Year=%y" -t "Track=%n" -t "Genre=%m" lame.exe --alt-preset extreme -c --space-id3v1 %s %d

And it started working again. Except that within a few rips, wapet.exe disappeared again.

I wish I knew what the Hell was going on. What is causing wapet.exe to be deleted in the middle of a rip & encode session?

I'm starting to wonder if maybe between this and my CD-RW drive being damaged a few days ago if this is a sign from God not to use MP3 any longer, and just use another codec instead.

Still, this is beyond odd. I've tried everything I can think of, including changing the name of wapet.exe to blah.exe, and it still winds up being deleted while ripping & encoding. I'm at a complete loss.

I've searched Google and these forums to no avail, I've tried absolutely everything I can think of, I ran System Mechanic on my system, I re-installed EAC and re-configured the settings, and wapet.exe is still being deleted while ripping & encoding. Whatever. Off to Ogg Vorbis land I go, heh.

I guess this kind of rules out the use of any codecs that support APEv2 tagging for me though.

Just FYI for those who are actually reading this thread , I've ripped & encoded 29 CDs using EAC and just plain lame.exe since my second post in this thread, so it is definitely the wapet.exe file that is causing the problem. I mean, obviously it was the one getting deleted, but I wasn't sure if that was what was causing the problem. Since lame.exe has stayed put for 29 CDs worth of ripping & encoding afterwards, I can only assume that there's a rare nasty little bug in wapet.exe somewhere that causes it to commit suicide.

That is strange, but stranger still is that you seem to be talking to yourself.

Later.

Heh, I know. I figured I'd just keep anyone that bothers to read this thread up to date on what the problem may be, since I couldn't find any information on it anywhere, in case anyone else happens to have the same problem. In any case, I'm done talking to myself now that it appears wapet.exe appears to be the culprit itself.

Wapet can't delete itself, Windows doesn't allow such things for executables. Sounds like something broken resident virus scanner would cause.

I suspected that myself as well, as files normally just don't disappear. I use Norton Anti-Virus 2003 with the latest definitions. However, I checked Norton's log file and quarantine sector (since I have it set to automatically quarantine bad files), and neither reported anything remotely related to wapet.exe, nor anything for those days period.

well, you were considering moving to vorbis...
why not musepack? the mpc encoder natively handles ape2 tags, so you don't need a 3rd party program to do it.

plus you'll fall in love with it's encoding speed

if you're overclocking your cpu, don't do it whille encoding using wapet. for some reason it barfs, I found out the hard way too.