From: backman@FTP.COM (Larry Backman)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Windows & PC/TCP 2.1
Date: 26 Sep 92 17:18:29 GMT
Distribution: world
Organization: The Internet


 >> First, your best be is to have PC/TCP v2.05 pl4 or better.  Results with
 >> pl3 vary.  >pl3 does not allow printing from Windows applications.
Better yest, get PCTCP 2.1; lots of bugs in print redirection fixed there..

 >> Set up print redirection.  Use the command reference manual.  You must 
 >> create or edit a configuration file which is set in the autoexec.bat file.
 >> We use the name "pctcp.cfg" and point to it by typing "set FTP_CONFIG=
 >> c:\ftp\pctcp.cfg".  Hint:  FTP suggests you set the timeout variable to 
 >> >60.  I set mine to 10.  I'll tell you later.
10 is fine in PCTCP 2.1; larger numbes were necessary in previous versions..

 >> Edit the system.ini file and add the seven line found in the system.ini 
 >> example given by FTP S/W.  DON'T LOOK IN THE MANUAL.  There is nothing in
 >> there that describes anything about installing anything in Windows there.
again, get 2.1

 >> If you have Win 3.0, select LPT1.OS2 if you redirected from PRN/LPT1.
 >> 
 >> If you have Win 3.1, I've been told that you can only select LPT1 because
 >> of a Windows problem.  I have edited the win.ini and added another port 
 >> called LPT1.DOS which as had some success.  Who knows?
I do; its a long story, but you can use LPT2 & 3 in PCTCP 2.1...Now that we
just patch DOS's io.sys driver's data space periodically LPT2 & 3 work
fine.  Dos stinks...

 >> Run the Window's application.  Edit, save, then print selecting the printer
 >> which you have chosen to redirect to.  The output is printed to a file.
 >> If you set the timeout variable to 10, you have to wait ten seconds for
 >> a prompt screen to appear which tells you it is ready to print the output
 >> file to your printer.  You must answer OK.  You have no choice.  After that
 >> the file is sent (crossed fingers) to the printer.

prompt screen can be turned off in 2.1 (I'm starting to sound like
a broken record :-) ).

The timeout value controls when the <predir> TSR decides to send a
"print it now" message to Wprespl.  There are wolves out there; for
instance if your doing multiple applications and after you start your
rpint job, switch to a second application which seizes control of
Windows for longer than the timeout value (try repaginate under Winword
as an example :- ) ); the print job will fire prematurely and
get split up into 2 or more print jobs.  In this case increase the timeout
value..

 >> Never use interrupts 2 or 3 when using pc/TCP and Windows.

never use these interrupts & anything & Windows :-).

 >> Watch shared memory with PC/TCP, your card, and Windows.  I haven't been 
 >> able to get this going even with FTP's suggestions.

Use the EMMExclude stataement in Windows system.ini file to control this.
This should solve the problem.

 >> Watch out when using EMM386.  Sometime an error occures asking you to set a
 >> parameter D=64.(???)
I believe that the Windows 3.0 EMM386 was broken and that the
DOS 5.0 was is reliable.  Win 3.1's EMM driver appears to work correctly.

Larry Backman
FTP Software

Newsgroups: comp.protocols.tcp-ip.ibmpc