delorie.com/archives/browse.cgi | search |
Xref: | news-dnh.mv.net comp.os.msdos.djgpp:2837 |
Path: | news-dnh.mv.net!mv!news.sprintlink.net!newsfeed.internetmci.com!newsxfer.itd.umich.edu!gumby!andrews-cc!glass |
From: | glass AT andrews DOT edu (Brian Glass) |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | print screen with GRX2.0 |
Date: | 25 Oct 1995 15:01:55 GMT |
Organization: | Andrews University, Berrien Springs, MI, 49104 |
Lines: | 19 |
Nntp-Posting-Host: | jazz.cs.andrews.edu |
To: | djgpp AT sun DOT soe DOT clarkson DOT edu |
Dj-Gateway: | from newsgroup comp.os.msdos.djgpp |
I recently posted a similar question but with inadequate details. I have a program that I ported from Borland compilers to DJGPP. I converted the routines that do graphics to use the GRX library. Previously printing of graphics was done using the DOS Graphics program that does a screen capture and dump to the printer invoked by the prtscrn key. This unfortunately works incorrectly now. I can dump text screen information to the printer with no problem but when I try to print graphics I get either a blank page or a totally black page. My theory is that GRX maps the graphics screen to a block of memory that DOS's Graphics program doesn't know about and thus prints out garbage from a totally unrelated block of memory. I really hope that this can be made to work since if it doesn't I will have to write my own printer drivers! How might I remedy this situation? Any help would be GREATLY appreciated! Thanks in advance.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |