- CS Odessa
- Microsoft
- Mark/Space, Inc.
- Bare Bones Software
- Readers Like You!
- Web Crossing
- VMware
- Fetch Softworks
- MacSpeech
- Circus Ponies

We're at Macworld Expo 2009 in San Francisco with the latest news about the show. Check back often this week for updates!
- Phil Schiller Delivers Lackluster Keynote
- iPhoto '09 Adds Faces and Places
- iMovie '09 Seems to Fix Everything from iMovie '08
- GarageBand '09 Adds Music Lessons
- iWork Turns '09
- Apple Moves to Unprotected Music, Tiered Prices
- Apple Pioneers New Battery Tech with 17-inch MacBook Pro
- Jobs Clears the Air on Health Issue
- Welcome to Macintosh Movie to Screen at Macworld Expo
- MacHEADS Movie to Premiere at Macworld Expo
- TidBITS Events at Macworld SF 2009
Enter Dashboard, Expose, or Spaces Temporarily
Hold down F9, F10, F11, or F12 (or whatever you've set for the Expose and Spaces keyboard shortcuts) for a few seconds, and then release the key to enter and leave the appropriate mode without having to press the key again. This is particularly useful for Dashboard, in which you can check the contents of a widget and then return to your work with a single key press.
Visit plucky tree
Submitted by cricket
Recent TidBITS Talk Discussions
- iWork.com and MobileMe? (1 message)
- Safari Stalling on Opening PDF files (6 messages)
- A contrarian view of Macworld Expo's utility (3 messages)
- Secure Certificate Hack Doesn't Imperil Users (15 messages)
Published in TidBITS 140. Subscribe today to receive TidBITS in email every Monday.
- Administrivia
- Excel Workbook Backup Tip
- A/UX... More Is Better?
- Portable Battery Bye-Bye
- Norris Ear PHONE
- MacDraw Pro Speed Comparisons
- Windows Does CDs
Conflict Catcher Article Conflicts
I want to correct some misinformation in TidBITS-139 about Conflict Catcher. The article claims that Conflict Catcher automates the process of loading startup documents one-by-one to identify conflicts. Conflict Catcher does not load INITs one-by-one, but instead loads half of the startup extensions at a time to minimize the number of restarts it takes to locate an INIT conflict. Here's how Conflict Catcher begins to tackle a problem. After you start Conflict Catcher, it loads the extensions that it wants while restarting the computer. When the Finder comes up, you check to see if the problem exists (and that includes opening an application if that's where the problem shows up), and restart the computer. Conflict Catcher will then ask you if the problem exists or has gone away and enables or disables extensions as needed. It usually takes about four or five restarts to pin down a conflict, although that of course varies with the number of INITs you use.
Conflict Catcher is always the first INIT to load, so if the conflict is between two INITs and causes a crash during startup, you can inform Conflict Catcher that the problem exists when you restart the machine. If the problem is more subtle (i.e. the Finder has a corrupt display), then you tell Conflict Catcher when you restart.
Also, Conflict Catcher is able to isolate conflicts between multiple INITs. The article also mentioned incorrectly that Conflict Catcher somehow traces code after startup. Actually, Conflict Catcher only patches a few traps to perform the startup file reordering and to do the ICON wrapping. Both of these features can be disabled so that Conflict Catcher is guaranteed not cause any problems.
[Thanks for the explanation, Jeff. It sounds as though Conflict Catcher will help the user identify and solve conflicts, which is even better than it doing it automatically because then the user will learn from the process as well. -Adam]
READERS LIKE YOU! Support TidBITS with a contribution today!<http://www.tidbits.com/about/support/contributors.html>
Special thanks this week to Michael Destefano Jr., Bob Dahl,
Jason Kerr, and Michael Blaguszewski for their generous support!






