sound packager

The same Problem here. Just wanted to post about it. Sound packager was working fine before, now i always get an error message when starting it up, and needs to be closed.
Running XP

I tried uninstall, (with restart, reg clean, etc) and reinstall, nothing really helped.

Email [email protected] and reference this thread.

i have tried uninstall, even system restore, even that didnt help have put a ticket in.

Not happy with SP. After the uninstall reinstall it most have killed my Messenger Sounds. My messenger sounds dont work anymore. Its all mute. But the sounds are still there and i can play them (all options are checked etc, and the sounds are enabled, its not a problem of this)

But when i check the registry
HKEY_CURRENT_USER\AppEvents\Schemes\Apps\MSNMSGR\

there is a stardock SP entry. So im pretty sure this problem is connected with SP.

Also when u look at the timeline

1. SP update
2. Sp doesnt start anymore,
3. Sound packages (aquarium) are still working, so is MSN
4. Uninstall SP, Reinstall,
5. SP still not working, MSN sounds are gone,

I completely uninstalled SP
Reinstalled Messenger
still no sounds

It kind of a pain in the a** when u dont here your Messenger sounds, u dont know whats going on.

Hope Stardock has a help.
Still waiting for my mail

No good news.

You also had the problem with Messenger?

Try reinstalling sound packager. There's a button on the Welcome panel that will allow you to set your sounds back to the Windows default. SP doesn't modify the sound settings for the Windows Default scheme, nor any other Schemes you may have created. It also doesn't modify any of the sound setup for MSN (or any other application) for any of the Windows Shound Schemes. But that doesn't mean that something couldn't have gone wrong.

If you're willing to play around a bit maybe you'll be able to diagnose what has happened on your system (before support gets the chance to follow up with you). The first step is to understand what you're actually looking at in the registry. I'll explain with a screenshot.



What you're seeing here is something *similar* to what you should see on your system. Now, look at the MSNMSGR > MSNMSGR_Buzz node that I have expanded. Let's explain what those do...

'.Current' - This contains the path to the file that is currently used by windows, under the current selected sound scheme, to play the sound when the event fires off.
'Sample_Package' - This is a node containing the sound file path for the file that the 'Sample_Package' SP package is instructing windows to play. This has no bearing on any other sound scheme, created by soundpackager or otherwise.

That's where there is a misconception. Now, if you expand the 'Names' node you'll notice a '.Default' node, and a 'Sample_package' node. These nodes specify the name of schemes that are currently recognized by the system. The '.Default' node represents the default Windows Sound Scheme.



Now let's look at this next screenshot. See how the _NewSMSMessage node has the '.default' node, but the _Buzz node does not? That means that MSN did not define a default sound, for the default sound scheme on Windows, for the _Buzz sound even. However, MSN *did* define one for the _NewSMSMessage event. Now, that's not the fault of SoundPackager, but rather the MSN Installer, or application, which should be setting these nodes up properly. Unfortunately, if an application doesnt handle these things properly, even going through the Control Panel to setup sounds manually, 1 by 1, for a new sound scheme will have the same effect.

In the next version of SoundPackager we're going to automatically backup the settings that were present on your system, when SoundPackager is first run, even if the original settings were incorrect or corrupt. that way you can always just revert. I don't have the exact date when the next version is coming out, but it's something to look for. As with any modification software, we're always battling the weird, unusual and incorrect things that other applications force upon the system.

I hope that explains some what is going on, and what you can look for in the future.


Edit: I also wanted to mention that registry cleaning, CCleaner and rebooting will have no effect on this area of the registry. If an application doesnt handle entries into this area of the registry properly, there really isn't much that can be done aside from manual editing, or using SP to reconstruct your original sound packager (which will create the entries properly according to the documentation).

I am not having any problems on my machine but that was a great post andrew_.

Hi Andrew, thanks for your detailed reply

I was able to restore my Messenger. Using Revo Uninstaller, manually deleting all keys, manually deleting all left overs (Application Data, Local Settings).

But back to the first problem. Where everything started.

My SP still crashes at load up. Any solution for this? It all happened after the update. SP was running just fine before. Now as soon as SP starts up and tries to load up the sound packages it crashes.

I`m not afraid of manually editing Registry, using cmd, etc. Just needed to be pointed at the right direction.

TXS so far

Never mind. Figured it out already. And SP is working again

@daygo here is what i did

1. Uninstall SP
2. Make Disc Cleanup (temporary files, etc) not sure if this step is actually necessary
3. When using My Computer for file managment, check show hidden files (cuz there are still some left)
check c:\documents settings (for SP folders)
* All users\application data\stardock
* All users\shared documents\stardock
* Username\application data\stardock

delete them all

4. Go to your SP installation folder. Look for SP. Delete

5. Start Run, regedit root key -> Stardock.Sound>Packager delete

6. Restart

7. Reinstall

Thats what i did. And it worked like a charm

If you not used to edit the registry try 1-4,5,7 without the regedit. And try if it works.
Make a backup before editing the registry, otherwise you might have even bigger problems.

cheers

Be aware that deleting the 'Stardock' directories in step 3 may effect more Stardock applications than just SoundPackager. I wouldn't reccommend doing that.

andrew_ is right on this one. Deleting the whole Stardock directory is a bad idea if you have multiple Stardock titles. That will make them all go away, which is bad. But, going into the above mentioned folders and removing any folders relating to the product you're trying to uninstall (in this case SoundPackager) is a good course of action if you're having problems even after uninstalling.

Also, just to reiterate on something andrew_ mentioned above, if you are having problems with any of the customization apps it is a good idea to use the app itself to reset back to the Windows default before uninstalling/reinstalling. This usually makes the process go a whole lot smoother.

thanks will try and let you know.minus no. 3 that is.

Sry. Perhaps i should have written more precise.

Of course dont delete the Stardock folder. But delete the Sound Package folders in the Stardock folders.

-->check c:\documents settings (for SP folders)

thank you ocrzo and andrew, did what you said and is working fine.

I'm running on vista x86 right now. Just installed Sound Packager (trials) and it doesn't works well. It just stopped working when I start the program. I restarted, reinstalled and downloaded again from the stardock.com and the same things happens. Any solves?

You might want to try the fix listed in this thread....although I would've thouoght that Stardock had already addressed the item.

https://forums.wincustomize.com/?postid=373107