Yzzerdd
Veteran Member
OK, so I've got my IBM PS/2 70-386 running, right? Well I had it running for an hour before I attended to it, but everything was fine once I got to it. I exit Windows 3.11, and go to DOS to install Partition Magic. I was bored and kinda felt like installing something. Well I get 100% through and it asks me if I want to open the read me file. I click "no." It doesn't click so I click it like 10 times, then I finally just press enter for "yes" on the keyboard and get nothing. Great, it froze. CTRL ALT DEL(universal *Fu**) combo) and still get nothing. So turn it off, wait a few minutes, and turn it back on. Err 10483 is displayed, and when it is the HDD spins down a bit and then continues spinning.
10483 * PS/2 - controller reset failure (on POST - (8555-061 HDSK not at speed (st-177I stiction) IBM warrenty)
10483 * PS/2 - controller (drv sel 0 - config/stat bad)
Another two restarts brings no avail, so I am now running tests off the floppy drive. Anyone know a fix or why this has happened? Happen to anyone else?
--Ryan
NOTE: The spinning down the HDD makes is the exact same as when you restart the unit. Possible reset signal stuck?
Let it also be known that during the wait for the error code to come up, a swift smack to the unit will make the HDD load the information to test the RAM that is on the expansion board. The error comes up the very moment I smack the computer. Hmmm?
10483 * PS/2 - controller reset failure (on POST - (8555-061 HDSK not at speed (st-177I stiction) IBM warrenty)
10483 * PS/2 - controller (drv sel 0 - config/stat bad)
Another two restarts brings no avail, so I am now running tests off the floppy drive. Anyone know a fix or why this has happened? Happen to anyone else?
--Ryan
NOTE: The spinning down the HDD makes is the exact same as when you restart the unit. Possible reset signal stuck?
Let it also be known that during the wait for the error code to come up, a swift smack to the unit will make the HDD load the information to test the RAM that is on the expansion board. The error comes up the very moment I smack the computer. Hmmm?
Last edited: