mxh5795@cs.rit.edu (Michael X Houwers) (02/19/91)
I'm having a problem with printing graphics screens. The hardware setup is an AT clone (MicroDirect), Samsung motherboard, Award 3.03 BIOS, 1M memory with no extended driver installed, EGA card and monitor, 32M drive, 1.2M and 360K floppies, DOS 3.3, Epson FX-80 printer. I'm working on a stats package that does all sorts of interesting calculations with a set of data and specs (the details of which I don't understand and don't care to..I'm not a math major.. :-) When it's calculated everything it needs to, it plots a couple of graphs. In order to support a variety of different video and printer configurations, I'm using GrafPlus from Jewell Technologies to print the graphics images. It basically sits on the PrtScr interrupt (5) and intercepts the calls and does its thing. It's a TSR, and when you install it, you tell it what kind of video system you have, and what kind of printer you'll be printing to, and it has the drivers for a whole bunch of different types of printers. At any rate, the problem is this: as of last week, everything was fine and happy, no problems printing. However, this week, after some modifications to the code to do some more graphics output, doing a PrtScr now hangs the system dead. I spent A while looking for a software problem, and then took it to an almost identical system (true IBM AT, EGA, same printer) and it worked fine. So, that seems to rule out a software problem. But, GrafPlus works fine with any other application I try to print. So that pretty much rules out a hardware problem. See my dilemma yet? :-( I tried to check if it was a memory problem (i.e. running out so it couldn't print), so I allocated all the memory I could and still have the graphics driver load, and it still printed fine. So, now for the question (finally). Has anyone seen behavior like this with any similar system? If so, any suggestions? Or, does anyone have any suggestions on what might be at the core of this problem? I have seen some strange things when printing before, so maybe it's a hardware problem that was shaken out by the new code? (I know, I'm grasping at straws here...) Any ideas anyone? Thanks in advance, mike houwers -- --------------------------------------------------------------------------- Michael Houwers "I'm not sleazy, I"m morally challenged" bitnet: MWH5795@RITVAXA internet: mxh5795@cs.rit.edu