Subject: printing problem using e-mail

From: "Menno Diliberto (OU)" <[email-masked]>
Date: Tue, 15 Apr 1997 15:19:49 -0400 (EDT)

i have the following:
modem:
sportstar winmodem (internal)
28.8 faxmodem for windows 
software:
quicklink ii  fax  win/dos 

i am using windows 3.1

my problem:

i have not been able to print any of my incoming/outgoing e-mail.

i have tried using "control Y", capturing text (as quicklink ii

recommends, and recommendations by other sources without success.

my printer is an hp deskjet 500.  if there is anyone out there

who can offer any help i certainly would appreciate it.

thank you.

menno diliberto      :helios.acomp.usf.edu

---

From: Robin S Socha <[email-masked]>
Date: Tue, 15 Apr 1997 22:08:43 +0200 (MET DST)

-----BEGIN PGP SIGNED MESSAGE-----

  >my problem:

Your problem are the above two programs. Have you tried getting the FAQ for
pine? There is a lengthy passage about how to set up printers with PCs
running Dos. Here's the (at least I hope so... ;-) ) decisive part:

 1. Check For Software Flow-Control Problems
    A. Try enabling "preserve-start-stop-characters" (requires 3.91 or later)
    B. If that doesn't help, verify that the OS is enabling s/w flow
       control; if it isn't, you can either change that in a global
       .login script, or as a worst case, wrap pine in a script that does
       it.  By the way, on our AIX systems, we had to execute "stty -ixon"
       followed by "stty ixon" --no one here knows why the first stty
       is needed.  (Note that explicitly enabling s/w flow control in the OS
       will not be needed in 3.92 or later).
    C. If neither of the above apply, double-check that you actually have
       *some* kind of flow control enabled on your system, either hardware
       or software.
 2. Check Your Comm Software For Ansi Printing Capability
    A. After ruling out s/w flow control problems, if printing still
       doesn't work, the odds are that the PC or Mac comm s/w is at fault.
       I don't know how to determine this other than via trial-and-error
       and word-of-mouth.
    B. The "ansiprt" utility included in the pine distribution can also
       be used for testing.  It simply sends the specified text file to
       user's terminal device, bracketed with the ANSI escape sequences
       for print diversion.  This is just what Pine does as well (although
       some versions of ansiprt offer a few options not available via Pine.)
 3. Possible Other Printing Problems
    A. Printing via Pine's "attached-to-ansi" facility to a postscript-only
       printer.  Pine does not yet have the ability to encapsulate text
       into postscript, ala "enscript", so the custom print option using
       enscript and ansiprt will be needed in that case.
    B. Other printer-specific configuration problems.  For example,
       whether or not the printer needs a trailing formfeed to eject the
       last page, or a control-D, or non-Unix newline conventions, etc.
       Many of these problem will also require using the custom print
       command option and "ansiprt".

Hope that helps. BTW, your message looked kinda ugly. Either you're manually
inserting blanks lines or your line width is too high (i.e. exceeding the
recommended 75 characters). Don't :-)

  >who can offer any help i certainly would appreciate it.

- -----
Robin S. Socha,
Political Science Dept., Bonn University, Bonn
Key fingerprint = 7F F2 84 73 CF E9 2C 92  F6 6E F9 B4 8F FE AC 1E
To get my pgp public key, send an e-mail with the subject "get pgp-key"

GMC d++ s+:+ a- C++ UL++$>+++$ P+>++$ E>+ W- N+ o@ w--- M-- PS--- PE+++ Y+
PGP++>+++ t+() 5-- tv++(+) b+++ DI++ D+(++) G++>+++ e++>+++ h r++>+++ y+**