[Matthew Attoe]

Hi,

I'm just interested in people's opinions of this.

Do you believe that an install can be bad, and just doesn't "take" as it were?

I did a complete reinstallation of Tiger (including formatting the drive!) a couple of months ago, but since then my Mac has been acting a little off. One example is it seems like my hard drives keep going to sleep after a few minutes, because if I leave the machine alone for a few minutes then try and open up a folder or something I get a beachball and I hear the hard drives spinning up. Then everything is okay, until I leave the machine alone again. I've double-check the Energy-Saver control panel and allow drives to sleep isn't checked. I've even tried ticking it on and off several times, in case the setting got stuck.

There's been a few other little niggles as well, that I don't remember having on previous install too. I'm going to stick with this install until Leopard .1 or .2 is available then go for that.

This is what got me thinking about bad installs. Anyone else ever had one?

Cheers,

Matthew

[analogika]

I believe in bad RAM.

Bad RAM WILL result in a bad install - often in very strange and subtly bizarre ways.

[Cold Warrior]

I think a ball install can happen, but it's usually related to a larger problem of disc/drive corruption or damage, or bad RAM. However, I do believe that a random bad install can happen even if those items aren't factors.

[Kevin]

Not with final software no. I've had a few installs go bad using dev and beta OSs installations though.

One dev of OS X messed my SCSI card up so badly it didn't work anymore.

But that was my own fault for messing with dev builds.