Printing to Network Printer?

@chris
ipq -p -P http://192.168.1.3/

freezes my system rather often

I have seen it saying it could not access ipp.template(?) and that probably HHOME env variable is not set (I realisnow that was when it was in ram: )



I checked with my printer page, almost all protocols including lpd, raw and ipp are enabled, for ipp the ports are 631 and 80

@JosDuchIt

Right, yes, there's some other stuff you have to do to get ipq (and probably ipr) to work. I'm not sure how useful it will be in that case, but basically:
copy ipp-template ENVARC:.ipp-template
edit ENVARC:.ipp-template
Set printer-uri to your printer. I had to set mine to the actual printer, ie. http://demeter:631/printers/hp-LaserJet-1015, so you probably need http://192.168.1.3:631/ipp
Uncomment the requesting-user-name line and change it if you like.

It doesn't query the printer unless the printer-uri line is correct, no matter what you specify on the command line, which is why I think it's not particulary helpful.

You could give it a try anyway, it should spew out a load of text if it is working.

You're not using a wireless network by any chance?

@Chris
- My printer is connected to the router with an ethernet cable
- my sams are connected both wifi (2 Netgear WNC2001 units)

i followed your instructions, 'requesting user-name' was commented out by default. I also copied ipp-template to env: too
as i had still crashes renamed ipp-template in the ipr folder.

ipq still crashes. :(

I could send you the crashlogs?

@JosDuchIt

I had problems with lpr device on SAM, because there was no PAR device in DEVS:

Get it from Storage and try again

Luca

@JosDuchIt

Quote:

I ask because I had problems when my SAM was on 802.11a, I had an 802.11a/b/g router and the device I was connecting to was using an 802.11n dongle. I doubt that's the issue here if the printer is wired in (it was the 802.11n dongles causing my problems).

Quote:

Did you call it ENVARC:.ipp-template? The initial dot is important.

It also needs to have the printer-uri section modified.

Quote:

Probably of limited usefulness, the crashing is within the voodoo CUPS library I think. If it is crashing any amount of fixing isn't going to make it print, as when it works it doesn't crash, if that makes sense

@Ricossa

That was a hit, imoved it in
and
echo prt: "something"
at least brougth some life in the printer (a number of empty pages were produced;
edit:
Sadly not pertinent for ipp.device: the printer prefs were set on netprinter.device ,

I've just realised it might be looking in ENVARC: because I have a HOME env-var pointing to ENVARC:, so you might want to try creating one of those too.

@chris
Never succeded to avoid a crash
i have been using
ipq -t .ipp-template -p -P http://192.168.1.3/ipp
after eliminating all concerned env variables
No complaint though, just a crash

And you've put that same URL in .ipp-template as printer-uri?

@ chris
yes indeed: i copied the file back from envarc:
ipq accepts a number if variants for the printer-uri without complaining;, may complain about not finding the .ipp-template, but f he finds it and accepts the uri: always a crash


Note all tests till now on the sam 460ex

Hmm, I'm out of ideas, but given you're having problems with both LPR and IPP it sounds suspiciously similar to the problem I was having connecting between various devices on my wireless network. Can you wire the Amiga to the router with a cable temporarily, to see if you get the same problems?

@all
i have restarted my tests now with the 440ep.
Hoepfully i learned something and get it right now
Starting with lpr.device first
@Iazi
@jbni
The docs explain you should remap parallel.device to lpr.device
I don't have parallel.device on my SAM's OS4.1, (allthough there is a PAR1 DOSdriver) Where should it come from ?

@JosDuchIt

You don't need to do that remapping, just set whatever device you're using in printer prefs.

>
@Chris
thanks

i could get the printer to respond using
>setenv SAVE lpr.device HOST=192.168.1.3 RAW PORT=9100
>echo >prt: "hello printer"

a number of pages were spit out, but no printing
The printer prefs are set up with Printerdriver PostScript and Port device lpr.device


> copy thisfile.ps prt:
results in a 1 blank page

@JosDuchIt

Quote:

That will convert your PostScript file to PostScript before it gets to the printer

If it was working, you'd probably end up with the text of the original PostScript being printed out. You should be copying to LPR: or whatever device is set up with port-handler and lpr.device.

But it's clearly not working anyway. Have you tried directly cabling everything yet?

@chris
i used
> copy thisfile.ps lpr:
with the sameeffect : a blank page printed.
Quote:
No i did not.

The printer is connected to the router with an ethernet cable downstairs, and it is used most by my wife .

The installation was done with her laptop (Windows 7)
Could it be a windows problem?

@JosDuchIt

No, but it could be a WiFi network problem.

@Chris

I am going to test it with my SAM440ep which has two material ethernet ports
the printer has one and the router one too

i understand that they can't be used at the same time and i am not sure how they coud be used in this printing context.

I guess i could just plainly connect the printer to one of SAM4's port. Do i need a crossover connecting cable to do that?

@Chris

On my Sam 460 I had to do the remapping and to mount par: (including parallel.device). Else I could only print one page befor getting a full crash.
In Printer Prefs I have (both X-1000 and SAM) :

postscript, directing to parallel.device, port 0
(I think on SAM it is a1parallel.device or something like this)

In the postscript preferences, I had to select Direct printing

(I am not sure for the exact wording, as I use the french locale)

Using lpr.device with redirecting from parallel.device (not using lpr.device directly)

I have to apologize. I just checked my SAM460 and indeed printer-prefs point to lpr.device BUT I had to put PAR from storage into devs/dosdrivers in order to get it working.
On the X-1000 I have everything as stated above