• Welcome to OS2World OLD-STATIC-BACKUP Forum.
 

News:

This is an old OS2World backup forum for reference only. IT IS READ ONLY!!!

If you need help with OS/2 - eComStation visit http://www.os2world.com/forum

Main Menu
Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - vbien

#1
Quote from: RobertM on 2012.05.15, 02:34:29
Here's the "How To" document (sans images, which I will add later):

http://www.os2world.com/wiki/index.php?title=OS2_World_Wiki:HOW_TO:_Printing_to_an_OS2_Printer_From_a_Windows_Computer

It's probably a little easier to read than my forum post below.

-R

Now it work!  So problem solved!  Thanks very much.

  The bit I was missing was applying the OS/2 "physical" printer name to the Windows printer property dialogue - the section in the above link headed Final Port Configuration.  The "physical printer" name is the name of the printer on the WPS.  In my case it is called DOS which uses the IBM Null driver.  Unassisted I would not have known about selecting the LPR protocol and clicking LPR Byte Counting.

  Also to answer Alex Taylor above, DOS is the correct Queue name or Physical name although it's a bit counter-intuitive.  The Windows driver is Lexmark but the queue name has to be via IBM Null because the stream of data going to OS/2 is correct for the printer so one does not want OS/2 to do anything other than just pass the stuff through.  This has been true from the year dot.  When printing from Win-OS2 on the OS/2 computer the native OS/2 printer to use has always been DOS (IBM Null).  However, the driver inside Win-OS2 has to be Lexmark.  So by extension that is what I expected would be required from a Windows computer connected via the network.

  So the salient difference between Win-OS2 and a network connected Windows computer comes down to a piece of blue LAN cable!

  However, when printing from native OS/2 programs such as DeScribe, PMMail or PMView one has to use a queue name which uses the OS/2 Lexmark driver.  I call my Lexmark physical or queue name Lexmark Optra E310.

  If either queue name is used inappropriately you quickly know!  You get gibberish!
#2
Quote from: RobertM on 2012.05.13, 00:47:30
That method fails on many versions of Windows - or on many printers. Its a long standing bug over ten years old.

The way that generally works is as follows (yes, as idiotic as this issue) in EVERY version off Windows from XP through Win7:

Choose to create a LOCAL printer (manual route, not auto-detect), then hit the appropriate version to add a new port, select TCP/IP port, add the appropriate IP address, then cancel or continue the printer creation selecting that port. Obviously, if you choose the cancel method (trying to continue sometimes hangs the installation on some versions off Windows) then u must start with the printer creation again. Again, pick LOCAL, and simply select the port you created above.

HTH,
Rob

Still doesn't work.  I followed the above idea and created the new port and created the (local) printer icon with the Lexmark driver but when a test print is done nothing prints.  The job appears, when the icon is opened, but soon an error notice appears for the print job.

By my figuring there would have to be something missing; some linkage missing.  What I mean is that the lpd daemon is a command or process that works at the filesystem level but the print objects are at the WPS level - comparable to the Window's GUI desktop.  The printer objects are specified in the ini files, the equivalent of Windows Registry.  So how does the data stream flowing into lpd get to a printer object?  Or does it go automatically to prn?  The catch is that in my case the printer is not connected to the parallel port; it is connected to an USB port.  Can prn be redirected from LPT1 (the parallel port) to the USB port?  How would one do that?
#3
Quote from: ALT on 2012.05.11, 13:22:29
Quote from: vbien on 2012.05.11, 10:47:53
I've installed an SLPR port and made the LPD server IP address that of my OS/2 computer (192.168.1.14) and made the LPD printer the IBM Null printer.  This idea effectively makes the OS/2 computer a print server doesn't it?  I was wondering whether that setup could be created. 
I am finding it hard to understand the logic of SLPR.  It gets installed as an "Output port" which seems to imply it's for printing from the OS/2 computer to a print server?  Surely what I need is an "Input port" (from the network) to the printers.  So what I want to do is the other way round.  I want my OS/2 computer to be the repository machine for data and for printing from Windows computer essentially as smart terminals.  Was your discussion about using the OS/2 machine as a client?

You are correct, SLPR is for printing from OS/2 to a network printer server.  It is not relevant to what you are trying to do.

What you want to do is to run LPD on your OS/2 system.  You can configure this through your TCP/IP Configuration GUI but that's such an ugly and cumbersome program to use that I think it's easier to just edit the configuration by hand.

Edit \tcpip\bin\tcpstart.cmd and locate the line "REM start lpd" (around line 26).  Change this line to "detach lpd -c" and save the file.  That'll start LPD whenever the system boots up.  To start it directly without rebooting, just run "detach lpd -c" from a command line.

You should then be able to print to any printer queue defined on OS/2 using TCP/IP (lpr) from another system.  The IP address is the IP address of your OS/2 system, and the print queue name is the "physical name" of the printer object shown on the first page of the printer object's properties notebook.


Still doesn't work.  When you add a network printer, using the Windows add a printer wizard, and you type the IP address of say an HP4000 network printer, and click Next the wizard moves to the next screen that asks you to specify the printer driver you need.  On my OS/2 computer with the lpd -c running and also lptportd running and you do the same you still get the critical stop error message.  It does not seem sufficient to just specify the IP address of the OS/2 machine.  The wizard seems to be asking for the path to the printer but how would you do that which makes sense to the Windows machine?  Typing 192.168.1.14/dos (DOS being the queue name of the OS/2 IBM Null printer driver) doesn't work.  When you look at the DOS printer in the WPS (and all the others) it's actually under D:\Desktop\Connections\Printers\ (D: is my OS/2 boot drive).  I wouldn't think this makes sense to Windows.  I tried typing that path and it also did not work, not surprising.  There is no link between lpd or lprportd and any particular installed printer.

