Path: utzoo!mnetor!uunet!husc6!psuvax1!vu-vlsi!cbmvax!daveh From: daveh@cbmvax.UUCP (Dave Haynie) Newsgroups: comp.sys.amiga Subject: Re: One more modem Please! Message-ID: <2992@cbmvax.UUCP> Date: 21 Dec 87 23:25:45 GMT References: <6327@jade.BERKELEY.EDU> Organization: Commodore Technology, West Chester, PA Lines: 30 in article <6327@jade.BERKELEY.EDU>, spencer@eris.BERKELEY.EDU (Randy Spencer) says: > Keywords: Help me! > > In article <4300@garfield.UUCP> joseph@garfield.UUCP (Joseph Dawson) writes: > > How do you get software designers to acknowledge your board, in either > of the above situations the software designer has to either allow the > user to open the serial.device with a specific unit number, or has to > allow you to open a named device (like I want to open the parallel.device > and run a terminal program between two Amigas!). Or do we send the > programmers to talk to Dos Devices and open SER2:? I think the best solution for supporting alternate devices is to pass the DOS name to the program, and then let it look up the specifics on that name if it need Exec level access. Obviously you can't run a 9600 or faster serial port very nicely just by opening "SER2:" or something like that, but you can certainly pass the DOS name and let the program find out that SER2: is actually attached to "serial1.device", unit 0, or "serial.device", unit 1, or whatever. The DOS namespace is a level of complete abstration, while the Exec device namespace isn't, so this feature should and can be exploited without any disadvantages. > Randy Spencer P.O. Box 4542 Berkeley CA 94704 (415)222-7595 > spencer@mica.berkeley.edu I N F I N I T Y BBS: (415)222-9416 > ..ucbvax!mica!spencer s o f t w a r e AAA-WH1M > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- -- Dave Haynie Commodore-Amiga Usenet: {ihnp4|uunet|rutgers}!cbmvax!daveh "The B2000 Guy" PLINK : D-DAVE H BIX : hazy "I can't relax, 'cause I'm a Boinger!"