wayned@wddami.spoami.com (Wayne Diener) (11/23/90)
I picked up an A2232 card last week as a first step toward helping me automate switching between about seven different serial channels. Talking to all the different devices, individually, from the keyboard is no problem when I'm sitting here controlling everything myself. Everything seems to work ok. So, now on to the next stage. I'm building some development hardware for a comp sci class next quarter and it will normally be sitting down here in my basement. I need to allow the rest of the class to call in to my modem and get "switched through" to either of two serial ports on the development hardware, or to switch through to my AT (the development software is presently capable of running only in a messy-dos environment and I don't have a bridgeboard) when they need to compile. Some of them don't have pc compatibles, so they can't run the software at home. After the compile/assembly they then need to be able to be able to transfer the binary files ( S records actually ) to the development hardware. If this isn't enough, the Amiga <-> AT link normally runs at 19.2K, the development hardware runs at 9600, and my modem runs at 2400/1200 and I have a midi keyboard that I'd like to keep hooked up. My Amiga is running 24 hrs a day, with getty set up to accept a remote login for my uucp news feed, so I should be able to use it to accept the incoming calls by giving it another password, but how do I : 1) Open multiple serial channels at once. 2) Make sure the incoming callers can't access the rest of the Amiga. 3) Buffer the various channels (if necessary). 4) Run it all in the background. 5) Maintain my multi-tasking. And, as long as I'm wishing, be able to route the AT through to the modem at its request (assuming the modem isn't busy). I'm running 1.3.2 (but can anticipate 2.0?) on a 2500/30 and have Manx 3.6 to work with. Any and all suggestions gratefully accepted.