aodear

Q: MacBook Pro running slow again after memory and processing upgrades about a year ago. All of the sudden about two months ago my macbook pro has slowed down to a snails pace. Opening applications take over 15 seconds and even within apps it is slow.

Hello There,

 

 

 

Re: 2011 Macbook Pro- currently running El Captain

 

 

About a year ago I upgraded my memory and processing ( I am such a computer novice I don't even know what to call these things). With the help of you folks on the forum and some online videos I rescued my computer. But about 2 months ago it seemed to all of the sudden return to its old snail pace. . .Not sure what the problem is. When I check the usage tool (CPU? etc) it looks like I have plenty of memory and it doesn't look like any particular program is hogging up resources. I upgraded to El Capitain thinking that maybe that was the issue. i wouldn't say the computer is much slower with El Cap but it certainly is not any faster. I am  happy to provide one of those diagnostic lists (etra something) but will need some reminders on how to do it. Even typing this message is taking forever as I have to wait for that beach ball thing every few lines!! ARG!

Thanks in advance for any help!!

 

Best,

 

Anne

MacBook Pro (13-inch Early 2011), OS X Yosemite (10.10.1)

Posted on May 22, 2016 9:58 AM

Close

Q: MacBook Pro running slow again after memory and processing upgrades about a year ago. All of the sudden about two months ago my ma ... more

  • All replies
  • Helpful answers

Previous Page 2
  • by aodear,

    aodear aodear May 22, 2016 1:50 PM in response to Linc Davis
    Level 1 (8 points)
    Notebooks
    May 22, 2016 1:50 PM in response to Linc Davis

    YES!! I figured out what you were referring to!

     

    5/22/16 1:44:27.445 PM iconservicesagent[346]: -[ISGenerateImageOp generateImageWithCompletion:] Failed to composit image for descriptor <ISBindingImageDescriptor: 0x7fa78961b6b0>.

    5/22/16 1:44:27.445 PM quicklookd[7418]: Error returned from iconservicesagent: (null)

    5/22/16 1:44:29.972 PM iconservicesagent[346]: -[ISGenerateImageOp generateImageWithCompletion:] Failed to composit image for descriptor <ISBindingImageDescriptor: 0x7fa7895229b0>.

    5/22/16 1:44:29.972 PM quicklookd[7418]: Error returned from iconservicesagent: (null)

    5/22/16 1:44:37.421 PM Silhouette Studio[7427]: WARNING: The Gestalt selector gestaltSystemVersion is returning 10.9.4 instead of 10.11.4. This is not a bug in Gestalt -- it is a documented limitation. Use NSProcessInfo's operatingSystemVersion property to get correct system version number.

    Call location:

    5/22/16 1:44:37.421 PM Silhouette Studio[7427]: 0   CarbonCore                          0x9673fe3d ___Gestalt_SystemVersion_block_invoke + 135

    5/22/16 1:44:37.421 PM Silhouette Studio[7427]: 1   libdispatch.dylib                   0x938c783f _dispatch_client_callout + 50

    5/22/16 1:44:37.421 PM Silhouette Studio[7427]: 2   libdispatch.dylib                   0x938c771b dispatch_once_f + 78

    5/22/16 1:44:37.421 PM Silhouette Studio[7427]: 3   libdispatch.dylib                   0x938c8fa5 dispatch_once + 31

    5/22/16 1:44:37.421 PM Silhouette Studio[7427]: 4   CarbonCore                          0x966bb8e1 _Gestalt_SystemVersion + 1047

    5/22/16 1:44:37.422 PM Silhouette Studio[7427]: 5   CarbonCore                          0x966bb08a Gestalt + 154

    5/22/16 1:44:37.422 PM Silhouette Studio[7427]: 6   rbframework.dylib                   0x03f14104 RuntimeDebugMemoryUsed + 20372

    5/22/16 1:44:39.354 PM aspex_helper[7435]: WARNING: The Gestalt selector gestaltSystemVersion is returning 10.9.4 instead of 10.11.4. This is not a bug in Gestalt -- it is a documented limitation. Use NSProcessInfo's operatingSystemVersion property to get correct system version number.

    Call location:

    5/22/16 1:44:39.354 PM aspex_helper[7435]: 0   CarbonCore                          0x9673fe3d ___Gestalt_SystemVersion_block_invoke + 135

    5/22/16 1:44:39.354 PM aspex_helper[7435]: 1   libdispatch.dylib                   0x938c783f _dispatch_client_callout + 50

    5/22/16 1:44:39.354 PM aspex_helper[7435]: 2   libdispatch.dylib                   0x938c771b dispatch_once_f + 78

    5/22/16 1:44:39.354 PM aspex_helper[7435]: 3   libdispatch.dylib                   0x938c8fa5 dispatch_once + 31

    5/22/16 1:44:39.354 PM aspex_helper[7435]: 4   CarbonCore                          0x966bb8e1 _Gestalt_SystemVersion + 1047

    5/22/16 1:44:39.354 PM aspex_helper[7435]: 5   CarbonCore                          0x966bb08a Gestalt + 154

    5/22/16 1:44:39.354 PM aspex_helper[7435]: 6   rbframework.dylib                   0x00516104 RuntimeDebugMemoryUsed + 20372

  • by aodear,

    aodear aodear May 22, 2016 1:52 PM in response to aodear
    Level 1 (8 points)
    Notebooks
    May 22, 2016 1:52 PM in response to aodear

    here, this one includes the problems I have while I am typing on this forum:

     

     

    5/22/16 1:44:27.445 PM iconservicesagent[346]: -[ISGenerateImageOp generateImageWithCompletion:] Failed to composit image for descriptor <ISBindingImageDescriptor: 0x7fa78961b6b0>.

    5/22/16 1:44:27.445 PM quicklookd[7418]: Error returned from iconservicesagent: (null)

    5/22/16 1:44:29.972 PM iconservicesagent[346]: -[ISGenerateImageOp generateImageWithCompletion:] Failed to composit image for descriptor <ISBindingImageDescriptor: 0x7fa7895229b0>.

    5/22/16 1:44:29.972 PM quicklookd[7418]: Error returned from iconservicesagent: (null)

    5/22/16 1:44:37.421 PM Silhouette Studio[7427]: WARNING: The Gestalt selector gestaltSystemVersion is returning 10.9.4 instead of 10.11.4. This is not a bug in Gestalt -- it is a documented limitation. Use NSProcessInfo's operatingSystemVersion property to get correct system version number.

    Call location:

    5/22/16 1:44:37.421 PM Silhouette Studio[7427]: 0   CarbonCore                          0x9673fe3d ___Gestalt_SystemVersion_block_invoke + 135

    5/22/16 1:44:37.421 PM Silhouette Studio[7427]: 1   libdispatch.dylib                   0x938c783f _dispatch_client_callout + 50

    5/22/16 1:44:37.421 PM Silhouette Studio[7427]: 2   libdispatch.dylib                   0x938c771b dispatch_once_f + 78

    5/22/16 1:44:37.421 PM Silhouette Studio[7427]: 3   libdispatch.dylib                   0x938c8fa5 dispatch_once + 31

    5/22/16 1:44:37.421 PM Silhouette Studio[7427]: 4   CarbonCore                          0x966bb8e1 _Gestalt_SystemVersion + 1047

    5/22/16 1:44:37.422 PM Silhouette Studio[7427]: 5   CarbonCore                          0x966bb08a Gestalt + 154

    5/22/16 1:44:37.422 PM Silhouette Studio[7427]: 6   rbframework.dylib                   0x03f14104 RuntimeDebugMemoryUsed + 20372

    5/22/16 1:44:39.354 PM aspex_helper[7435]: WARNING: The Gestalt selector gestaltSystemVersion is returning 10.9.4 instead of 10.11.4. This is not a bug in Gestalt -- it is a documented limitation. Use NSProcessInfo's operatingSystemVersion property to get correct system version number.

    Call location:

    5/22/16 1:44:39.354 PM aspex_helper[7435]: 0   CarbonCore                          0x9673fe3d ___Gestalt_SystemVersion_block_invoke + 135

    5/22/16 1:44:39.354 PM aspex_helper[7435]: 1   libdispatch.dylib                   0x938c783f _dispatch_client_callout + 50

    5/22/16 1:44:39.354 PM aspex_helper[7435]: 2   libdispatch.dylib                   0x938c771b dispatch_once_f + 78

    5/22/16 1:44:39.354 PM aspex_helper[7435]: 3   libdispatch.dylib                   0x938c8fa5 dispatch_once + 31

    5/22/16 1:44:39.354 PM aspex_helper[7435]: 4   CarbonCore                          0x966bb8e1 _Gestalt_SystemVersion + 1047

    5/22/16 1:44:39.354 PM aspex_helper[7435]: 5   CarbonCore                          0x966bb08a Gestalt + 154

    5/22/16 1:44:39.354 PM aspex_helper[7435]: 6   rbframework.dylib                   0x00516104 RuntimeDebugMemoryUsed + 20372

    5/22/16 1:48:15.985 PM Safari[2485]: tcp_connection_tls_session_error_callback_imp 180 __tcp_connection_tls_session_callback_write_block_invoke.434 error 22

    5/22/16 1:48:15.000 PM syslogd[40]: ASL Sender Statistics

    5/22/16 1:48:33.065 PM WindowServer[180]: device_generate_desktop_screenshot: authw 0x0(0), shield 0x7fc9bd2c5000(2001)

    5/22/16 1:48:33.122 PM WindowServer[180]: device_generate_lock_screen_screenshot: authw 0x0(0)[inf, inf, 0, 0] shield 0x7fc9bd2c5000(2001), dev [1280,800]

    5/22/16 1:48:33.161 PM identityservicesd[361]: <IMMacNotificationCenterManager: 0x7fbee1c4e0e0>: notification observer: com.apple.iChat   notification: __CFNotification 0x7fbee1c313c0 {name = _NSDoNotDisturbEnabledNotification}

    5/22/16 1:48:33.162 PM imagent[410]: <IMMacNotificationCenterManager: 0x7fc241c2bb60>: notification observer: com.apple.FaceTime   notification: __CFNotification 0x7fc241ea2690 {name = _NSDoNotDisturbEnabledNotification}

    5/22/16 1:48:39.468 PM identityservicesd[361]: <IMMacNotificationCenterManager: 0x7fbee1c4e0e0>:    NC Disabled: NO

    5/22/16 1:48:39.468 PM imagent[410]: <IMMacNotificationCenterManager: 0x7fc241c2bb60>:    NC Disabled: NO

    5/22/16 1:48:39.479 PM identityservicesd[361]: <IMMacNotificationCenterManager: 0x7fbee1c4e0e0>:   DND Enabled: YES

    5/22/16 1:48:39.479 PM imagent[410]: <IMMacNotificationCenterManager: 0x7fc241c2bb60>:   DND Enabled: YES

    5/22/16 1:48:39.479 PM imagent[410]: <IMMacNotificationCenterManager: 0x7fc241c2bb60>: Updating enabled: YES   (Topics: (

        "com.apple.ess",

        "com.apple.private.ac"

    ))

    5/22/16 1:48:39.479 PM identityservicesd[361]: <IMMacNotificationCenterManager: 0x7fbee1c4e0e0>: Updating enabled: YES   (Topics: (

        "com.apple.madrid"

    ))

    5/22/16 1:48:39.479 PM identityservicesd[361]: <IMMacNotificationCenterManager: 0x7fbee1d0c260>: notification observer: com.apple.iChat   notification: __CFNotification 0x7fbee1e7cad0 {name = _NSDoNotDisturbEnabledNotification}

    5/22/16 1:48:39.485 PM identityservicesd[361]: <IMMacNotificationCenterManager: 0x7fbee1d0c260>:    NC Disabled: NO

    5/22/16 1:48:39.490 PM identityservicesd[361]: <IMMacNotificationCenterManager: 0x7fbee1d0c260>:   DND Enabled: YES

    5/22/16 1:48:39.490 PM identityservicesd[361]: <IMMacNotificationCenterManager: 0x7fbee1d0c260>: Updating enabled: NO   (Topics: (

    ))

    5/22/16 1:49:57.109 PM ntpd[186]: time set +0.962990 s

    5/22/16 1:50:27.482 PM WindowServer[180]: CGXDisplayDidWakeNotification [93560739773186]: posting kCGSDisplayDidWake

    5/22/16 1:50:27.483 PM WindowServer[180]: handle_will_sleep_auth_and_shield_windows: Deferring.

    5/22/16 1:50:27.619 PM identityservicesd[361]: <IMMacNotificationCenterManager: 0x7fbee1d0c260>: notification observer: com.apple.iChat   notification: __CFNotification 0x7fbee1d84390 {name = _NSDoNotDisturbDisabledNotification}

    5/22/16 1:50:27.620 PM imagent[410]: <IMMacNotificationCenterManager: 0x7fc241c2bb60>: notification observer: com.apple.FaceTime   notification: __CFNotification 0x7fc241c77360 {name = _NSDoNotDisturbDisabledNotification}

    5/22/16 1:50:27.940 PM imagent[410]: <IMMacNotificationCenterManager: 0x7fc241c2bb60>:    NC Disabled: NO

    5/22/16 1:50:27.940 PM identityservicesd[361]: <IMMacNotificationCenterManager: 0x7fbee1d0c260>:    NC Disabled: NO

    5/22/16 1:50:27.953 PM imagent[410]: <IMMacNotificationCenterManager: 0x7fc241c2bb60>:   DND Enabled: NO

    5/22/16 1:50:27.953 PM identityservicesd[361]: <IMMacNotificationCenterManager: 0x7fbee1d0c260>:   DND Enabled: NO

    5/22/16 1:50:27.953 PM imagent[410]: <IMMacNotificationCenterManager: 0x7fc241c2bb60>: Updating enabled: YES   (Topics: (

        "com.apple.ess",

        "com.apple.private.ac"

    ))

    5/22/16 1:50:27.953 PM identityservicesd[361]: <IMMacNotificationCenterManager: 0x7fbee1d0c260>: Updating enabled: YES   (Topics: (

        "com.apple.private.alloy.icloudpairing",

        "com.apple.private.alloy.continuity.encryption",

        "com.apple.private.alloy.continuity.activity",

        "com.apple.ess",

        "com.apple.private.ids",

        "com.apple.private.alloy.phonecontinuity",

        "com.apple.madrid",

        "com.apple.private.ac",

        "com.apple.private.alloy.phone.auth",

        "com.apple.private.alloy.keychainsync",

        "com.apple.private.alloy.fmf",

        "com.apple.private.alloy.sms",

        "com.apple.private.alloy.screensharing",

        "com.apple.private.alloy.maps",

        "com.apple.private.alloy.thumper.keys",

        "com.apple.private.alloy.continuity.tethering"

    ))

    5/22/16 1:50:27.953 PM identityservicesd[361]: <IMMacNotificationCenterManager: 0x7fbee1c4e0e0>: notification observer: com.apple.iChat   notification: __CFNotification 0x7fbee1d8e4c0 {name = _NSDoNotDisturbDisabledNotification}

    5/22/16 1:50:27.962 PM identityservicesd[361]: <IMMacNotificationCenterManager: 0x7fbee1c4e0e0>:    NC Disabled: NO

    5/22/16 1:50:27.967 PM identityservicesd[361]: <IMMacNotificationCenterManager: 0x7fbee1c4e0e0>:   DND Enabled: NO

    5/22/16 1:50:27.967 PM identityservicesd[361]: <IMMacNotificationCenterManager: 0x7fbee1c4e0e0>: Updating enabled: YES   (Topics: (

        "com.apple.madrid"

    ))

    5/22/16 1:50:44.555 PM secd[368]:  SOSAccountThisDeviceCanSyncWithCircle sync with device failure: (null)

  • by Linc Davis,

    Linc Davis Linc Davis May 22, 2016 1:57 PM in response to aodear
    Level 10 (207,926 points)
    Applications
    May 22, 2016 1:57 PM in response to aodear

    Please read this whole message before doing anything.

    This procedure is a test, not a solution. Don’t be disappointed when you find that nothing has changed after you complete it.

    Step 1

    The purpose of this step is to determine whether the problem is localized to your user account.

    Enable guest logins* and log in as Guest. Don't use the Safari-only “Guest User” login created by “Find My Mac.”

    While logged in as Guest, you won’t have access to any of your documents or settings. Applications will behave as if you were running them for the first time. Don’t be alarmed by this behavior; it’s normal. If you need any passwords or other personal data in order to complete the test, memorize, print, or write them down before you begin.

    Test while logged in as Guest. Same problem?

    After testing, log out of the guest account and, in your own account, disable it if you wish. Any files you created in the guest account will be deleted automatically when you log out of it.

    *Note: If you’ve activated “Find My Mac” or FileVault, then you can’t enable the Guest account. The “Guest User” login created by “Find My Mac” is not the same. Create a new account in which to test, and delete it, including its home folder, after testing.

    Step 2

    The purpose of this step is to determine whether the problem is caused by third-party system modifications that load automatically at startup or login, by a peripheral device, by a font conflict, or by corruption of the file system or of certain system caches.

    Please take this step regardless of the results of Step 1.

    Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards, if applicable. Start up in safe mode and log in to the account with the problem.

    Note: If FileVault is enabled in OS X 10.9 or earlier, or if a firmware password is set, or if the startup volume is a software RAID, you can’t do this. Ask for further instructions.

    Safe mode is much slower to start up and run than normal, with limited graphics performance, and some things won’t work at all, including sound output and Wi-Fi on certain models. The next normal startup may also be somewhat slow.

    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. It will be slow, but there should be no beachballing. Same problem?

    After testing, restart as usual (not in safe mode) and verify that you still have the problem. Post the results of Steps 1 and 2.

  • by aodear,

    aodear aodear May 23, 2016 3:57 PM in response to Linc Davis
    Level 1 (8 points)
    Notebooks
    May 23, 2016 3:57 PM in response to Linc Davis

    Step 1: still ridiculously slow (takes much time to respond- pre-beachball) and beach balling when opening safari or other folders. Everything slow. Not good.

     

    Step 2: Also slow, same problem in both scenarios. Slow to respond ( lagging) then beach ball.

     

    Then I restarted in regular mode. Still So so so slow. Even typing this message, after e every few lines,  I have to wait for the words to appear after I have typed them. SO annoying!

     

    Interestingly after my first or second etracheck, everything seemed to be working perfectly again with minimal lag time. But the problem came back within minutes

     

    Just took me 4 minutes to type this message . . . really hoping you can help!

     

     

    -Anne

  • by aodear,

    aodear aodear May 24, 2016 10:58 AM in response to Linc Davis
    Level 1 (8 points)
    Notebooks
    May 24, 2016 10:58 AM in response to Linc Davis

    any ideas?

  • by padams35,

    padams35 padams35 May 24, 2016 11:23 AM in response to aodear
    Level 2 (163 points)
    Desktops
    May 24, 2016 11:23 AM in response to aodear

    Is time machine connected? Have you adjusted time machine settings or installed an alternative backup system? Are any backups currently in progress?

     

    The high CPU usage for the backupd process is suspicious, and I find it odd that your latest backup is listed as occurring on the 6th.

  • by aodear,

    aodear aodear May 24, 2016 12:06 PM in response to padams35
    Level 1 (8 points)
    Notebooks
    May 24, 2016 12:06 PM in response to padams35

    The time machine was connected when I did the etracheck. I don't think I had it connected when I did the other thing  Linc Davis recommended. Isn't time machine  the back up?

  • by Linc Davis,

    Linc Davis Linc Davis May 24, 2016 1:55 PM in response to aodear
    Level 10 (207,926 points)
    Applications
    May 24, 2016 1:55 PM in response to aodear

    1. This procedure is a diagnostic test. It changes nothing, for better or worse, and therefore will not, in itself, solve the problem. But with the aid of the test results, the solution may take a few minutes, instead of hours or days.

    The test works on OS X 10.8 ("Mountain Lion") and later. I don't recommend running it on older versions of OS X. It will do no harm, but it won't do much good either.

    Don't be put off by the complexity of these instructions. The process is much less complicated than the description. You do harder tasks with the computer all the time.

    2. If you don't already have a current backup, please back up all data before doing anything else. The backup is necessary on general principle, not because of anything in the test procedure. Backup is always a must, and when you're having any kind of trouble with the computer, you may be at higher than usual risk of losing data, whether you follow these instructions or not.

    There are ways to back up a computer that isn't fully functional. Ask if you need guidance.

    3. Below are instructions to run a UNIX shell script, a type of program. As I wrote above, it changes nothing. It doesn't send or receive any data on the network. All it does is to generate a human-readable report on the state of the computer. That report goes nowhere unless you choose to share it. If you prefer, you can act on it yourself without disclosing the contents to me or anyone else.

    You should be wondering whether you can believe me, and whether it's safe to run a program at the behest of a stranger. In general, no, it's not safe and I don't encourage it.

    In this case, however, there are ways for you to decide whether the program is safe without having to trust me. First, you can read it. Unlike an application that you download and click to run, it's transparent, so anyone who understands the code can verify what it does.

    You may not be able to understand the script yourself. But variations of it have been posted on this website many times over a period of years. Any one of the millions of registered users could have read the script and raised the alarm if it was harmful. Then I would not be here now and you would not be reading this message. See, for example, this discussion.

    Nevertheless, if you can't satisfy yourself that these instructions are safe, don't follow them. Ask for other options.

    4. Here's a general summary of what you need to do, if you choose to proceed:

    ☞ Copy the text of a particular web page (not this one) to the Clipboard.

    ☞ Paste into the window of another application.

    ☞ Wait for the test to run. It usually takes a few minutes.

    ☞ Paste the results, which will have been copied automatically, back into a reply on this page.

    These are not specific instructions; just an overview. The details are in parts 7 and 8 of this comment. The sequence is: copy, paste, wait, paste again. You don't need to copy a second time.

    5. Try to test under conditions that reproduce the problem, as far as possible. For example, if the computer is intermittently slow, run the test during a slowdown.

    You may have started up in safe mode. If the system is now in safe mode and works well enough in normal mode to run the test, restart as usual before running it. If you can only test in safe mode, do that.

    6. If you have more than one user, and only one user is affected by the problem,, and the affected user is not an administrator, then please run the test twice: once while logged in as the affected user, and once as an administrator. The results may be different. The user that is created automatically on a new computer when you start it for the first time is an administrator. If you can't log in as an administrator, test as the affected user. Most personal Macs have only one user, and in that case this section doesn’t apply. Don't log in as root.

    7. Load this linked web page (on the website "Pastebin.") Press the key combination command-A to select all the text, then copy it to the Clipboard by pressing command-C.

    8. Launch the built-in Terminal application in any one of the following ways:

    ☞ Enter the first few letters of its name ("Terminal") into a Spotlight search. Select it in the results (it should be at the top.)

    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.

    ☞ Open LaunchPad and start typing the name.

    Click anywhere in the Terminal window to activate it. Paste from the Clipboard into the window by pressing command-V, then press return. The text you pasted should vanish immediately.

    9. If you're logged in as an administrator, you'll be prompted for your login password. Nothing will be displayed when you type it. You will not see the usual dots in place of typed characters. Make sure caps lock is off. Type carefully and then press return. You may get a one-time warning to be careful. If you make three failed attempts to enter the password, the test will run anyway, but it will produce less information. If you don't know the password, or if you prefer not to enter it, just press return three times at the password prompt. Again, the script will still run.

    If the test is taking much longer than usual to run because the computer is very slow, you might be prompted for your password a second time. The authorization that you grant by entering it expires automatically after five minutes.

    If you're not logged in as an administrator, you won't be prompted for a password. The test will still run. It just won't do anything that requires administrator privileges.

    10. The test may take a few minutes to run, depending on how many files you have and the speed of the computer. A computer that's abnormally slow may take longer to run the test. While it's running, a series of lines will appear in the Terminal window like this:

        Test started
            Part 1 of 4 done at: … sec
            …
            Part 4 of 4 done at: … sec
        The test results are on the Clipboard.
        Please close this window.

    The intervals between parts won't be exactly equal, but they give a rough indication of progress.

    Wait for the final message "Please close this window" to appear—again, usually within a few minutes. If you don't see that message within about 30 minutes, the test probably won't complete in a reasonable time. In that case, press the key combination control-C or command-period to stop it. Then go to the next step. You'll have incomplete results, but still something.

    In order to get results, the test must either be allowed to complete or else manually stopped as above. If you close the Terminal window while the test is still running, the partial results won't be saved.

    11. When the test is complete, or if you stopped it manually, quit Terminal. The results will have been saved to the Clipboard automatically. They are not shown in the Terminal window. Please don't copy anything from there. All you have to do is start a reply to this comment and then paste by pressing command-V again.

    At the top of the results, there will be a line that begins with the words "Start time." If you don't see that, but instead see a mass of gibberish, you didn't wait for the "close this window" message. Please wait for it and try again.

    If any private information, such as your name or email address, appears in the results, anonymize it before posting. Usually that won't be necessary.

    12. When you post the results, you might see an error message on the web page: "You have included content in your post that is not permitted," or "The message contains invalid characters." That's a bug in the software that runs this website. Please post the test results on Pastebin, then post a link here to the page you created.

    If you have an account on Pastebin, please don't select Private from the Paste Exposure menu on the page, because then no one but you will be able to see it.

    13. When you're done with the test, it's gone. There is nothing to uninstall or clean up.

    14. This is a public forum, and others may give you advice based on the results of the test. They speak for themselves, not for me. The test itself is harmless, but whatever else you do may not be. For others who choose to run it, I don't recommend that you post the test results on this website unless I asked you to.

    15. The linked UNIX shell script bears a notice of copyright. Readers of ASC may copy it for their own personal use. Neither the whole nor any part may be redistributed.

Previous Page 2