Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!ceres.physics.uiowa.edu!news.iastate.edu!cs352a41 Newsgroups: comp.os.msdos.programmer Subject: Re: Legality of distributing Borland's BGI files Message-ID: From: cs352a41@cs.iastate.edu (Adam Goldberg) Date: 13 Apr 91 15:55:50 GMT Sender: news@news.iastate.edu (USENET News System) References: <500@ceco.ceco.com> Organization: Iowa State University, Ames IA Lines: 28 sung@ceco.ceco.com (Sung Han) writes: >This is probably a stupid FAQ, but I haven't seen it addressed, so here goes.. >If I write a program that uses Borland's graphics BGI interface, and decide to >distribute it, can I also ship out the corresponding runtime BGI file (e.g., >the 'egavga.bgi' file)? I searched the manuals for restrictions on the use and >distribution of the runtime library, but couldn't find anything. Quoting the 'Borland's No-Nonsense License Statement!': "Programs that you write and compile using the Turbo C language compiler may be used, given away or sold without additional license or fees. You are not required to indicate that your programs were developed using Turbo C or that they contain source code provided with Borland language products (toolboxes)." I'm not sure whether this directly addresses the BGI files, but it sure seems like if you link the BGI file into the executable file by using things like registerbgidriver(), then it'll be legal (and nicer to the user). If you're still unsure, mail to sidney@borland.com (sorry Sidney if you don't want to receive mail of this sort) and ask him. -- +-----------------------------------------------------------------------------+ ! Adam Goldberg ! * ! "It's simple! Even a PASCAL ! ! cs352a41@cs.iastate.edu ! * ! programmer could do it!" ! +-----------------------------------------------------------------------------+