Printing to network printer.

[Stuart]

For years I have used a shared printer on a PC for printing from Risc OS

I was using Lanman98, now I am trying to use Omni on an Iyonix

The pathname I was using from Lanman, in the printer connection dialogue,
"file" was

Lanman98#printer;Chopin;Dell2330:

Where Chopin is the name of the PC with the shared printer and Dell 2330
the printer.

When I tried this, Omni complained about a wildcard, presumably the #. I
removed the # but my printout just disappeared. What is the correct
path I should type into the "File" dialogue to be able to print?

--
Stuart Winsor

Tools With A Mission
sending tools across the world
http://www.twam.co.uk/

[Richard Darby]

In article <57909a5d...@argonet.co.uk>,

Stuart <Spa...@argonet.co.uk> wrote:
> For years I have used a shared printer on a PC for printing from Risc OS

> I was using Lanman98, now I am trying to use Omni on an Iyonix

> The pathname I was using from Lanman, in the printer connection dialogue,
> "file" was

> Lanman98#printer;Chopin;Dell2330:

> Where Chopin is the name of the PC with the shared printer and Dell 2330
> the printer.

> When I tried this, Omni complained about a wildcard, presumably the #. I
> removed the # but my printout just disappeared. What is the correct
> path I should type into the "File" dialogue to be able to print?

I don't use this method myself, but looking at the Lanman98 help, I am
wondering if a recent update of windows has changed the printer share for
Dell2330 and unshared it. Worth a check.

The syntax of the command looks ok to me.

Richard Darby.

--

Richard Darby.
website: http://www.rjdarby.co.uk
Do not reply to this address all mail is deleted.
Reply to: <my first name> at <my domain>

[Stuart]

In article <5790a7e...@rjdarby.co.uk>,

Richard Darby <ne...@rjdarby.co.uk> wrote:
> I don't use this method myself, but looking at the Lanman98 help, I am
> wondering if a recent update of windows has changed the printer share for
> Dell2330 and unshared it. Worth a check.

Lanman is fine and working well with my ARMX6, the issue lies with !Omni.

In any case, the printer is shared from my WXP machine so not really
subject to the issues W10 has.

[Steve Fryatt]

On 6 Mar, Stuart wrote in message
<57909a5d...@argonet.co.uk>:

> The pathname I was using from Lanman, in the printer connection dialogue,
> "file" was
>
> Lanman98#printer;Chopin;Dell2330:
>
> Where Chopin is the name of the PC with the shared printer and Dell 2330
> the printer.
>
> When I tried this, Omni complained about a wildcard, presumably the #. I
> removed the # but my printout just disappeared. What is the correct
> path I should type into the "File" dialogue to be able to print?

The RO5 User Guide[1] says:

OmniPrint#FilingSystem;Server;Printer;User;Password;Options;Size:

or, more specifically, perhaps:

OmniPrint#LanMan;Chopin;Dell2330;User;Password;Options;Size:

The User, Password, Options and Size fields are optional.


1. It's worth getting a copy; I'm finding myself referring to it more that
I'd expected...

--
Steve Fryatt - Leeds, England

http://www.stevefryatt.org.uk/

[Chris Newman]

In article <57909a5d...@argonet.co.uk>,
Stuart <Spa...@argonet.co.uk> wrote:

> For years I have used a shared printer on a PC for printing from Risc OS

> I was using Lanman98, now I am trying to use Omni on an Iyonix

> The pathname I was using from Lanman, in the printer connection dialogue,
> "file" was

> Lanman98#printer;Chopin;Dell2330:

I now have a Dell 2330dn & can use it directly from my RiscPC using
PostScript 3 printer driver from Martin Würthner & John Tytgat. RiscOS also
comes with PostScript 2 if you don't want to fork out any loot. It was a
doddle to set up. Therefore why not forget networking & go direct?

--
Chris Newman

[Stuart]

In article <mpro.pnyv4z02...@stevefryatt.org.uk>,

Steve Fryatt <ne...@stevefryatt.org.uk> wrote:

> or, more specifically, perhaps:

> OmniPrint#LanMan;Chopin;Dell2330;User;Password;Options;Size:

Thanks but LanMan isn't, as yet, installed on this Iyo. I understood that
the latest !Omni was more capable than !LanMan so just stuck with the
installed !Omni.

I simply replaced Lanman with Omni in the original path. Thus instead of

Lanman98#printer;Chopin;Dell2330:

Which works with Lanman installed, I used

Omni#printer;Chopin;Dell2330:

which failed, as I explained

Do I need to install Lanman after all to drive the printer?

I do have !Uniprint and can print that way but the driver provided by CJE
allows me to make use of the printer's duplex capability, whereas
!Uniprint bypasses that and will only print single sided.

[Stuart]

In article <579103c2...@waitrose.com>,

Chris Newman <cvj...@waitrose.com> wrote:
> I now have a Dell 2330dn & can use it directly from my RiscPC using
> PostScript 3 printer driver from Martin Würthner & John Tytgat. RiscOS
> also comes with PostScript 2 if you don't want to fork out any loot. It
> was a doddle to set up. Therefore why not forget networking & go direct?

I also have PS3 but how do you print directly?

What magic is required to get RISC OS to drive a printer connected via
Ethernet instead of the normal parallel port?

[Tim Hill]

In article <5791157e...@argonet.co.uk>, Stuart

<Spa...@argonet.co.uk> wrote:
> In article <mpro.pnyv4z02...@stevefryatt.org.uk>, Steve
> Fryatt <ne...@stevefryatt.org.uk> wrote:

> > or, more specifically, perhaps:

> > OmniPrint#LanMan;Chopin;Dell2330;User;Password;Options;Size:

> Thanks but LanMan isn't, as yet, installed on this Iyo. I understood
> that the latest !Omni was more capable than !LanMan so just stuck with
> the installed !Omni.

I'm confused. If I use Omni to open a filer window on the USB stick
plugged into my router, the path is "LanMan::READYSHARE" and I never
installed Lanman because it was already there.

AFAIK Omni is just a way of packaging network filing systems such as
LanMan; it isn't in an of itself, a filing system.

> I simply replaced Lanman with Omni in the original path. Thus instead of

> Lanman98#printer;Chopin;Dell2330:

I think that "98" may be the problem.

--
Tim Hill
--------
Find an event to attend at:
http://timil.com/riscos/calendar/
Mimemap and other stuff:
http://timil.com/riscos/

[Stuart]

In article <579117...@invalid.org.uk>,

Tim Hill <t...@invalid.org.uk> wrote:
> I'm confused. If I use Omni to open a filer window on the USB stick
> plugged into my router, the path is "LanMan::READYSHARE" and I never
> installed Lanman because it was already there.

Not as much as I am!

> AFAIK Omni is just a way of packaging network filing systems such as
> LanMan; it isn't in an of itself, a filing system.

Oh! That's interesting.

In the meantime I seem to be struggling to get !Uniprint to work too.

Yes, I can see the shared directory on Chopin in the usual way.

[Tim Hill]

In article <57911419...@argonet.co.uk>, Stuart

<Spa...@argonet.co.uk> wrote:
> In article <579103c2...@waitrose.com>, Chris Newman
> <cvj...@waitrose.com> wrote:
> > I now have a Dell 2330dn & can use it directly from my RiscPC using
> > PostScript 3 printer driver from Martin Würthner & John Tytgat.
> > RiscOS also comes with PostScript 2 if you don't want to fork out any
> > loot. It was a doddle to set up. Therefore why not forget networking
> > & go direct?

> I also have PS3 but how do you print directly?

> What magic is required to get RISC OS to drive a printer connected via
> Ethernet instead of the normal parallel port?

These should handle the LPR protocol that the Dell 2230 supports:

RemotePrinterFS
https://www.filebase.org.uk/software/utilities/941

or JetDirectFS
http://www.sbellon.de/sw-modules.html

RISC OS seems to have network connectivity built into the printers app
but in the absence of a network printer, I can't test this on an
up-to-date system as it is greyed out. I used to use JetDirectFS with an
old network printer and all you have to do is have the correct entry in
the 'file' writable icon, just as you do if you are printing to a PC.

[Stuart]

In article <579117...@invalid.org.uk>,
Tim Hill <t...@invalid.org.uk> wrote:

> I'm confused. If I use Omni to open a filer window on the USB stick
> plugged into my router, the path is "LanMan::READYSHARE" and I never
> installed Lanman because it was already there.

> AFAIK Omni is just a way of packaging network filing systems such as
> LanMan; it isn't in an of itself, a filing system.

> > I simply replaced Lanman with Omni in the original path. Thus instead
> > of

> > Lanman98#printer;Chopin;Dell2330:

> I think that "98" may be the problem.

