[tavilach]

Well, OS X froze on me for the first time ever! Yay!

I woke up my PowerBook, but the screen didn't update. It displayed what had been on the screen before I put it to sleep. I experimented with quickly looking at the clock after waking up the PowerBook, and sure enough, it takes a second to update from the previous time. Something obviously went wrong, and it just didn't update. Thus, my PowerBook was frozen, and I had to force restart.

I know that in Windows, restarting incorrectly isn't good for the computer, causing loose memory fragments and random stuff like that. Is what I did a problem? If so, is there any way to defragment?

[gorickey]

It's fine, I wouldn't worry about it unless it's a repeating pattern of "freezing" that occurs...

[tooki]

That's not even how it works on Windows. Disk fragmentation is one thing, and not relevant here. Memory fragmentation is another thing altogether -- but when you restart, ALL the memory is erased.

Crashes are bad if they happen frequently. If it's just one now and then, don't sweat it.

Keeping journaling turned on (10.3 does this automatically on installation) should be enough to prevent most disk corruption from crashes.

tooki

[tavilach]

Originally posted by tooki:
That's not even how it works on Windows. Disk fragmentation is one thing, and not relevant here. Memory fragmentation is another thing altogether -- but when you restart, ALL the memory is erased.

Crashes are bad if they happen frequently. If it's just one now and then, don't sweat it.

Keeping journaling turned on (10.3 does this automatically on installation) should be enough to prevent most disk corruption from crashes.

tooki

I knew I had it wrong .