As it is, when exporting a soundpack if one .dat custom sound file can't be read and validated properly, the creation of a soundpack immediately fails....

So I was just wondering if perhaps instead of not creating anything at all, Plus! could create a soundpack with all the "valid" custom sounds, and perhaps inform the user of any "corrupt" ones.

I purposely corrupted a sound file a while back when testing something, and then couldn't remember which one, so Plus! now fails when making a soundpack of all my custom sounds. Maybe the "corrupt" ones could have their information removed from the registry and the file deleted or something similar?

Just a small suggestion

Yeah, there are also other small inconveniences with adding/exporting/importing custom sounds and sounds packs.

Anyways, I'm not sure if you did found the corrupted file or not (not clear from your post), but in case you didn't, you could use the MsgPlus Sound Library Fixer for that.

You can find this out in two ways: either you first remove all the custom sound data from the registry (do not use Plus! for that, otherwise the files will also be deleted) and then use the Sound Library Fixer to re-add them all.

Or you simply scan your sound library with the Sound Library Fixer and compare the given list with what you'll see in the Sound Library in Messenger Plus!.

This because the Sound Library Fixer will not read in, nor add, corrupted or invalid sounds.

I'm probably getting a new hard drive soon, and gonna do a fresh install of Windows, hence the wanting the sounds as a soundpack.

I never did find the corrupted sounds, and so I will be using the MsgPlus Sound Library Fixer when i have the new drive

Hadn't thought about deleting the registry data though Thanks Cookie

Edit: Thanks again Cookie, it worked