Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!hellgate.utah.edu!caen!zaphod.mps.ohio-state.edu!magnus.acs.ohio-state.edu!csn!kessner!david From: david@kessner.denver.co.us (David Kessner) Newsgroups: comp.sys.ibm.pc.hardware Subject: Re: DTK computers Message-ID: <1991Mar13.200229.6284@kessner.denver.co.us> Date: 13 Mar 91 20:02:29 GMT References: <1991Mar11.103429.1354@infoac.rmi.de> <1991Mar12.102433.1590@kessner.denver.co.us> <1991Mar13.151726.4816@javelin.es.com> Reply-To: david@kessner.denver.co.us (David D. Kessner) Organization: Kessner, Inc Lines: 46 In article <1991Mar13.151726.4816@javelin.es.com> bgeer%javelin@dsd.es.com writes: >david@kessner.denver.co.us (David Kessner) writes: >>I also like DTK very much-- but I have been into computers long enough to >>decipher their badly translated Tiwaneese. I always laugh about thier >>error message, "Parity Error But Segment Dosent Found." (I've been working >>with DTK's long ehough to cause my share of these.) > >I'm intrigued by your phrase "...cause my share of these" wrt the >error message -- does the message indicate a real parity error was >encountered, or is there some other condition that can cause it to >display? I saw this error often when running my plain-jane Win3 & >SmartDrive installation in 386Enh mode on a DTK 386DX-20 w/ 5Megs. >Power-up ram test thinks all 5 megs are ok, tho I doubt the power-up >test is very thorough. I deleted SmartDrive & haven't seen it since. > >Would appreciate your posting any info you might have...Thanks. >-- ><> Bob `Bear' Geer <> bgeer@javelin.sim.es.com <> Well, two things here: I have caused my share of parity errors buy inserting a RAM chips in wrong, and various other things... (If you play with enough computers you do these sort of things from time to time.) Also, the 32-bit ram board used in the DTK 306/20 has had a "revision" done to it quite a long time ago (a year or more, I think). You can tell, because the model is ???-301, rather than ???-300 (I forgot the letters). The bug in the old board would cause problems when running some 386 software. When intalling Novell Netware 386, you'd have to keep the thing in "non-turbo" mode until it was finished "booting" then you could hit afterburner. When the newer ram board was installed, all worked fine. Also, I have found many other instances where if the memory on a computer is borderline, running 386 software will push it over. A system that may run MS-DOS fine will FAIL when DesqView/QEMM, Windows(enhanced), Netware 386, etc. Often, this is a better test of a system than other diagnostic programs. This is true of any system, not just DTK's. I also assume that you are using 80ns RAM chips in your DTK 386/20? - David K -- David Kessner - david@kessner.denver.co.us | do { 1135 Fairfax, Denver CO 80220 (303) 377-1801 (p.m.) | . . . If you cant flame MS-DOS, who can you flame? | } while( jones);