Existing users, 
Now, the big clue that hit me was that the problem Clone had an alias to the real iClock folder on the internal drive.
So, I deleted the alias on the SuperDuper-generated Clone and installed another complete iClock folder on to the Clone and problem disappears. I'm guessing the reason = the invisible
.com.ScriptSoftware.iClock.plist
which has the version # is NOT on the Clone, but on the internal drive where the iClock app folder resides. Remember that the Clone has an alias to the Users Folder on the internal drive.
Maybe?, programmatically iClock checks for the version number before you install iClock on the menubar, so naturally you look at the startup drive and NOT where the real iClock folder resides
It's wierd that the Preferences are properly picked up, but not the version number?????
iClock Pro
Menubar clock replacement: multiformat time, time zones date, stocks, calendars...
Version: 1.0rc4
Follow up to "Old Info with a New Twist"
Feedback Type: Troubleshooting Report
Contributed by: johnlove Monday, May 08 2006 @ 10:36 AM PDT
Product Platform: MacOSX
Used Product For: 6-12 months
System Info:
Comments
Follow up to "Old Info with a New Twist" - johnlove
My SuperDuper Clone is "Shared Users and Apps". Therefore, SuperDuper installs an alias (external Clone) to the iClock Folder (internal original).iClock gets confused with the alias.
Wednesday, May 10 2006 @ 03:27 AM PDT
Follow up to "Old Info with a New Twist" - barberfloyd
You have a SuperDuper clone of your internal drive that is not a clone because you modified the cloned files? Yes - that is weird. It is also no surprise that it does not function the same as your internal drive. I thought a SuperDuper clone was supposed to be an exact copy for backup purposes. It works perfectly that way for me. iClock does not get confused when I startup from my external cloned drive.Reply to This
Monday, May 08 2006 @ 07:11 PM PDT