T.R | Title | User | Personal Name | Date | Lines |
---|
852.1 | please explain | RDCV01::FSL | Rob Aldridge, FSL/BACIS | Wed Aug 26 1987 18:00 | 8 |
|
...but why? I don't understand your application/need.
If you simply want to print an .LN03 file to an LN03 which is
connected to your printer-port, there are "zillions" of little
programs out there that will do this for you.
-Rob-
|
852.2 | Make it 'User Friendly' | HLDG01::HOFLAND | | Thu Aug 27 1987 03:54 | 19 |
| << ...but why? I don't understand your application/need.
<<
<< If you simply want to print an .LN03 file to an LN03 which is
<< connected to your printer-port, there are "zillions" of little
<< programs out there that will do this for you.
If we support direct printing for other destinations why not on
the printerport ??
DOCUMENT will be used also by non-technical users who don't have
access to the 'fancy' tools, so it has to be as
'User Friendly' as possible.
<Eric>
|
852.3 | There may be more to this than meets the eye... | YUPPIE::COLE | I survived B$ST, I think..... | Thu Aug 27 1987 09:53 | 7 |
| Someone here in Atlanta was trying to print some LN03 files on an
attached DECmate LN03, and was getting trashed output in random spots. He had
two memory units loaded, also. There might be some subtle control character
or setup problems that would have to be worked out if DOCUMENT was to do this
directly.
And of course, this would preclude any batch runs!
|
852.4 | Use tool 'PORT' | HLDG01::HOFLAND | | Mon Aug 31 1987 03:49 | 100 |
| < Note 852.3 by YUPPIE::COLE "I survived B$ST, I think....." >
-< There may be more to this than meets the eye... >-
Someone here in Atlanta was trying to print some LN03 files on an
attached DECmate LN03, and was getting trashed output in random spots. He had
two memory units loaded, also. There might be some subtle control character
or setup problems that would have to be worked out if DOCUMENT was to do this
directly.
============================================================================
A good tool for printing via the printerport is PORT from the METOO
Toolshed:
Note 687.0
VNX::TOOLSHED 33 lines 19-MAR-1987 21:00
--------------------------------------------------------------------------------
-< PORT PORT is a flexible tool that prints files to a terminal's >-
(The information in this file is for INTERNAL USE ONLY.) MAR-87
TOOL NAME: PORT
FUNCTION: PORT prints files to a terminal's printer port
VERSION: V1.2-04 (February 1987)
SYSTEM: VMS V4.x
LANGUAGE: BLISS
LOCATION: METOO""::TOOLS$DIRECTORY:[PORT]PORT.COM
METOO""::TOOLS$DIRECTORY:[PORT]PORT.OBJ
METOO""::TOOLS$DIRECTORY:[PORT]PRINT.OBJ
METOO""::TOOLS$DIRECTORY:[PORT]PORT1.CLD
METOO""::TOOLS$DIRECTORY:[PORT]PORT.HLP
METOO""::TOOLS$DIRECTORY:[PORT]BANNER.OBJ
METOO""::TOOLS$DIRECTORY:[PORT]PORTMSG.OBJ
MORE INFO: A help file is installed into the main HELP library.
SOURCE: Steven Curtis @SHR1-3/E10 @GUMDRP::CURTIS
GENERAL DESCRIPTION:
PORT allows files to be printed to a terminal's printer port. The user
can exercise some control over the final format of the text, such as
horizontal pitch, vertical pitch, and letter quality (or enhanced print)
mode.
ADVANTAGES: PORT is faster and more flexible than similar command
procedures.
LIMITATIONS: None stated.
OTHER:
See also LA50, LA50KIT.
To install the kit, execute PORT.COM after getting the tool kit files.
Note 687.1* 33 lines
VNX::TOOLSHED 41 lines 19-MAR-1987 21:01
--------------------------------------------------------------------------------
-< PORT.KIT >-
$! VMS Installation kit for PORT
$ PORT_VER= F$VERIFY(0)
$ IF F$EXTRACT(0,2,F$GETSYI("VERSION")) .EQS. "V3" THEN GOTO install
$ WRITE SYS$OUTPUT "Installing PORT"
$ GOTO 'F$MODE()
$ INTERACTIVE:
$ INQUIRE ans "Do you wish to install in batch mode? [Y]"
$ IF ans .EQS. "" THEN ans = "Y"
$ IF .NOT. ans THEN GOTO install
$ default := "''F$LOGICAL("SYS$DISK")'''F$DIRECTORY()'"
$ SUBMIT/notify/noprint/par='default' 'F$ENVIRONMENT("PROCEDURE")
$ GOTO exit
$ BATCH:
$ set nover
$ set default 'p1'
$ install:
$ COPY/LOG METOO""::TOOLS$DIRECTORY:[PORT]PORT.COM *.* !
$ COPY/LOG METOO""::TOOLS$DIRECTORY:[PORT]PORT.OBJ *.* !
$ COPY/LOG METOO""::TOOLS$DIRECTORY:[PORT]PRINT.OBJ *.* !
$ COPY/LOG METOO""::TOOLS$DIRECTORY:[PORT]PORT1.CLD *.* !
$ COPY/LOG METOO""::TOOLS$DIRECTORY:[PORT]PORT.HLP *.* !
$ COPY/LOG METOO""::TOOLS$DIRECTORY:[PORT]BANNER.OBJ *.* !
$ COPY/LOG METOO""::TOOLS$DIRECTORY:[PORT]PORTMSG.OBJ *.* !
$ ASSIGN /USER NL: SYS$OUTPUT:
$ DIR SYS$SHARE:NM_MAILSHR.EXE
$ NMAIL_STATUS = $STATUS
$ IF NMAIL_STATUS THEN DEFINE STC "NM%METOO::STC"
$ IF .NOT. NMAIL_STATUS THEN DEFINE STC "METOO::STC"
$ IF NMAIL_STATUS THEN DEFINE STC_PORT_SOURCE NM%GUMDRP::CURTIS
$ IF .NOT. NMAIL_STATUS THEN DEFINE STC_PORT_SOURCE GUMDRP::CURTIS
$ ASSIGN /USER NL: SYS$OUTPUT:
$ MAIL /SUBJ="PORT installed ''f$log("SYS$DISK")'''f$dir()'" -
NL: STC
$ ASSIGN /USER NL: SYS$OUTPUT:
$ MAIL /SUBJ="PORT installed ''f$log("SYS$DISK")'''f$dir()'" -
NL: STC_PORT_SOURCE
$! ASSIGN /USER NL: SYS$OUTPUT:
$! MAIL /SUBJ="Has the tool PORT been installed on this system before?" -
! NL: SYSTEM
$exit:
$ PORT_VER=F$VER(PORT_VER)
|
852.5 | | CLOSET::ADLER | | Wed Sep 02 1987 17:16 | 5 |
| This is the first request we've gotten for it. Nevertheless, consider it added
to the wishlist for consideration. If there are any others out there who need
such a feature, let us hear from you.
--Brian
|
852.6 | a big YES ! | REGENT::MERRILL | Glyph, and the world glyphs with u,... | Thu Sep 03 1987 10:45 | 13 |
| First, VT330's with dual sessions make the use of the printer port for
long documents emminently feasible, since your keyboard can still
be used on the one session while the printer is fed via the other
session!
Secondly, the LN0x can be a very "personal" printer with the user
grabbing data hot off the thermal-setter, inserting and removing
font cartridges, changing paper sizes, feeding in letterhead or
transparency materials, and otherwise servicing the printer.
Rick
Merrill
|