Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ncar!ames!ucsd!ucsbcsl!hbo@nobbs.ucsb.edu
From: hbo@nobbs.ucsb.edu
Newsgroups: comp.sys.amiga
Subject: Re: Serial Ports
Message-ID: <1187@hub.ucsb.edu>
Date: 8 Feb 89 03:31:25 GMT
Sender: news@hub.ucsb.edu
Organization: UC, Santa Barbara. Physics Computer Services
Lines: 61

In article <466@madnix.UUCP>, perry@madnix.UUCP (Perry Kivolowitz) writes...

>I can respond to your points in two ways:
> 
>1. Of course we will supply driver software which will conform to the
>   1.4 standards when 1.4 comes out (in oh, say, n years). Until then
>   ASDG  can  provide  multiple serial  support that  works with your
>   existing software. After that point, ASDG will provide the upgrade
>   needed for conformity.

   "Good answer," as they used to say on Family Fued. 8-)

>2. What makes you  think ASDG  is not involved in the actual creation
>   of the new standards anyway?  And,  what  makes you think that our
>   present support is not already compatible?
>

     The fact that the description you posted of your approach to multiple 
serial ports was at variance with the description of Commodore's scheme posted 
by Bryce Nesbitt. Here is how Bryce describes how to get old applications
to use the new driver:

>    o  Old applications that ask for the serial port will be given        
>       the "default" port.  Using the Preferences tool, the user will     
>       be able to set the default to any valid port.                      

 Now here is your explanation of how to do the same thing with siosbx.device:

>1. Find your favorite compiled program making use of serial.device.         
>2. Load this file into CEDPro. Do a search and replace of serial.device with
>   siosbx.device                                                            
>3. Enjoy.                                                                   
>                                                                            
>Of course, the short form limits you to using port 0 unless you are good at 
>locating a push of 0 in the OpenDevice call.                                

   Which approach do you prefer, really? "Mine," I hear you say, "it works 
now." Good answer again, but don't you sense the potential for chaos in all 
this? It's not just ASDG that's working on their own drivers to handle multiple
serial ports. You've said yourself you aren't going after the consumer market.
Who's serial driver will win the popularity contest, FUBAR inc's? How will you
coexist with their driver? How will they coexist with yours? FUBAR indeed!


>Amazing. If a message on Usenet from a CBM representative is enough to 
>sour a market,  there's  absolutely no  reason  for any third party to 
>participate. 
> 
>I hope this point is well taken.

   The potential for chaos would exist whether or not Commodore posted a 
description of their contribution to it. The problem is not the dissemination 
of information on usenet, but the late introduction of a standard by Commodore. 
CBM should not concentrate on being more circumspect in their postings, they 
should try to be more timely in their product introductions.

--
Howard Owen, Computer Systems Manager           internet: hbo@nobbs.ucsb.edu
Physics Computer Services                       BITNET: HBO@SBITP.BITNET
University of California, Santa Barbara         HEPNET/SPAN:   SBPHY::HBO
"I am not a pay TV service!"                    805-961-8366 (work)