Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!rutgers!att!att!fang!alfred!tous!tarpit!bilver!bill
From: bill@bilver.uucp (Bill Vermillion)
Newsgroups: comp.unix.sysv386
Subject: Re: Help with ESIX ESDI No-translation Mode
Message-ID: <1990Dec21.055405.1053@bilver.uucp>
Date: 21 Dec 90 05:54:05 GMT
References: <122@bsts00.UUCP> <94408976@bfmny0.BFM.COM>
Distribution: usa
Organization: W. J. Vermillion - Winter Park, FL
Lines: 26

In article <94408976@bfmny0.BFM.COM> tneff@bfmny0.BFM.COM (Tom Neff) writes:
>In article <122@bsts00.UUCP> gatech!sbmsg1!rlb@bsts00.UUCP (Ronald (Ron) L. Bolin) writes:
>>Has anyone out there installed a Maxtor ESDI 4380E on ESIX with a WD1007SE2
>>controller without using translation mode in the controller BIOS.

>I have been around and around and around this every way from Sunday.  I
>have tried every configuration known to Elvis.  I have been tenacious
>and devious and hackerly about it.  And I tell you, give up and take
>translation mode.  It should NOT impact performance.

I have been running in translation mode from day one.   The reason it was
put there is so that you can run bigger drives and not give anything up.
Why do you feel you have to run it WITHOUT translation.

At the 1023x16x53 (or is it 52 - I used the spare sector scheme for bad
blocks), you come out with 867504 sectors. Divide back by 16 and 32 and you
come out with the number of tracks the drive originally had.  You aren't
losing anything.

Am I missing something here?   Why not use the translation?



-- 
Bill Vermillion - UUCP: uunet!tarpit!bilver!bill
                      : bill@bilver.UUCP