Currently Being ModeratedNov 23, 2012 4:57 AM (in response to andyBall_uk)
Well...after properly editing the .ini file and changing <1> to <0> and saving, the software causes a reversion to the saved file and changes things back to the <1> which then restarts scanning. Very odd that a properly admin adjusted/saved file is then changed by the software.
I have asked retrospect what is going on. Perhaps there is a bug in there?
Currently Being ModeratedNov 23, 2012 7:59 AM (in response to jordanmthunger)
Modifying the retro_isa.ini file
1) Locate the file using the path listed above
2) Get Info on the retro_ISA.ini file.
3) Unlock the file using the lock button
4) Change the file permissions to "Read & Write" for Admin, Everyone and your logged in user account.
5) Double click the file and make any needed edits
6) Save your changes
7) Restart RetroISA using the below directions
Step five: what application is opening that file for you?
Currently Being ModeratedNov 23, 2012 8:09 AM (in response to WZZZ)
Absolutely/positively have done as above...textwrangler used to edit the file. It really is a simple edit.
One new thing I've done is <stop> the retrospect engine (Sys Preferences), then make the .ini edit, save and lock the file THEN <restart> the engine...the edit seems to have taken at this point/fingers are crossed.
Currently Being ModeratedNov 24, 2012 1:37 AM (in response to jordanmthunger)
The .ini file was "modified" at 0417 DST here on the east coast when i started the Mac this AM - this modification I did not do/scanning has resumed. Apparently, Retrospect has a mind of its own in this regard and any changes one makes to this file are discarded when one reboots:
71 RetroISA root 100.4 18 455.8 MB Intel (64 bit)
Currently Being ModeratedNov 24, 2012 2:34 AM (in response to jordanmthunger)
AND, I am relieved to find I am not making this all up!
Currently Being ModeratedNov 24, 2012 3:56 AM (in response to jordanmthunger)
What's keeping you from simply disabling it?
Macintosh Terminal Commands
Stop the RetroISA process: sudo launchctl unload /Library/LaunchDaemons/com.retrospect.retroisa.plist
Start the RetroISA process: sudo launchctl load /Library/LaunchDaemons/com.retrospect.retroisa.plist
Currently Being ModeratedNov 24, 2012 5:18 AM (in response to WZZZ)
Right...saw that advice. Thanks.
The fact that no one else has tried this puts me off a bit...it has already been established that the Retrospect FAQ has missed some things and I am hesitant to add to that with following this sudo advice.
Currently Being ModeratedNov 24, 2012 5:50 AM (in response to jordanmthunger)
It's easily reversed if it doesn't work out. sudo is no big deal here.
EDIT: In case you've never used the sudo prefix before, you will be asked for your admin pword, which you won't see anywhere when you type it in. You will also get a warning about using sudo. Just keep going.
Message was edited by: WZZZ
And, this isn't for me, but please have a look at the Legend in the right sidebar.
Currently Being ModeratedNov 24, 2012 9:55 AM (in response to jordanmthunger)
Yep...the sudo unload kills things for sure...all scanning stopped, CPU usage to reasonable levels and temp immediately dropped by 7/10 degrees.
I imagine I'd have to reinable if I wished to backup but for now I have reached a major turn in the Retrospect 10 road.
Currently Being ModeratedNov 24, 2012 12:56 PM (in response to jordanmthunger)
Thanks for the solved, but I really had Andy in mind, whose help was really critical to this. Anyway, what's important is you found something that worked, at least short term.
Perhaps you can downgrade to the 9, or just dump it entirely and get CCC? None of these problems with CCC.
Currently Being ModeratedNov 29, 2012 12:10 PM (in response to WZZZ)
Folks...meant to pass this along. Retropect has confirmed there is an issue with Retro 10 and Mac editing of the .ini file. Same with high CPU% usage.
Disabling scanning via sudo is the present way to go until issues are solved with an upcoming revision of 10.