A mate of mine gave me a black gaming case a few years ago. It's pretty cool. It's got 2 fans at the rear, a fan at the side (glows neon), and I stuck another fan at the front. In fact I stuck 2 fans at the front but then I took it out and put it in my Dad's PC case. You can never have too many fans. Well I suppose you can.
Anyway, the front of the case opens out as it's actually a cover. The front of the case has got "eye" shaped lights which glow red when the HDD is being red. Awesome.
But when I open the door, I'm greeted by my *beige* DVD-RW drive and my *beige* transfer panel. Ugh! So after 3 years I've decided to do something about it. Bring out the black spray paint!
I could have just got a black bezel which I'm sure are pretty cheap nowadays but that would require waiting for delivery and I wanted it black NOW!! At the minute the plates are out drying in the garage - I'll give them another coat tomorrow and maybe post some pics too.
Am I that bored?
Thursday 23 October 2008
M$ Error 0x00000024 - what the crap?
Man, I hate BSOD (Blue Screen of Death - for those who don't know. Keep with the times!).
One day you're happy, sitting at your PC, maybe burning a few songs to CD or whatever, and next minute BAM!!! Your computer tells you it's been shut down for whatever reason. One course of action is to stare in disbelief for 60 seconds as you wonder how this world can be so cruel. Another is to kick that stupid piece of crap that you WOULD get rid of, except it probably holds your entire life on the hard drive.
The only good thing about BSOD is that it gives you an error code. A bit of an improvement from the old WIN 9x days!
In this case, it's 0x00000024. A family in my church experienced this problem. XP wouldn't even get to the logon screen. In fact, it didn't even show me the BSOD until I pressed F8 on startup and selected an option to not shut down immediately on error.
It's got something to do with ntfs.sys and how it becomes corrupted I do not know. This is why I love M$. Not.
To fix:
1) Insert XP CD and boot from it
2) Press F8 to agree to terms and press R for recovery console
3) Press 1 and hit return to log into C:\Windows
4) Press return when it asks for an admin p/w (default - leave blank)
5) Type "CHKDSK /p /r" and hit return (no quotes)
6) Wait....keep waiting.....wait even longer.....In fact, return after 2 hours.
It'll tell you that its found errors, and has fixed them.
Maybe this little scare will finally get you to back up your data!! Maybe not.
One day you're happy, sitting at your PC, maybe burning a few songs to CD or whatever, and next minute BAM!!! Your computer tells you it's been shut down for whatever reason. One course of action is to stare in disbelief for 60 seconds as you wonder how this world can be so cruel. Another is to kick that stupid piece of crap that you WOULD get rid of, except it probably holds your entire life on the hard drive.
The only good thing about BSOD is that it gives you an error code. A bit of an improvement from the old WIN 9x days!
In this case, it's 0x00000024. A family in my church experienced this problem. XP wouldn't even get to the logon screen. In fact, it didn't even show me the BSOD until I pressed F8 on startup and selected an option to not shut down immediately on error.
It's got something to do with ntfs.sys and how it becomes corrupted I do not know. This is why I love M$. Not.
To fix:
1) Insert XP CD and boot from it
2) Press F8 to agree to terms and press R for recovery console
3) Press 1 and hit return to log into C:\Windows
4) Press return when it asks for an admin p/w (default - leave blank)
5) Type "CHKDSK /p /r" and hit return (no quotes)
6) Wait....keep waiting.....wait even longer.....In fact, return after 2 hours.
It'll tell you that its found errors, and has fixed them.
Maybe this little scare will finally get you to back up your data!! Maybe not.
Subscribe to:
Posts (Atom)