Newsgroups: comp.os.msdos.programmer Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!bronze!copper!rschmidt From: rschmidt@copper.ucs.indiana.edu (roy schmidt) Subject: Re: Legality of distributing Borland's BGI files Message-ID: <1991Apr30.230153.25261@bronze.ucs.indiana.edu> Summary: RTFM Keywords: Will=Way Sender: news@bronze.ucs.indiana.edu (USENET News System) Organization: Indiana University, Bloomington References: <500@ceco.ceco.com> <1991Apr14.062213.15711@uwasa.fi> Date: Tue, 30 Apr 91 23:01:53 GMT Lines: 22 In article <1991Apr14.062213.15711@uwasa.fi> ts@uwasa.fi (Timo Salmi) writes: >In article <500@ceco.ceco.com> sung@ceco.ceco.com (Sung Han) writes: > >>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. > >Did you also take a look at the inside cover of your manuals? There >is Borland's No-Nonsense License Statement in there which best >answers your query. > Also, if you read the manual a little farther than the front cover :-) you will see that there is a way to include the BGI drivers in your EXE files ... namely by using the BGI object code file and linking with your code. This is much more convenient for your customers! -- -------------------------------------------------------------------------- Roy Schmidt | #include Indiana University | /* They are _my_ thoughts, and you can't Graduate School of Business | have them, so there! */