mkindred Posted April 29, 2003 Report Share Posted April 29, 2003 In OS X 10.1, I'd been having trouble with autolaunch turning itself off (but still appearing to be turned on in the prefs). Periodically, I'd have to turn off "Automatically launch Retrospect" in the prefs, then turn it back on in order for it to work. But now that I've upgraded to 10.2.5, Retrospect will not autolaunch at all. I've followed the directions at http://www.dantz.com/index.php3?SCREEN=kbase&ACTION=KBASE&id=27803 , to no avail. Here's my setup: OS X 10.2.5 I stay logged in overnight, with a screen saver running Retrospect Desktop 5.0.238 As soon as I start up Retrospect, all my scripts run immediately. Link to comment Share on other sites More sharing options...
CallMeDave Posted April 29, 2003 Report Share Posted April 29, 2003 Quote: As soon as I start up Retrospect, all my scripts run immediately. Trash the file: "/Library/Preferences/Retrospect/retrorunfile" then launch Retrospect and quit. Then launch it again, create a test script to run a couple of minutes in the future, then quit it again. Check with Process Manager to assure that the "retrorun" process is running as you wait for your test script to run. Dave Link to comment Share on other sites More sharing options...
mkindred Posted April 29, 2003 Author Report Share Posted April 29, 2003 I did what you suggested, but the new script did not run. I checked, and retrorun was not running. Link to comment Share on other sites More sharing options...
CallMeDave Posted April 29, 2003 Report Share Posted April 29, 2003 Since scripts _cannot_ auto-launch unless retrospect is running, at least now we know _what_ is going wrong. The remaining question is why. Did you move the Retrospect application from its default install location? The script in the StartupItems folder describes the path to where it expects the retrorun process file to be (it lives inside the Retrospect application bundle). If you move the bundle, you break the script. If you _have_ moved the bundle, you can A) move it back or edit the script to reflect the new location. Dave Link to comment Share on other sites More sharing options...
mkindred Posted April 29, 2003 Author Report Share Posted April 29, 2003 I have not moved Retrospect. It still resides in "/Applications/Retrospect 5.0" What script must I edit? I see two files in /Library/StartupItems/RetroRun/: StartupParameters.plist and RetroRun. StartupParameters.plist is just XML with no paths, except the DTD. RetroRun appears to be a binary file. Link to comment Share on other sites More sharing options...
mkindred Posted April 29, 2003 Author Report Share Posted April 29, 2003 I just noticed that my RetroRun.crash.log is growning. So it appears it's trying to start. Would it help if I emailed the error log to you? Link to comment Share on other sites More sharing options...
CallMeDave Posted April 29, 2003 Report Share Posted April 29, 2003 Quote: Would it help if I emailed the error log to you? Not me? No, I'm just playing around with everyone else. But you could post the last entry of your log here. Start the last time it shows something like: Date/Time: 2003-01-13 11:58:54 -0800 OS Version: 10.2.3 (Build 6G30) Host: localhost Command: RetroRun PID: 12329 Link to comment Share on other sites More sharing options...
mkindred Posted April 30, 2003 Author Report Share Posted April 30, 2003 Here's my crash log: ********** Date/Time: 2003-04-29 16:52:32 -0500 OS Version: 10.2.5 (Build 6L29) Host: Gossimer.local. Command: RetroRun PID: 648 Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_INVALID_ADDRESS (0x0001) at 0x001eb694 Thread 0 Crashed: #0 0x00003950 in GetPID (main.c:258) #1 0x000045c0 in main (main.c:577) #2 0x000031c8 in _start #3 0x00002ff8 in start PPC Thread State: srr0: 0x00003950 srr1: 0x0200d030 vrsave: 0x00000000 xer: 0x00000000 lr: 0x0000394c ctr: 0x90073c20 mq: 0x00000000 r0: 0x0000394c r1: 0xbffffad0 r2: 0x00143010 r3: 0x00000000 r4: 0x00000003 r5: 0x00000028 r6: 0x0000002c r7: 0x00000703 r8: 0x00000000 r9: 0x001eb67c r10: 0x00000001 r11: 0xa0004894 r12: 0x90073c20 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000 r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x00000000 r20: 0x00000000 r21: 0x00000000 r22: 0x00000000 r23: 0x00000000 r24: 0x00000000 r25: 0x00000000 r26: 0xbffffeb4 r27: 0x00000008 r28: 0x00000001 r29: 0xbffffec0 r30: 0xbffffad0 r31: 0x000037c0 Link to comment Share on other sites More sharing options...
CallMeDave Posted April 30, 2003 Report Share Posted April 30, 2003 Quote: Thread 0 Crashed: #0 0x00003950 in GetPID (main.c:258) It looks as if your system is using the retrorun process from the earlier, non-Jaguar compatible version of Retrospect. Others users on the Fourm experienced this, back when Dantz first released the update from 5.0.205 to 5.0.238. You should trash the entire Retrospect application icon and the directory at /Library/StartupItems/RetroRun/, empty the trash, then run the 5.0.238 installer again. Your preferences will remain untouched. Dave Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.