Xref: utzoo alt.msdos.programmer:2384 comp.os.msdos.programmer:3045
Path: utzoo!utgpu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!think.com!mintaka!bloom-beacon!eru!hagbard!sunic!news.funet.fi!hydra!cc.helsinki.fi!teittinen
From: teittinen@cc.helsinki.fi (Marko Teittinen)
Newsgroups: alt.msdos.programmer,comp.os.msdos.programmer
Subject: Re: Borland BGI Limitations...
Message-ID: <1991Jan30.001740.4715@cc.helsinki.fi>
Date: 30 Jan 91 00:17:40 GMT
References: <91028.164531ACPS2924@Ryerson.Ca>
Organization: University of Helsinki
Lines: 20

In article <91028.164531ACPS2924@Ryerson.Ca>, ACPS2924@Ryerson.Ca writes:
> This is my problem,
> in using the Borland BGI interface in TurboC++ i find that
> the functions {imagesize(),getimage(),putimage() } all seem to work
> for images that are <64k.  This poses a problem in anything better
> than cga.  Imagesize returns only an unsigned int,(16 bits).
> This works fine if you use malloc() and not farmalloc().
> Has anyone gotten around this limitation?

There is a very simple workaround for this limitation. You just divide
the area into such pieces that each of the pieces takes less than 64 kB
of memory. Using VGA high resolution mode, you shouldn't need more than
4 pieces. If you divide the area vertically and place the pieces on the
screen from top to bottom, there won't be even very much difference in
the way the image is drawn.

-- 
E-Mail: teittinen@finuh.bitnet               ! "Studying is the only way
        teittinen@cc.helsinki.fi             !  to do nothing without
Marko Teittinen, student of computer science !  anyone blaming you" -me