Re: script for USB printers

[Philip Friedman pfilf@xxxxxxxx]

Reply to message from

Robert Holmgren 
Jun 10, 2006 4:31 AM

Robert, thanks for the clarifications on mapping. I think I have it straight.

And for the advice about U2 frame TYN  ....  I do have a Print Server and a Router (wireless) so
that might do the trick...  but for now I'm still stuck with (on) Xy3+, so if I've been reading
aright since I joined the list, U2 will not help me at this point. 

My affinity for and almost 20 years' experience with xy3+ has not deafened me to the clear
preference y'all have for Xy4 (Dave Erickson, too, as he told me a good ten or more years ago. Did
I listen? No)  I have downloaded xy4 and archived locally your (and others') major posts about U2
and the Xy4 manual in anticipation of the day when I have the time and attention span to attempt the
transition. As soon as I finish this draft of this book, I tell myself....


.. Philip, you might want to experiment with a new-ish frame in U2
>(7 June refresh) called TYN, which TYpes [prints] to a Network resource using
>NT's built-in LPR client (and offers, for download, a command line LPR client
>for 9x). TYN responds instantly, literally before you can remove your finger
>from the Enter key -- boom! paper starts spitting from the printer. TYN
>requires a slightly more elaborate setup than you (apparently) have presently,
>namely EITHER a printer that is networkable, i.e. has its own *static* IP
>(network) address and HostName (more and more printers are networkable
>nowadays), OR a printer which is attached to a hardware Print Server (attached,
>in turn, to a Router, thus providing an indirect way of achieving a *static* IP
>address and HostName for your printer -- a Router is an advisable [and cheap,
>~US$50] piece of hardware for nearly everyone to have, even single-computer
>broadband users, because it is a much more effective and unobtrusive firewall
>than software solutions, although it still won't prevent you from shooting
>yourself in the foot, which is what XP's absurdly intrusive firewall endeavors
>to do by constantly sticking its nose into your business). The printer *must*
>understand PCL and/or Postscript, but it *need not* explicitly support the DOS
>OpSys. If you can meet these requirements, TYN (and underlying LPR) is an
>excellent way to go. This represents another and, for U2, new option in the
>panoply of alternate methods for old DOS apps to print.
>
>-----------------------------
>Robert Holmgren
>holmgren@xxxxxxxx
>-----------------------------
>