SEO

Hi Guys,

totally stuck here. Got two Ultra 10's running sol10 for web development
and serving a small website/mysql database via Apache. As a newbie and
after reading dozens of how-to's etc got all this working and felt
proud, coming from a Win background.

What I AM stumped with is getting either of the Ultra boxes to print to
a Laserjet5 with a jetdirect card. I've searched google, read the Sun
Big Admin document, spent all afternoon on HP's site and drawn a blank.
It seems Jetadmin software is the way to go (according to suns bigadmin
document). It seems Jetadmin solaris support ended with v8 or v9
(according to which document you believe on HP's site)

Please, please can someone point me to a Step by Step guide to enable my
Ultras to communicate with the Laserjet.

On windows, a wizard basically asked, a)what printer is it, b)whats its
IP addy, c) it then worked....... Why is it so complex on Solaris??

Many thanks,

Adrian

Adrian wrote:

> Hi Guys,
>
> totally stuck here. Got two Ultra 10's running sol10 for web development
> and serving a small website/mysql database via Apache. As a newbie and
> after reading dozens of how-to's etc got all this working and felt
> proud, coming from a Win background.
>
> What I AM stumped with is getting either of the Ultra boxes to print to
> a Laserjet5 with a jetdirect card. I've searched google, read the Sun
> Big Admin document, spent all afternoon on HP's site and drawn a blank.
> It seems Jetadmin software is the way to go (according to suns bigadmin
> document). It seems Jetadmin solaris support ended with v8 or v9
> (according to which document you believe on HP's site)
>
> Please, please can someone point me to a Step by Step guide to enable my
> Ultras to communicate with the Laserjet.
>
> On windows, a wizard basically asked, a)what printer is it, b)whats its
> IP addy, c) it then worked....... Why is it so complex on Solaris??
>
> Many thanks,
>
> Adrian

HP's Jetadmin works on Solaris 9 as well as Solaris 8. It may not be
"supported" but it works. I'd go ahead and try it on 10. But first,
try Solaris native HP support. S10 let me pick my HP-LJ4000 off a menu.
Yours might be on the menu too. (I did the FULL install; if you did
not, you may have to install whatever package(s) implement HP support.
(Lots of luck figuring out what they're called. . . . That's one reason
WHY I did the full install.)

As to why it's so complex I can only guess, but Solaris, and unix in
general, comes from an era in which there were no such things as
standards. No two video terminals, even different models from the same
manufacturer, were compatible with each other. No two printers accepted
the same codes for anything. Unix was built to support just about any
random printer or video terminal. The complexity is part of the price
for being able to use a few hundred different "standards".

Later on, ANSI X3-64 prescribed standards for terminals and printers.
IBM and HP ignored them but didn't agree with each other. . . . Digital
implemented the standards (with some additions of their own) VT100 et.
seq. and their LN series of laser printers (LN03, LN05....) but nobody
else did.

On 2006-08-22 00:09:46 +0100, Adrian <ady_hume@hotmail.com> said:

> On windows, a wizard basically asked, a)what printer is it, b)whats its
> IP addy, c) it then worked....... Why is it so complex on Solaris??

It's complicated because HP didn't employ a team of 10 people to write
the code to support it for Solaris.

--tim

On 2006-08-22, Tim Bradshaw <tfb@tfeb.org> wrote:
> On 2006-08-22 00:09:46 +0100, Adrian <ady_hume@hotmail.com> said:
>
>> On windows, a wizard basically asked, a)what printer is it, b)whats its
>> IP addy, c) it then worked....... Why is it so complex on Solaris??
>
> It's complicated because HP didn't employ a team of 10 people to write
> the code to support it for Solaris.

The Windows situation is *slightly* more complicated, because so
far as Windows is concerned a network printer isn't a network printer
unless it's an SMB printer, otherwise it's a local printer even if
it's a network printer. Grrrrrr.

--
"Other people are not your property."
[email me at huge [at] huge [dot] org [dot] uk]

On Tue, 22 Aug 2006 00:09:46 +0100, Adrian <ady_hume@hotmail.com> wrote:

>What I AM stumped with is getting either of the Ultra boxes to print to
>a Laserjet5 with a jetdirect card. I've searched google, read the Sun
>Big Admin document, spent all afternoon on HP's site and drawn a blank.
>It seems Jetadmin software is the way to go (according to suns bigadmin
>document). It seems Jetadmin solaris support ended with v8 or v9
>(according to which document you believe on HP's site)

I have never used the HP Jetdirect software. It's not necessary either.
JetDirect cards speak the Unix lpr/lpd protocol, so you can point your
AdminTool (or whatever it is called in this version) to the printer's IP
address. Use raw as queue name.

Mit freundlichen Grüßen

Frank-Christian Krügel

Adrian wrote:

> totally stuck here. Got two Ultra 10's running sol10 for web development
> and serving a small website/mysql database via Apache. As a newbie and
> after reading dozens of how-to's etc got all this working and felt
> proud, coming from a Win background.
>
> What I AM stumped with is getting either of the Ultra boxes to print to
> a Laserjet5 with a jetdirect card. I've searched google, read the Sun
> Big Admin document, spent all afternoon on HP's site and drawn a blank.
> It seems Jetadmin software is the way to go (according to suns bigadmin
> document). It seems Jetadmin solaris support ended with v8 or v9
> (according to which document you believe on HP's site)
>
> Please, please can someone point me to a Step by Step guide to enable my
> Ultras to communicate with the Laserjet.
>
> On windows, a wizard basically asked, a)what printer is it, b)whats its
> IP addy, c) it then worked....... Why is it so complex on Solaris??

