Re: Handic VIC-Switch

From: Mia Magnusson <mia_at_plea.se>
Date: Wed, 1 Nov 2017 13:19:12 +0100
Message-ID: <20171101131912.0000615c@plea.se>
Den Wed, 1 Nov 2017 12:08:15 +0000 skrev smf <smf@null.net>:
> On 01/11/2017 10:59, Mia Magnusson wrote:
> 
> > Maybe some kind of matrix function would be nice, like 2 or more
> > ports for disks and printers. But that would mean twice as many
> > 4051's and perhaps some interesting auto logic to assign certain
> > ports to certain computers. Feature creep deluxe++.
> It sounds like you really want an intelligent switch with an embedded 
> cpu with enough i/o pins to allow any computer to talk to any device.
> It could detect which port the devices were on and then make that
> port unavailable as soon as a computer starts talking to it. You
> could probably make it detect a fast loader that used ATN and isolate
> it from the other devices and computers.

yes, or maybe just some passive switch would do, like rewire one of
those 4-1 25-pin d-sub switches. :)

> > What I would like to have though, which is super easy to implement,
> > is front panel switches to select device ID of attached disk drives.
> > Although both my 1571 and 1541-ii have dip switches it would be
> > nice to not have to use those. (AFAIK you want to have 1571 as
> > device 8 for C128 CP/M mode and C128 in general, and you want to
> > have 1541 as 8 for some games and maybe demos for C64).
> 
> That wouldn't be possible unless you had an intelligent switch,
> because you would need to rewrite the bits in the data stream or send
> a memory write to the device.

I were thinking about just a three wire cable to each drive connected
in parallell with the dip switches. Just to use the "vic switch 2.0"
case as a place for better switches, as I don't want to modify the case
of the drives. Perhaps it would be both easier and better to use some
separate case for this though.

-- 
(\_/) Copy the bunny to your mails to help
(O.o) him achieve world domination.
(> <) Come join the dark side.
/_|_\ We have cookies.

       Message was sent through the cbm-hackers mailing list
Received on 2017-11-01 13:00:02

Archive generated by hypermail 2.2.0.