Real computer horror story

Here's the situation: You're using your dual-boot freeBSD/windows XP computer normally which contains two partitions a C drive and a D drive. The C drive is composed of the system, small programs such as firefox, limewire and vlc, and other small, disposable files. Now on the other hand your D drive is composed of anime, porn, games such as counter-strike and unreal tournament, and miscellaneous files (more porno and anime) which you have collected over the years and are so neumerous in fact that it would take years to replace. Whilst using the computer normally you notice it's moving slower and certain programs are crashing, deducting it's due to the lack of restarting your normally restart, thinking it will solve your problem. The computer starts up normally displaying the intel pentium 4 processor with hyper threading screen and then moves onto the freeBSD boot manager. You select drive C as usual as it contains your operating system. You see the Windows XP Home Edition loading screen and usual and when it dissapears and is replaced by nothingness, your computer then restarts and the intel screen is displayed once more, you continue with the same process in desperation but are only faced by dissapointment by the fact that your windows system is fucked. You try the option "Do not restart upon system failure" but are faced with a blue screen of death displaying an error  with your log-in screen! You quickly pull out your Windows XP boot disk and whip into action. After 20 minutes of installing and formatting your operating system is back to normal and your precious D drive is still in tact. The problem lies in the fact that your freeBSD boot loader becomes corrupt after ever re-format of your C drive and so you just have to re-install freeBSD. You pull out your freeBSD bootdisk and continue normally, setting your C drive to bootable and re-installing all your packs which takes the course of about thirty minutes to an hour. At the end of your freeBSD installation yougo to do some quick post-install config. You go into your fdisk utility to make sure your boot manager is correctly configured and it is so you press the Q key for finished, only it doesn't exit but instead it makes all the partitions go away you're confused and look at the instructions on the screen and notice that instead of pressing "Q" for finished you pushed "A" for "use all of disk" you quickly push "U" for "Undo all changes" but are faced with a "You're changes have already been written and cannot be undone!!!." Instead of going into your freeBSD operating system after the install you frantically restart and your fears are then realized when instead of showing the boot manager you are faced with the freeBSD start up. Thinking that all your years of data are gone in a second, reformatted with the accursed freeBSD operating system. You start to cry and damn your life as you mourn the loss of all that necessary data.

--First part respond to thread if you want the ending

Always has to have once before you start taking "always have a backup" seriously.

Something happened to me like that, twice.
One was my desktop, the other was my laptop.
My laptops internal power supply failed and died, but the data is still there.
My desktop has very similar stuff, if you know what I mean.
Long story short, computer died, data lost, and the funny thing is that I do not want the stuff off that disk recovered because of the porn and stuff.
Life sucks sometimes. Computers can make it worse.

You reach for your Sony Vaio recovery disk and put it in then quickly rush to the option "recover C drive" then wait as it goes from 1 to 100%. Hoping that it did something you restart praying to god (which you don't beleive in) to bring back your D drive. The computer restarts and goes into the windows XP post-install config screen where it tells you to set up your accounts and accept the EULA agreement. The computer then restarts and the freeBSD boot manager is once again corrupt. You reach for your freeBSD boot disk and make sure to take a domino stacker's caution as you install. You goto the fdisk utility and see a light of hope, 3 partitions show up, the main VAIO one, your C drive and what looks like it could be your D drive! You Frantically set up the C drive to bootable and configure freebsd and before installing freeBSD first does the operations on the boot manager, you don't wait for the finish, instead you quickly turn off the power after the boot config and hope to god your por... err valuable data is still intact. The computer starts up, your hear your heart pounding, the Intel screen shows up quickly followed by the boot manager. You check to see 4 partitions and grow cheerful but not yet out of desperation. Since it is the first restart after your format it takes long - too long. You start pulling at your hair and bitting on your shirt until it reaches the desktop screen. You ravish the mouse, quickly right clicking on the start button and opening the explorer. You click on the D drive which since only seconds have passed since your desktop appeared takes seconds that seems like minutes to load. To your hearts content all your files are still there! You thank god you bought a VAIO with such an exceptional emergency recovery kit and resume to beat... i mean watch anime to your hearts content after the biggest scare of your life. (Didn't say it was a VAIO 'cuz it might've ruined the suspense if some of you know how thuroughly the emergency kits actually recover) And you live happily ever after. The end. What a great ending! This actually happened to me yesterday night and since it was so late i had to sleep thinking my data was gone to wake up the next day with a clear head ready to trouble shoot the problem.

