Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!unisoft!gethen!bdt!david
From: david@bdt.UUCP (David Beckemeyer)
Newsgroups: comp.sys.atari.st
Subject: Re: alternative operating systems (was Re: Multi-Bashing)
Message-ID: <180@bdt.UUCP>
Date: 17 Mar 88 03:21:54 GMT
References: <8803060401.AA21207@ucbvax.Berkeley.EDU> <419@mks.UUCP> <301@wsccs.UUCP>
Reply-To: david@bdt.UUCP (David Beckemeyer)
Organization: Beckemeyer Development Tools, Oakland, CA
Lines: 22

In article <301@wsccs.UUCP> wes@wsccs.UUCP (Barnacle Wes) writes:
>The different pieces of the kernel communicate with each other via message
>passing.  The Minix file system is basically just a task running at the
>kernel level that accepts and handles requests to read/write disk-type
>devices.  With this in mind, it should be pretty straight forward to 
>develop a network for Minix using the MIDI ports.  BTW, the MIDI hardware
>on the ST can be driven at 500 Kbps without modification.  I don't know
>what the interrupt overhead would be at that kind of speed, though :-).


I like the idea of the above, but why do I remember that the MIDI
port was hardwired to a timer that gives you 31.5 Kbit/sec (or whatever
MIDI is, I forget exactly).

And it as also been my experience that MIDI cannot even rrun reliably
contiuously at 31.5 Kbps becuase the ISP runs at low level (I think 1),
below every thing else.  So I doubt that it would be anywhere near
reliable enough at 500 kps!
-- 
David Beckemeyer			| "To understand ranch lingo all yuh
Beckemeyer Development Tools		| have to do is to know in advance what
478 Santa Clara Ave, Oakland, CA 94610	| the other feller means an' then pay
UUCP: ...!ihnp4!hoptoad!bdt!david 	| no attention to what he says"