Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!rpi!crdgw1!sixhub!davidsen
From: davidsen@sixhub.UUCP (Wm E. Davidsen Jr)
Newsgroups: comp.unix.sysv386
Subject: Re: UHC Migration Offer
Message-ID: <2678@sixhub.UUCP>
Date: 19 Dec 90 04:07:34 GMT
References: <460@pallas.athenanet.com> <786@dptspd.sat.datapoint.com> <22@mport.COM> <51197@bigtex.cactus.org>
Reply-To: davidsen@sixhub.UUCP (bill davidsen)
Organization: *IX Public Access UNIX, Schenectady NY
Lines: 29

In article <51197@bigtex.cactus.org> james@bigtex.cactus.org (James Van Artsdalen) writes:

| The current rumor is that it's only SCSI controllers, maybe adaptec,
| maybe the device driver, that doesn't work right if the 486 runs at
| 33MHz.  I have not tested this configuration myself.
| 
| I know for fact that at least our SysVr4 works at 33MHz just fine with
| ESDI - I run my work machine at that speed most of the time.

  I expect to know later this week. We're getting SCSI for a 33MHz
system (Dell 433E) and will shake it out in several disk configurations.
I'm moving this off an SX, but it's been on a 486-25 for a while too.
The system has never, ever, paniced. Even while loading X from tape
while building a kernel and running a DOS process with direct access to
its i/o ports for a scanner.

  We're going to try 766MB ESDI with UltraStor, 766MB ESDI with CompuAdd
cache controller, and Adaptek and 400MB SCSI. In all configurations it
will be tested with NFS in place, running a "magic make" of 2000 modules
on multiple 386's and the 486, with the 386s NFS mounting the filespace.
If double digit load averages will break it, we'll know.

  If it breaks I'll call the Dell guys at home Christmas eve and tell
them... I'm kidding James!
-- 
bill davidsen - davidsen@sixhub.uucp (uunet!crdgw1!sixhub!davidsen)
    sysop *IX BBS and Public Access UNIX
    moderator of comp.binaries.ibm.pc and 80386 mailing list
"Stupidity, like virtue, is its own reward" -me