Jump to content

Fooking computers


Shamus_McFartfinger
 Share

Recommended Posts

Bloody hell. One of my HDs crapped itself last night. A boot drive of all things. Wouldn't it just give you the shits? Apart from the obvious pain in the arse it causes, the machine itself contains a large common drive, Drive O:, which I use all the time and that I no longer have access to. It also ran my little FTP server, synchronisation software for backups and various other tasks. The rotten bastard. The drive is probably salvageable but not bootable. Sigh.

Link to comment
Share on other sites

Does that mean you won't be hosting any more of my porn Shamus?

 

Regards

 

Tragically, no. :)

 

Should have it all up and running again in a few days. Decided to take a leap into the 90's and install XP on it. What a bucket of crap. I hate it. Stupid fukcing menus. Stupid hardware wizard. Stupid naming convention for shared drives (shared folders are fine), making me re-map every pc connected to it. What a heap-o-shit.

 

W2k was (and still is) brilliant. Much more intuitive and easier to manage. The start menu is nothing short of tragic. Go to the classic menu and half your options dissapear. What a great way to fuck up an OS.

 

Linux is starting to look mighty good.

Link to comment
Share on other sites

what make Maxtor ?

 

and is it making a pinking sound ?

 

It fills me with terror everytime i hear that noise.

 

No idea. :) The drive didn't die. Windows did. A summer storm hit the other day and I raced inside to yank everything out of the wall. We don't get hurricanes here but the summer storms can be pretty nasty, as evidenced by the trees in my back yard laying 30 degrees above the horizontal instead of standing upright. Anyways, I pulled the plug on everything and went to fire it all up a few hours later and the boot drive had been corrrupted. I'm guessing it was writing a large file at the time it lost power and crashed the drive head. :(

Link to comment
Share on other sites

just a suggestion Shamus , check the ram modules out . the resolve to my problem in anotehr thread where a win 2k machine wouldnt boot and kept showing BSOD'S was 1 faulty RAM chip/module.

took the duff 1 ( of 2 ) out, and hey presto, instant boot up , confimed this by changing the RAM over, and instant BSOD . im down to 256 instead of 512, but up and running again

Link to comment
Share on other sites

 Share

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.