tl;dr

that what you noobs get for attempting to use linux. silly faggots.

par·a·graph ( P )  Pronunciation Key  (pr-grf)
n.

   1. A distinct division of written or printed matter that begins on a new, usually indented line, consists of one or more sentences, and typically deals with a single thought or topic or quotes one speaker's continuous words.

   2. A mark ( ¶ ) used to indicate where a new paragraph should begin or to serve as a reference mark.

   3. A brief article, notice, or announcement, as in a newspaper.

>>6
Uhm... I hope you are joking. He said FreeBSD and *BSD is not Linux as Solaris is not Windows.

Fails for being a noob.

>>8
fails for being another one of those fags splitting hairs when it comes to precious linux

Holy fuck I'm not gonna read all that text. I think >>7 is the winner.

>>9
So is Mac OS X Linux too?

>>6
Replace linux with UNIX and that post will be correct.

Reminds me of how so many people use iPod for MP3 Player and Tivo for DVR nowadays, no matter what brand it actually is.  Linux is taking over in the minds of the ignorant, hehehe.

>>1
It doesn't matter what OS you use.  Follow this advice:  Save early, Save often, Make backups.

>>6,9
Kindly explain to me how Linux (or, as others have rightly pointed out, Unix) could possibly be the cause of a sudden and mysterious failure for Windows to boot?  Hmm?  At least once a month, I get a computer brought into my shop for repair because Windows XP BSOD's on boot, exactly as >>1 saw, when no other operating system -- not even one of Microsoft's own -- has ever touched the machine.  Microsoft Windows is horribly fragile and self-breaking, and XP is no exception.

I remember when I tried installing SATA RAID drivers and it trashed my partition table. Eventually got everything back with a pretty awesome program called 'GetDataBack'.

>>14
Hey fag how about you actually read what >>1 wrote.
He wiped out his precious porn while doing something as simple as reinstalling the freebsd boot manager. He is a complete and utter failure it's as simples as that.

>>11
to a lesser degree yes

>>17
WTF are you talking about? Mac OS X has very little to do with Linux, it has a lot to do with FreeBSD.

>>16
Hey fag I *did* read what >>1,4 wrote.  I struggled through reading the *entire* story, but I somehow managed it.

Yes, the poor soul deserves to be laughed at for not following such obvious advice.  I posted it in hopes that he'll be less of a luser next time around.  Lord knows the world has too many as it is.

>>17,9,6
What in God's creation are you smoking?  Whatever it is, puff puff give!

This is why you should use GRUB instead of the default fbsd bootloader.

>>7 wins the thread
>>1 fails for nuking his prawn by accident
>>1 fails for not having a backup so that this would've been an "oops" instead of an "oh snap"
>>1 fails for not realizing that OPs don't have the same line limit as replies
>>1 *WINS* for owning up to his mistake and being willing to post the story of it
>>17 fails for calling Apple's OS "Linux"

>>9
*BSD has nothing to do with Linux.

>>21 fails for plain being gay and defending mac os which is just another rip off of linux that fags *actually* pay for but don't know it

>>23 fails at trolling.

Better luck next time.

>>1

A terrible story.  Unfortunately, you made some mistakes, most of which consist of BACKUPS and NOT REINSTALLING FREEBSD JUST FOR THE BOOTLOADER.