Error while installing program

[Net Llama!]

On Fri, 30 Jun 2006, Mike Reinehr wrote:
> On Friday 30 June 2006 12:46 pm, Harry Giles wrote:
> > On Tuesday 27 June 2006 11:48 am, Mike Reinehr wrote:
> > > On Tuesday 27 June 2006 08:10 am, Harry Giles wrote:
> > > > I am trying to install  Xerox's print drive system for Linux, and when
> > > > running I get the following error:
> > > > sh setup.sh
> > > > uninstall: dynamic-link.h:57: elf_get_dynamic_info: Assertion `! "bad
> > > > dynamic ta                                        g"' failed.
> > > > setupdb-bin.WiRVAh: dynamic-link.h:57: elf_get_dynamic_info: Assertion
> > > > `! "bad d                                        ynamic tag"' failed.
> > > > Keeping existing configuration file.
> > > > Warning: LPP_Init() failed! Waiting 2 seconds...
> > > > Warning: LPP_Init() failed! Waiting 2 seconds...
> > > > Warning: LPP_Init() failed! Waiting 2 seconds...
> > > >
> > > >
> > > > Can anybody explain this to me in english?
> > > >
> > > > Harry G
> > >
> > > Harry,
> > >
> > > I can't help you with this specific problem, but I can help you with your
> > > Xerox printer. First, are you using CUPS? If so, there is no need to
> > > install Xerox's software. All you need to do is extract the appropriate
> > > PPD file from the Xerox archive, then use the lpadmin command to install
> > > a new printer using the PPD file, and your done.
> > >
> > > I've been using a Xerox DC425 & Debian Linux for several years with few
> > > problems.
> > >
> > > Hope this helps!
> > >
> > > cmr
> >
> > finally back and trying what you said.  I am not familiar with using
> > lpadmin. Can you give me an example on what to run?
> >
> > Thank you sir!
> >
> > Harry G
>
> No problem.
>
> It usually takes me a couple of tries to get it right. Here's a quick test
> that I just did, to be sure that I gave you a working example:
>
> lpadmin -p test_xerox -v lpd://alfheim/lp -D 'Xerox DC425ST' -E -L 'In the Office' -P xr_dc440.ppd
>
> In this example the printer name is test_xerox,
> the device uri is lpd://alfheim/lp (you can use a domain name or ip number),
> a description of the printer is 'Xerox DC425ST',
> -E enables the printer and accepts jobs,
> -L just provides a location, and
> xr_dc440.ppd is the name of the Post Script printer definition file (in the local directory).
>
> This uses the TCP/IP support that's built into my DC425ST and it's embedded lpr/lpd
> print spooler.
>
> If you make a mistake just run lpadmin -x test_xerox, to remove the
> new printer, and try again.
>
> odin# lpstat -t
> scheduler is running
> system default destination: ricoh
> device for arvak: lpd://arvak/lp
> device for ricoh: lpd://192.168.168.2/lp
> device for test_xerox: lpd://alfheim/lp
> device for xerox: lpd://alfheim/lp
> arvak accepting requests since Jan 01 00:00
> ricoh accepting requests since Jan 01 00:00
> test_xerox accepting requests since Jan 01 00:00
> xerox accepting requests since Jan 01 00:00
> printer arvak is idle.  enabled since Jan 01 00:00
> printer ricoh is idle.  enabled since Jan 01 00:00
> printer test_xerox is idle.  enabled since Jan 01 00:00
> printer xerox is idle.  enabled since Jan 01 00:00
>
> You also can use the http interface to configure CUPS, if you would
> prefer not to use the command line: http://localhost:631/
>
> One note, this use of lpadmin is predicated upon your having the
> Easy Software Products version of lp that comes with CUPS. It's been
> a long while since I used the UNIX version of lp and I don't remember
> how it works.
>
> Finally, I see that the newer Xerox printers list IPP as a supported protocol.
> If that's the case, you might not even have to install a printer locally. If you're
> using CUPS, then the Xerox might advertise itself as a CUPS device and your
> CUPS client would recognize it and use it.

I might be completely misunderstanding this issue, however on my FC box, I
ran into a similar problem a few months ago (CUPS didn't have a driver for
the printer I wanted to use, and Xerox/Tectronix had a ppd file on their
website).  All i needed to do was copy that ppd file into the directory
where CUPS kept its PPD files, and restart cups.  At that point, it was as
easy as just setting up a new printer.

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Lonni J Friedman                        netllama at linux-sxs.org
LlamaLand				http://netllama.linux-sxs.org