Re: 8x ZipChip and DHR: Anyone else having problems?

[supertimer@aol.com (Supertimer)]

phoenyx <quazar@dcnet2000.com> wrote:

>Obsbedia2 wrote:
>
>> <<
>> This problem may come from accessing the video memory to fast. In the case
of
>> DHR the timing had to be pretty precise. If I recall correctly, this was one
of
>> the problems the designers had during the R&D.
>>
>> Phoenyx
>>  >>
>>
>> Did they eventually solve it?  I have an update on my ZipChip utility disk
that
>> is suppose to allow it to work with the mouse.
>> Jay
>
>It's been awhile since I've used a ZIP. If I remember correctly, you had to
>use a control program to set different speeds for different slots. I don't
>think this completely solved the problems with 8 bit Zips. I'm not sure
>if this was ever completely resolved. Early accelerators solved this
>problem by using memory on the accelerator board and bypassing the
>memory on the motherboard. With the Zip this was not an option. Even
>with these problems, the Zip was a remarkable piece of hardware.

I repeat, something else in Jay's system must be tripping
up the Zip because I used a Zip 8Mhz while I had my IIe
and it worked great with mouse based double hires stuff.
In fact, I got the Zip expressly for using GEOS at an
acceptable speed.

I also used it with Publish-It! and Multiscribe IIe.  GEOS,
Publish-It!, and Multiscribe IIe are all mouse based DHR
programs.  All worked with the Zip.

The Zip uses 8k of cache RAM to run cached and
motherboard memory at different speeds.  For a
computer that mainly used two 64k banks (128k),
that was more than enough.  The Zip is designed to
accelerate up to 2MB of RAM in the aux slot,
meaning it'll attempt to cache segments in any of
those memory banks.  Beyond 2MB, it will not
cache data.