Miscellaneous > The Lounge

Funny Computer Mishaps

(1/4) > >>

Kat:
....well, at least they are funny now.
What are some of the things you did that were dumb to mess up your computer?

What i did was i took the new hdd i got, put Windows on it and hooked up my old Windows drive as a slave with Windows and programs still installed on it. I got lazy and decided it would be a good idea to see if the programs worked on the Slave and use those instead of installing them again on C:\. One of those programs was Window Washer and it worked. The first time i ran it, it came across some odd numerical files i didn't recognize. It asked me if i wanted to skip them and i said yes. The second time,i decided what the Hell, i'll get rid of them. Well, i finish the wash and like two seconds later my computer screen goes black. Turns out i deleted the files that the hdd uses to identify itself to Windows(or something like that). It took me two hours with the Western Digital floppy to get it all back.

My brother spilled Coke on my Dad's keyboard and all the keys died except for a few alphabetic ones. My brother opens up Notepad and whatever working key he would press it would spell out FAGFAGFAG. Now, we refer to it as the FAG keyboard.

beltorak0:
hmm... once i edited COMMAND.COM to have the screen clear to grey-on-blue instead of black-on-blue.  My dad had to re-buy Dos 3.31 twice for editing command.com.  stupid non-write-protected originals.

more recently, I invoked the awesome power of root in kde to change all the files in /usr to owner :user and mode 640.  yup. even directories.  after everything quite working because none of the /usr libs could be found, i realised my mistake, and tried to hand-change them back.  after two hours, i decided to re-install slack 8 over the existing install.  that fixed it fairly well. don't cain me yet; i was only using linux for 2 weeks at that point.

about two months later, i [ctrl]-[c]'d out of slack's install script with the windows partition still mounted.... and had to fix a "mount table corrupt" error by digging thru the code to see what it was cdhecking.... fixed that.  Then the next day, i came home from work to find a note taped to my computer: FIX WINDOWS!!!!!!!!.  it wouldn't boot.  two hours of searching the net reveiled the following a precedure that entailed moving the old msdos.sys; runing sys on drive c:, deleting the newly created msdos.sys, and moving the old one back into it's place.  how messed up is that?

-t.

SpeeDFreaK:
Well, there was a time whem my comp dual booted between Mandrake 8.0 for windows and Win2K (or was is 98?). Had it installed, everything running fine. Looking through mandrake installation in Windows. (ran it on a fat32 part, bulk of installation was in a 2-3gb file). Eventually it crapped out on me and i was left with just windows. Looking around at my trashed linux install, i found a folder marked grub. I figured "Hey linux doesn't work anymore, so shift-right click, delete!" Next time i turn on my computer i'm greeted with "start 1". Restarted about 5 times, same message, then I realized i just f'd my bootloader...reinstalled windows for the nth time.

choasforages:
hmmmm, i installed redhat 7.0 and didn't know how to start the gui with the command startx. i had to reinstall redhat 7.0 again, so i could use the computer. hmmmmmmm, i installed FreeBSD on the wrong harddrive, obliterating my unreal and unreal tournament installs. installed from source gnome2, just to have sawfish decide not to compile/*well, metacity does look nice though*/ used a yahoo keyboard. get water on my microsoft intelie mouse, buy a lexmark printer with binary only linux drivers, buy a thinkpad 600, only to find out that the soundchip will probabluy never work under linux. put $100 into a powerbook 1400, just to have it not connectto my network/*im working ont he one though*/

rtgwbmsr:

quote:Originally posted by beltorak0:
FIX WINDOWS!!!!!!!!
--- End quote ---


Why bother? It's broken beyond repair!
   :D  

Everytime I come across a Wintel PC with Windows problems I buy an old Mac or install Mandrake/RedHat/Slackware/Debian (depending on who it's for)

XP is the worst though. When it breaks, it automatically restarts, so you can't see the error code on the BSOD (note: turning off the "Restart on Error" option does shit) I couldn't count how many people called me to fix this problem. Only option: Reinstall Windows (Or preferably talk them into using Linux or buying a Mac - I've converted so many fed up people this way)

-Dustin

[ August 16, 2002: Message edited by: The_Muffin_Man/ Dustin /B0b ]

Navigation

[0] Message Index

[#] Next page