1 Reply Latest reply: Mar 24, 2012 8:05 AM by Linc Davis
cgapperi Level 1 Level 1 (0 points)

Anyone else have issues with slow directory content display with Lion? Having the same issue with 3 machines. It is agonizing up to 30 seconds to display the contents of directories. Think this would be a no brainer, but obviously not. This happens when opening files from within programs and simply in the Finder. Two of the machines are MacPro 2x Quad Core machines with 14GB RAM. Wouldn't think either machine would have any problem with doing this simple task.


Mac Pro, Mac OS X (10.7.3), 2 x 2.26 Ghz Quad-Core 14GB DDR3
  • Linc Davis Level 10 Level 10 (173,925 points)

    Please read this whole message before doing anything.

     

    This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.

     

    The purpose of this exercise is to determine whether the problem is caused by third-party system modifications that load automatically at startup or login. Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards. Boot in safe mode and log in to the account with the problem. The instructions provided by Apple are as follows:

     

    • Be sure your Mac is shut down.
    • Press the power button.
    • Immediately after you hear the startup tone, hold the Shift key. The Shift key should be held as soon as possible after the startup tone, but not before the tone.
    • Release the Shift key when you see the gray Apple icon and the progress indicator (looks like a spinning gear).

     

    Safe mode is much slower to boot and run than normal, and some things won’t work at all, including wireless networking on certain Macs.

     

    The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.

     

    Test while in safe mode. Same problem(s)?

     

    After testing, reboot as usual (i.e., not in safe mode.)