Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!utgpu!water!watmath!clyde!rutgers!ames!sdcsvax!ucbvax!COGSCI.BERKELEY.EDU!bryce From: bryce@COGSCI.BERKELEY.EDU.UUCP Newsgroups: comp.sys.amiga Subject: Re: shared libraries, a call for CATS to come to the rescue! Message-ID: <8706110603.AA27095@cogsci.berkeley.edu> Date: Thu, 11-Jun-87 02:03:25 EDT Article-I.D.: cogsci.8706110603.AA27095 Posted: Thu Jun 11 02:03:25 1987 Date-Received: Sat, 13-Jun-87 07:45:27 EDT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 39 In article <10334@decwrl> jmsynge@sqm.dec.com (James M Synge, DTN 381-1545) > >Imagine two libraries named "Music.library". > >I would suggest that Commodore perform the same registration service with >library names as they've done with Zorro id's and IFF hunk names. I second the motion! All that is needed is a simple set-up at C-A. You would simply send a SASE to the mail drop at 1200 Wilson Drive with your desired name, and what you are using it for. The letter would come back with either a yes or a unique name. (eg. Music3.library) Libraries, IFF types, public ports, DOS ID's. input.device handler names, device names, DOS handler names, fonts, resource names, resident tags, and any classes of conflictable names that I forgot. ("DOS " "NDOS" and "KICK" are taken, but I will stake claim to "DOS2" or "DOS+") There are plenty of names to go around, so everyone would be encouraged to participate. PD and commercial. Keep it SIMPLE and people will use it. Make provisions for un-registering a name and also EMAIL (Bix, USENET, etc.). "Advertise" the service well (AmigaMail, paper in new RKM's, and EMAIL to all the services. Describe the procedure and list types of registration). This record will be permanent, provided someone a C-A keeps backup tapes :-)! Official comment from CATS/anyone else encouraged. ------------- Ack! (NAK,EOT,SOH) |\ /| . {o O} . bryce@cogsci.berkeley.EDU -or- ucbvax!cogsci!bryce ( " ) U Single tasking? Just say *NO!*