Welcome to the MacNN Forums.

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

You are here: MacNN Forums > Hardware - Troubleshooting and Discussion > iMac, eMac & Mac mini > Mac needs to "die"...

Mac needs to "die"...
Thread Tools
Fresh-Faced Recruit
Join Date: Nov 2009
Status: Offline
Reply With Quote
Nov 18, 2009, 10:07 AM
 
Now that I have your attention...

Suppose the company I work for has an end-of-life policy on iMacs that basically says if it fails before the New Year, it gets replaced with an awesome new, top-of-the-line Mac from an enterprise-level pool of money. Otherwise, your department has to foot the cost of the bill for the new Mac.

Now, suppose I could probably get along fine with this old iMac for testing purposes, but also suppose I could really make more money for the company if I had a newer one to match the kind of dev specs for writing iPhone apps and such that I'd really need.

Suppose I can't make a solid business case for department-appropriated money because of some neanderthal luddites in my way who recently and inexplicably and illogically decided to ELIMINATE all hardware budgets for 2010. ("You want to do what with the whoseit and the hulahoops? No! That's crazy talk! We need that money for schmoozing clients at expensive restaurants and jetting to conferences.").

Suppose I want my Mac to just "wear out" in a way that is non-destructive but makes a clear business case for replacing it from that enterprise pool of money in the sky. After all, I still need a Mac for testing.

What would need to happen? Run SETI@Home at full bore night and day to reach mean time between failure? Know what I mean? *nudge nudge*
     
Clinically Insane
Join Date: Jun 2001
Location: planning a comeback !
Status: Online
Reply With Quote
Nov 18, 2009, 10:53 AM
 
Depends on how smart your IT department is in checking the Mac for issues.

Bad RAM can do "wonders" in terms of making the machine unreliable.

-t
     
Fresh-Faced Recruit
Join Date: Nov 2009
Status: Offline
Reply With Quote
Nov 18, 2009, 11:14 AM
 
Hmm. "Bad RAM". Do tell. How might a person allegedly go about making one's RAM go or appear "bad" without being dishonest or overtly destructive? My integrity (and losing my job) is not worth the price of a Mac, you see, so it is imperative that an autopsy be seen as not necessary given apparent cause of demise.
     
Posting Junkie
Join Date: Dec 2000
Status: Offline
Reply With Quote
Nov 18, 2009, 11:17 AM
 
Wouldn’t doing something like this constitute fraud?

Ticking sound coming from a .pkg package? Don't let the .bom go off! Inspect it first with Pacifist. Macworld - five mice!
     
Fresh-Faced Recruit
Join Date: Nov 2009
Status: Offline
Reply With Quote
Nov 18, 2009, 11:30 AM
 
Fraud: Only if there wasn't anything wrong with the machine and I said there was, or if I did something to it to make it broken. Ultimately, if nothing is wrong with it, I'm resigned to be stuck with it. BTW, I'm not really being as sneaky as my message implies. The man at the top who controls the flow of new to old replacements gave me his permission to make a case for replacement based on anything I might find wrong with it. His call.

What's the best way to test the RAM on a Mac to probe it for flaws? What about the hard drive or motherboard, or other components? That's the route I'm really looking into.
     
Clinically Insane
Join Date: Jun 2001
Location: planning a comeback !
Status: Online
Reply With Quote
Nov 18, 2009, 11:38 AM
 
Originally Posted by p2b4f View Post
Now, suppose I could probably get along fine with this old iMac for testing purposes, but also suppose I could really make more money for the company if I had a newer one to match the kind of dev specs for writing iPhone apps and such that I'd really need.
Why don't you put together an quick calculation that shows how much more productive you could be with a new machine.

If it saves you 1 hr per week, x 52, x your hourly rate, this should easily pay for a new computer.

-t
     
Posting Junkie
Join Date: Dec 2000
Status: Offline
Reply With Quote
Nov 18, 2009, 12:04 PM
 
Originally Posted by p2b4f View Post
Fraud: Only if there wasn't anything wrong with the machine and I said there was, or if I did something to it to make it broken.
Your original post seemed to suggest that you were looking for the latter, which certainly is something I wouldn’t recommend.

If you are just looking for something that’s already broken, if it’s got an NVidia card, those tend to be pretty flaky. Do a bunch of intensive 3D stuff (oddly enough, the “flip” animation that Front Row’s music player does is a good way to trigger this) and you might get a bunch of weirdness followed by a long string of errors in the Console. My MBP went through three motherboard replacements and one full unit swap before I finally got the GPU to work right.

Ticking sound coming from a .pkg package? Don't let the .bom go off! Inspect it first with Pacifist. Macworld - five mice!
     
Fresh-Faced Recruit
Join Date: Nov 2009
Status: Offline
Reply With Quote
Nov 18, 2009, 12:24 PM
 
Your original post seemed to suggest that you were looking for the latter, which certainly is something I wouldn’t recommend.
Sorry. Not my intent. Had hoped my later replies would have clarified, but running on empty mentally this morning. LOL

I like your suggestion about testing for flaws in the video card. Will give that a shot. Thanks all for the ideas!
     
   
Thread Tools
Forum Links
Forum Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On
Top
Privacy Policy
All times are GMT -5. The time now is 04:28 PM.
All contents of these forums © 1995-2009 MacNN. All rights reserved.
Branding + Design: www.gesamtbild.com
vBulletin v.3.8.4 © 2000-2009, Jelsoft Enterprises Ltd., Content Relevant URLs by vBSEO 3.3.2