Message-Id: <199911260829.DAA15959@glitch.crosswinds.net>
From: "Kalum Somaratna aka Grendel" <kalum AT crosswinds DOT net>
To: djgpp AT delorie DOT com
Date: Fri, 26 Nov 1999 15:27:34 +0600
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: fprintf() and using under graphic modes
In-reply-to: <81khu1$jhu$3@portraits.wsisiz.edu.pl>
X-mailer: Pegasus Mail for Win32 (v3.12)
Reply-To: djgpp AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

On 25 Nov 99, at 19:35, Chaos wrote:

> But hey, can I redistribute my soft with SciTech's Univbe without any
> copyrights law consequences? Is it free for spreading?

Hi Chaos,
	SciTech used to provide a linkable version of UNIVBE so that 
when your program starts it runs UNIVBE.  But you might have to 
purchase univbe from scitech for that.

I got my non expiring copy of univbe from a game called Settlers2.
How this happenned was that Scitech releases fully functional trial 
versions of UNIVBE (SDD) and AFAIK there are no restrictions for 
distributing the trial version. 
However the game company has also added a program 
(CRACK.EXE) to crack UNIVBE and fake registering it. So after 
getting the game and running crack.exe on univbe I got a fully 
functional version of UNIVBE which gave me VBE2.0 support and 
I've been using it ever since.

So IMHO you should be able to bundle the trial univbe version and 
a program to crack it (there are sooo many on the www) with your 
game without any copyright infringment  or illegal things occuring. 

By all means please check up on what i've said from experts about 
such matters. Maybe there are some legal gurus on this list who 
would like to comment?.


>BTW. Is there, in DJGPP, a way to get assembler source of C >source. I searched but with no success. In Borland 3.1 -S switch >did that.

Please have a look at section 8.20 the DJGPP FAQ as it has info 
about  the above problem. But for your quick reference here is a 
small part of it listed below

*A*: Use the `-S' (note: *capital* S) switch to GCC, and it will emit 
the
assembly code to a file with a `.s' extension.  For example, the 
following
command:

       gcc -O2 -S -c foo.c

will leave the generated assembly code on the file `foo.s'.

If you want to see the C code together with the assembly it was 
converted to,
use a command line like this:

      gcc -c -Wa,-a,-ad [other GCC options] foo.c > foo.lst

which will output the combined C/assembly listing to the file 
`foo.lst'.

Hope this Help!
Grendel