Article View: comp.sys.ibm.pc.misc
Article #3632"1701" on boot = HD Death?
From: John Yee/;093090;eegrad
Date: Tue, 02 Oct 1990 20:56
Date: Tue, 02 Oct 1990 20:56
10 lines
1069 bytes
1069 bytes
Sorry if this is a repeat, the 1st post seems to have misfired. Anyway, I have a Miniscribe 40 MB which has worked flawlessly for 2 years. The other day, I had to track down a bad memory chip, thus I had to do lots of power up and downs and chip switching. Now, I get a "1701" at boot time and the system does not recognize the HD. I thought I was careful, but could something like removing a single memory chip too soon after powering down zap one of those super chips on the HD controller card? Is there another explanation? Any experience, helpful comments etc. welcome at yee@ee.ucla.edu, jy.
Technical Details
Message-ID:
<1235@lee.SEAS.UCLA.EDU>Path:
arc1-ca.pugleaf.net!utzoo!attcan!uunet!jarthur!ucivax!ucla-cs!ucla-seas!edison!yeeReferences:
<17100070@ux1.cso.uiuc.edu> <1990Oct2.073358.14409@nmt.edu> <2AQ%AT=@rpi.edu>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!jarthur!ucivax!ucla-cs!ucla-seas!edison!yee From: yee@edison.seas.ucla.edu (John Yee/;093090;eegrad) Newsgroups: comp.sys.ibm.pc.misc Subject: "1701" on boot = HD Death? Message-ID: <1235@lee.SEAS.UCLA.EDU> Date: 2 Oct 90 20:56:17 GMT References: <17100070@ux1.cso.uiuc.edu> <1990Oct2.073358.14409@nmt.edu> <2AQ%AT=@rpi.edu> Sender: news@SEAS.UCLA.EDU Organization: SEASnet, University of California, Los Angeles Lines: 10