" I'm dictating this from a machine running a working copy of IBM ViaVoice on 10.4.7 thanks to your tip plus a little bit of investigation. The culprit seems to be the keywatcher application Service. It seems to get hung up in the background. I disabled it by going to /Library/Application Support/ViaVoice/Utilities/ where it lives and creating a utilities disabled folder.
The only difference I have noticed with the background process disabled, is that certain commands in SpeakPad such as, "Pick 1" do not work anymore.
I hope this helps, it has certainly helped me.

In my experience ViaVoice has been quite superior to iListen. I own both. I'm going to get iListen updated in working and see if I can uncomfortably use it. I just have Moral issues with an application that uses modal error correction.
Sincerely, David G. "

Another reader suggested enabling Access for Assistive devices (instead of speakable items)

" I thought I might suggest that users having problems with ViaVoice (or any vocal input app) first try instead the following:
1) Open System Preferences > Universal Access
2) Check the box at the bottom of the window labeled "Enable Access for Assistive Devices"
3) Enjoy.

Headset and microphone problems occured with Ventrilo until this was done (it's the first thing the Vent troubleshooting FAQ tells you do check if you can't use outgoing communications). Apparently what that little checkbox does is let ALL applications have access to ALL input/output devices.

Just thought I'd throw in another potential tip for your users to try (it's also less irritating than speakable items, as it doesn't...speak.)
- Chibi D. "

"I installed a 1gb memory upgrade on Friday - after the upgrade to 10.4.7, for a total of 1.5gb. Last night, I noticed that MenuMeters showed only 1gb, and like your other feedback, System Profiler showed the lower memory slot as empty. I thought that I messed something up installing the new ram, so I opened up the memory compartment, and switched the DIMMS around. I fired it up again, and now I only had 512MB.
I removed both DIMMs, and only replaced the 512mb in the lower slot and left the upper slot empty. I fired it up and OS X correctly identified the memory. I shut it down again, added the 1gb DIMM again and presto, all 1.5GB are up and running. I did all this before 6:00 AM today, and I have not had the chance to see how it fairs after the next reboot.
-Dave"

I've added this to the 'lost ram' section of the 10.4.7 reports page.

• Investors sue Apple over stock option grants
• Get your Mac, it's raining Trojans
• Do MacBooks Make Business Sense as PC Laptops?
• NetShred X v3.17 released
• Apple rids product line of CRT monitors
• GraphicConverter X 5.9.1 / GraphicConverter 5.9.1
• Podcast Maker 1.2.6
• Find Free WiFi with your PSP