Re: Printing from Win-OS/2



Bill, Thank you for your thorough description (this is most likely something
that has come up a number of times...) I got it working using Jim's
suggestion just before I saw your post.

On Sun, 19 Feb 2006 17:11:48 -0600, William L. Hartzell wrote:

:>Sir:
:>
:>Elmer Fudd wrote:
:>> Mark, I am sending OS/2 print jobs to /PIPE/LPD0 -- how do I configure
:>> Win-OS/2 to use this port?
:>>
:>> On Tue, 14 Feb 2006 04:11:49 -0600, Mark Klebanoff wrote:
:>>
:>> :>On Tue, 14 Feb 2006 01:30:32 UTC, "Elmer Fudd" <bitbucket@xxxxxxxxx>
:>> :>wrote:
:>> :>
:>> :>> Is it possible to print from a Win-OS/2 application to a networked printer
:>> :>> when I am running LPRPORTD (or whatever it is called) to point all OS/2
:>> :>> printing to the networked printer? If so, how should I configure printing in
:>> :>> Win-OS/2?
:>> :>>
:>> :>> TIA.
:>> :>
:>> :>Dear Elmer :-)
:>> :>
:>> :>Yes, I have such a setup. If you sent lprportd to monitor one of the
:>> :>lpt ports, you can print with WINOS/2 to that port.
:>> :>
:>>
:>>
:>>
:>I not had to do this, so... You need to create a printer object for
:>your network printer, the one that is attached to the pipe. If you
:>already have done this, then you need look to see what parallel port is
:>currently unassigned (OS/2 desktop-> Connections-> (any) printer->
:>properties-> output port: not cross hatched), like lpt4, and make an
:>entry in the WinOS2's Win.ini file like this:
:>LPT1:=
:>LPT2:=
:>LPT3:=
:>COM1:=9600,n,8,1,x
:>COM2:=9600,n,8,1,x
:>COM3:=9600,n,8,1,x
:>COM4:=9600,n,8,1,x
:>FILE:=
:>LPT1.OS2=
:>LPT2.OS2=
:>LPT3.OS2=
:>LPT4.OS2=
:>
:>The last line I just added. Next enter the WinOS/2 session and go into
:>Control Panel -> Printer-> (pick your printer)-> Connect-> (pick the
:>LPT4.OS2 port). Select Ok to save the entry and back out clicking Ok.
:>Close the WinOS2 session. Next open OS/2 Desktop-> Connection (I'm not
:>on my eCS system, so where ever they put the next folder if you are
:>using eCS)-> Printers-> (any printer object) properties-> Output port->
:>(select LPT4)-> redirection-> (pick the pipe you mentioned above).
:>Close the object windows to save. I picked LPT4 as my lower numbered
:>ports had something already assigned to them (you can have up to nine
:>lpt ports, but that requires you to add them to OS/2
:><http://hobbes.nmsu.edu/pub/os2/util/printer/addlpt.zip>).
:>
:>IF you have not installed your printer into WinOS2, then you need to do
:>that before doing the above. If your printer came with no Window 3.1
:>drivers (& they are getting hard to find), pick a printer that your
:>printer can emulate (called an allomorph) and install that printer's Win
:>3.1 driver. If on the other hand, your printer does not emulate any
:>printer that has a Windows 3.1 driver, then install an ANSII compatible
:>printer like IBM Proprinter into both OS/2 and Winos2. You'll need to
:>change the spool format to PM_Q_RAW (OS/2 desktop-> Connections->
:>Printer-> IBM Proprinter-> properties-> print driver-> properties->
:>Print Spool Type-> PM_Q_RAW). You will lose most pretty formatting &
:>all graphics, but it will print. You can select to print the raw text
:>to file (OS/2 desktop-> Connections-> Printer-> IBM Proprinter->
:>properties-> output port-> check box 'Print to file') and import it, the
:>file, to an OS/2 application to add the pretty formatting and graphics.
:>--
:>Bill
:>Thanks a Million!
:>
:>
:>
:>
:>
:>
:>
:>



.



Relevant Pages

  • Re: Clustered printing issue
    ... tcp/ip port. ... accessible unless you install the printer driver. ... printers restored via the print migrator tool. ...
    (microsoft.public.windows.server.clustering)
  • Re: KMDF Fakemodem not working
    ... I'm using the `Windows Vista and Windows Server Longhorn x86 Checked Build ... install the fakemodem with devcon: ... INf in the sample should tell you how to use devcon to install the driver. ... Why do I need to choose a COM port? ...
    (microsoft.public.development.device.drivers)
  • KMDF Fakemodem not working
    ... I'm trying to develop my first device driver but have some problems getting ... I succeeded to install the WDM version on a Win 2003 Server x86 using the ... I had to disable a real modem driver, ... Why do I need to choose a COM port? ...
    (microsoft.public.development.device.drivers)
  • Re: NDIS WDM driver installation for multi-port NIC
    ... Windows 2k/XP/2k3 Filesystem and Driver Consulting ... miniport's inf and to install the miniport driver. ... the miniport driver (the bus driver starts up fine). ... identify the particular port you are communicating with. ...
    (microsoft.public.development.device.drivers)
  • Re: Found, a new rootkit
    ... Your MS-DOS box is no more secure ... machine has a device driver for that device, ... to the serial port. ... So if I install a modem on it, ...
    (Fedora)