Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!seismo!gatech!bloom-beacon!think!ames!lll-tis!lll-lcc!ptsfa!ihnp4!inuxc!iuvax!pur-ee!newton.physics.purdue.edu!pur-phy!mrstve!mdbs!mike From: mike@mdbs.UUCP (Mike Gagle) Newsgroups: comp.sys.ibm.pc Subject: MSC 5.0 License Agreement Message-ID: <407@mdbs.UUCP> Date: Fri, 17-Jul-87 10:19:54 EDT Article-I.D.: mdbs.407 Posted: Fri Jul 17 10:19:54 1987 Date-Received: Sun, 19-Jul-87 19:48:46 EDT Organization: Micro Data Base Systems, Inc., Lafayette Indiana Lines: 52 >From: dennisti@microsoft@larry >To: LOCAL!mike >Subject: Licensing Crud >Date: Thu Jul 16 10:56:40 1987 > >Mike: I think this will clarify the confusion regarding the runtimes >for C. Please pass it on to the originator of the complaint so we can >stop the misunderstanding before it goes further. Let me know if you >need additional clarification. >Thanks, Dennis > >---------------------------------------------------------------- >>From: jnj@mibte.UUCP (Jim Jackson) >>Newsgroups: comp.sys.ibm.pc,comp.lang.c >>Subject: MSC 5.0 License Agreement >>Organization: Michigan Bell Telephone Company > >> Does anyone know if the 5.0 license agreement will be the same >>as 4.0? That is, does Microsoft demand that you display THEIR company >>name on the screen everytime YOUR program is run? . . . >>I've talked to several people at microsoft and can't convince them >>that this practice is not in their best interest. >---------------------------------------------------------------- > >A user has the right to distribute their .exe file. > >The paragraph that he's referring to is #2. Distribution of Runtime Modules. >At the end of this paragraph it explains what "Runtime Modules" are: > "The runtime modules are limited to runtime files, install files, and > ISAM and REBUILD files." > >--- These files are referring to products like BASIC and COBOL, where > we provide Runtime modules and in order to run your .exe, you > need to have the Runtime modules on the disk that comes with the > compiler. > And you need to have a Microsoft Copyright notice with these. > >In the case of C, the user creates a stand-alone program (the portions > of the runtime module are linked in). > >People should not distribute any portions of the Microsoft C compiler > or runtime libraries (slibc.lib,...) > >Hope this helps > I personally interpret this response as meaning that we are not required to propogate Microsoft's copyright notice for executables compiled with and utilizing libraries from the Microsoft C compiler. We sure do not intend to do so. Standard disclaimers apply. If Microsoft goes after you, you're on your own!