#4
Quote from: melf on 2012.05.03, 17:34:58
I can't help you with the Samba print, but as a better work around (till you get proper help) you could install a SLPR port (eCS) and print to your computers IP-number. My setting, printing form an eCS machine looks like in the picture (the properties window for the SLPR port is opened) . In windows it's called "Print over TCPIP" or something, where you can choose "LPR " and IP and printer name. I use it from both win and os2 machines. Added a pic from win.

I've installed an SLPR port and made the LPD server IP address that of my OS/2 computer (192.168.1.14) and made the LPD printer the IBM Null printer.  This idea effectively makes the OS/2 computer a print server doesn't it?  I was wondering whether that setup could be created.  On a Windows computer when I tried to create a network printer with the above OS/2 computer IP address I get an error saying Windows cannot connect to the printer.  Checking with ping shows the OS/2 computer responds correctly but as a print server it's not working.

So still nothing.  Did I need a restart?  When restarted the WPS would not come back up!  The WPS would hang after the welcoming sound emitted.  Because I have experienced these panic situation before, I have learnt and created a Maintenance partition where I have access to the WPS to run Back Again 2000 and restore the ini files from backup, which I take everyday.  So that installation of an SLPR port wrecked the WPS!!

I am finding it hard to understand the logic of SLPR.  It gets installed as an "Output port" which seems to imply it's for printing from the OS/2 computer to a print server?  Surely what I need is an "Input port" (from the network) to the printers.  So what I want to do is the other way round.  I want my OS/2 computer to be the repository machine for data and for printing from Windows computer essentially as smart terminals.  Was your discussion about using the OS/2 machine as a client?

The non-functioning of the Samba print function is very disappointing and the pdf method works but is very inconvenient.
#5
Quote from: herwigb on 2012.05.04, 15:59:01
>Basically the scenario you describe has been tested and does work.

>Everything you did seems appropriate, however there's one sentence, I don't quite understand:

>>> My printer is a Lexmark Optra E310.  With the LAN manager arrangement, which prints normally, I use the same driver and print to the IBM Null driver on the OS/2 computer. <<

OK that's a bit too terse.  Since WinOS2 days, even to the present in my case, Windows print requests are processed by its own printer drivers, the Optra E310 in my case, and sent to the Null driver which just passes all the bytes through to the printer like the physical ports.  I have experimented and tried linking the Windows printer to the OS/2 Optra printer driver and you just finish up with gibberish.  One uses the Optra driver from OS/2 programs to print to the Optra.  If one prints from an OS/2 program to the Null driver printer you get gibberish.

>The Samba concept for printers is quite simple: Samba takes any (printer specific) file from a client and sends it to the local printer object, the printer object on the server must me configured properly with the appropriate driver. On the client you also must have a printer object with the appropriate driver.

>The IBM Null driver does not fit into the picture here...

  Up to now with LAN Manager I have only shared the IBM Null printer for the reasons above.  When Samba did not work similarly. I tried adding the OS/2 Optra printer as a second share and linking the Windows driver to that.  That does not print either.  That setup is the one which causes the printer light to blink but despite that fails to print as I mentioned in the initiating post.  Printing to the Samba shared Null driver printer does not produce any reaction at all.

   For now I have tracked down a free print to pdf driver which I have setup to print to a temp folder on OS/2.  Then I just go over to the OS/2 machine and run the Acrobat 5 there to physically print.  Not too painful.

#6
Following through from http://svn.netlabs.org/samba I downloaded all the WPI and the few associated supplementary zip files and I installed the ver 3.3.x version of the server on my OS/2 ver 4.52 computer.
  After suitably editing the config.sys including putting in two LIBPATH spots where the Samba packge is installed, suitably editing boot drive\IBMCOM\protocol.ini removing the tcpbeui lines and rebooting I got connection!
  This is confirmed for all three Windows computers: XP SP3, Vista laptop and the new 64 bit Windows 7 I'm working up to replace the XP.
Connecting to the OS/2 disks/volumes is 100%.  I test copied a folder with over 2000 files occupying about 25 MB and it came across in a jiff.
  However I can't print to the printers from any of the Windows computers.  When I do a test print you can see a brief Samba message popup saying various things are happening but no job appears in the OS/2 printer window; the printer light blinks hopefully but nothing prints.
  I used the appropriate Windows printer driver in the XP computer but a close model in the Win 7 computer which did not have the exact driver.  My printer is a Lexmark Optra E310.  With the LAN manager arrangement, which prints normally, I use the same driver and print to the IBM Null driver on the OS/2 computer.
  The installation gives one the option of creating a new Samba configuration from scratch or porting over one's IBM LAN Manager settings.  I chose the latter.
   I have not manually edited the smb.conf file which the installation produced.  Looking at it, from what I know and read up on, it looks correct.
   Can this problem be fixed?  It is almost a case of so near yet so far.  I'm thinking of a work around - installing a pdf create virtual printer and copying the pdf file so generated over to the OS/2 computer and using the OS/2 Acrobat to print from there.  Very inconvenient but a work around I can live with for a while.