Troubleshooting tips

    The best way to make sure iDo Script Scheduler does what you want is to make sure your scripts do what they're supposed to. Apple's web site has a wealth of information on AppleScript, including tutorials for novices and complete references for experts. If you're having troubles writing or debugging your scripts, you'll find it all at <http://www.apple.com/applescript>.

Should I save my AppleScripts as "scripts" or "applications"?

    iDo Script Scheduler can run scripts saved as both "scripts" and "applications". Which you should use depends on the needs of the script. iDo Script Scheduler can send parameters only to "scripts", but in Mac OS 9, they may run out of memory trying to run large scripts with lots of scripting additions. "Applications" can't accept parameters, but they can be double-clicked by the user, and in Mac OS 9, you can give them as much memory as they need. See "iDo Script Scheduler doesn't run my script" below for more information.

My script doesn't appear in the list when I click the "Choose..." button in the Event Editor.

    iDo Script Scheduler only runs AppleScripts that have been saved as "scripts" or "applications", not "text". Open your script in the Script Editor and select "Save As..." from the File menu. Make sure "script" "compiled script", "application" or "applet" is shown in the pop-up menu.

    For shell, Perl, Python, Ruby and Tcl/Tk scripts, iDo Script Scheduler only recognizes files ending in ".sh", ".pl", ".py", ".rb" and ".tcl" extensions respectively. Make sure your script uses the appropriate filename extension.

In Mac OS 9, iDo Script Scheduler doesn't run my AppleScript, even though it works fine in the Script Editor.

    If you're using Mac OS 9, and your script runs in the Script Editor but not when scheduled, it may require more memory than iDo Script Scheduler has available. This is especially true of scripts which use many Scripting Additions. Try saving your script as an "application" or "applet".

    Tip: You can give your "application" script as much memory as it needs using ResEdit, which is freely available from Apple's web site. Open your script in ResEdit and open the "SIZE -1" resource, then set the "Size" and "Min Size" values to the number of bytes you desire (one 'K' = 1024 bytes).

In Mac OS X, iDo Script Scheduler doesn't run my AppleScript, even though it works fine in the Script Editor.

    In Mac OS X, iDo Script Scheduler runs AppleScripts as background processes. These processes don't have direct access to elements of the Mac user interface, such as "beep" commands or commands that open dialog boxes.

    To get around this, surround these commands in a "tell" block to the Finder or another open application. For example, if a simple "beep" script doesn't work, try the following:

       tell application "Finder"
          beep
       end tell

In Mac OS X, iDo Script Scheduler doesn't run my Unix script, even though it works fine from the Terminal.

    For system security reasons, iDo Script Scheduler runs scripts as the "Nobody" user. Therefore, the script can only access files which grant permission to "others".

    To grant permission to access a file, select the file and use the "File -> Get Info" command to open the Info window. Then disclose the "Ownership & Permissions" section of the info window to see the permissions for the file. (You may need to click the "unlock" button to enable the permission menus.) If your script reads from this file, make sure the permission menu for "Others" is set to "Read only" or "Read & Write". If your script writes to the file, make sure the pop-up menu is set to "Read & Write". (From the Terminal command line, you can use the "chmod" command.)

One or more of my scripts ran or failed to run when I adjusted my computer's clock.

    iDo Script Scheduler keeps track of the next time each script is scheduled to run. If you set your clock forward past the next time a script should run, iDo Script Scheduler may run the script immediately to "catch up". This was designed so that the script will not accidentally be skipped when doing small time adjustments, or when daylight saving time begins; it does not occur if you set the clock very far forward.

    Similarly, if you set your clock backward past the last time the script ran, iDo Script Scheduler will not run it again. This is so the script will not run twice if the clock is set backwards slightly, or when daylight saving time ends.

Related topic


Table of contents