- This topic has 21 replies, 13 voices, and was last updated 21 years, 9 months ago by
.
-
Posts
-
Hello I had same problem with version 6.2
And I found out that there are no sound defined.
Go to messenger Tools- options- General
and there You see Play sounds. Then press button Sounds
And scroll down to MSN Messenger
there you should see 4 entries for messenger
If there are no entries you have same problem than I had.
If somebody needs to resolve this send me a mailKlaus
You are missing some registry entries…
In:
KEY_CURRENT_USERAppEventsEventLabelsMSNMSGR_ContactOnline the ‘data’ entry should read ‘Contact Online’ (you should find that it is blank).In:
HKEY_CURRENT_USERAppEventsSchemesAppsMSNMSGR
add:
HKEY_CURRENT_USERAppEventsSchemesAppsMSNMSGRMSNMSGR_ContactOnline.currentand set the data value to (say) ringin.wav
That should get that first sound going (and it will now appear in the ‘sounds and multimedia’ section of start>settings>control panel. You should be able to work out the rest for yourself (if you shouldn’t then you SHOULDN’T be playing with the registry!)
Hope this helps.
pm.
MSN Messenger 6.2 doesn’t install all the registry keys required under MS-Windows 2000. To solve this problem follow this 3 single steps that actually worked in my PC
1. Copy the blue text below and save it in your pc as a plain text file with .reg extension, e.g. msnsounds.reg (there must be a blank line after each line in the .reg file, including one blank line after the last “[HKEY…. ” line)
REGEDIT4
[HKEY_CURRENT_USERAppEventsEventLabelsMSNMSGR_ContactOnline]
[HKEY_CURRENT_USERAppEventsEventLabelsMSNMSGR_NewAlert]
[HKEY_CURRENT_USERAppEventsEventLabelsMSNMSGR_NewMail]
[HKEY_CURRENT_USERAppEventsEventLabelsMSNMSGR_NewMessage]
[HKEY_CURRENT_USERAppEventsEventLabelsMSNMSGR_IncomingRing]
[HKEY_CURRENT_USERAppEventsSchemesAppsMSNMSGRMSNMSGR_ContactOnline.Current]
[HKEY_CURRENT_USERAppEventsSchemesAppsMSNMSGRMSNMSGR_NewAlert.Current]
[HKEY_CURRENT_USERAppEventsSchemesAppsMSNMSGRMSNMSGR_NewMail.Current]
[HKEY_CURRENT_USERAppEventsSchemesAppsMSNMSGRMSNMSGR_NewMessage.Current]
[HKEY_CURRENT_USERAppEventsSchemesAppsMSNMSGRMSNMSGR_IncomingRing.Current]
2. Locate the msnsounds.reg file that you just created using Windows Explorer and double click on it to run it. It will add the missing events keys to your windows registry.
3. Open the Control Panel, activate the Sounds option, locate the MSN Messenger events and add the desired sound to each one of them (you can also leave some events with no sound).
Any comments will be welcome.
hey streetcat,
how bout we just stick to your new thread for askin the exact same question, instead of asking it in different places. Many people have problems and we try to help everyone, all we ask for is patience. It is unnecissary to ask a question in one thread and a few minutes later go create a new thread. So we can now just stick with your thread to answer your questions. Thanks a lot! 🙂
Hi Ventech,
Thanks for publishing the adjustments to the Windows 2000 registry. I did exactly as you explained in your message and it worked. There is however a small problem. I try to explain.
When I first opened Messenger options there were no entries un Messenger for assigning sounds. Now there is a space between Messenger and the next event that can use sounds. This space is exactly 5 lines high, but there is no text. I can click on each line though and then assign a soundfile. The problem is that I cannot see to which event I assign which sound file. Do you have any idea what may be the cause of this?
I use bothe W2k and Messenger in Dutch.
Thanks,
LucMy girlfriend was having this same problem and unfortunatly when she did the registry editing it gave her the Blank lines in Sound however she couldn’t change the sound at all. So I am posting some registry entries that will set the sounds as the default sounds for messenger. I hope this helps someone out there, Have a nice day.
[HKEY_CURRENT_USERAppEventsSchemesAppsMSNMSGR]
@=”MSN Messenger”[HKEY_CURRENT_USERAppEventsSchemesAppsMSNMSGRMSNMSGR_ContactOnline]
[HKEY_CURRENT_USERAppEventsSchemesAppsMSNMSGRMSNMSGR_ContactOnline.Current]
@=”C:\Program Files\MSN Messenger\online.wav”[HKEY_CURRENT_USERAppEventsSchemesAppsMSNMSGRMSNMSGR_NewAlert]
[HKEY_CURRENT_USERAppEventsSchemesAppsMSNMSGRMSNMSGR_NewAlert.Current]
@=”C:\Program Files\MSN Messenger\newalert.wav”[HKEY_CURRENT_USERAppEventsSchemesAppsMSNMSGRMSNMSGR_NewMail]
[HKEY_CURRENT_USERAppEventsSchemesAppsMSNMSGRMSNMSGR_NewMail.Current]
@=”C:\Program Files\MSN Messenger\newemail.wav”[HKEY_CURRENT_USERAppEventsSchemesAppsMSNMSGRMSNMSGR_NewMessage]
[HKEY_CURRENT_USERAppEventsSchemesAppsMSNMSGRMSNMSGR_NewMessage.Current]
@=”C:\Program Files\MSN Messenger\type.wav”Hello again!
this version of the registry patch has been modified from my original one in order to add a label name to each event, making easier to assign the sound values vía Control Panel – Sounds
I do not include the values for every sound key ’cause the path name changes depending on the Windows language, my one runs in spanish and it says “c:archivos de programa…” where the english version should say “c:program files…”, but the keys values in the message posted just above work Ok too and, you can include them to create your own version of the patch file.
REGEDIT4
[HKEY_CURRENT_USERAppEventsEventLabelsMSNMSGR_ContactOnline]=”Contact on line”
[HKEY_CURRENT_USERAppEventsEventLabelsMSNMSGR_NewAlert]=”Alert”
[HKEY_CURRENT_USERAppEventsEventLabelsMSNMSGR_NewMail]=”New incoming e.mail”
[HKEY_CURRENT_USERAppEventsEventLabelsMSNMSGR_NewMessage]=”New message”
[HKEY_CURRENT_USERAppEventsEventLabelsMSNMSGR_IncomingRing]=”New incoming call”
[HKEY_CURRENT_USERAppEventsSchemesAppsMSNMSGRMSNMSGR_00ContactOnline.Current]
[HKEY_CURRENT_USERAppEventsSchemesAppsMSNMSGRMSNMSGR_00NewAlert.Current]
[HKEY_CURRENT_USERAppEventsSchemesAppsMSNMSGRMSNMSGR_00NewMail.Current]
[HKEY_CURRENT_USERAppEventsSchemesAppsMSNMSGRMSNMSGR_00NewMessage.Current]
[HKEY_CURRENT_USERAppEventsSchemesAppsMSNMSGRMSNMSGR_00IncomingRing.Current]
Hope this information will be useful for all of you. Any comments will be welcome.
- You must be logged in to reply to this topic.