[Coco] Any resolution to patching a Multipack for Coco 3?
mmarlett at isd.net
Sat May 8 07:02:05 EDT 2004
At 05:56 AM 5/8/2004 -0500, you wrote:
I also forgot to add if your CoCo never addresses the conflict range then
the conflict will never occur.....Kind of like waiting for an accident to
occur rather than prevent one from EVER happening........
>At 10:23 PM 5/6/2004 -0700, you wrote:
>No real two schools about it. If you want it done right, do the patch. The
>problem is that in the non modified packs, the address range of the MPI
>ghosted the GIME. Two devices on the bus at the same time is called bus
>conflict, not a desirable thing. The PAL updates for the 26-3024 are
>available at Cloud-9 and I do the other satellite updates as well but that
>is a Time and Material charge and I charge $25 plus s/h. Paul Barton has a
>web page up on how to do the modification if you want to do it yourself on
>This simple test will detect if any Mulitpak has been upgraded
>to work with a CoCo3. From DECB prompt enter the following:
>If 126 is returned then the multipak has been upgraded. If
>it returns 255 then it has NOT been upgraded.
>The test above seems to work in the models I have upgraded......
>>I was reading through my old Rainbows the other day as I was trying to get
>>my floppy controller working with my Multipack on my Coco 3.
>>Apparently, there were 2 schools of thought with patching the newer, white
>>Multipacks with a Coco 3, with some people saying it had to be done, and
>>some people saying it did not need to be done.
>>The group that said it needed to be done suggested that slow degeneration of
>>the computer (the GIME chip?) was possible if you used an unpatched
>>Now that it's been 10+ years, has anyone experienced any faults? Are the
>>parts still available to patch the 26-3124s? Does this need to be done?
>>Coco mailing list
>>Coco at maltedmedia.com
>Coco mailing list
>Coco at maltedmedia.com
More information about the Coco