TIP: Click on subject to list as thread! ANSI
echo: os2dos
to: ANDREA FLEISHMAN
from: JONATHAN DE BOYNE POLLARD
date: 1996-05-21 23:04:00
subject: Print color Win-OS2

AF>
  >  JdeBP> What is the DPMI_MEMORY_LIMIT setting for the VDM running Windows 
?
  >
  > I have it at 64.  That should be high enough, isn't it?
AF>
  It should be.  But it all depends from how much memory your Windows
  printer driver needs to render the colour image.
AF>
  > What about HMS handles
AF>
  Irrelevant when you are running Windows in your VDM.  It sets the number
  of handles available to DOS applications using XMS.  Windows does not
  use XMS.
AF>
  > Would it make a difference if I put a / after the device=print.01 line in 
t
  > config.sys.
AF>
  BASEDEV=PRINT01.SYS /IRQ
  It wouldn't affect your current problem, but your printing would impact
  much less on what else you were doing at the same time.
AF>
  > I understand removes the IRQ from the printer.  But that shouldn't make a
  > difference on printing color.  It does print in black and
  > white.  So the printer itself is working.
AF>
  Correct.  The printer itself *is* working.
  In fact, we can eliminate the OS/2 side of things completely, since, as
  you say, you can print B&W images from your Windows application without
  problem.
  The problem almost certainly lies within the Windows printer driver.
  For some reason it needs, or at least *thinks* that it needs, enormous
  gobs of memory when rendering colour images.
  (1) Look for an updated copy of the Windows printer driver.  It is not
      unlikely that the driver itself is buggy.  It's not uncommon with
      Windows printer drivers, believe it or not.
  (2) Check your printer's manual.  Do you need a certain amount of buffer
      RAM on the printer itself for printing in colour ?  Could it be that
      you have told the Windows printer driver that you only have (say) a
      1Mb buffer on your printer, and it is quite properly telling you
      that 1Mb is not enough for printing in colour ?
  (3) Attempt to contact the printer driver manufacturers and find out
      what the "not enough memory" message can be caused by.  It could be
      something completely unconnected to memory, such as the driver's
      inability to create a temporary file in your TEMP directory.  It all
      depends from how the driver has been writtem.
  > JdeBP <
___
 X MegaMail 2.10 #0:Dr Who is back on U.K. television!
--- Maximus/2 3.01
---------------
* Origin: DoNoR/2,Woking UK (44-1483-725167) (2:440/4)

SOURCE: echomail via exec-pc

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.