12.0.01 update does not fix Entourage Notification Sounds

[wmw]

I ran the 12.0.1 updater in the hope that the Entourage/OS 10.5 sound issue
would be resolved - as promised in the update description. The Entourage
version now reads 12.0.1 and the update seems to have gone smoothly.
However, it made no difference whatsoever - still no sounds (they also do not
play when clicking on the speaker icon in preferences).

 

[Michel Bintener]

Hmm, that's very strange. In my case, Entourage is still at 12.0.0 after the
update, but the sounds work as expected. I will post back if I hear anything
from Microsoft about this particular problem.

I ran the 12.0.1 updater in the hope that the Entourage/OS 10.5 sound issue
would be resolved - as promised in the update description. The Entourage
version now reads 12.0.1 and the update seems to have gone smoothly.
However, it made no difference whatsoever - still no sounds (they also do not
play when clicking on the speaker icon in preferences).

--
Michel Bintener
Microsoft MVP
Office:mac (Entourage & Word)

*** Please always reply to the newsgroup. ***

 

[Kerry]

Hmm, that's very strange. In my case, Entourage is still at 12.0.0 after the
update, but the sounds work as expected. I will post back if I hear anything
from Microsoft about this particular problem.



--
Michel Bintener
Microsoft MVP
Office:mac (Entourage & Word)

*** Please always reply to the newsgroup. ***

My sounds work fine.

 

[Scott K]

My sounds do not work either

 

[aRKay]

I ran the 12.0.1 updater in the hope that the Entourage/OS 10.5 sound issue
would be resolved - as promised in the update description. The Entourage
version now reads 12.0.1 and the update seems to have gone smoothly.
However, it made no difference whatsoever - still no sounds (they also do not
play when clicking on the speaker icon in preferences).

I just installed 12.0.1 and the sent and new mail sounds work. I did
not have to mess with the settings

 

[Diane Ross]

My sounds do not work either

Check your Preferences to be sure they are still selected. Also check Sync
Services to be sure they are set correctly. Some users have reported that
Sync Services were turned off during the install.

 

[Doug (Microsoft)]

Hi,

For the sound issue, can you please let me know the following:
1. What version is your Entourage telling you it is? 12.0.0 or 12.0.1.
2. What account types do you use? (Exchange, POP, IMAP, Hotmail)
3. What sound settings preferences do you have set, say ALL ON if all
are set.

Thanks

Doug - dougstATmicrosoftDOTcom
Microsoft
Disclaimer: This mail is provided "AS IS" with no warranties, and confers
no rights.

 

[Art Shotwell]

I've run the update and Entourage is at 12.0.0 and my sounds work. I notice
Word is at 12.0.1.

 

[Diane Ross]

I've run the update and Entourage is at 12.0.0 and my sounds work. I notice
Word is at 12.0.1.

There is a problem with updating the version info. Just be glad the
application is updated and working.

 

[BoliviaKid]

I'm running Entourage 12.0.1. Just installed it a few days ago fresh out of the box. Installed fine and all the sounds worked...until I went in to turn off the just the notification of "no mail" sound. After that no sounds worked, nor does clicking on the little speaker icon next to the sound.

 

[huchin]

Hmmm I'm not seeing that on my machine. Are you using an Intel or PPC
machine? Do the sounds work if you create a new identity and turn off the
"no mail" sound?





Regards,
Hui Nee Chin - huchinATmicrosoftDOTcom
Microsoft Entourage Test
Disclaimer: This mail is provided "AS IS" with no warranties, and confers
no rights.

 

[BoliviaKid]

I'm running an iMac Intel Core 2 Duo, 2.8 GHz

I installed the SP1 update but no change on notification sounds. Maybe I'll try rebooting just for fun!

 

[BoliviaKid]

Ok - on a whim I thought I would reboot (that used to solve many of the Windows XP ills) and voilà! Notification sounds are working after the reboot! I'm not touching them for now - maybe someone else can be a guinea pig.

Thanks for your replies.

 

[Diane Ross]

Ok - on a whim I thought I would reboot (that used to solve many of the
Windows XP ills) and voilà! Notification sounds are working after the reboot!
I'm not touching them for now - maybe someone else can be a guinea pig.

After applying any update, it's advised that you restart your computer.
Repair Permissions is also advised but some say it's useless. It's quick and
it's and certainly doesn't hurt anything.

Using Repair Permissions after installing MS Office or any application that
uses an installer is often advised. To use Repair Permissions:
1. Open Disk Utility in your Applications/Utility folder.
2. Click on the First Aid tab and select Repair Permissions
3. Click on the icon for your boot volume.
4. Click the repair permissions button.

Don't run from CD. Updates contain a newer versions of the application's
permissions.

 

[Diane Ross]

Why would you say that? Many updates in Mac OS X don't even require a
log out - much less a restart.

First, the developers at MSFT advise it. It will clear caches as well.

Repair Permissions isn't the magical tool most Mac users seem to assume
it is. It's a tool that is meant to repair ownership and permissions of
specific sets of files, and only those files listed in the receipts of
specific software in the /Library/Receipts folder.

Office 2008 has receipts in the /Library/Receipts folder.

As you can see, Repair Permissions is a rather brain-dead tool, and is
certainly not half as useful as a lot of people seem to believe. I wish
more people understood this - we probably wouldn't see so many Mac users
running Repair Permissions at the drop of the hat or on a regular
schedule as we see so often. ; )

If you are not experiencing problems with a specific piece of software
listed in the /Library/Receipts folder, there's really no reason to run
Repair Permissions.

Can you explain why it hurts to do this?

 

[William Smith]

That's fine, but I suggest you not make a blanket statement that you
should restart your computer after applying *any* update. There are many
updates for Mac OS X that in fact do not require a restart.

The reason restarting is suggested is not necessarily because of the
installer itself but because restarting can correct *other* issues
unrelated to the update. No application developer wants the user to have
a bad user experience but this could happen and be wrongly blamed on the
update if something else is happening. Restarting the computer puts the
computer into a cleaner state and can prevent a bad user experience.

And your point is?

If you install Office 2008, the installer sets the permissions on all
files it installs - there's no reason to turn right around and run
Repair Permissions, because the files were *just installed*.

Actually, repairing permissions after installing anything that requires
admin privileges, such as Office 2008, is a good idea. Once you enter
your admin credentials then you're giving the installer free reign on
your system.

If you're familiar with QuarkXPress 6.x you may have heard of an
*abominable* issue that it caused. It literally made the entire
/Applications folder read/write to all users (777 permissions).
Repairing permissions would correctly reset all the Apple application
permissions.

The mistake many folks make is that *any* receipt in /Library/Receipts
is used by Disk Utility to repair permissions for that product. Only
Apple products are affected by repairing permissions. Repairing
permissions will not affect any Microsoft product.

I never said it hurts. It's simply a waste of time. Actually, because of
the brain-dead nature I described, it can report conflicting errors and
cause confusion - some might consider that "hurting".

Repairing permissions *should* be done after any install that requires
admin privileges.

--

bill

William M. Smith, Microsoft Interop MVP - Mac/Windows
Entourage Help Page <http://entourage.mvps.org/>
Entourage Help Blog <http://blog.entourage.mvps.org/>