Slashdot Mirror
Abused, But Working Hardware Stories?
RPI Geek writes "Everyone's heard the stories about people who, knowingly or unknowingly, abuse their computers. Personally, I've had a faulty power supply literally burn a hole through the motherboard, with the only ill effects being a dead PCI slot and USB ports. I'm curious as to what kind of abuse fellow /.ers have done or seen done to electronics while the hardware still worked afterwards. Soldered a broken keyboard PCB back together so that it worked fine? Taken sticks of RAM out of a running computer to see when it would notice? Overclocked a 386... to 386MHz? I'm interested in hearing any stories about abused-but-working hardware."
So far I've done the following while my PC was running:
- Removed RAM. Windows died. Reboot. Problem solved.
- Inserted PCI cards. Windows died. Reboot. Problem solved.
- Removed PCI cards. Windows survived.
- Hot-swapped hard drives. Windows survived.
- Hot-swapped CD/DVD drives. Windows survived.
My power supply and mobo must be very fault-tolerant, I suppose, because other systems have not taken a liking to this behavior. I have an Enermax 350W and an Asus P4C800-E. Currently I own two SATA hard drives. According to the standards group, SATA is "hot-swappable." Given my previous activities, I can verify their claims.
Obviously, the system did not enjoy having its RAM removed. And while it did not mind the removal of a PCI card, it froze up solid when I inserted a new one. A quick reboot took care of that.
I've also dropped my iPod about 5-6 times, and it still keeps on ticking!
Homestarrunner.net -- It's Dot Com!
Back in 1996 I built a dual Pentium Pro computer in an SKB music case (for rackmounted music gear) as a luggable computer. After a few years the thing was pretty antiquated, so when I had to move from Europe back to the US I decided to doom the thing to the fates and have it travel back with me with my luggage, facing the perils of baggage handling. It just wasn't worth taking any extra precautions. I knew the thing wouldn't survive the trip, but I didn't want to throw it out. It had no shock protection at all, and I didn't place any fragile stickers on it or anything. After the trip I opened the case up to find the CPUs and memory sticks had unseated themselves and been knocking around inside the case, many of the CPU pins were bent this way and that. The memory seemed scratched but otherwise ok. some of the chips mounted on the motherboards seem to have suffered the impacts of the CPUs flying about (some bent wires going to the chips). Just to see what would happen I straightened the wires, pins, re-seated the memory, and turned it on. The damn thing worked fine. And went on to live an unexpected few years as a file server. I'm not sure what lesson I learned, I suppose that computers can be far more robust than I expect (but only when I don't expect it).
Don't vote for Eugene Papansanovich for Congress!
Well, this was unintentional, but I had a 60 Mhz Pentium and after a couple of years decided to replace it. I bought some new components and opened up the case to pull the memory and found the heat sink lying at the bottom of the case. It had completely fallen off at some point in the past. Strangely, there were never any symptoms and it worked fine the whole time.
A while ago, I needed some cheap 1U servers... I decided to use some cheap motherboards with "onboard everything"... There was just one problem. The sound port did not fit in a 1U rack cabinet. The solution was to fetch the soldering iron and remove it. It worked!
thomasdamgaard.dk.
How about that! Got a guy who took a trashed P4, solder some 24 guage wire on to create a pin and is using the CPU now. I am quite amazed at the man's skill. I for one can't do crap with a soldering iron except ruin things.
I plugged an 18 volt AC adapter into 6 volt computer speakers. They made a really high pitched sound before they popped and spewed lots and lots of acidy smoke.
We later found the correct AC adapter, plugged them back in, and to our surprise, both speakers worked just fine. It makes you wonder what useless part broke in the speakers, and why that part was in there to begin with.
I often soap up and hose off old gear and it all works fine. You need to let it dry for a couple of days, though. Never lost a PC that way.
Hey, I just thought of something! You know how toaster ovens say DO NOT IMMERSE? Well, if you DO immerse them, water gets into the heating tubes, which are filled with compressed poweder magnesium oxide. It takes a very long time to dry, more than a few days. If you decide to plug the thing in because it LOOKS dry, the water in the tubes turns to steam, which cannot escape fast enough, and the tubes RIIIPPP open from end to end, blasting powdered MgO all over the place.
That would be a funny prank, huh?
Several years ago I had my PC's setup in a shed. The shed was well setup with power and lights, and one day I was doing a motherboard transplant (swapping a 386dx40 with a 486dx2/66 from memory).
I didnt get it finished so i left both my desktop PC's with the covers off and went to bed.
That night there was rain (as usual) but it was also severely windy - enough to blow the rain at enough of an angle so it went under the eave section and straight onto my desk.
I got up in the morning and found both PCs and motherboards completely soaked and water pooled everywhere. Turned them upside down, dried them as best I could and left them (inside the house this time) for 2 days. When I powered them up they both worked, without a hitch and continued to work for years afterwards.
(one mouse was dead though - a small price to pay)
You can't expect to wield supreme executive power, just because some watery tart threw a sword at you
Back when memory was around $100/megabyte the school I was attending received some donated hardware that included one non-functioning 1 MB SIMM. Rather than toss $100 in the trash, I examined the SIMM and found a broken pin on the side of one of the chips. Using a battered soldering iron and a length of cold solder to replace the pin, I managed to get a good enough connection to restore the SIMM to operation. It functioned perfectly in a 486SX machine for several years afterward. I also managed to upgrade that same machine to a DX (MMU and FPU added) by salvaging a 486DX chip off another dead motherboard installing it in a cleverly included socket on the SX motherboard and disabling the onboard chip via jumper settings. This was before the ZIF socket, so the amount of force and screw driver based prying required to first remove and then install that 486DX chip could easily have killed it.
Luck was definitely required in the days of expensive parts, and $0 technology budgets.
I'd like to say we later installed Linux on that machine and used it to run our first web server, but alas, we used it for playing deathmatch Doom after the computer lab was closed. That's why we needed 4MB of memory and a FPU.
In late 80s one of my friends brought a brand new computer from USA and asked me to help him to set it up. I switched the power supply to 220 Volts and plugged it in. There was a loud bang and small cloud of black smoke came out of the case.
The power supply, while worked fine on 120V, had pretty much shorted the 220V to the motherboard. There was a quarter sized hole on the motherboard, with black charred remains of a chip sprinkled around.
Amazingly, the computer came with a circuit diagram, so we figured out that the charred chip was actually a simple 4xNAND or something like that. After we found a replacement chip, just soldered its legs with wires to the closest intact parts of the motherboard, replaced the power supply. And it actually worked. The chip was hanging over the hole supported by the wires, like a little spider. I wish I took a picture.
Needless to say the owner was very happy.
One day the show operators called our tech support to tell us that the BeBox was acting a bit sluggish (BeOS, as you may know, is normally quite snappy). On his next visit, our tech took a look inside the case, and found that the fan responsible for cooling one of the two PowerPC 603 CPUs had stopped turning, causing that CPU to overheat and desolder itself from its socket. The BeBox had survived the self-destruction (and self-extraction) of a CPU and continued to run shows for nearly a week without complaint.
The other story involves a piece of hardware surviving impalement on a forklift fork and continuing to function with no apparent ill effects...
I don't care if it's 90,000 hectares. That lake was not my doing.
I work in hardware/firmware development - bringing up new boards and building firmware on hacked-to-all-hell prototypes. I've soldered on stuff while it's running. I've swapped cpu, memory, pcmcia, and other components while the system is running. I'll run my feet across the carpet on purpose to test ESD tolerance... shorting signals on purpose because it's easier than cutting a trace and wiring the input to ground. It is amazing how much of a beating like this a system can take for months or years on end and still run perfectly. It does not surprise me at all when people talk about systems that have caught fire but still mostly work.
Now one of my favorite stories: a friend of mine worked for AlphaSmart - they make inexpensive portable word processors - really PC keyboards with memory. He said they got a report of a woman in India who had run her alphasmart through the dishwasher to clean some gummed up keys.
If you think about it it's not surprising... the equipment they use to clean PCBs at the factory is pretty much the same as a home dishwasher - just different solvents I guess.
I have that beat.
.45 while trying to end his crime spree.
An armed robber broke into my house, collected various valuables, put my TI SR-51II calc into his chest pocket, and I shot it with my
Bullet went thru the padded case, bounced off the manual, and into his chest. The calculator was not even dented.
I should make a jacket of those old TIs.
The latest Slashdot meme.
Actually, I forgot the time my SNES got tossed across the room into the wall and still survived, except for a chip in the case and a slightly bent RF cable.
In the dim, dark past, intel machines didn't have an FPU on die. You could buy an exernal floating point processor, which was most commonly installed by the store that sold the machine.
Well, Compaq made a system where the the main processor along with all the other chips were mounted so that the letter was right-side up when standing at the front of the machine.
However, the coprocessor socket was rotated 90 degrees. If you installed it so the lettering was the same as everything else, one of the pins melted off when power was applied. Don't ask me how I know.
great design.
You are not a beautiful or unique snowflake -- but you could be if you got off your ass.
Well, we got a batch that we just couldn't get installed. Tried the cards on a few different systems, different bios settings trying to force irq's and whatnot, but not a thing. We declared them all defective (being a 17 year old kid working as a co-op student mind you), and decided to go with the tried and true Sound Blaster pci's instead. We then proceeded to take some of the Sonic Impacts and play frisbee, use them as coasters and ridiculously large keychain items.
Years later I'm assembling spare parts to make a secondary system, and realize I have no sound card to put in it. All I have are isa cards, and this motherboard is without an isa slot. So I go rummaging in my room and of course what do I find but a well worn Diamond Sonic Impact. I figure what the hell, and toss the thing into the box. On first reboot XP found the card, and proceeded to lock up while installing it's drivers.. On second reboot the drivers completed, but windows core dumped shortly after. Third time was a charm though, and I still can't believe this thing produces sound after what I did to it.
Turned out that there was a current in the shield of the coax. Why? Because the outlet that one of the boxes was plugged into was miswired. 110 volts running between the computers for months, maybe even a year.
When I realized what was going on, I shut both PCs down and repaired the faulty outlet. Both booted right up. The problem that I was troubleshooting never appeared again.
I set a full glass of water on an old Commodore 1541 disk drive. I then knocked it over and the entire glass of water poured into the drive via the top air vents. After drying for a few days it worked fine for years to come.
Spilled a glass of grape juice (real stuff, not cool aid) into the keyboard of my Commodore 128 computer. Again, after some washing and drying it worked fine. Well, except some keys would stay depressed if you were not real light with the typing.
My friend tried to overclock a his near new Amiga 3000. While trying to desolder a chip he managed to yank it off, along with a half dozen traces off the motherboard. He ripped apart some speaker wire, resoldered the lines and it booted up fine.
While working at a computer dealer, a co-worker tried to replace a hard drive on some IBM machine. Problem was it LOOKED like IDE but was really some wacky mainframe thing. When turned on, about 5 of the wires in the IDE cable turned red hot and exploded into flame. The HD was toast, but the computer was fine once the right HD was ordered from IBM.
While using my trusty old Pentium II I heard a SCSI drive inside make a PING-PING-PING and a horrid grinding noise as the platters ground to a halt. Opening up the drive case revealed a read write head had somehow come loose and gotten wedged under the arm against a platter. Carved a nice circular trench in the disk platter.
Umm, guess the last one isn't a survival story. But I did have backups...
I've noticed the exact same thing with my 12" PowerBook. (The new 1.33 GHz model) I fractured my left wrist at the start of summer, so for the past few weeks I've been in a brace while it's finishing up healing. I was in a rush one day, so rather than make two trips to my car, I foolishly carried my PowerBook in my left hand while carrying the heavier parts of my load in my good right hand. I lost my grip with my left and narrowly missed grabbing the PowerBook with my right hand before it hit the ground. There was a pretty loud thud, and I thought it was a goner.
Much to my surprise and delight, it worked flawlessly when I opened it up. It was sleeping, and it was ready for use near instantaneously like you expect from an Apple laptop. It had landed on the corner by the power and Ethernet ports, and sure enough the case crumpled noticeably. However, I can still plug into both ports (not sure about the modem jack though), so I haven't bothered hammering out the dents yet since they are only cosmetic.
I must applaud Apple for excellent laptop design. After seeing what happened to my laptop, I suspected that they had designed the case to be a crumple zone. Your story confirms my theory. If I'm faced with the worst case scenario being paying $50-$100 for case repair to a dropped laptop, I'll take that any day of the week over having to get a new mobo at first drop.
I awoke in a panic, with just barely enough time to make it to pick up my Mom in time. I raced outside, jumped in the car, and tried to back out of the driveway. The car wouldn't move. I thought it was just a snowdrift, so I pressed harder on the gas. Still no good. So, I pulled forward a little and got up some speed in reverse. After a few more attempts, I finally managed to make it over this huge hill. I looked at the mass in the car's headlights. As my eyes adjusted, the horror of what I had just done began to dawn on me. Lying on the ground in front of me was my laptop's bag, with my laptop and several floppy disk cases full of floppy disks.
What I had done was so overwhelming that I did not even try to feel an emotion. I just picked up my laptop and carefully placed it in the back seat of the car.
When I had the chance, I checked out the results of the evening. The LCD screen was fractured down the middle and the case was split down the middle. As I balanced each half of my laptop on my lap, I turned on the power. To my surprise, she booted up. One thumb-sized piece of the screen revealed the DOS prompt.
I still have that laptop, though, of course, I have not used it very much since then. I was able to perform some important data transfer operations with it, though, relying entirely on memory of what the computer should be displaying in response to each of my inputs. Most of the 3.5-inch floppies came out OK, too, though a few were unusable due to their shutters being welded into the plastic. The floppy disk cases cracked a little, but I still use them, too.
Taking stuff apart since 1969 (TM)
A spot of background: Wycliff Bible Translators is a charity that has set out to provide a translation of the Christian Bible in every language on Earth. This includes, of course, thousands of languages that have no written form, so part of their work involves volunteer linguists traveling to remote parts of the planet to create written languages for tribes and teaching them literacy in their own tongue.
... and the PDP 11/40 was still chugging along, happy as can be. Now, obviously they panicked and got the air conditioning fixed as quickly as possible. But they did prove that at least this one PDP 11 could run for at least a week at temperatures in the 160F to 180F range.
Back in the late 1970s, I did some volunteer programming for them. At the time, translation support ran on a PDP 11/40 that was installed in the cargo hold of this aging steamship that they owned; they'd sail to the port nearest to the next tribe they were working for, teams would collect dictionary words, create orthographic phonetic spellings for them, and send them back to the ship to be collated for the dictionary, then printed out and sent back out to the teachers and translators. The rest of the ship had no air conditioning, so they built a climate-controlled computer room below decks, with orders to people that they were only to enter on the rare occasions that a magnetic tape needed to be changed.
Unbeknownst to them, the air conditioning failed as soon as they left port and never actually turned on. When they went in to change a tape while docked in Rio de Janeiro, they found that the temperature in the computer room had risen to somewhere in the close vicinity of 180F
But then, what can I say about 1970s DEC hardware? The original VT-100 was top-rack dishwasher safe. No, really - that was the standard DEC repair instructions in case someone spilled something into a keyboard. Place the keyboard key-side down on the top rack of a dishwasher, normal wash cycle, air dry.
Computers may have been expensive back then, and huge, and we thought that 128k of RAM was a lot, but boy could they take a beating, at least if you bought them from Digital Equipment Corporation.
I put my computer together on the kitchen table, stood nervously looking at it for a few seconds, took a deep breath, and turned on the power. There was an immediate loud POP, and half of a capacitor made an arc that took it across the kitchen. A cloud of bright pink smoke rose up from the shattered capacitor as a small flame burned from the capacitor. I quickly turned off the power and blew out the fire. After I calmed down and looked over my setup carefully, I found that I had plugged the AT power supply cable one pin over on the AT power supply plug. I adjusted the cable and turned my computer on, again. To my surprise, my computer worked! It was a beautiful sight!
I still have that computer (in fact, she is on the table behind me right now, watching me type this). She still works when I turn her on, but I have to adjust the system date to less-than 2000. She is not Y2K compliant.
Taking stuff apart since 1969 (TM)
The iDX4/100 CPU that was supposed to be powered by 3.3v but was configured by the vendor without the motherboard's voltage regulator module, so was running off 5.0v (I fought to have them replace it anyway).
The sound board that needed a new edge connector fitted after I slipped on some stairs whilst carrying it, landed on it and ripped the old connector off, together with some tracks.
The PCs that were under a leaking air conditioning unit at a former employer and got soaked in water and/or coolant. Once dried out, they worked (mostly) and were given the hostnames 'itchy' and 'scratchy' in order to make people suitably nervous about using them for anything important. One of them even had a failing hard disc, so I partitioned around the failed sectors.
The 17" CRT monitor that was dropped (NOT by me!) down some stairs in 1998 whilst the same employer was moving buildings. It acquired a large crack in the case, but is still working fine.
The M68000 CPU that had several pins bent and re-bent whilst I was attempting to fit it to a new socket on an Amiga accelerator card (that in turn fitted into the original CPU socket on the Amiga motherboard).
--
I'm writing this post on a Dell Dimension 8250 that was in a basement when the watermain in the front yard blew, filling the basement to a depth of about two feet for about eight hours. Yep, completely submerged. Thing sat on the back step for a week before I got to it. Scrubbed everything down with an old toothbrush (the insides looked like they'd been spraypainted with rust-coloured paint), and blew everything out with compressed air. The HDD was shot (no real surprise there), but *everything* else works just fine, including the CDRW and the Radeon 9700.
Tune In, Turn Up, Geck Out.
It's late, so I'm pretty sure this will get lost in the din, but....
I was at a computer repair shop, and I noticed that all the counters were covered with cheap, commercial-grade carpet. It was a dry day, and I shocked myself several times just moving about.
So, I asked the guy (the owner) at the shop about this, and problems with ESD (Electro-Static Discharge) with the carpeted counter tops.
He laughed. On the counter was a high-dollar memory tester. He grabbed a then-expensive 4 MB 30 Pin SIMM and, holding it in one hand, walked around the room, dragging his feet. He did this until (No kidding) his own hair was beginning to stick up.
Then, holding one end of the SIMM, he walked over to a doorknob, and threw a 1", bright blue spark directly thru the simm to the doorknob.
He then calmly walked over to the memory tester, and ran tests on it. It ran for 5 minutes with a hitch.
I don't worry much about ESD, and haven't for years, with no trouble. The problems I have are with stressing the parts - putting undue stress on a MB when inserting a RAM stick, for example.
I have no problem with your religion until you decide it's reason to deprive others of the truth.
Except this baby seems to work just fine.
Hmm, let's see what I can find in the back of my head at this hour....
;))! So we would do voltage readings with multimeters on the ISA/EISA ports and on the PSU pins with a back probe while it was on and connected to a HD/CD. So after we finished, me and my partner got curious and started tripping pins with the back probe wire we had. Eventually we found out how to trip the PSU and shut it off due to a short we found across the ISA socket. We kept doing this over and over, moved on to removing RAM while it was one and pulling the power on the IDE devices and stuff. We didn't blow anything up that time but everything seemed to work fine after.
1. Back doing some PC tech stuff in a class I took a couple years ago back in high school, we had a couple P1 and 386/486 mobos around, so the teacher would have us use those, god forbid we touch the P3(smart guy haha
2. This wasn't me but another group in my electronics class in HS. We were doing more voltage testing on PSUs in our basic electronics class this time, and 2 smart guys decided to take paper clips and metal wires and stick them inside the AT PSUs while they were on. An explosion, lotsa sparks, tripped circuit breakers, and a pissed teacher later we found that the PSU had still worked, just 2 of the IDE power plug didn't work.
3. My friend had purchased a little 1.53GHz P4 CPU, and bought a very cheap motherboard, some offbrand name. Well as he was driving around crazily like usual, the the CPU unit was in his trunk upside down so the CPU/heatsink was hanging. You all know how heavy those P4 heatsinks are! So the heatsink clip breaks off the motherboard, and goes crashing around for another 10 min till he gets to my house. When he brings it over, he notices that his computer keeps shutting down, we open it up, look inside, and the CPU was burning hot besides the fact the heatsink was off. We saw the heatsink did plenty of damage and knocked dings all over the case but didn't touch any chipsets luckily. Our solution was simple......duct tape! Yes he had that heatsink somehow strapped down tightly with duct tape. Don't ask me how he did it, but I was afraid the tape would somehow catch fire. Sure enough he gave it to me recently after he upgraded for a server. I took the heatsink off and to my suprise the CPU came out too! The thermal grease basically glued it to the heatsink, so I had to take a flat head screwdriver and pry it off. It went flying a bit, bent a pin or two, I fixed them, put it back together, and walla it worked!
4. Someone at my dad's office who worked in the field somehow dropped one of those rugged outdoor special laptops off a 2 story building. It went flying to the ground with a thud landing LCD screen open flat onto the ground. As you can imagine the guy was pretty much ghost white. They rushed down to check it out, turns out that the thing survived! Perfectly, there was no damage to any components, just the RF wireless network access antena was a flimsy aluminum strip, it bent in half, but still worked!
5. At a small buisness I had worked for a while, had a server in the back storage room that backed up their tax files (it was some tax/investment buisness). There was no AC back there so they left the side window open that just opened 6" to a tall cinder block wall. So they never go back there, and it rains a couple times. I come back and turn on the server monitor, it makes a this LOUD screeching noise as it warms up. I quickly turn it off and run out of the room(wouldn't you?). I told my boss and he just says, "Oh, we left the window open over the weekend, some of the rain musta got on the monitor, it's ok right?" I just shook my head lol. So we got a broom, and went back, we poked the monitor power switch with the end of the broomstick from outside the door, then as it turned on we flipped and hid around the other side of the wall. As it warmed up the screeching quieted, then we noticed smoke comming up from the monitor, but we realized it was water vapor when it didn't smell like it. The
-Conrad
The only thing to try is to shoot it.
I worked in the US with a large manufacturing client. They had a large group of AS/400s running their ERPs. One night the security guard was drunk on duty and decided, we do not know why, to take out his anger on an AS/400. It was shot twice, front to back. This took out one processor board and an external connection that provided one of two connections to the storage.
In the morning two things happened
1) Security Guard was arrested
2) IBM turned up to put in a new processor board and external connection.
Total downtime : ZERO.
A fault tolerant power supply is nothing, AS/400s really are bullet proof.
An Eye for an Eye will make the whole world blind - Gandhi
When my employer retired an old sun they gave it to me. I was very fond of the thing because I, when I was a student, learned Unix and programming on that beast. It was the workstation all the (geek-) students wanted to use.
Anyway, I got home with the thing and found out I didn't have the root-password for the OS. So, install a new OS: OpenBSD. To do that, you need to be able to tell the thing to boot from floppy. You do that using a little command at bootup. And you need.... a password to enter that mode.
great.
No-one on earth was left that could tell me about those passwords, so I googled around and found the sollution:
1. Startup the sun
2. Press STOP-A (or something) to get into the OpenPROM / OpenBOOt/Whatever menu
3. When it askes for the password RIP OUT THE PROMCHIP FROM THE MOTHERBORD
4. Enter blank password. The machine will try to validate it against its non-existing memory.
5. It will accept the blank password and you can do "ALTER PASSWORD"
6. INSERT THE PROMCHIP JUST BEFORE YOU ENTER THE NEW PASSWORD
7. Enter the new password
8. It stores it in the now replaced memory-chip.
9. Install OS. Have Fun.
It really amazed me that this just worked. But it did.
This unique sig is intended to make this user more recognisable.
(I onced shared this story with a popular computer magazine, and it got published)
Years ago, I went with a friend of mine to his boss's house to fix his computer. This guys' house wasn't a house, but a log cabin in a rustic town along a river with a winding one-lane road to get there. There was a general store and everything!
So we get there, and I sit down at this computer on a desk and start plugging away. Meanwhile, my friend gets a call from his wife. He starts pacing around, handling the various antiques and oddities one rarely sees except in a rustic environment like this.
When he picks up the revolver, his boss starts yelling "Put that down! Put that down!", but my friend was too distracted with his conversation to pay attention to the outside world. Sure enough, a loud *BANG* rang out. My friend dropped the phone and everyone checked themselves for holes.
After we were confidet we were all still alive, we noticed the HP LaserJet III printer sitting inches away from me on the desk had a hole in it. Wiping the sweat form my brow, I started laughing because the printer was still printing at the time! We later took some of the external housings off the printer and found some fragments, but the printers guts weren't damaged and it was printing fine.
(I wish HP's products were still that good)
The gun, of course, was real. My friend's boss sais he kept it on the end table to shoot the bats that inevitably found their way into his cabin. I think now he might stowe it when guests come over.
I used to work at a space company that produces the OBC (onboard computer) for the Ariane 5 (you can see where this is going already right?)
Well, I don't know if you remember (most Europeans probably do) but the first Ariane 5 blew up (due to software reasons) in spectacular style. The French foreign legion was tasked with finding any important bits in the swamps surround the launch site. Surely enough they found the OBC intact (it is built like a tank), eventually it got returned to the company I worked for, and whilst it didn't work entirely, it did return some diagnostic bits that *something* had gone terribly wrong. The original computer was sat in a cupboard by where I worked for a while, had a few dents in it but looked quite okay. if you are into these kinda things you can see a picture of it in this pdf hereBeat that for hardware abuse :)
Ooh, do I have a good one for this thread!
:)
Back in the late '70s I was stationed on a guided missile destroyer (DDG class) in Pearl Harbor. I checked in just as the ship was preparing to go into the yards after a long Indian Ocean/WestPac deployment. She was overdue for a major overhaul by about 18 months. Since DDGs were supposed to be on 12 month maintenance cycle, you can imagine just how close to riding on the ragged edge a lot of the systems on board were.
Well, I was assigned to the electronic tech comm group (ETN) and told that I was taking over the UHF and HF radios from a guy who had left the ship about six weeks before I got on board. The ship had 4 HF transmitters, 2 100W and 2 1KW, 4 HF receivers, and a bank of 8 UHF transceivers. The UHF tranceivers were in pretty good shape, as there was still a guy assigned to them who had been doing most of the work. The HF receivers were sorta OK. The HF transmitters, OTOH, was a complete mess. I found to my (literal!) pain that mixing high powered electronics with an incompetent tech is a really, really bad idea.
Not knowing exactly where to start, I picked one of the 100W transmitters at random and dove in. I found 13 problems in 11 days. I should have known that I was in serious trouble when I closed it up to take it over to MOTU-9 (MObile Technical Unit number 9, a support facility full of senior techs), then couldn't get it re-opened when I got it on their bench. It turned out that the slide rails had been completely trashed somewhere along the line and the previous tech hadn't bothered to order replacements. Instead he had just let it sit partially open. After about 3 weeks I still didn't have it completely up to snuff. At least it would transmit on a portion of its designed frequency range.
The second 100W transmitter turned out to be in somewhat better shape. It would at least transmit across its assigned spectrum, but it had far more in the way of reflected power than it should have had. I finally figured out that he had damaged the antenna jack somehow. Considering that those things are almost impossible to put on wrong, I don't know how he managed it. In any case, after running so long with that much RF bouncing through the circuitry, the entire output amplifier was always iffy. I never did get it all the way back up to full strength.
The first 1KW amplifier was dead, dead, dead. That one turned out to be a simple fix, though. I just had to replace the last stage output tube and some burned out control circuitry from when the output tube had shorted across a couple of its plates.
The last 1KW amplifier was the worst. It had a habit of going from full strength power to off as the ship rolled, then back on again. When I pulled the power supply apart, I found that he had replaced all four diodes in the full wave rectifier. Not such a problem, except that most of the leads leading to the rectifier on the board had burned away when the rectifier burned up. Rather than lay down some new ones, he had simply threaded the leads of each diode through their holes, folded the legs down to touch the unburned part of the leads, AND HAD NOT BOTHERED TO SOLDER THEM DOWN!!!!
Every time the ship would roll, the diodes would shift enough to break contact, then reconnect. The truly amazing part is that he didn't start a fire in the comm shack from all the sparks in that power supply.
It says a lot about how well built that comm gear was built that even after all of that abuse, I was able to keep at least some HF transmitting capability up at all until we made into the yards. Granted, most of the time I was busier than a one armed paper hanger.
We went out 3 times before we went into the yards on training exercises. The exercises were in Hawaiian waters, and lasted 3 days, 3 days, and a week. I actually had 8 hours at the start of the week's cruise where I had every piece of hardware assigned to me up and operational at the same time. After two months straigh
Man, that's like some sort of bizarre, dark geek action flick. Perpetrator breaks in, beats geek with hammer (see his other posts for more details) and steals all his valuables.
The helpless geek can do nothing until his calculator is stolen, which is CROSSING THE LINE for a true nerd. Enraged and empowered by having a reason to fight, the geek fights back, killing the calculator-kidnapper, but in a horrible twist, discovers he has shot the very thing he was trying to save.
Fortunately, due to the heroic engineering efforts of TI, the calculator pulls through, leaving the geek and his arithmetical love to live happily ever after.
Back in the day, at MIT's Lab for Computer Science, we were working on a new hardware/software system called Project L. The astute readers here have heard me spout on about this project before, as it was years and years ahead of it's time. (Regrettably, funding issues forced it's early demise.)
... and the computation chugged along just fine, completing somewhat more slowly than it would have otherwise. These were not idle nodes, but rather ones intimately involved in the computation. While we, naturally, designed the system to be able to do this, it was actually pretty cool.
One of the goals of this project was to create an extensible, modular multiprocessor computer. The idea was that you would have some commodity hardware which was packaged in neat little blocks that you would snap together. Each neat little block would be more-or-less a fully functional unit, so if you had, say $1000 you could buy a 100-node machine, but if you had $2000, you could buy one twice as big, and hopefully, twice as powerful.
One of our demonstrations of the redundancy concepts involved to achieve this kind of extensibility was to have a four-node L machine running a reasonably long parallel process (realtime spectrographs). In the middle of one such computation, we physically removed half the nodes
Put my fist through my alarm clock with its ding-dong death inside my ear. - The Blackjacks.
Someone in the USA had a PDP-11 and a Fujitsu Eagle disk drive sink under muddy water during a flood (the water eventually covered the rack and came to just below the ceiling). The machine continued to operate until the power failed, after the flood peaked. Underwater. Under muddy water.
When the flood subsided, they needed the computer back up in a hurry so they hosed it out, dried it off, replaced the air filter in the hard disk and tried powering it up again. It worked. The tape drive (Cipher F880, I think) didn't survive, the rest did.
Got time? Spend some of it coding or testing