Path: utzoo!attcan!uunet!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!gvlv2!gvlv1!kleonard
From: kleonard@gvlv1.gvl.unisys.com (Ken Leonard)
Newsgroups: comp.sys.ibm.pc.misc
Subject: Re: Any dirt on Zeos?
Message-ID: <1022@gvlv2.GVL.Unisys.COM>
Date: 22 Oct 90 12:50:45 GMT
References: <4181@sactoh0.SAC.CA.US> <1327@lee.SEAS.UCLA.EDU>
Sender: news@gvlv2.GVL.Unisys.COM
Reply-To: kleonard@gvlv1.UUCP (Ken Leonard)
Organization: Unisys Defense Systems, NISD, Great Valley Laboratory
Lines: 37

In article ... ...  writes:
* Well, I have recently had an uncomplimentary experience with a Zeos machine.
...............................^^^^^^^^^^^^^^^^^^^^^^^^^^
huh
* ...
* but I found that file integrity was no good in turbo mode.  This was
* mostly cured by (low level? -- sorry about ambiguity, not my machine)
............................^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
oh
* ...
* In the course of this latter ordeal, I tried to run CHECKIT on the 
* machine and found that it crashed.  ...
* compatiblity, though the makers of CHECKIT recommend you calling them
* on any machine that says "Standard" for its system bios maker and I 
* did not do this.
..^^^^^^^^^^^^^^^
uh-huh
* Well, I guess I do not recommend Zeos.
........^^^^^^^
do tell
* ...
* on a larger initial charge for a better machine?  Well, whatever.
....................................................^^^^^^^^^^^^^^
* (One more thing, there was some kind of mixup on the initial shipping
.............................^^^^^^^^^^^^^^^^^^
*  so the machine went around twice -- I don't know whose fault it was, but
.......................................^^^^^^^^^^^^
*  care should be taken in the addresses I suppose.  I also don't know
.........................................^^^^^^^^^..........^^^^^^^^^^
*  how much the added knocks in transit are responsible for the final
* ...
----------
Gee, fella, thanks a _HEAP_ for such good, firm, well-substantiated,
self-confident information!
----------
regardz,
Ken