Ah, so it seems we have Lanman and Lanman98. Lanman98 was a separate, Warm
Silence program, which I purchased years ago and somehow works with !Omni.
!Omni already includes a different program called Lanman.

Having entered the path as given by Steve (without the options) I can now
print.

http://www.cjemicros.co.uk/micros/individual/newprodpages/prodinfo.php?prodcode=WSS-LAN98-E

[Philip Draper]

In message <5791157e...@argonet.co.uk>

Stuart <Spa...@argonet.co.uk> wrote:

> In article <mpro.pnyv4z02...@stevefryatt.org.uk>,
> Steve Fryatt <ne...@stevefryatt.org.uk> wrote:

>> or, more specifically, perhaps:

>> OmniPrint#LanMan;Chopin;Dell2330;User;Password;Options;Size:

[snip]

>

> Do I need to install Lanman after all to drive the printer?

> I do have !Uniprint and can print that way but the driver provided by CJE
> allows me to make use of the printer's duplex capability, whereas
> !Uniprint bypasses that and will only print single sided.

Something funny there. I use !Uniprint to print double-sided on a HP
printer on my PC. No special RISC OS setting needed.

Philip.



--
Philip Draper

Main address (new): Phi...@borehamh.org.uk

Old address: Phi...@borehamh.demon.co.uk still works
but will expire Aug 2019. Please do not use.

[News]

In article <5791157e...@argonet.co.uk>,
Stuart <Spa...@argonet.co.uk> wrote:

> Thanks but LanMan isn't, as yet, installed on this Iyo. I
> understood that the latest !Omni was more capable than !LanMan so
> just stuck with the installed !Omni.

LanManFS comes within !Omni. !Omni is just a front end for any filing
system you care to give it.

If you look inside !Omni.RMStore you should find find LanManFS. There
may be other filing system modules as well.

--
Chris Johnson

[Stuart]

In article <579119...@invalid.org.uk>,

Tim Hill <t...@invalid.org.uk> wrote:

> > What magic is required to get RISC OS to drive a printer connected via
> > Ethernet instead of the normal parallel port?

> These should handle the LPR protocol that the Dell 2230 supports:

> RemotePrinterFS
> https://www.filebase.org.uk/software/utilities/941

> or JetDirectFS
> http://www.sbellon.de/sw-modules.html

Ah, so additional programs are required, I thought that to be the case.

[Steve Fryatt]

On 7 Mar, Tim Hill wrote in message
<579119...@invalid.org.uk>:

> In article <57911419...@argonet.co.uk>, Stuart
> <Spa...@argonet.co.uk> wrote:
>
> > What magic is required to get RISC OS to drive a printer connected via
> > Ethernet instead of the normal parallel port?
>
> These should handle the LPR protocol that the Dell 2230 supports:
>
> RemotePrinterFS https://www.filebase.org.uk/software/utilities/941
>
> or JetDirectFS http://www.sbellon.de/sw-modules.html

Just use RemotePrinterFS from http://www.sbellon.de/sw-modules.html

With it installed, the File entry will be something like

RemotePrinterFS#proto=LPD;host=192.168.0.1;queue=Dell2330;buffer=yes:

(you need to set the IP address correctly).

[Bill (Adopt)]

In article <579119...@invalid.org.uk>,
Tim Hill <t...@invalid.org.uk> wrote:

> In article <57911419...@argonet.co.uk>, Stuart
> <Spa...@argonet.co.uk> wrote:
> > In article <579103c2...@waitrose.com>, Chris Newman
> > <cvj...@waitrose.com> wrote:
> > > I now have a Dell 2330dn & can use it directly from my RiscPC using
> > > PostScript 3 printer driver from Martin Würthner & John Tytgat.
> > > RiscOS also comes with PostScript 2 if you don't want to fork out any
> > > loot. It was a doddle to set up. Therefore why not forget networking
> > > & go direct?

> > I also have PS3 but how do you print directly?

> > What magic is required to get RISC OS to drive a printer connected via
> > Ethernet instead of the normal parallel port?

> These should handle the LPR protocol that the Dell 2230 supports:

> RemotePrinterFS
> https://www.filebase.org.uk/software/utilities/941

> or JetDirectFS
> http://www.sbellon.de/sw-modules.html

> RISC OS seems to have network connectivity built into the printers app
> but in the absence of a network printer, I can't test this on an
> up-to-date system as it is greyed out. I used to use JetDirectFS with an
> old network printer and all you have to do is have the correct entry in
> the 'file' writable icon, just as you do if you are printing to a PC.

