poor little bear:(
Printable View
poor little bear:(
one more screw up. I was adding a cd RW to my Computer well as you all know there is a patch cable in the back well first off I didnt get one with the rw so I ran to compusa to get one for it and when I got home I realise there is an adapter on the original one DUUUUUh. then Like all men we dont read instructons so I connect the rw without switching pins from master to secondary. DUUUUUH part 2. Well hope you feel smarter than I now.
More mistakes to come I just got a Server with Skuzzy Drives (god help me ) that brings me to this does anyone have knowledge of a NetFrame Server and a good Idea on how much it costs?
Thanks but no thanks sebastos12, it only proves that I was stupid to think that I could **** around with the registry without reading up sufficiently on the matter. Ok misstakes are made, but totaly screwing up my puter like I did is beyond that. Do I have to say that I won´t do something like that again..
It´s education.
And education is the key to power :D
Your are philosopher Pooh-Bear.
I wish I could skip VB, but school thinks you can teach java after a semester of cobol / VB. Stupid.
This may seem lame, but I would play with the boot up and log out screens in Win95, and it worked fine, but when I got 98 it wouldn't cooperate. How come
Micro$oft doesn't want you to change the logo?
heh join the club :)Quote:
Originally posted by Rewandythal
Jesus... much as it annoys me when my computers **** up, i enjoy the process of workin out why and repairing them because its the learning process... I live for knowledge.
[Some people say knowledge is power... if that were true i'd be in search of a nuclear generator!!!]
i have does this on more than 1 situation.
1. Just because i wanted to see what happened (had backup image of disk sort of 10 minutes reinstall after reboot via floppy)
2. By various commands.
a) scripts using the .. in directories and finding ../../../../ and finding (/)
b) typing things like "rm -rf /tmp/ ." instead of rm -rf /tmp/.
but i think the best is is using a symlink to / and rm -rfv symlink/.
on a term without colour and not knowing it was a symlink.
just a few there are many more :/
Oh gosh here we go again... :D
I fried a monitor, formatted my term papers... the normal stupid mistakes. :D
Yes yEs yeS
If confusious was alive today, he would say...
Even Bill Gates forgets things and screws up stuff.
Now watch him strike me dead and destroy my computers from his office.
Here is a good one that just happened today.
I have a 300 Amd that i just upgraded to a 500. I have it dual booting with nt4 and 2000 prof. with an extra 20GB of space. Over all i have 6 GB used of files. I wanted to change the partitions so i could have triple boot with NT4, 2000 Prof, and 2000 Server. I first ghosted my hard drive to a spare 30GB and then disconnected it and set it off to the side, for a backup incase anything went wrong. I started on my origional, i used partition magic and changed it to how i wanted it. I saved the config and restarted. The computer came up and the config didn't work my partitions were still the same. So i tried again. Same thing. So I thought i would just use fdisk and create the partitions. I created them and shut down the computer. I hooked back up the spare drive and went to ghost each partition to the origional harddrive.
To my suprise there is not a single damn file on the spare backup harddrive. My original hard drive had already been repartitioned. I lost everything. Now i am reinstalling them all. Except that i have 98SE instead of NT4.
The only way to learn how to do more than the basics on a computer w/out damaging it in some way:
1. read, read, read
2. study, study, study
3.never, ever, ever, touch a computer
Ain't that the truth. Except why would you never want to touch a a computer.Quote:
The only way to learn how to do more than the basics on a computer w/out damaging it in some way:
1. read, read, read
2. study, study, study
3.never, ever, ever, touch a computer
I have a couple of dozeys for you(and the second is within the last 6 months) My stupidest software mistake was downloading a file and decompressing it into my root directory(512 file entry limit) the next day I treid to erase some of the entires and deleted something critical.I hosed win 95. when I went to reinstall windows I got halfway thru and used all the root directory entries up and locked it up at the reinstall.the result was a full format/reinstall.That was a longggg time ago. For something really STUPID i was building an athon 1ghz box and forget to plug the cpu fan in.it was a crispy critter.Now thats bad. But THEN I got a replacement(from my cool and understanding source)I rebuilt the machine again this time with the fan plugged in. It booted..almost posted and went dead. when i took it apart it turns out I forgot the put the thermal paste on the cpu(building a couple of hundred systems in my life) what a dumbass I was. I am now in a postion to help alot of new users and enjoy doing so
I just hate know-it-all complaining geeks(I now know as much as most of them) but thats not saying much :dunce: :duh:
it happens with everybody and i agree with ennis "we learn from mistakes"...i still remember it happened with me once...and this is the incident i willl never forget in my life....
it was my 16th day on my new job as a system programmer adn i was suppose to check certain programmes which where huge satellite communication programmes , i was working on them and also was very much tired , my head was heavy as i was working since 36 hours non-stop. and i don't know what command i gave that deleted 163 programmes from that particular directory. and i nearly felt dizzzy.....
i was using unix , but then luckily we were having back ups ans so we restored it back...
so it happens......
intruder... :borg:
I haven't read all the posts, but with one thing i agree:" we learn from mistakes, but we can destroy many things with big mistakes" I'm philosopher :D like ancient Greek people.
I disagree:Quote:
Originally posted by casper3699
make sure the power is unpluged before you play take it all apart.
Only power off the box, keep the powercord plugged in otherwise you have the risk of ESD. With the power cord plugged the electrostatic discharge goes threw the earth cable (or your body) so it helps against ESD. (This goes for every repair on the unit except of course the transfo!)
don't ever try to clean up your desktop in a windows box by deleting icons
i deleted that damn "e" and lost my internet connection
so i couldnt connect to do an update and try to get it reinstalled
couldnt install it off the oem
couldnt just reformat i had 60 full gigs of mp3s
sooo
i finally just upgaded, no downgraded from 98se to ME
blah
I once plugged a current wire into the ground connection on a motherboard. Pushed the power on button, threw the circuit breaker in my house, and smoke starting coming off the board. woo, yeah baby, fun stuff.
I had Norton Systemworks tried to resolve a 'problem' on the master boot record of the first HDD. Norton did not see that the box was using a bual boot config (NT4.0 and Linux) so all that the box did after the repair was giving a black screen with a blinking cursor in the left upper corner.
Norton overwrited LILO.
I had the luck to be the owner of a Linux boot floppy; it was the only way to get the MBR back. No way M$ could bring a solution.
No you're not, you don't know **** and you're a bitter, twisted little **** - most of the advice you dole out is wrong, and you talk nothing but ****. "I wrote an os, i'll post the source code" - so do it then. "i work for microsoft" - as much as i'd like to think you work for microsoft, acting as a catylyst to thier imminent downfall, i have a hard time believing you work at anything that involves using your brain you absolute imbecile.Quote:
I am now in a postion to help alot of new users and enjoy doing so
(edges away from petemcevoy) I hope I don't get trashed like that! Hah!
Before I proceed with some of my more glorious screw-ups, my mentor for unix told me once:
"There are two kinds of sysadmins: those that have completely ****ED a system up, and those that will."
That said, onward we go!
1: deleted the font file for solaris 2.51. If you're booting into anything other than single-user mode, it won't boot. Period.
2: destroyed the swap file by accidentally dd'ing it to /dev/null (this is what happens when you don't pay attention to what you're typing while talking to someone)
3: set the first tape device as the swap device...mainly because I wanted to see how long it would take for a box to boot...a loooooooong time.
4: did 'cleanup' on the DNS server and unfortunately blew out all the zone files because bind hadn't updated in over a month due to a previous change BY AN NT ADMIN WHO HAD ROOT ACCESS FOR SOME REASON (don't get me started on what I was yelling that day) that didn't work, go figure.
5: powered off an N-class HP 9000 server without knowing that Oracle was in hot-backup mode with Omniback...the DBAs didn't like me very well that night.
6: accidentally zero-lengthed the kernel for an HP box (I still don't know how I did this?)
I think those are some of my more glorious screwups that halted business to some level. Windows problems, while I've had many, don't really count because everyone knows there's two methods to fixing Windows: reboot or reinstall.
Peter,
Whoever you quoted could be a janitor for Microsoft. It's like I could say I work for RedHat, but maybe I am just the guy that makes the coffee.... Well I don't work for RedHat, because I am a consultant downtown...
I am the Chat Nazi though!!!!
Good one - I probably would've tried that sooner or later if I ddin't read up on *nix before I started screwing around with it.....Quote:
Originally posted by DjM
I too have had my share of screw-up's. I am a member of the
rm -rf (as root, from the root directory) club.
Unix doesn't like that very much.
:p
I always thought it funny to get ppl who you don't like to press alt-F4 ;)
Hows about receiving 200 new computers and as the Junior Tech was told to clone the drives from the computer in the corner, OK not too difficult, finished the whole lot, went back to check the first couple. All were blank, I had just been cloning from 1 internal drive to another.
Small screwup - chown -R oracle:oinstall /u* (trying to cover all of the /u01, /u02, etc file systems)...what's bad is, /usr is first, hehe...
Medium screwup - tried to make a mounted drive a virtual 'man page from cd' file system for an AIX 4.2 system. Instead I copied the cd, per instructions, to the mount point, which filled it up to 100%, and then mounted the cd on top, hiding all the files. Took me 30 minutes to find out what I had done...bleh.
Major screwup - was halfway through copying one machine to another for a /usr and /bin copy...then I realized machine A was solaris and machine B was hp....oops! I became real intimate with the phrase 'nobody cares if you can backup, they only care if you can restore.'.
"There are two kinds of sys-admins - those that've really ****ed a machine up, and those that will."
yeah i had my share of screws up too
deleted the tacacs lists servers from a critical node ... whole network down for 3 days till we found a work around ....
Found a great site for anyone wanted to grow their knowledge of IT (and pretty much anything else).
www.howstuffworks.com
Live as though you'll die tomorrow,Learn as though you'll live forever.