*BSD News Article 4481


Return to BSD News archive

Path: sserve!manuel!munnari.oz.au!spool.mu.edu!uunet!haven.umd.edu!darwin.sura.net!mlb.semi.harris.com!uflorida!sinkhole.unf.edu!shite
From: shite@sinkhole.unf.edu (Stephen Hite)
Newsgroups: comp.unix.bsd
Subject: Re: DTK Motherboards
Message-ID: <1992Sep3.015820.21306@sinkhole.unf.edu>
Date: 3 Sep 92 01:58:20 GMT
References: <1992Aug24.211748.22040@mksol.dseg.ti.com> <3429@ra.nrl.navy.mil>
Organization: University of North Florida, Jacksonville
Lines: 31

In article <3429@ra.nrl.navy.mil> deal@hightop.nrl.navy.mil (Richard Deal) writes:
>In article <1992Aug24.211748.22040@mksol.dseg.ti.com> kylscott@mksol.dseg.ti.com (kyl w scott) writes:
>>Hi. I am looking at buying a DTK 486-33/50 (haven't decided which yet).
>>I remember someone saying that the DTK boards suffered from 
>>"spurious interrupts" which DOS didn't care about, but UNIX
>>hated.  Does anyone have any info on this?  Is anyone running
>>unix or xenix on a DTK systems?  Is there a better 486 board
>>to buy?
>
>I don't know about 386BSD on DTK's but I used to support several DTK 
>machines running SCO and Interactive UNIX.  The DTK's were very nice
>machines I particullarly liked the designe and layout of them.  We had
>486/33 towers.  I also preffered Interactive to SCO, SCO was very difficult
>to install and maintain and often had random crash fits.  The SCO box's 
>had problems with the 150 meg Archive tape drive hanging the system.  The 
>Interactive machine rarly crashed and was up for months.  
>16 MRam, 3.5, 4.25, 150 Meg Archive tapes, 650 Meg SCSI Hard disks, 
>(up to 4) Chase 16 port serial boards, mono display, Keridge BASIC interpriter.
>We used the machines to replace WANG equipment.  The Keridge interpriter 


   Eric S. Raymond in his hardware guide posts to the net says to
avoid the DTK motherboards like the plague for use as a 386/486 Unix box.
Hmm, it's interesting to hear someone with *real* experience and 
obviously several versions of the DTK boards have no complaints. ;-)
Perhaps the company has fixed some problems they used to have?


P.S. Don't ask me for Eric's hardware guide because I don't have it.
     I *think* he posts it here and in comp.unix.sysv386 from time to
     time.