Jaguar Cache Cleaner

[Gary S]

I'm a registed user of Jaguar Cache Cleaner 1.8.6 and I downloaded the newest version 1.8.7.

It shows it's registered to me but it won't accept my administrator's password.

Any suggestions?

I emailed northern software, the developer so i may get a reply from them.

TIA.

[rongold]

Check the following:

http://www.techsurvivors.net/forums/index....t=ST&f=1&t=3392

[Gary S]

rongold,

I don't understand what your pointing to. Maybe you could explain?

[Mrious_be]

What's so special about the "cache cleaner" Gary?
I mean... since you payed for it, it must have or do something that the build in "empty cache" doesn't do?

Just curious

[rongold]

Sorry if my reply was confusing: I couldn't tell from your post whether you were experiencing similar problem to mine.

I experienced only one problem while having OS X 10.2.8 installed: both MacJanitor and iClock failed to launch. The failure occurred both with the recent versions as well as older versions of both programs, including freshlyg downloaded versions. Consolde showed the identical error occurring during the failure to launch eitherr program, namely:

"Sep 27 12:36:47 localhost WindowServer[609]: ERROR! execle(/Applications/iClock Folder/iClock.app/Contents/ Mac OS/iClock) returned, err=22"

Curiously, the error persists after performing clean install (or rather "Archive and Install with Preserve Users and Network Settings turned on) of OS x 10.2.6.

The error does not occur with Eudora Pro 6.0, iCab 2.9.6, Explorer, Mozilla Firebird, Word, Excel, Powerpoint, Hypercard, Cocktail, Spamsieve, Keyboard Maestro, Scrapit Pro X, Stuffit 8.0 components, or any other programs I have tried. I suspect the problem is in the preferences of MacJanitor and iClock, but why does it persist in OS X 10.2.6 after deinstalling and reinstalling the two programs and their preferences?

Problem solved by team at iClock:
http://scriptsoftware.com/forum/viewtopic....250e00e61600a4f

The problem: 'Aladdin [with release of Version 8.0] changed the default for Stuffit (.sit) archive in Version 8.0 from setting all files executable to non-executable (since .sit does not record executable permission) for security reasons (stop the possibly of distributing virus or trojan scripts in stuffit archives)."

[Mrious_be]

Oooops....
forget that last one Gary, i thought you were talking about Safari cache cleaner, but it's Jaguar

[Gary S]

rongold,

QUOTE

The problem: 'Aladdin [with release of Version 8.0] changed the default for Stuffit (.sit) archive in Version 8.0 from setting all files executable to non-executable (since .sit does not record executable permission) for security reasons (stop the possibly of distributing virus or trojan scripts in stuffit archives)."

Hummmm. That's interesting because when I downloaded the new version of JCC Stuffit didn't kick in, it just downloaded to my disk without unstuffing it. I had to double click on the .sit file to get it to expand.

The thing is when I launch the new version of JCC, it launches fine without any errors and if it shows I'm a registered user when I go to about JCC. It's just that you need a valid Administrator's password to run it and it won't take my password!

Thanks.
GaryS

[Bill]

Try your sons pass Gary. Ya never know.

[Gary S]

Bill,
That didn't work...i'm glad it didn't!

I'm still waiting for the Author to email me back. He wanted to know the exact message I got.

He wrote:

If you would, can you tell me exactly what the rejection message says.  It may seem silly, but JCC will display slightly different messages depending on the type of failure.  Knowing the text of the message will point me in the right direction.  Also, can you tell me if you are using the long or short login name?

I emailed him the info but haven't heard from him. Maybe tommorrow.  

[Bill]

"Also, can you tell me if you are using the long or short login name?"

Could be the 'key' Gary.


side bar: Oh and Rob W, my "H" is fine.

[RobW]

QUOTE(Bill @ Oct 1 2003, 9:29 PM)

"Also, can you tell me if you are using the long or short login name?"

Could be the 'key' Gary.


side bar: Oh and Rob W, my "H" is fine.

   

[kps]

Gary,

You could try running the application as root, and see if it works. If you enabled root through NetInfo, you could log in as the root user or just launch the application as root through the Terminal like so:

CODE

Last login: Thu Oct  2 01:07:46 on ttyp1
Welcome to KARCOM!
The Terminal is your friend!
[KARCOM:~] karl% su
Password:
[KARCOM:/Users/karl] karl# open /Applications/Jaguar\ Cache\ Cleaner.app
[KARCOM:/Users/karl] karl# exit
exit
[KARCOM:~] karl%

Remember, root=# user=% as the prompt. Also, "exit" from root, then exit from Terminal, then Quit the Terminal. Use the su to "Substitute User", type your password, then use the "open" command followed by the path to the application. The backslashes " \ " are used to 'escape' the spaces in the app's name. JCC will launch in the finder as soon as you hit 'enter'.

It would be interesting to know if you get the same err msg.

[Gary S]

I got an email from john at Northern this morning with a link to a d/l of JCC that works for me. He said it was a bug and thanked me for letting him know.
Evidently others had the same problem.

[Bill]

Never thought about the OS cashe before.
Wonder how you clean out Jags cashe manually or which one to toss?

[kps]

You having problems, bill?

I haven't cleaned any caches since I installed Jag. There's no reason to do it unless there are problems that might be caused by a corrupt cache or caches.

I know what you're thinking...how does one know when it's a corrupt cache causing the problem. I have no clue.  But, if you're having constant app crashes, crashes on application launch, etc. it may be a good idea to do it then, provided nothing else has been able to fix it.

The cool thing about JCC, is that it gives you options to do a light cleaning or heavy duty cleaning amongst other options. Manually, it may be a hit 'n miss unless you know specifically what is what.

Caches are stored in all the major directories:

/Library/Caches
/System/Library/Caches
/Users/username/Library/Caches