Well, yes! :))

Excuse me if I think I'm being un..utter..ably, um,
less than bright - but RISCO OS, with Remote#PrinterFS
and JetDirectFS installed really does work ..with both
PS2, (useful when text printing particularly from
!Pluto, or PS3 when using Martin Würthner's nice and
finer colour palette(s).

However, if it's helpful to you Stuart, I don't use
and have never used anything like !Uniprint - but then
I use RISCOS, RISCOS/Linux RPis and various Linux machines,
(being about the nearest thing to, but nothing like,
Microsoft!). Never could get Andrew's LanMan98 to work... ;((

All machines, (including TVs, DVRs, streaming et al),
are connected to my network router, either directly in
the case of the Risc PC, or mostly for everything else
wirelessly, bluetoothly, whatever - and so, via an RJ45
(although again wirelessly would probably do), to my
printer - an HP451dn, which then prints out automatically
single side and duplex according to presentation.

No matter what's being used, the printer picks them all
up and, well, has printed everything without fail through
many years, without ever getting mixed up -
- (although I do need to remember to fill the printer with
part reams of paper - says he vacantly to his'self as
he stands at the bottom of the stairs, wondering what he's
doing carting a spare bog roll around the house)!

My Risc PC, (yes, now almost 25 yrs old and in full daily
use from 05 Dec 1994), doesn't have wireless capability so
is directly connected to the networking router ..which router,
like most if not all, is itself perfectly wireless capable.

Long and short: as Tim says, install Remote#PrinterFS and
JetDirectFS - and just wire, (RJ45 or whatever), your RiscPC
to the router/network switch, which then takes care of
everything. Magic - and it doesn't even need Sergei's
twinkle-eyed high-5!

Hope the ramble ..well, sort of ..helps.. ;))

Bill ZFC

--
Adoption InterLink UK with -=- http://www.billsimpson.com/
Domain Host Orpheus Internet -=- http://www.orpheusinternet.co.uk/

[Steve Fryatt]

On 7 Mar, "Bill (Adopt)" wrote in message
<579133b...@billsimpson.com>:

> Long and short: as Tim says, install Remote#PrinterFS and JetDirectFS

No, install just RemotePrinterFS. It is newer, has subsumed JetDirect
functionality, as far as I'm aware -- and you certainly only need one at a
time.

[Chris Newman]

In article <579103c2...@waitrose.com>,
Chris Newman <cvj...@waitrose.com> wrote:

I see from the traffic down thread that I should have explained my Dell is
wired to the PC via the parallel port. I have a switcher box to flip between
printer & scanner

--
Chris Newman

[Stuart]

In article <579133b...@billsimpson.com>,

Bill (Adopt) <ad...@billsimpson.com> wrote:

> However, if it's helpful to you Stuart, I don't use
> and have never used anything like !Uniprint

Ah well, without it I would not be able to use our Epson WF-7515 A3 colour
inkjet from any RISC OS machine because, unsurprisingly, there are no RISC
OS drivers.

Here, everything except portable devices (Phones, tablets) and one "Smart"
TV is connected by CAT5/6 cabling, to cascaded switches connected by
single cable to the router.

[Stuart]

In article <57913905...@waitrose.com>,

Ah, yes, well

My Kinetic, ARMX6, WXP and W7 PC are in my den in the loft.
My Iyonix, my wife's W7 PC is in the dining room with our Dell 2330 and
our Epson WF-7515 multifunction A3 printer.

[Tim Hill]

In article <57914829...@argonet.co.uk>, Stuart

<Spa...@argonet.co.uk> wrote:
> In article <579133b...@billsimpson.com>, Bill (Adopt)
> <ad...@billsimpson.com> wrote:

> > However, if it's helpful to you Stuart, I don't use and have never
> > used anything like !Uniprint

> Ah well, without it I would not be able to use our Epson WF-7515 A3
> colour inkjet from any RISC OS machine because, unsurprisingly, there
> are no RISC OS drivers.

Hmm. That's odd. I can print any RISC OS document on a non-driver printer
attached to a PC without Uniprint.

I print to a PDF file which is created in a common folder which in
windows I simply select and then print. Simple stuff though, I print very
little these days. Dried nozzles are my biggest problem.

> Here, everything except portable devices (Phones, tablets) and one
> "Smart" TV is connected by CAT5/6 cabling, to cascaded switches
> connected by single cable to the router.

