Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!samsung!sdd.hp.com!elroy.jpl.nasa.gov!jarthur!nntp-server.caltech.edu!tybalt.caltech.edu!toddpw
From: toddpw@tybalt.caltech.edu (Todd P. Whitesel)
Newsgroups: comp.sys.apple2
Subject: Re: Super Serial Card drivers
Message-ID: <1990Aug9.010115.3970@laguna.ccsf.caltech.edu>
Date: 9 Aug 90 01:01:15 GMT
References: <HZ0$D}#@rpi.edu> <1990Aug8.195211.28266@laguna.ccsf.caltech.edu> <43780@apple.Apple.COM>
Sender: news@laguna.ccsf.caltech.edu
Organization: California Institute of Technology
Lines: 22

mattd@Apple.COM (Matt Deatherage) writes:

>However, please don't ANYONE write any kind of loaded serial port/card drivers
>without contacting DTS first.  We're trying to work out some specifications
>for such things so that all such drivers will work alike.  That way, if you
>have two programs that were written using two different serial drivers, they
>should both work with whatever driver you have installed.

Wouldn't think of it. That's why I'm waiting of the Class 1 manuals -- I expect
them to tell me what I can rely on and what I have to call DTS for.

>(Switching drivers requires activating one, deactivating the other and rebooting
>the system.  We're trying to avoid having to go through this just to switch
>programs that were written with different drivers.)

Could you give an example of that?

You seem to be implying that the system can only recognize one driver per
peripheral; if that is so then how is Appletalk/Printer/Modem handled?

Todd Whitesel
toddpw @ tybalt.caltech.edu