Path: utzoo!attcan!uunet!know!zaphod.mps.ohio-state.edu!mips!decwrl!ucbvax!agate!shelby!msi-s0.msi.umn.edu!cs.umn.edu!cybrspc!roy
From: roy%cybrspc@cs.umn.edu (Roy M. Silvernail)
Newsgroups: comp.sys.ibm.pc.hardware
Subject: Re: ROM BIOS
Message-ID: <4LFiP1w163w@cybrspc>
Date: 14 Sep 90 22:42:50 GMT
References: <1990Sep14.181312.10067@NCoast.ORG>
Organization: Villa CyberSpace, Minneapolis, MN
Lines: 19

tim@NCoast.ORG (Tim Stradtman) writes:

> We haven't had compatibility problems with the DTK, however, occasionally,
> we get an error message: "PARITY ERROR BUT SEGMENT DOESN'T FOUND"
> This seems to happen only when running in Turbo (10Mhz) mode, and only
> on rare (thankfully) occasions.  Both of our DTK's have done it, although
> they pass every memory test program we have been able to get our hands on.
> Could it possibly be cosmic radiation??? :-)

My ex-business partner had a DTK AT that would do that on occasion. He
was running a Galacticomm BBS on the machine, and had a Maxit card in
the machine. The best we were able to figure, the Maxit card was
throwing an occasional parity error, but the BIOS couldn't find it due
to the mapping scheme Maxit uses. If you have some extra memory
installed somewhere, that could be your problem.
--
Roy M. Silvernail |+|  roy%cybrspc@cs.umn.edu  |+| #define opinions ALL_MINE;
main(){float x=1;x=x/50;printf("It's only $%.2f, but it's my $%.2f!\n",x,x);}
"This is cyberspace." -- Peter da Silva  :--:  "...and I like it here!" -- me