Well, yes, that's how a network is constructed (!) although mine includes
powerline adapters in place of some of those wires as they mean you don't
have to perforate walls and/or ceilings.

[Bill (Adopt)]

In article <mpro.po0o1i02...@stevefryatt.org.uk>,

Steve Fryatt <ne...@stevefryatt.org.uk> wrote:
> On 7 Mar, "Bill (Adopt)" wrote in message
> <579133b...@billsimpson.com>:

> > Long and short: as Tim says, install Remote#PrinterFS and JetDirectFS

> No, install just RemotePrinterFS. It is newer, has subsumed JetDirect
> functionality, as far as I'm aware -- and you certainly only need one at a
> time.

Thank you, Steve, that I didn't know.

Having setup my RiscPC and printer(s) many years ago with
the help of Ian Hamilton - who also used me as a testbed
at the time.

Since everything has and is continuing to work sublimely,
I haven't ever thought to interfere!

Perhaps the wisest policy for me is, 'if it ain't broke,
don't attempt to fix'!

Thank you.. :))

[Bill (Adopt)]

In article <57914829...@argonet.co.uk>,
Stuart <Spa...@argonet.co.uk> wrote:

> In article <579133b...@billsimpson.com>,
> Bill (Adopt) <ad...@billsimpson.com> wrote:

> > However, if it's helpful to you Stuart, I don't use
> > and have never used anything like !Uniprint

> Ah well, without it I would not be able to use our Epson WF-7515 A3 colour
> inkjet from any RISC OS machine because, unsurprisingly, there are no RISC
> OS drivers.

Ummm ..I think that Tim, or Steve, might have answered
this but, if it's a help, then my RiscPC is setup to
print from it's Printer control 'table' -

LJ-5L LaserJet-5l Turbodriver Printer99 Active
ArcFax ArcFax To file Active
Taborca Adobe PDF To file Active
M451dn PostScript Level 2 To file Active
PoScript3 PostScript 3 To file Active
GhostPS2 PostScript to PDF Output To file Active

The first (two) is/are no longer used but, as it has
various CC proprietary bits tucked up in !Boot, I'm loath
to interfere in case the whole lot tumbles down.

Accordingly every printer above is lined up on the icon
bar ready just to click in whenever or if ever required
to produce output.

The operative printer line within the Acorn/RiscPC driver
[Printers; Printer manager; Acorn Computers Ltd 1995;
1.62 (14-June-1999)], with "File" ticked 'on' and
"Parallel"-"Serial" 'off' is:

"RemotePrinterFS#Proto=JetDirect;host=PrinterName;buffer=yes:"

"Append to file" remains unticked unless needed.

OK ..probably better ways of doing it with more modern
attributes and so on, but everything works with everything
else without problem.

The RiscPC, (and the wireless RPis), to reiterate, are
already connected via RJ45 (Cat5) to the router/netswitch
- and hence from the router/netswitch to the printer (Cat6).

All other devices, generally wirelessly, connect from
around the house, again to the wireless router and, via
the same Cat6, to the printer. All efforts print without
demur from all devices and with invisible ease. Obviously
they're using PostScript - at least I think they do!

The Linux machines seem to acquire their own drivers on
first connection - probably from Hewlett-Packard - again
without any intervention or setting up on my part It's
all done automagically.

I believe I can also, although never tried, print remotely
from a distance - even the other side of the World. Neat!

> Here, everything except portable devices (Phones, tablets) and one "Smart"
> TV is connected by CAT5/6 cabling, to cascaded switches connected by
> single cable to the router.

Yes! So you're pretty well ready for anything anyway :))
Your portable devices should also work - and probably
will have their own drivers - if needed - which they'll
probably setup themselves from within an 'app' anyway.
Try it from one of your 'phones or tablets. I'll hide
behind the barricade just in case.. ;))

I've probably missed something, but hope the additional
info helps.. :))

[Tim Hill]

In article <57917e3...@billsimpson.com>, Bill (Adopt)

<ad...@billsimpson.com> wrote:
> In article <mpro.po0o1i02...@stevefryatt.org.uk>, Steve
> Fryatt <ne...@stevefryatt.org.uk> wrote:
> > On 7 Mar, "Bill (Adopt)" wrote in message
> > <579133b...@billsimpson.com>:

> > > Long and short: as Tim says, install Remote#PrinterFS and
> > > JetDirectFS

I didn't. That's not what "or" means. :-o :-D

> > No, install just RemotePrinterFS. It is newer, has subsumed JetDirect
> > functionality, as far as I'm aware -- and you certainly only need one
> > at a time.

