Subject: [os2genau_digest] No. 1981
From: Digest <deadmail>
To: "OS/2GenAu Digest"<deadmail>
Date: Fri, 2 Jul 2010 00:01:14 EST-10EDT,10,1,0,7200,4,1,0,7200,3600

**************************************************
Thursday 01 July 2010
 Number  1981
**************************************************

Subjects for today
 
1  Re:  USB Printer support (Was:(3rd. Option)) : Ed Durrant <edurrant at durrant dot mine dot nu>
2  Re:  USB Printer support (Was:(3rd. Option)) : Ed Durrant <edurrant at durrant dot mine dot nu>
3  Re:  USB Printer support (Was:(3rd. Option)) : Paul Smedley <paul at smedley dot id dot au>
4   eCS 2.0 GA pack arrived : Ed Durrant <edurrant at durrant dot mine dot nu>
5  Re:  eCS 2.0 GA pack arrived : Mike O'Connor <mikeoc at internode.on dot net>
6  Re:  USB Printer support (Was:(3rd. Option)) : Peter Moylan <peter at pmoylan dot org>
7   Fuji Xerox 3125N printer - SUCCESS : Peter Moylan <peter at pmoylan dot org>
8  Re:  Fuji Xerox 3125N printer - SUCCESS : Chuck McKinnis <mckinnis at sandia dot net>
9  Re:  Fuji Xerox 3125N printer - SUCCESS : Alan Duval <amoht at westnet dot com dot au>
10  Re:  Fuji Xerox 3125N printer - SUCCESS : Peter Moylan <peter at pmoylan dot org>
11  Re:  Fuji Xerox 3125N printer - SUCCESS : Peter Moylan <peter at pmoylan dot org>
12   eCS & wireless : Alan Duval <amoht at westnet dot com dot au>
13  Re:  eCS & wireless : Ed Durrant <edurrant at durrant dot mine dot nu>

**= Email   1 ==========================**

Date:  Thu, 01 Jul 2010 07:44:44 +1000
From:  Ed Durrant <edurrant at durrant dot mine dot nu>
Subject:  Re:  USB Printer support (Was:(3rd. Option))

Ed Durrant wrote:
> .
>
> As for OS/2 Network printing. I will assume you will be using LPD - to 
> do this go into TCPCFG2 (i.e. start TCPCFG2 at the commandline), go to 
> the printing tab and enter the required data (print server name and 
> printer queue name). 
Forgot to say if you want to avoid using a HOSTS files (as I expect you 
don't have a DNS) you should be able to put the print server (in the 
printer)'s IP address as the print server name.

> Now restart the system and in the printer setup folder when you add a 
> printer one of the possible ports should be LPD - if you look at its 
> properties it will be the same as you set in TCPCFG2. Now select the 
> correct printer driver and set up the printer like any other local 
> printer.
>
> Somewhere I think we need to start the LPR or LPD or SLPR service. - 
> Can someone clarify this please - is this the LPD in the autostart 
> services section of TCPCFG2 ??
>
>
>

-- 
Cheers/eCS2.0

Ed

Please checkout my podcasts at:
http://eComStationAustralia.podbean dot com or via iTunes
To subscribe - click this: http://eComStationAustralia.podbean dot com/feed

--------------------------------------------------
 
 http://www./melbpc/  -  The Melbourne OS/2 SIG
===
**= Email   2 ==========================**

Date:  Thu, 01 Jul 2010 08:15:26 +1000
From:  Ed Durrant <edurrant at durrant dot mine dot nu>
Subject:  Re:  USB Printer support (Was:(3rd. Option))

Peter Moylan wrote:
>
> The situation was that the printer had a preconfigured address of
> 169.254.212.83
> My router's DHCP server allocated an address of 192.168.1.3
>   
A printer should be configured with a static address, not have the 
router provide a DHCP one as it can change and when it does you'll have 
to change the setup on all of  the PCs printing to it. Yes, I know you 
can "lock" the DHCP server so that whenever it sees the printers MAC 
address it gives it the same IP address, but I prefer the KISS principal 
and set a fixed IP address, subnet mask  AND default route/gateway 
address in the printer itself.

