Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!mcvax!hp4nl!botter!tjalk.cs.vu.nl!wallagh
From: wallagh@tjalk.cs.vu.nl (Wallagh Serge R)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Hard drive/Controller
Message-ID: <2367@botter.cs.vu.nl>
Date: 14 Jun 89 23:10:40 GMT
References: <14348@watdragon.waterloo.edu> <887@bimacs.BITNET>
Sender: news@cs.vu.nl
Reply-To: wallagh@cs.vu.nl ()
Organization: V.U. Informatica, Amsterdam, the Netherlands
Lines: 23

In article <887@bimacs.BITNET> grinberg@bimacs.UUCP (Dennis Grinberg) writes:
>
>>
>>But it is still not answered!!! Nearly everyone suggested that it is probably
>>not low-level formatted, and suggested using debug and the command g=c800:5
>>to intiate the ROM program. However, this hangs my machine big time, generating
>>1) Divide overflow, or 2)clear screen and hang, or 3) cold reboot, or any combo
>>of the above. Many people suggested that I should do this if my controller is
>>Western Digital. I'm guessing it's not, but how can I be sure? There are no
>>markings on my controller card, except for various IBM logos - does this mean
>>it's a (gasp) IBM controller? (No wonder nothing works).
>>

I have had the same problems  with my Olivetti M24 (= AT&T 6300) too.
The problem is not that the controller had no ROM (although there are
some controllers who don't have a ROM).
The problem was, that my PC was not able to USE that extended ROM.
 
The solution was simple: I had to use the program FMTDRIVE to 
low-level format my drive.
After that, I had no problems anymore.
 
				Serge Wallagh (wallagh@cs.vu.nl)