OK, heres an update on what Ive done:
1.
Permissions. As Ive mentioned before, Ive already run
Disk Utility many times, always after the SBBOD has been particularly bothersome. Every time Ive opened
DU, the Repair Disk button has been grayed out. And whenever Ive followed that with a Verify Disk, I was told that everything was OK. So, the disk repair tests have always come back clean.
On the other hand, when Id then run a Verify Permissions, it seems that Id always get the same "problem message" (i.e., the same exact problem would show up each time):
Verify permissions for Martin's HD
Reading permissions database.
Reading the permissions database can take several minutes.
Group differs on "private/etc/cups", should be 0, group is 26.
Permissions verification complete
Following that up with the Repair Permission would yield (not surprisingly):
Repairing permissions for Martin's HD
Reading permissions database.
Reading the permissions database can take several minutes.
Group differs on "private/etc/cups", should be 0, group is 26.
Permissions repair complete
These results are recent (a short while ago, actually). However, as I said, they seemed to be the same results Ive gotten each time before. It then occurred to me that I forgot all about a small utility I had installed a while back. Called
Macaroni, it automatically performs routine maintenance, including a daily Mac OS X Repair Permissions. So I checked the last run (which was at about 1:30 in the morning):
fixperms.pl started Sun Aug 24 01:38:58 EDT 2008
Repairing boot disk permissionss
Information on /:
Device Identifier: disk0s2
Device Node: /dev/disk0s2
Part Of Whole: disk0
Device / Media Name: Customer
Volume Name: Martin's HD
Mount Point: /
File System: Journaled HFS+
Journal size 24576 KB at offset 0x11a51000
Owners: Enabled
Partition Type: Apple_HFS
Bootable: Is bootable
Media Type: Generic
Protocol: SATA
SMART Status: Verified
Volume UUID: 0E8FFE86-E711-338E-B0F6-55CFE0777A67
Total Size: 297.8 Gi (319728959488 B) (624470624 512-byte blocks)
Free Space: 141.0 Gi (151433555968 B) (295768664 512-byte blocks)
Read Only: No
Ejectable: No
Whole: No
Internal: Yes
Repairing permissions on disk /
Started verify/repair permissions on disk disk0s2 Martin's HD
Group differs on "private/etc/cups", should be 0, group is 2610%
Finished verify/repair permissions on disk disk0s2 Martin's HD
Checking special permissions...
Privilege repair complete.
This seems to verify my recollection that the permissions problem Ive been seeing whenever I run
Disk Utility is the same. (I havent a clue what it means, but whatever it means, it certainly seems chronic, recurring after each repair.)
2.
Account. Here are the current account Login Items:
Microsoft AU Daemon
Palm Desktop Background
Transport Monitor
AirPort Base Station
Itunes Helper
ExpanderDaemon
Super Get Info Helper
Xmenu
DocumentPalette
SlimBatteryMonitor
Finderpop-daemon
PopChar
Microsoft Database
SpeechSynthesisServer
Microsoft Entourage
SMARTReporter
Istat menus Helper
GrowlHelperApp
MainMenu
As far as rebooting under a new test account: I havent done that. The SBBOD has been doing drive bys

lately, suddenly appearing, and giving me a lot of griefbut then, just as Im about to log out and log in under a test account, it vanishes.
3.
Apple Hardware Test. I ran it today. (BTW: On the newer Macssuch as mineyou can run
AHT without the Leopard install disk. Apparently, its buried somewhere on the internal HDD...just boot and hold down D as you would via the install disk.)
I ran it twice: The first time I did the quick test (runs a couple of minutes); the second time, I ran the extended test (had a cup of coffee while it ran). Each time it reported that everything was OK.
4.
iStat menus/Activity Monitor. I took particular notice today of what iStat menus was doing when the SBBOB showed up. Each time my system began to become unresponsive (which is a signal that the SBBOD is here, or is about to show up), I noticed that the CPU number shot up from about 5-10% to 80-90%. When I dropped down the CPU menu, I saw that Entourage accounted for almost all of that activity; opening
Activity Monitor simply verified that fact.
Whats next?
