From: "Damian Yerrick" Newsgroups: comp.os.msdos.djgpp References: <380EF520 DOT C2FAE759 AT connect DOT ab DOT ca> Subject: Re: Plague of the slow 'blit' routine :) Lines: 25 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Message-ID: <6noQ3.868$Ol4.21480@dfiatx1-snr1.gtei.net> X-Trace: /Kw5eG1xlMV77oHd9dacchwaaaIK8iLXW8tcv3ELC8dAJElIL5hsWuBPreYlroVdTe6+Oha6UEdr!mp61viLavKoTVHdCdtuq7QRBhxCETdpiXjctpnvP/Do25bmAoAX69JnzRTMOZo0YTWF1H2lD X-Complaints-To: abuse AT gte DOT net X-Abuse-Info: Please be sure to forward a copy of ALL headers X-Abuse-Info: Otherwise we will be unable to process your complaint properly NNTP-Posting-Date: Sat, 23 Oct 1999 19:53:38 GMT Distribution: world Date: Sat, 23 Oct 1999 19:53:38 GMT To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Tom Fjellstrom wrote: > Thank you Eli, > > But I can't be completely sure if the 'bitmap' i'm blitting > to or from is in video memory. If I could then it would > make sense to call the dosmemput or farptr functions > only for those 'bitmaps'. I may be wrong but I don't think > 'regular' memory can (or should?) be accessed with > dosmemput or those farptr functions. The only way I have > thought of determining that a bitmap is in video memory > is too add a variable to the bitmap struct when creating > it to indicate whether or not it is in video memory. If that > is the only safe way of doing it I guess i'll have to. That's the way it was done in Allegro. http://www.talula.demon.co.uk/allegro/ -- Damian Yerrick CM 398, Rose-Hulman Institute of Technology 5500 Wabash Ave | Terre Haute, IN 47803 http://come.to/yerrick <- redpinocchio http://yerricde.tripod.com/ <- pinocchio's brother