*BSD News Article 10421


Return to BSD News archive

Received: by minnie.vk1xwt.ampr.org with NNTP
	id AA88 ; Thu, 28 Jan 93 08:00:25 EST
Xref: sserve comp.unix.bsd:10474 comp.sys.ibm.pc.hardware:42424
Newsgroups: comp.unix.bsd,comp.sys.ibm.pc.hardware
Path: sserve!manuel.anu.edu.au!munnari.oz.au!spool.mu.edu!caen!saimiri.primate.wisc.edu!ames!haven.umd.edu!wam.umd.edu!tictac
From: tictac@wam.umd.edu (Shake it to the Left)
Subject: Vesa Local Bus and Companies (please read)
Message-ID: <1993Jan27.050642.15880@wam.umd.edu>
Sender: usenet@wam.umd.edu (USENET News system)
Nntp-Posting-Host: rac2.wam.umd.edu
Organization: University of Maryland, College Park
References: <1993Jan26.162704.13442@usasoc.soc.mil> <1993Jan26.220906.26671@netcom.com> <1993Jan27.044856.15406@wam.umd.edu>
Date: Wed, 27 Jan 1993 05:06:42 GMT
Lines: 33

Ok, now I am very confused.  I bought a machine from
Zenon which is ok except for the fact that I cannot
get the SB to work in it (its a 50 mHz machine), and
I have Memory Parity Errors.  Now then, I was flipping
through the computer shopper and my eyes came to rest
on 'The Hard Edge' which talks about technical information.

On page 780 of the January 1993 edition it says that
VESA's specification for its local bus interface 
defines a bus speed no greater than 40mHz.  
Then WHY does Zenon sell 486/DX50's claming to have
3 VLB slots in them?  I would very much appreciate
it if someone could quickly take the time to mail me
sorting out the details of VESA's VLB specifications,
and why Zenon can be justified in advertising a 486/DX50
(not Dx2 50) with 3 local bus slots.  I have one sitting
on my desk, hehe, and Im beginning to think...... hmm,
maybe THIS is why I'm having some of the problems I
am experiencing (which include the strange 'Memory
Parity Error').

Basically, if you could email me explaining
a) VESAs VLB specifications and limitations
b) why Zenon is advertising a DX50 with 3
    VLB slots when VESA supposedly said the
    limit (bus speed) is 40 mHz
c) what is the cause, and the solution for
   a Memory Parity Error.

Please send comments, suggestions, or thoughts to:
tictac@wam.umd.edu