-=> /* Quoting Jeff Malka to all */ <=-
 JM> I have develloped a wierd printing problem when printing from a
 JM> Windows app.  
 JM> I use Warp (red spline= no windows) with Windows 3.1 running under it
 JM> for Windows apps.  Recently, when I print from a Windows application,
 JM> the windows software does what it needs to do, but the data does not
 JM> get to the printer (that is the feed light does not go on) UNTIL I
 JM> exit from the windows app and get back to the OS/2 desktop.  Then the
 JM> printer feed light goes on immediately and the printer prints.
 JM> What is wierd is that this is a recent behavior that only started a
 JM> couple of months ago.  Prior to that printing from within Windows apps
 JM> worked just fine.
 JM> I have tried to solve the problem by ensuring trying with the Windows
 JM> "use print manager" both activated and not activated with no
 JM> difference.  It is getting really annoying.  Anyone have suggestions?
Sure.  Go into the DOS settings for the ICON you use to run
the Windows app (full screen Windows or whatever you're
running it from) and set the PRINT_TIMEOUT to 15 (seconds).
This is the default. It will allow your print job to start
15 seconds after it is sent to the printer from a DOS app.
If this value is set too long (say 500 seconds), you may
exit the app before the job is sent.  When exiting a DOS
app, any print job that is left remaining is printed
immediately.
-Frank
(fsexton@ibm.net)
--- PCBoard (R) v15.3 (OS/2) 5 (06-04-9
---------------