d37fc1fe-a25d-4df0-9b52-cb21971f1fde Posted March 2, 2012 Report Share Posted March 2, 2012 Hello, I was trouble-shooting something else and moved the file RetroRun from StartupItems to another folder (disabled StartupItems); after I finished my troubleshooting, I moved it back and receive this message on starting up my Mac Pro running OS10.6.8: Insecure Startup Item disabled. "/Library/StartupItems/RetroRun" has not been started because it does note have the proper security settings. How do I fix this? I can just uninstall and then reinstall Retrospect 8 but don't want to lose my scripts, sources, etc. Running Retrospect 8.2.0 (399). Advice much appreciated. thanks Quote Link to comment Share on other sites More sharing options...
twickland Posted March 2, 2012 Report Share Posted March 2, 2012 RetroRun was a process used back with Retrospect 6.1 and earlier. Whatever the reason for your error message (Retrospect 6.1 and earlier is unsupported after OS 10.5.x, which may well be the issue), it should have absolutely no effect on Retrospect 8. I would just trash that startup item. Quote Link to comment Share on other sites More sharing options...
d37fc1fe-a25d-4df0-9b52-cb21971f1fde Posted March 2, 2012 Author Report Share Posted March 2, 2012 This is useful info - thanks! The other issue is that the retrospect engine won't run. I assume the easiest fix is to uninstall and then reinstall. How can I save my scripts and the like, or do I need to re-enter everything? Quote Link to comment Share on other sites More sharing options...
twickland Posted March 5, 2012 Report Share Posted March 5, 2012 The other issue is that the retrospect engine won't run. What do you mean by this? That you can start the engine process from its preference pane but then it quits/crashes? Or that it won't start at all? Reinstalling the engine should not affect your scripts, source lists, etc.--which are stored at /Library/Application\ Support/Retrospect/Config80.dat--unless you specifically follow the instructions for removing the configuration data when running the Uninstall script. However, to be safe, it's always wise to create a backup copy of this file somewhere so that you can go back to it if/when the Config80.dat file becomes corrupted. (Note that Retrospect regularly creates and replaces its own backup copy called Config80.bak. However, this is not the same thing as creating your own copy, since it's likely that by the time you notice trouble, Retrospect's backup copy will already contain the same corrupt data that's in Config80.dat.) Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.