Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Click here to return to the 'Why would you use this?' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Why would you use this?
Authored by: monkeyvoodoo on Aug 20, '02 06:14:01AM
I just have one question. How is this a MacOS X hint?

This is something that will work on any *nix system, and really doesn't seem to hold any real value to the average user (unless I am completely unaware of some group of people who like their computer to run slow).

Perhaps what this site needs is a "Stupid Computer Tricks" section, or something...

[ Reply to This | # ]

Why would you use this?
Authored by: beastie on Aug 20, '02 07:13:54AM

hey no flames please!

yes it is not very useful hint, but i think it's amusing and may be of interest to some.

[ Reply to This | # ]
Authored by: robg on Aug 20, '02 08:28:01AM

I used it last night to see what would happen with iMovie rendering an effect, iTunes playing, and the CPU struggling ... amazingly enough, not much happened at all! But mainly it's a mildly amusing diversion.

If I use the criteria that if a UNIX hint submission works on any UNIX system then it's not an OS X hint, I wouldn't be able to run most of the UNIX hints! Probably 99% of the UNIX hints will work (perhaps with some modifications) on most all UNIX systems; the exceptions are things like GetFileInfo, SetFileInfo, cpMac, etc. That's part of the beauty of UNIX ... learn once, use anywhere.


[ Reply to This | # ]
Why would you use this?
Authored by: Likos on Aug 23, '02 12:53:50PM

I was having problems with my machine crashing on high loads. This hint would have helped me immensely when I wanted to artificially increase CPU loads to troubleshoot. (Ended up Dual 1Ghz was overheating. Silver thermal compound on CPU's solved issue)

Thanks for the tip!


[ Reply to This | # ]
Why would you use this?
Authored by: uochris on Jan 12, '06 09:54:36AM

I'm currently working on an iMac that presents an issue only when the CPU is under heavy load. This hint makes it a snap to reproduce the problem. I for one would like to thank the original poster for this hint.

[ Reply to This | # ]