4 ms·
When I was 13 or so I bricked my A7A-266. This had me beyond tears and in that petrified “my world is ending” state. After hours of a sunken stomach and readin
by Waterluvian 4y ago
When I was 13 or so I bricked my A7A-266. This had me beyond tears and in that petrified “my world is ending” state.
After hours of a sunken stomach and reading online, I cobbled together a floppy disk with a bunch of special files that I didn’t understand. I think I even had to type one out in notepad. I put it in the disk drive. It tells you to wait five minutes and then reboot but I waited ten. There were no beeps or signals. I rebooted and the thing came right back to life and lived for years until an A7V8X promised me a good time with faster RAM.
Godspeed my first private computer motherboard. You recovered from a teenager-induced coma and got me through most of high school.
- benjaminpv 4y agoThat feeling of absolute dread, thinking 'my parents are gonna kill me when they realize I killed the family computer' did a lot to prepare me for the white-knuckle experience of troubleshooting problems in Production. :) Bless the talented engineers that put together last-ditch recovery methods and bless the folks that documented things well enough to let us make use of them.
- BizarroLand 4y agoMy first family computer was a Tandy 386-sx that came with DOS 5.0. Not soon after, we got an update to DOS 6.22, which also came with Doublespace, an on the fly disk compression system, which upgraded our 80mb hard drive to 116 glorious megabytes. A few months later, I did something stupid and decided to reinstall everything from scratch. Used a boot disk and formatted the hard drive, tried to reinstall DOS 5.0 and the hard drive reported that it only had 2 Megabytes of storage available. Instant panic mode. I had no internet, I had the manual for DOS 5.0 and 6.22 and about 6 hours before my mom got home from her night job before I got murdered. After frantically reading page after page of documentation, I found that once Doublespace is activated, the hard drive only has enough normal readable room to launch Doublespace, not to launch DOS. A bit more reading, and I found that I could make a DOS 6.22 bootable floppy disk with the Doublespace system on it, so that is what I did. Breathlessly I booted the PC with the floppy and it worked! Full disk file size visible! I hurriedly opened Doublespace, de-doublespaced the drive, and rebooted. From there it was a race against time to reinstall DOS 5.0 (from 5 disks), install the DOS 6.22 update (3 disks), install Windows 3.11 (8 MORE disks), install all of the other software (12-15 disks in total) and then make sure everything was signed in and set up before the garage door opened. I was literally putting the finishing touches on everything when my mom surprised me by walking in the front door. She had parked in the driveway instead of the garage. She looked at me, asked me what I was doing to the computer, and I told her that I had messed something up and her solitaire history had been deleted (which was true). She said it was ok and went to bed and I collapsed after a marathon 8 hour blind computer repair.
- toast0 4y agoOh man. I bricked a board doing a bios update while I had time time set funny (post 2038). Well at least that's what I think the problem was. Floppy drive recovery didn't work out for me. But I ended up getting a duplicate board on a job later, and ruined that one by spilling water on it in a caseless setup. But I was able to pull the BIOS chip and swap it to the board I had messed up earlier. I guess I probably could have contacted support and gotten a new BIOS chip before, but that didn't occur to me until now, 25 years later. This was a Shuttle super7 board with the AMD 640 chipset that got disappeared. I was trying to flash the bios related to getting the software for a distance learning macroeconomics course to work. The course was still in development, there were a bunch of videos on cd-rs... Ended up getting a new computer instead.
- pluijzer 4y agoI feel you, around the same age I constantly bricked my BIOS. I forgot what motherboard it was. I had to find the same model motherboard from somebody, boot it with their BIOS, swap in when booted and use some rescue floppy to clone to BIOS. It happened quite a lot. Later I found out that it always happened when shutting down Windows 95. Just turning the power off did not result in a bricked BIOS. It was also the first time I felt ripped off. I went into a computer repair store with it. Told them what was wrong and how they could fix it. Two days later they told me to collect my PC. They did not fix it because the cause was a bricked BIOS, had to pay all my pocket money for the cost of their 'research'. Still wonder why shutting down Windows 95 made this happen, never found out, maybe somebody here knows it?