Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!rutgers!bellcore!tness7!texbell!sugar!ficc!uunet!mcvax!hp4nl!telmail!neabbs!richard
From: richard@neabbs.UUCP (RICHARD RONTELTAP)
Newsgroups: comp.unix.xenix
Subject: Re: SCO Xenix 2.3.1 with large ESDI drives
Message-ID: <44822@neabbs.UUCP>
Date: 15 Oct 88 19:02:09 GMT
Organization: NEABBS multi-line BBS +31-20-717666 (12x), Amsterdam, Holland
Lines: 36

> From: bill@cdin-1.UUCP (G. William Perrin)
> Has anyone managed to get Xenix up on a 338MB drive without lossing
60MB of
> the drive because SCO Xenix can't handle that large a drive?
 
Well, we didn't have any problem using the extra tracks on our
NBD (Newbury Data) 14380. That is a 380 MB (unformatted) drive,
used with a WD1005 ESDI controller.
 
We just put drive type 32 in the CMOS ram (a drive with 15
heads, but less cylinders and secs/track) and installed
Xenix/386 2.2.1 on the disk. During the install you get to the
dkinit program. There you can specify the exact parameters of
your drive. Ours looks like this:
 
        Disk Parameters         Values
        ---------------         ------
        1. Cylinders            1224
        2. Heads                15
        3. Write Reduce         0
        4. Write Precomp        65535
        5. Ecc                  0
        6. Control              8
        7. Landing Zone         1224
        8. Sectors/track        34
 
The drive itself can handle 36 secs/track, but I believe the
controller can't.
 
Success with your screamer box.
 
If you can't figure it out, send me one of your 25 Mhz cached
386 computers, I will galantly try it for you... (double -:)
 
Richard
(...!mcvax!neabbs!richard)