Its not AS complicated on Solaris 10 (as it was years ago). man
printmgr for info.
The printmgr interface is somewhat Wizard-like ..
Just run it as root and set things up for ppd files with the
description
file that matches up with your "Laserjet5" - there seems to be many : /

Adrian wrote:
> Hi Guys,
>
> totally stuck here. Got two Ultra 10's running sol10 for web development
> and serving a small website/mysql database via Apache. As a newbie and
> after reading dozens of how-to's etc got all this working and felt
> proud, coming from a Win background.
>
> What I AM stumped with is getting either of the Ultra boxes to print to
> a Laserjet5 with a jetdirect card. I've searched google, read the Sun
> Big Admin document, spent all afternoon on HP's site and drawn a blank.
> It seems Jetadmin software is the way to go (according to suns bigadmin
> document). It seems Jetadmin solaris support ended with v8 or v9
> (according to which document you believe on HP's site)
>
> Please, please can someone point me to a Step by Step guide to enable my
> Ultras to communicate with the Laserjet.
>
> On windows, a wizard basically asked, a)what printer is it, b)whats its
> IP addy, c) it then worked....... Why is it so complex on Solaris??
>
> Many thanks,
>
> Adrian


Complex no , badly documented - yes .

replace the IP adress below with your printers.
9100 is the TCP port used by jetdirect hardware


# lpadmin -p hp5000 -v /dev/null -m netstandard_foomatic \
-n
/usr/lib/lp/model/ppd/system/foomatic/HP/HP-LaserJet_5000-Postscript.ppd.gz
\
-o dest=192.168.1.253:9100 -o protocol=tcp -I postscript -T PS


# accept hp5000

# enable hp5000

//lars

Frank-Christian Kruegel wrote:
> On Tue, 22 Aug 2006 00:09:46 +0100, Adrian <ady_hume@hotmail.com> wrote:
>
>> What I AM stumped with is getting either of the Ultra boxes to print to
>> a Laserjet5 with a jetdirect card. I've searched google, read the Sun
>> Big Admin document, spent all afternoon on HP's site and drawn a blank.
>> It seems Jetadmin software is the way to go (according to suns bigadmin
>> document). It seems Jetadmin solaris support ended with v8 or v9
>> (according to which document you believe on HP's site)
>
> I have never used the HP Jetdirect software. It's not necessary either.

The HP software is good if you want to do nice things like duplex, 2up
and 4up pages. The print driver allows you to pass options to lp to
change the output format. So its not necessary, but it is much better
for printing.

John

> JetDirect cards speak the Unix lpr/lpd protocol, so you can point your
> AdminTool (or whatever it is called in this version) to the printer's IP
> address. Use raw as queue name.
>
> Mit freundlichen Grüßen
>
> Frank-Christian Krügel

Many thanks to all. Printing from both Ultra's is now fine.

Lars summed it up in a nutshell, not complex but poorly documented.

Got there in the end.

Adrian


Adrian wrote:
> Hi Guys,
>
> totally stuck here. Got two Ultra 10's running sol10 for web development
> and serving a small website/mysql database via Apache. As a newbie and
> after reading dozens of how-to's etc got all this working and felt
> proud, coming from a Win background.
>
> What I AM stumped with is getting either of the Ultra boxes to print to
> a Laserjet5 with a jetdirect card. I've searched google, read the Sun
> Big Admin document, spent all afternoon on HP's site and drawn a blank.
> It seems Jetadmin software is the way to go (according to suns bigadmin
> document). It seems Jetadmin solaris support ended with v8 or v9
> (according to which document you believe on HP's site)
>
> Please, please can someone point me to a Step by Step guide to enable my
> Ultras to communicate with the Laserjet.
>
> On windows, a wizard basically asked, a)what printer is it, b)whats its
> IP addy, c) it then worked....... Why is it so complex on Solaris??
>
> Many thanks,
>
> Adrian

On Tue, 22 Aug 2006 09:20:01 +0000, Huge wrote:

> On 2006-08-22, Tim Bradshaw <tfb@tfeb.org> wrote:
>> On 2006-08-22 00:09:46 +0100, Adrian <ady_hume@hotmail.com> said:
>>
>>> On windows, a wizard basically asked, a)what printer is it, b)whats its
>>> IP addy, c) it then worked....... Why is it so complex on Solaris??
>>
>> It's complicated because HP didn't employ a team of 10 people to write
>> the code to support it for Solaris.
>
> The Windows situation is *slightly* more complicated, because so
> far as Windows is concerned a network printer isn't a network printer
> unless it's an SMB printer, otherwise it's a local printer even if
> it's a network printer. Grrrrrr.

Ah, though I've configured them I didn't know why I had to
choose local then create a TCP/IP network port.