Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!lavaca.uh.edu!menudo.uh.edu!sugar!peter From: peter@sugar.hackercorp.com (Peter da Silva) Newsgroups: comp.sys.amiga.tech Subject: Re: Multi serial/parallel ports Message-ID: <6873@sugar.hackercorp.com> Date: 23 Oct 90 12:11:56 GMT References: <52508.656318355@atronx.UUCP> <2521@ucqais.uc.edu> Reply-To: peter@sugar.hackercorp.com (Peter da Silva) Organization: Sugar Land Unix - Houston Lines: 29 In article <2521@ucqais.uc.edu> blubaugh@ucqais.uc.edu (Dr. Blubaugh) writes: > mountlist or worry about the slot that a card exists in. When I access > the serial.device asking for a particular unit, I want EXEC or a > serial.device shell to figure out and direct all subsequent device/unit > IO to the relevent resident code. No you don't. You want to specify a device name and port number, just like you do for the regular serial.device. This is NOT a commodore problem... it's the fault of the folks writing programs that talk to the serial port. > I just wish I had more serial > and parallel ports that are software accessable thru similar mechanisms > that exist now ( e.g. SER2: , serial.device unit 2 ) Aren't they? If any manufacturer's product isn't available as xxxx.device unit then they should be shot. > Software Developers be addressing this instead?? If third parties could > agree upon a mechanism can we be sure that Commodore won't take a NIH > (not invented here) approach much as they did with ARP?? I don't know about Commodore, but I refuse to use ARP because it violates all sorts of interface standards Commodore had set out (mainly, wildcards... but I installed it and then had to keep backing out because the ARP versions of commands broke scripts). If ARP took an NIH approach to Commodore, is it any wonder Commodore reciprocated? -- Peter da Silva. `-_-' .