Apps and More Software Design, Inc.

An "endian" issue with Script Timer on Intel based Macs has recently been discovered. On such machines, if you make a change to the log file in Script Timer and then save the file, all subsequent information fed into the log file by the scheduling engine will appear as Oriental characters. This is because all text in the log file is stored in two byte Unicode UTF16 format, and the scheduling engine feeds data to the file in "big endian" format while on Intel Macs Script Timer automatically stores the data in native "little endian" format. Thus after a save, subsequent data will be interpreted as little endian (i.e. bytes will be interpreted in the wrong order). This won't be a problem if you avoid making changes to the log file in Script Timer, and won't be a problem on PowerPC based Macs (e.g. G3, G4, or G5).

If you do save changes to the log file in Script Timer on an Intel Mac, you must start a new log file (Preferences panel, Files and Folders).

A correction will be made for the next version of the program, which will be a free update to all registered users.