> Thank you, Steve, that I didn't know.

I wondered too why there are two.

[Snip]

> Perhaps the wisest policy for me is, 'if it ain't broke, don't attempt
> to fix'!

Always sage advice.

[Stuart]

In article <579174...@invalid.org.uk>,

Tim Hill <t...@invalid.org.uk> wrote:

> Hmm. That's odd. I can print any RISC OS document on a non-driver printer
> attached to a PC without Uniprint.

> I print to a PDF file which is created in a common folder which in
> windows I simply select and then print. Simple stuff though, I print very
> little these days. Dried nozzles are my biggest problem.

Yes, well, there are usually a number of ways round a problem but it's
hardly as convenient as hitting "print" from within whichever RISC OS
application you happen to be using and the result appearing moments later
on the printer is it?

[druck]

On 07/03/2019 17:01, Stuart wrote:
> Ah, so it seems we have Lanman and Lanman98. Lanman98 was a separate, Warm
> Silence program, which I purchased years ago and somehow works with !Omni.
> !Omni already includes a different program called Lanman.

LanmanFS was originally limited to DOS style 8.3 names, and Lanman98
supported long filenames. The modern RISC OS 5.x version of LanmanFS now
does long filenames too, making Lanman98 redundant.

---druck

[Stuart]

In article <q5uhqu$12c$1...@dont-email.me>,

Thank you for that clarification, now I understand.

[Tim Hill]

In article <5791a0aa...@argonet.co.uk>, Stuart

<Spa...@argonet.co.uk> wrote:
> In article <579174...@invalid.org.uk>, Tim Hill
> <t...@invalid.org.uk> wrote:

> > I print to a PDF file which is created in a common folder which in
> > windows I simply select and then print. Simple stuff though, I print
> > very little these days. Dried nozzles are my biggest problem.

> Yes, well, there are usually a number of ways round a problem

There are no problems, only solutions. ;-)

> but it's
> hardly as convenient as hitting "print" from within whichever RISC OS
> application you happen to be using and the result appearing moments
> later on the printer is it?

Maybe, but printing (even directly from the PC) is itself so rare for me
these days - two sheets of A4 a month and one of those is from the PC - a
couple of extra clicks with a mouse in each hand are not an inconvenience
worthy of a £79 cure even with the other interesting tricks up its
sleeve. Perhaps I would think differently if the PC's mouse, monitors and
keyboard weren't right here alongside the RISC OS ones and my printing
needs exceeded a few pages a month. If postal mailshots were a thing
again, I guess my opinion could change.

[Bill (Adopt)]

In article <579196...@invalid.org.uk>,

Tim Hill <t...@invalid.org.uk> wrote:
> In article <57917e3...@billsimpson.com>, Bill (Adopt)
> <ad...@billsimpson.com> wrote:
> > In article <mpro.po0o1i02...@stevefryatt.org.uk>, Steve
> > Fryatt <ne...@stevefryatt.org.uk> wrote:
> > > On 7 Mar, "Bill (Adopt)" wrote in message
> > > <579133b...@billsimpson.com>:

> > > > Long and short: as Tim says, install Remote#PrinterFS and
> > > > JetDirectFS

> I didn't. That's not what "or" means. :-o :-D

<vbg>
Yes! EOR the donkey! Remember that from
ArgoNet days ..almost decades ago now... ;))

[Richard Porter]

The date being 7 Mar 2019, Stuart <Spa...@argonet.co.uk> decided to
write:

> What magic is required to get RISC OS to drive a printer connected via
> Ethernet instead of the normal parallel port?

I just use (in Printer control... > Connections > File):

RemotePrinterFS#proto=JetDirect;host=192.168.1.96:

The LAN address is set up using the printer's user interface.

If I just want to print off a PDF file it's easiest just to drop it on an
FTPc window for the printer. The printer generally makes a better fist of
PDF than does !PDF. That assumes that the printer has its own PDF server.

[Matthew Phillips]

In message <21ec369...@user.minijem.plus.com>

I just have the system variable Alias$@PrintType_ADF set to

Copy %0 RemotePrinterFS#proto=LPD;address=xerox;sendfirst=datafile;format=l: ~C

You would need to change "xerox" to "192.168.1.96" and the proto to
JetDirect.

With this system vriable set, I can just take a PDF and drop it onto the
Printer icon on the iconbar. Easier than starting up FTPc.

--
Matthew Phillips
Durham