> The Windows computer, whose address was 192.168.1.2, couldn't see it.
> That is so obviously on the same subnet that I have to put it down to
> Windows stupidity.
>   
That could be the windows firewall blocking the traffic on the ports 
being used to inquire for configuration data from the printer. If you 
can ping the printer but the printer install software can't see the 
printer, that is most likely what it is. the normal process here is to 
turn off the windows firewall for a few minutes while the install 
program works and turn it on again once the install is complete as the 
configuration inquiry command is normally only executed during initial 
setup.

> I then entered the MAC address in the Windows utility, plus the IP
> address 192.168.1.3 and the subnet mask 255.255.255.0. Now Windows could
> see it. The only new information was the MAC address.
> Finally, I changed the IP address to 192.168.1.250. Windows could still
> see it.
>
> In addition, Firefox on both the Windows machine and the OS/2 machine
> were able to view the printer status page on http://192.168.1.250.
> That's clear evidence that we were always on the same subnet.
>
>   
>> As for OS/2 Network printing. I will assume you will be using LPD -
>> to do this go into TCPCFG2 (i.e. start TCPCFG2 at the commandline),
>> go to the printing tab and enter the required data (print server name
>> and printer queue name). Now restart the system and in the printer
>> setup folder when you add a printer one of the possible ports should
>> be LPD - if you look at its properties it will be the same as you set
>> in TCPCFG2. Now select the correct printer driver and set up the
>> printer like any other local printer.
>>     
>
> Now we get to the tricky bit. I didn't know what to enter for the print
> server name and the printer queue name, so I entered "3125N" for both.
> When I rebooted there was no LPD among the port options.
>
>   
I'm sure someone will jump in here and correct me, and I know there is a 
simplified procedure but in any case you do need the print queue name - 
you can use the printers IP address for Print Server name I think.

Go into printers, pick a printer you have already installed (or install 
a dummy one if you have none so far - you can always delete it 
afterwards) go to its properties and the output port tab - what you are 
looking for is a printer icon with a sheet of paper behind it and 
\PIPE\LPD0 written below it. If this is missing , you'll need to click 
"Install new port" if you don't see a \Pipe|lpd0 port here, you can use 
the SLPR port instead - when you install this, it will also ask you for 
the print server name (use its IP address) and the print server queue 
name - this should be in the printers documentation somewhere - I've no 
doubt it will be in the Windoze printer config somewhere as well - but 
not sure where to look at the moment. Manufacturers tend to stick to the 
same queue name for all of their own printers, (except it seems 
Xerox!!!) searching the web for you, I found the following for Fuji Xerox:

http://www.brooksnet dot com/faq/210-04.html

You could try each of the options listed in turn, perhaps try RAW first, 
or if you access the printer management console in the printer from your 
browser - I would expect it to be shown there, somewhere.
 
> I have the impression that your instructions were for the "print
> sharing" option. I haven't yet had the courage to install Samba, so I'm
> not trying to create a workgroup.

No this is nothing to do with sharing the printer from the eCS system.

>  Instead, I'm trying to create a
> printer with a fixed IP address on the local subnet 192.168.1.*. So far,
> I haven't figured out how to do that.
>   
You will be able to do this through the printers management interface 
but of course as soon as you change it you will lose connectivity and 
have to connect to the new address. Chose an address outside of the 
range your router assigns (you'll need to log into the routers 
management web page to check this but my guess would be that it assigns 
addresses between 192.168.1.2 and 192.168.1.100 or so - so you could 
take for example 192.168.1.240 for the printer and be fairly sure it 
wont clash with an IP address assigned by the router !).

> (OK, I should try the help files. But I've already spent a solid hour on
> the Windows help files. It turns out that if you click "Help" on the
> Xerox driver, it makes you download a browser plugin that checks for a
> legal Windows installation, which in turn downloads another program that
> scans your hardware ... Big Brother is here already. After jumping
> through all these hoops, you get messages about what all the icons mean,
> which is no help at all. The Microsoft help articles allow you to
> respond that this was completely unhelpful, but the Xerox help files
> don't offer this option.)
>
>   

-- 
Cheers/eCS2.0

Ed

Please checkout my podcasts at:
http://eComStationAustralia.podbean dot com or via iTunes
To subscribe - click this: http://eComStationAustralia.podbean dot com/feed

--------------------------------------------------
 
 http://www./melbpc/  -  The Melbourne OS/2 SIG
===
**= Email   3 ==========================**

Date:  Thu, 01 Jul 2010 08:30:13 +0845
From:  Paul Smedley <paul at smedley dot id dot au>
Subject:  Re:  USB Printer support (Was:(3rd. Option))

Hi Peter,

Peter Moylan wrote:
> Ed Durrant wrote:
>> Peter Moylan wrote:
> Now we get to the tricky bit. I didn't know what to enter for the print
> server name and the printer queue name, so I entered "3125N" for both.
> When I rebooted there was no LPD among the port options.
> 
> I have the impression that your instructions were for the "print
> sharing" option. I haven't yet had the courage to install Samba, so I'm
> not trying to create a workgroup. Instead, I'm trying to create a
> printer with a fixed IP address on the local subnet 192.168.1.*. So far,
> I haven't figured out how to do that.
Go to the OS/2 printer object you've created for the new printer. On the 
Printer Properties page, there is 'Output Port'.  On this page you can
define the port to be printed to.

To install a new port 'Install New Port...'  SLPR is used to print to 
LPD printers - LPD Server is the IP of the printer, 'LPD Printer' is the 
name of the queue on the printer.  Hard to say what the name of the 
queue would be - on some older HP printers it used to be RAW

I'd concur with chuck that socket printing (printing to port 9100) is 
much easier to setup.  To check if the printer supports this type of 
printing, telnet to it on port 9100, ie 'telnet 192.168.1.250 9100' - if 
connection is accepted then the printer accepts this type of input.

For socket printing, all you need is the IP address - so I'd suggest 
taking a look at the ipspool package.

Hope this helps...

Paul.
--------------------------------------------------
 
 http://www./melbpc/  -  The Melbourne OS/2 SIG
===
**= Email   4 ==========================**

Date:  Thu, 01 Jul 2010 11:52:24 +1000
From:  Ed Durrant <edurrant at durrant dot mine dot nu>
Subject:   eCS 2.0 GA pack arrived

After all, it wasn't lost - just received my eCS 2.0 media pack, and yes 
Mensys kindly included a keyring and fob for me as well.

-- 
Cheers/eCS2.0

Ed

Please checkout my podcasts at:
http://eComStationAustralia.podbean dot com or via iTunes
To subscribe - click this: http://eComStationAustralia.podbean dot com/feed

--------------------------------------------------
 
 http://www./melbpc/  -  The Melbourne OS/2 SIG
===
**= Email   5 ==========================**

Date:  Thu, 01 Jul 2010 12:50:31 +1000
From:  Mike O'Connor <mikeoc at internode.on dot net>
Subject:  Re:  eCS 2.0 GA pack arrived

Ed Durrant wrote:
> After all, it wasn't lost - just received my eCS 2.0 media pack, and 
> yes Mensys kindly included a keyring and fob for me as well.
>
Hi Ed,

Welcome to the Keyring Club! 8-)

I'll soon be getting around to doing the real installation here after I 
clean out all the subsidiary stuff from all the old Beta2 /Beta3a 
/Beta4, RC1, RC2, RC3, RC4, RC5, RC6a, Silver (bis), and amalgamate all 
the mail off those too!!

Regards,
Mike

-- 
Failed the exam for
--------------------
MCSE - Minesweeper Consultant and Solitaire Expert
--------------------
Personal replies to any of : 
mikeoc (at) internode (dot) on (dot) net
mikeoc (at) austarnet (dot) com (dot) au
majilok (at) gmail (dot) com
[Please ZIP any attachments, other than GIF/JPG or plain-text]
If you are missing a response from me - check Tweed Heads WX status at:
http://www.bom.gov.au/products/IDR663.loop.shtml#skip

--------------------------------------------------
 
 http://www./melbpc/  -  The Melbourne OS/2 SIG
===
**= Email   6 ==========================**

Date:  Thu, 01 Jul 2010 14:24:52 +1000
From:  Peter Moylan <peter at pmoylan dot org>
Subject:  Re:  USB Printer support (Was:(3rd. Option))

Paul Smedley wrote:
>
> I'd concur with chuck that socket printing (printing to port 9100) is
> much easier to setup.  To check if the printer supports this type of
> printing, telnet to it on port 9100, ie 'telnet 192.168.1.250 9100' -
> if connection is accepted then the printer accepts this type of input.
>
> For socket printing, all you need is the IP address - so I'd suggest
> taking a look at the ipspool package.
>
Thanks to both you and Chuck for this suggestion. It worked beautifully,
in a sense. The printer does indeed respond to a telnet connection on
port 9100. IPSpool was a lot easier to configure than I expected. Once I
had configured it and started it, and tried to print a text document,
the expected message from IPSpool popped up, and everything seemed to
happen correctly.

Unfortunately, no printed page popped out of the printer. Since the
printer is in another room while it's connected to the router, I had no
way of seeing whether the printer light flickered. (If it did, the error
could be something as simple as a missing or extra ctrl-D.) I'll try to
repeat the experiment when I have a friend with me to look at the light.

For now, I've (temporarily) given up on network printing, and have gone
back to a parallel port connection - see separate e-mail about this It
sounds as if I need to work up in complexity gradually.

-- 
Peter Moylan                          peter at pmoylan dot org
                                      http://www.pmoylan dot org

--------------------------------------------------
 
 http://www./melbpc/  -  The Melbourne OS/2 SIG
===
**= Email   7 ==========================**

Date:  Thu, 01 Jul 2010 14:35:24 +1000
From:  Peter Moylan <peter at pmoylan dot org>
Subject:   Fuji Xerox 3125N printer - SUCCESS

I have now connected my new laser printer via a parallel port printer
cable. With this configuration, it worked immediately.

I still have to get the USB and the network options working, but at
least I have confirmed that this printer works using the OS/2 Postscript
printer driver. Anyone who's been waiting on my tests before deciding
whether they can safely buy the printer can now go ahead while
Officeworks has it at a very low price. If you want an affordable
black-and-white laser printer that's OS/2 compatible, this is it. (And,
now that I have it working with a simple interface, I'm confident that
I'll eventually also get it working as a network printer. Firefox can
already see it on my LAN.)

The printing isn't quite as black as I would have liked, but maybe
that's because I didn't shake the toner cartridge hard enough before
installing it. The setup instructions aren't very clear about this.

One observation: this printer supports both Postscript 3 and PCL 6. I'm
using a Postscript driver, but the Windows device driver for this
printer defaults to PCL. Does anyone know whether this would be a better
choice (less overhead, or something like that)? And, if I want to test
with PCL, is this best done with an HP LaserJet printer driver?

-- 
Peter Moylan                          peter at pmoylan dot org
                                      http://www.pmoylan dot org

--------------------------------------------------
 
 http://www./melbpc/  -  The Melbourne OS/2 SIG
===
**= Email   8 ==========================**

Date:  Wed, 30 Jun 2010 23:21:04 -0600
From:  Chuck McKinnis <mckinnis at sandia dot net>
Subject:  Re:  Fuji Xerox 3125N printer - SUCCESS

I just happen to always use Postscript drivers even though I have a HP 
and a Lexmark that support PCL6.  I feel that Postscript is just not as 
"proprietary" as PCL6.

On 6/30/2010 10:35 PM, Peter Moylan wrote:
> I have now connected my new laser printer via a parallel port printer
> cable. With this configuration, it worked immediately.
>
> I still have to get the USB and the network options working, but at
> least I have confirmed that this printer works using the OS/2 Postscript
> printer driver. Anyone who's been waiting on my tests before deciding
> whether they can safely buy the printer can now go ahead while
> Officeworks has it at a very low price. If you want an affordable
> black-and-white laser printer that's OS/2 compatible, this is it. (And,
> now that I have it working with a simple interface, I'm confident that
> I'll eventually also get it working as a network printer. Firefox can
> already see it on my LAN.)
>
> The printing isn't quite as black as I would have liked, but maybe
> that's because I didn't shake the toner cartridge hard enough before
> installing it. The setup instructions aren't very clear about this.
>
> One observation: this printer supports both Postscript 3 and PCL 6. I'm
> using a Postscript driver, but the Windows device driver for this
> printer defaults to PCL. Does anyone know whether this would be a better
> choice (less overhead, or something like that)? And, if I want to test
> with PCL, is this best done with an HP LaserJet printer driver?
>

-- 
Chuck McKinnis
Sandia Park, NM
http://www.7cities dot net/~mckinnis/
But he was wounded for our transgressions, he was bruised for our 
iniquities: the chastisement of our peace was upon him; and with his 
stripes we are healed. Isaiah 53:5

--------------------------------------------------
 
 http://www./melbpc/  -  The Melbourne OS/2 SIG
===
**= Email   9 ==========================**

Date:  Thu, 01 Jul 2010 16:39:06 +1000
From:  Alan Duval <amoht at westnet dot com dot au>
Subject:  Re:  Fuji Xerox 3125N printer - SUCCESS

Peter Moylan wrote:
> I have now connected my new laser printer via a parallel port printer
> cable. With this configuration, it worked immediately.
>
> I still have to get the USB and the network options working, but at
> least I have confirmed that this printer works using the OS/2 Postscript
> printer driver. Anyone who's been waiting on my tests before deciding
> whether they can safely buy the printer can now go ahead while
> Officeworks has it at a very low price. If you want an affordable
> black-and-white laser printer that's OS/2 compatible, this is it. (And,
> now that I have it working with a simple interface, I'm confident that
> I'll eventually also get it working as a network printer. Firefox can
> already see it on my LAN.)
>
> The printing isn't quite as black as I would have liked, but maybe
> that's because I didn't shake the toner cartridge hard enough before
> installing it. The setup instructions aren't very clear about this.
>
> One observation: this printer supports both Postscript 3 and PCL 6. I'm
> using a Postscript driver, but the Windows device driver for this
> printer defaults to PCL. Does anyone know whether this would be a better
> choice (less overhead, or something like that)? And, if I want to test
> with PCL, is this best done with an HP LaserJet printer driver?
>   
That's heartening Peter. I'll connect mine up over the weekend via a 
parallel cable
and hopefully get the printer to work with my system.
Is there a specific postscript driver to use or are postscript drivers  
generic?.
Also do I have to install a  ppd driver?
I take it that the standard printer setup in eCS is what I should follow.

Regards,

Alan Duval
--------------------------------------------------
 
 http://www./melbpc/  -  The Melbourne OS/2 SIG
===
**= Email   10 ==========================**

Date:  Thu, 01 Jul 2010 17:33:49 +1000
From:  Peter Moylan <peter at pmoylan dot org>
Subject:  Re:  Fuji Xerox 3125N printer - SUCCESS

Peter Moylan wrote:
> I have now connected my new laser printer via a parallel port printer
>  cable. With this configuration, it worked immediately.
>
USB printing still a total failure, though. I went right back to
scratch, deleted USB printer from the available set of ports, deleted
3125N Postscript printer driver, leaving IBMNULL as the only installed
printer driver. Made sure that printer was connected and powered up.
Made sure that CONFIG.SYS contained all the right stuff.

Rebooted, then ran the "Printer driver import utility" to create a new
3125N PS printer driver. Installed a new printer object, then opened its
properties, went to the Output Port page, chose "Install New Port",
selected "USB", clicked "Install".

That's where it goes wrong. There's an error message "No new USB
printers found, a new USB port not created." The system is simply not
seeing the printer, even though it's powered up and connected.

The "USBPRT Auto monitor" is being run from the Startup folder, by the way.

Just before mailing this I tried connecting to a different USB
interface, the one I usually plug my key drive into. It didn't help.

-- 
Peter Moylan                          peter at pmoylan dot org
                                      http://www.pmoylan dot org

--------------------------------------------------
 
 http://www./melbpc/  -  The Melbourne OS/2 SIG
===
**= Email   11 ==========================**

Date:  Thu, 01 Jul 2010 17:44:07 +1000
From:  Peter Moylan <peter at pmoylan dot org>
Subject:  Re:  Fuji Xerox 3125N printer - SUCCESS

Alan Duval wrote:
> Peter Moylan wrote:
>> I have now connected my new laser printer via a parallel port printer
>> cable. With this configuration, it worked immediately.
>>
>>
>>   
> That's heartening Peter. I'll connect mine up over the weekend via a
> parallel cable
> and hopefully get the printer to work with my system.
> Is there a specific postscript driver to use or are postscript
> drivers  generic?.
> Also do I have to install a  ppd driver?
> I take it that the standard printer setup in eCS is what I should follow.

The PPD file you need is on the Windows XP installtion CD, with the name
"XP3125.ppd". (There are 30 copies of this on the CD, but I'm pretty
sure they're all identical.)

To install, open the "Printers" folder, which is inside the "Local
System" folder on your desktop. Run the "Printer driver import utility",
and choose the option "Import Postscript Printer Description". Then
point it to the above-mentioned PPD file. At the end of this, you'll
find that you have a new "Xerox Phaser 3125 PS" driver in your list of
printer drivers that may be installed. It's actually a copy of the
generic Postscript driver, but with embedded knowledge of which options
the 3125 supports.

Next, run "Install Printer" from the Printers folder. From there it will
probably be obvious, since you now have the right printer driver in the
list of drivers that you have to choose from, but ask again if anything
is unclear.

As I've said elsewhere, I'm having no luck at all installing it as a USB
printer, and I still have to figure out how to install it as a network
printer; but if you're happy with a simple parallel port interface, that
works just fine.

-- 
Peter Moylan                          peter at pmoylan dot org
                                      http://www.pmoylan dot org

--------------------------------------------------
 
 http://www./melbpc/  -  The Melbourne OS/2 SIG
===
**= Email   12 ==========================**

Date:  Thu, 01 Jul 2010 19:08:54 +1000
From:  Alan Duval <amoht at westnet dot com dot au>
Subject:   eCS & wireless

Peter mentions wanting to get a printer that works via wireless.
I didn't know that eCS supported wireless connections.
Is there any info that I can read about this?

Regards,

Alan Duval
--------------------------------------------------
 
 http://www./melbpc/  -  The Melbourne OS/2 SIG
===
**= Email   13 ==========================**

Date:  Thu, 01 Jul 2010 20:18:26 +1000
From:  Ed Durrant <edurrant at durrant dot mine dot nu>
Subject:  Re:  eCS & wireless

Alan Duval wrote:
> Peter mentions wanting to get a printer that works via wireless.
> I didn't know that eCS supported wireless connections.
> Is there any info that I can read about this?
>
> Regards,
>
> Alan Duval
>
 From a printer set up point of view, whether the network is wired or 
wireless makes no difference - once the wireless link is in place, when 
the printer queue looks for a specific network printer name and hence IP 
address, it talks to it.

-- 
Cheers/eCS2.0

Ed

Please checkout my podcasts at:
http://eComStationAustralia.podbean dot com or via iTunes
To subscribe - click this: http://eComStationAustralia.podbean dot com/feed

--------------------------------------------------
 
 http://www./melbpc/  -  The Melbourne OS/2 SIG
===