🚀 go-pugleaf

Terryc <newsfourspam-spam@woa.com.au> writes:

>And no, I don't want the brainless twit suggestion of upgrading to the 
>latest linux printing bloatware. This is a postscript printer dammit, it 
>shoud just work under linux lprng.

But Cups _does_ support the IBM Infoprint 20. PostScript PDL isn't
everything you know; the host still has to get the data to the
printer somehow.

Try this: ftp://service.boulder.ibm.com/printers/specs/410linuxreadme.pdf

Nick.

Nick Andrew wrote:
> Terryc <newsfourspam-spam@woa.com.au> writes:
> 
>> And no, I don't want the brainless twit suggestion of upgrading to the 
>> latest linux printing bloatware. This is a postscript printer dammit, it 
>> shoud just work under linux lprng.
> 
> But Cups _does_ support the IBM Infoprint 20. PostScript PDL isn't
> everything you know; the host still has to get the data to the
> printer somehow.

That is the problem, it isn't.
> 
> Try this: ftp://service.boulder.ibm.com/printers/specs/410linuxreadme.pdf

Confirms my suspiscions that IBM has once again developed a proprietary 
comms method rather than just use a *nix standard like everyone else has 
for twenty years.

Hopefully, it is a simply port redirection.

Terryc wrote:
> Nick Andrew wrote:
>> Terryc <newsfourspam-spam@woa.com.au> writes:
>>
>>> And no, I don't want the brainless twit suggestion of upgrading to 
>>> the latest linux printing bloatware. This is a postscript printer 
>>> dammit, it shoud just work under linux lprng.
>>
>> But Cups _does_ support the IBM Infoprint 20. PostScript PDL isn't
>> everything you know; the host still has to get the data to the
>> printer somehow.
> 
> That is the problem, it isn't.

and the problem was instead of the line (in /etc/printcap)
	:rp=lp:\
it should be
	:rp=PASS:\

and it works for postscript and pcl.

No it`s not plug and play you dumbfuck.
It`s help to fix what doesn`t work.

It`s all free (so far) your contribution is always helpful!

"Terryc" <newsfourspam-spam@woa.com.au> wrote in message 
news:hkt3h7$b5b$1@speranza.aioe.org...
> Looking for clubies on getting an IBm Info printer 20 running under Linux 
> Debian with lprng.
>
> Basically it has postscript so there shouldn't be any problems, but zip, 
> zilch nothing from it thru it or out of it in relationship to linux.
>
> Basically a hand me down  that floated around as ballast in the vehicle 
> until the HP4v said it might need a couple of parts replacing. bugger 
> that, sothe Infoprt was lugged into the print area and connected up via 
> its TCP/IP jack.
>
> arp -s <ip-number> mac-address and various linx boxen were happily 
> piniging it. No luck with web interface, as it has a password set and 
> search engines don't return any concept of a default pass words for it.
>
> Investigate front panel and find I can set ip, netmask and gateway there, 
> so problem is solved.
>
> Rolled printool and zip, zilch nothing.
>
> Treid a second config on /dev/lp0 and after nothing thru the printtol 
> config, tried direct feeding various file thru /dev/lp0 and again zip 
> zilch nothing, Not a squark from printer.
>
> Meanwhile did the fudge config of a remote (non-workgrp) printer under 
> win2000 and ye olde test page is barfed up by printer with out a blink,
>
> Sigh, looking for clubies.
>
> And no, I don't want the brainless twit suggestion of upgrading to the 
> latest linux printing bloatware. This is a postscript printer dammit, it 
> shoud just work under linux lprng.
>
> T.I.A. 

none wrote:
> No it`s not plug and play you dumbfuck.
> It`s help to fix what doesn`t work.
> 

I take it you drew a total zilch at the pick up bar last night.

> It`s all free (so far) your contribution is always helpful!

Yep, try to post the fix when I find it.

"Terryc" <newsfourspam-spam@woa.com.au> wrote in message 
news:hlkku0$dah$4@speranza.aioe.org...
> none wrote:
>> No it`s not plug and play you dumbfuck.
>> It`s help to fix what doesn`t work.
>>
>
> I take it you drew a total zilch at the pick up bar last night.
>

Got @ root
then entered an account.
Floppy was difficult at first
needed a command prompt.
Once instructed it went straight in.

>> It`s all free (so far) your contribution is always helpful!
>
> Yep, try to post the fix when I find it.

<read above>