![]() ![]() I downloaded the standalone upgrade to Mac OS X 10.4.1, repaired permissions, and restarted under Safe Mode, did the install and then restarted and repaired permissions again. They indicated that new mail was there, but it was inaccessible. "After I updated with Software Update, my mailboxes wouldn't show the contents. MacFixIt reader Steve Siegel, for instance, writes: Re-installing the standalone Mac OS X 10.4.1 updater Several readers have reported that re-applying the standalone Mac OS X 10.4.1 updater rather than the version available through Software Update resolves this issue. Then it shows that 2 emails came through but that is all and it tries to get email again followed by another spinning beach ball." My only recourse is to Force Quit and restart Mail. But then the application freezes and a spinning beach ball appears for the cursor. When I open up mail, the activity viewer shows that it is trying to get mail in four separate accounts I have for me and my family. "I have been having big problems with Mail after upgrading to Mac OS X 10.4 (first 10.4, then 10.4.1) on my Aluminum PowerBook G4. My Yahoo! mail sub-inbox would show mail, but it wouldn't show up in the general inbox." However in my largest mailboxes, it would not. In some cases, clicking on one of the headers in the mailbox ('From,' 'Sent,' 'Attachment,' etc.( would sometimes show the mail. "I, too, had problems with seeing mail in my various mailboxes since upgrading to 10.4.1. MacFixIt reader Steve Sussmann corroborates and further describes the issue: Mail.app 2.0: Problems with stored mail Yesterday we noted an issue in Mail.app 2.0 (running under Mac OS X 10.4.x) where the application becomes unresponsive (displays the spinning beach ball status indicator indefinitely) or exhibits other issues when the user attempts to view mail messages from a non-IMAP account (POP, etc.). However, it still follows it's privacy defaults so still ignores system folders." He did inform me that Spotlight reverts to filename/catalog b-tree search if an index isn't present. A user can force an index of system folders using the mdimport command, but it is not recommended at all. Image spotlight spiking CPU constantly for this. With how often system is changing it's files, caches, installing updates, etc. ![]() Anything spotlight has indexed, will be reindexed every time file is modified. "There is also a noted issue about spotlight performance he brought up. He told me it is apples wishes to keep system files from appearing to the common user who might type in a phrase that could pull up system files that a less experienced user could harmfully alter. This prevents Spotlight from indexing these system folders. "He told me this is why spotlight wasn't finding invisible files: mdimport (the process used by Spotlight for indexing) has a built in list of privacy folders on top of those defined in the Spotlight System Preferences pane. More specifically i was trying to locate files in usr directory and other system directories. "I talked with a buddy of mine that works at Apple about the spotlight invisible file issue. ![]() More on invisible file limitations MacFixIt reader Adam Williams shares some insight gleaned from an Apple employee on why Spotlight will not find some invisible files: "So I used the Privacy-Tab of Spotlight's preferences to kick the backup-drive out of Spotlights universe - and the -process went fine and complete this time." When Retrospect wants to copy the files it finds newer versions already present that it can not overwrite because they are 'in use.' This appalls Retrospect so much - it doesn't even want to finish the rest of the "I concluded that Spotlight was indexing the clone-partition while it was written. "When trying to create my first bootable backup since installing Tiger, Retrospect stalled in the middle of the action with several errors. MacFixIt reader Thomas reports one such issue when using Retrospect to perform a routine backup: Disable Spotlight for backup target volumes Users should disable Spotlight for backup target volumes (by using the "Privacy" tab of the Spotlight pane in System Preferences) before beginning the backup process to prevent live indexing as the files are copied.įailing to do so can result in failed backups, significant performance issues, and other problems.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |