Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!sun-barr!lll-winken!unixhub!slacvm!esr
From: ESR@SLACVM.BITNET (Ed Russell)
Newsgroups: comp.sys.ibm.pc.hardware
Subject: Re: HELP: THINKS C: IS D:
Message-ID: <90291.225638ESR@SLACVM.BITNET>
Date: 19 Oct 90 06:56:37 GMT
References: <1990Oct17.101516.24070@cbnewsl.att.com>
Organization: SLAC Computing Services
Lines: 21

In reply to:

>From: rl@cbnewsl.att.com (roger.h.levy)
>Subject: HELP: THINKS C: IS D:
>Message-ID: <1990Oct17.101516.24070@cbnewsl.att.com>
>Date: 17 Oct 90 10:15:16 GMT
>
>I have an AT&T 6300 with an ST-225 and Adaptec controller that has suddenly
>refused to boot from the hard disk because it seems to believe that C: is
>D:.  Apparently the boot process gets as far as reading config.sys since
>error messages like "C:\BIN\ANSI.SYS NOT FOUND" and "C:\COMMAND.COM NOT
>FOUND" appear.  If I boot from a floppy and then select C:, I get "GENERAL
>DISK FAILURE".  However, if I select D:, I can see and access all the files
>on the drive (which is really C:).  What is likely to have gone wrong and
>how can I correct it?
>

Did you change the jumpers on the hard drive printed circuit board.  There
are usually jumpers to identify whether your hard drive is to answer to
drive 1 or drive 2.  If it is jumpered to answer to drive 2, it will act
like a D: drive even if you don't have a C: