In message <6697ad8a5a.MSPro@Marker.Dommel.be>
riscos@markerdesign.be wrote:
> Hi to all.
> About RPCEmu on top of Linux Ubuntu
> Has anyone found a way to switch the RPCEmu "Full Screen" function
> permanently on? So the Emulator automatically starts up in Full Screen
> Mode? It seems RPCEmu can not remember this setting, therefore I need
> to "try" to click the full screen box during start-up every time. This
> before it goes full screen, otherwise the emulator starts out of
> center and is unusable because the toolbar is billow the screen scoop.
> I always need 2 up to 5 attempts to get it wright :-(
Here is a suggestion based on what I do to go in and out of VirtualRPC:
I have a small AutoIt3 script (free Windows app) that runs the emulator
and sets the application's window attributes as needed. It also
creates a small file in the emulator's filesystem and monitors it.
When a small obey file is run from RISC OS to delete the file, the
AutoIt3 script knows its time to set the emulator window attributes
to push it onto the task bar.
If the emulator is running and the AutoIt3 script is run again, it
knows to change the window attributes and create the file to say its
running full screen.
I would have thought that a similar process could be implemented in
Ubuntu.
--
Mike Hobbs
_______________________________________________
RPCEmu mailing list
RPCEmu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
Saturday, 25 March 2023
[Rpcemu] RPCEmu "Full Screen"
In article <6697ad8a5a.MSPro@Marker.Dommel.be>,
<riscos@markerdesign.be> wrote:
> Hi to all.
> About RPCEmu on top of Linux Ubuntu
> Has anyone found a way to switch the RPCEmu "Full Screen"
> function permanently on? So the Emulator automatically
> starts up in Full Screen Mode? It seems RPCEmu can not
> remember this setting, therefore I need to "try" to
> click the full screen box during start-up every time.
> This before it goes full screen, otherwise the emulator
> starts out of center and is unusable because the toolbar
> is billow the screen scoop. I always need 2 up to 5
> attempts to get it wright :-(
There are a couple of ways. My preferred is to get it into
full screen *before* it reaches the desktop. However, don't
let the mouse cross the window: bring the cursor down from
above.
Others like to set the default resolution to less than that
for the screen and then, after the program has reached the
desktop, go into full screen and only then change the
resolution to what you want.
The Windows version doesn't exhibit this behaviour.
John
--
John McCartney
j.mccartney@blueyonder.co.uk
_______________________________________________
RPCEmu mailing list
RPCEmu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
<riscos@markerdesign.be> wrote:
> Hi to all.
> About RPCEmu on top of Linux Ubuntu
> Has anyone found a way to switch the RPCEmu "Full Screen"
> function permanently on? So the Emulator automatically
> starts up in Full Screen Mode? It seems RPCEmu can not
> remember this setting, therefore I need to "try" to
> click the full screen box during start-up every time.
> This before it goes full screen, otherwise the emulator
> starts out of center and is unusable because the toolbar
> is billow the screen scoop. I always need 2 up to 5
> attempts to get it wright :-(
There are a couple of ways. My preferred is to get it into
full screen *before* it reaches the desktop. However, don't
let the mouse cross the window: bring the cursor down from
above.
Others like to set the default resolution to less than that
for the screen and then, after the program has reached the
desktop, go into full screen and only then change the
resolution to what you want.
The Windows version doesn't exhibit this behaviour.
John
--
John McCartney
j.mccartney@blueyonder.co.uk
_______________________________________________
RPCEmu mailing list
RPCEmu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
[Rpcemu] RPCEmu "Full Screen"
Hi to all.
About RPCEmu on top of Linux Ubuntu
Has anyone found a way to switch the RPCEmu "Full Screen" function
permanently on? So the Emulator automatically starts up in Full Screen
Mode? It seems RPCEmu can not remember this setting, therefore I need
to "try" to click the full screen box during start-up every time. This
before it goes full screen, otherwise the emulator starts out of
center and is unusable because the toolbar is billow the screen scoop.
I always need 2 up to 5 attempts to get it wright :-(
--
Regards, SteveRM
_______________________________________________
RPCEmu mailing list
RPCEmu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
About RPCEmu on top of Linux Ubuntu
Has anyone found a way to switch the RPCEmu "Full Screen" function
permanently on? So the Emulator automatically starts up in Full Screen
Mode? It seems RPCEmu can not remember this setting, therefore I need
to "try" to click the full screen box during start-up every time. This
before it goes full screen, otherwise the emulator starts out of
center and is unusable because the toolbar is billow the screen scoop.
I always need 2 up to 5 attempts to get it wright :-(
--
Regards, SteveRM
_______________________________________________
RPCEmu mailing list
RPCEmu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
Monday, 20 March 2023
Re: [Rpcemu] Network Printing from RPCEmu
Are you using JetDirectFS on both systems? I'm wondering if the printer is always using PCL for data that comes in that way.
I'm using something else, the name of what escapes me at the moment and I'm at work so can't quickly check.
Cheers
Chris
Sent from my iPhone
> On 20 Mar 2023, at 09:57, John Bilton <jbilton@freeuk.com> wrote:
>
> Hello Chris,
>
> I also have my printer set to KPDL (auto) and use the
> PostScript2 driver on an old Windows 7 machine running
> RPCEmu (0.83), which works fine. The new machine is
> running Windows 10 and RPCEmu (0.94). The networking is
> working fine and with the JetDirectFS software I can
> print to the Kyocera printer in B/W using the generic
> PCL driver. To print in colour, I have tried using a
> PostScript2 driver, which waits a long time, then prints
> rubbish, as though the PS prologue has not been understood.
>
> My guess is that somewhere (when I updated !Printers from
> 1.64 on the old machine to 1.91 on the new machine), the
> software location/content has changed. This is what I am
> trying to resolve. The problem is that I am trying to
> configure an old operating system (RiscOS 4.02) with more
> up to date software (!Printers 1.91), where it is needed.
> It seems as though the location of the printer definition
> files has moved from Printing directory on the Hard Disc
> to PrntDefs directory inside System.Resources. Perhaps
> other changes have occurred, as well. This is what is
> taking time to resolve.
>
> As a separate issue, I believe that the Kyocera printer
> will print /pdf files directly, but there doesn't seem
> to be a way for this to be handled in RiscOS !Printers.
>
> I will continue my investigations, when I have the time.
>
> Many thanks, John
>
>
>
> This e-mail message and accompanying data is confidential and for use by the addressee only. If you are not the intended recipient, you must not use, disclose, copy or forward this transmission. Please return the message to the sender by replying to it and then delete the message and accompanying data from your computer.
_______________________________________________
RPCEmu mailing list
RPCEmu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
Re: [Rpcemu] Network Printing from RPCEmu
Hello Chris,
I also have my printer set to KPDL (auto) and use the
PostScript2 driver on an old Windows 7 machine running
RPCEmu (0.83), which works fine. The new machine is
running Windows 10 and RPCEmu (0.94). The networking is
working fine and with the JetDirectFS software I can
print to the Kyocera printer in B/W using the generic
PCL driver. To print in colour, I have tried using a
PostScript2 driver, which waits a long time, then prints
rubbish, as though the PS prologue has not been understood.
My guess is that somewhere (when I updated !Printers from
1.64 on the old machine to 1.91 on the new machine), the
software location/content has changed. This is what I am
trying to resolve. The problem is that I am trying to
configure an old operating system (RiscOS 4.02) with more
up to date software (!Printers 1.91), where it is needed.
It seems as though the location of the printer definition
files has moved from Printing directory on the Hard Disc
to PrntDefs directory inside System.Resources. Perhaps
other changes have occurred, as well. This is what is
taking time to resolve.
As a separate issue, I believe that the Kyocera printer
will print /pdf files directly, but there doesn't seem
to be a way for this to be handled in RiscOS !Printers.
I will continue my investigations, when I have the time.
Many thanks, John
This e-mail message and accompanying data is confidential and for use by the addressee only. If you are not the intended recipient, you must not use, disclose, copy or forward this transmission. Please return the message to the sender by replying to it and then delete the message and accompanying data from your computer.
_______________________________________________
RPCEmu mailing list
RPCEmu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
I also have my printer set to KPDL (auto) and use the
PostScript2 driver on an old Windows 7 machine running
RPCEmu (0.83), which works fine. The new machine is
running Windows 10 and RPCEmu (0.94). The networking is
working fine and with the JetDirectFS software I can
print to the Kyocera printer in B/W using the generic
PCL driver. To print in colour, I have tried using a
PostScript2 driver, which waits a long time, then prints
rubbish, as though the PS prologue has not been understood.
My guess is that somewhere (when I updated !Printers from
1.64 on the old machine to 1.91 on the new machine), the
software location/content has changed. This is what I am
trying to resolve. The problem is that I am trying to
configure an old operating system (RiscOS 4.02) with more
up to date software (!Printers 1.91), where it is needed.
It seems as though the location of the printer definition
files has moved from Printing directory on the Hard Disc
to PrntDefs directory inside System.Resources. Perhaps
other changes have occurred, as well. This is what is
taking time to resolve.
As a separate issue, I believe that the Kyocera printer
will print /pdf files directly, but there doesn't seem
to be a way for this to be handled in RiscOS !Printers.
I will continue my investigations, when I have the time.
Many thanks, John
This e-mail message and accompanying data is confidential and for use by the addressee only. If you are not the intended recipient, you must not use, disclose, copy or forward this transmission. Please return the message to the sender by replying to it and then delete the message and accompanying data from your computer.
_______________________________________________
RPCEmu mailing list
RPCEmu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
Sunday, 19 March 2023
Re: [Rpcemu] Network Printing from RPCEmu
Hi John
If it helps, I have mine set to KPDL (Auto) and use the PostScript2 drivers.
Cheers
Chris
On 18/03/2023 19:52, John Bilton wrote:
> Hello David,
>
> Many thanks for your helpful comments, I now have a
> working RPCEmu connection to the printer (Kyocera
> cdn5521) and can send documents for printing. Whether
> or not they print seems to depend on whether postscript
> or pcl drivers are used in RiscOS and I am now puzzling
> over the various printing mechanisms available. At least
> the documents seem to be making their way from RPCEmu
> to the network printer, which is a big step forwards.
>
> Many thanks, John
>
>
> This e-mail message and accompanying data is confidential and for use by the addressee only. If you are not the intended recipient, you must not use, disclose, copy or forward this transmission. Please return the message to the sender by replying to it and then delete the message and accompanying data from your computer.
>
> _______________________________________________
> RPCEmu mailing list
> RPCEmu@riscos.info
> http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
_______________________________________________
RPCEmu mailing list
RPCEmu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
If it helps, I have mine set to KPDL (Auto) and use the PostScript2 drivers.
Cheers
Chris
On 18/03/2023 19:52, John Bilton wrote:
> Hello David,
>
> Many thanks for your helpful comments, I now have a
> working RPCEmu connection to the printer (Kyocera
> cdn5521) and can send documents for printing. Whether
> or not they print seems to depend on whether postscript
> or pcl drivers are used in RiscOS and I am now puzzling
> over the various printing mechanisms available. At least
> the documents seem to be making their way from RPCEmu
> to the network printer, which is a big step forwards.
>
> Many thanks, John
>
>
> This e-mail message and accompanying data is confidential and for use by the addressee only. If you are not the intended recipient, you must not use, disclose, copy or forward this transmission. Please return the message to the sender by replying to it and then delete the message and accompanying data from your computer.
>
> _______________________________________________
> RPCEmu mailing list
> RPCEmu@riscos.info
> http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
_______________________________________________
RPCEmu mailing list
RPCEmu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
Re: [Rpcemu] Network Printing from RPCEmu
On 2023-03-19 19:25, Dave wrote:
> Do you know if the printer is Postscript or PCL?
According to:
https://www.printerland.co.uk/product/Kyocera-ECOSYS-M5521cdn/138537
it's: PCL5/6 & Postscript 3
though in the details lower down, under "software", these are
described as "emulations" which probably means it's Kyocera's
reverse-engineered implementations of something that's meant
to be the same as PCL & PS.
--
Jeremy Nicoll - my opinions are my own
_______________________________________________
RPCEmu mailing list
RPCEmu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
> Do you know if the printer is Postscript or PCL?
According to:
https://www.printerland.co.uk/product/Kyocera-ECOSYS-M5521cdn/138537
it's: PCL5/6 & Postscript 3
though in the details lower down, under "software", these are
described as "emulations" which probably means it's Kyocera's
reverse-engineered implementations of something that's meant
to be the same as PCL & PS.
--
Jeremy Nicoll - my opinions are my own
_______________________________________________
RPCEmu mailing list
RPCEmu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
[Rpcemu] Network Printing from RPCEmu
In article <af353a875a.jbilton@jbilton.mail.co.uk>,
John Bilton <jbilton@freeuk.com> wrote:
> Hello David,
> Many thanks for your helpful comments, I now have a
> working RPCEmu connection to the printer (Kyocera
> cdn5521) and can send documents for printing. Whether
> or not they print seems to depend on whether postscript
> or pcl drivers are used in RiscOS and I am now puzzling
> over the various printing mechanisms available. At least
> the documents seem to be making their way from RPCEmu
> to the network printer, which is a big step forwards.
> Many thanks, John
That's at least some steps forward. :-)
Do you know if the printer is Postscript or PCL?
With regard to Printer Def Files...
I'm assuming you've looked in the Printers.PDF directory and had a look at
the the Kyocera printer def files to see if any of them might do the
business.
I do remember when we got the HP printer (Postscript) we are now using,
needing to try out a couple of the RISC OS HP driver files before settling
on one in particular.
Dave
--
Dave Triffid
_______________________________________________
RPCEmu mailing list
RPCEmu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
John Bilton <jbilton@freeuk.com> wrote:
> Hello David,
> Many thanks for your helpful comments, I now have a
> working RPCEmu connection to the printer (Kyocera
> cdn5521) and can send documents for printing. Whether
> or not they print seems to depend on whether postscript
> or pcl drivers are used in RiscOS and I am now puzzling
> over the various printing mechanisms available. At least
> the documents seem to be making their way from RPCEmu
> to the network printer, which is a big step forwards.
> Many thanks, John
That's at least some steps forward. :-)
Do you know if the printer is Postscript or PCL?
With regard to Printer Def Files...
I'm assuming you've looked in the Printers.PDF directory and had a look at
the the Kyocera printer def files to see if any of them might do the
business.
I do remember when we got the HP printer (Postscript) we are now using,
needing to try out a couple of the RISC OS HP driver files before settling
on one in particular.
Dave
--
Dave Triffid
_______________________________________________
RPCEmu mailing list
RPCEmu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
Saturday, 18 March 2023
Re: [Rpcemu] Network Printing from RPCEmu
Hello David,
Many thanks for your helpful comments, I now have a
working RPCEmu connection to the printer (Kyocera
cdn5521) and can send documents for printing. Whether
or not they print seems to depend on whether postscript
or pcl drivers are used in RiscOS and I am now puzzling
over the various printing mechanisms available. At least
the documents seem to be making their way from RPCEmu
to the network printer, which is a big step forwards.
Many thanks, John
This e-mail message and accompanying data is confidential and for use by the addressee only. If you are not the intended recipient, you must not use, disclose, copy or forward this transmission. Please return the message to the sender by replying to it and then delete the message and accompanying data from your computer.
_______________________________________________
RPCEmu mailing list
RPCEmu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
Many thanks for your helpful comments, I now have a
working RPCEmu connection to the printer (Kyocera
cdn5521) and can send documents for printing. Whether
or not they print seems to depend on whether postscript
or pcl drivers are used in RiscOS and I am now puzzling
over the various printing mechanisms available. At least
the documents seem to be making their way from RPCEmu
to the network printer, which is a big step forwards.
Many thanks, John
This e-mail message and accompanying data is confidential and for use by the addressee only. If you are not the intended recipient, you must not use, disclose, copy or forward this transmission. Please return the message to the sender by replying to it and then delete the message and accompanying data from your computer.
_______________________________________________
RPCEmu mailing list
RPCEmu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
Tuesday, 14 March 2023
Re: IPv6 support on RISC OS
On 13/03/2023 21:56, David Higton wrote:
> Hi devs,
>
> Is there a plan to support IPv6 on RISC OS, now the RISC OS Developments
> TCP/IP stack (Internet V7) is commonly available?
Not to my knowledge, no. Note that NetSurf itself doesn't care about
Internet Protocol versions and has long supported IPv6 literals in URIs.
Both libcurl and libcares have supported IPv6 for years -- even when
built for RISC OS.
However, none of this is likely to work if the platform runtime doesn't
understand IPv6 (or does, but not in the same way as the underlying
Internet stack). In the case of NetSurf, the platform runtime in
question is UnixLib[1] and, as far as I know, it does not know anything
about the ROD TCP/IP stack (or, indeed, any RISC OS Internet stack that
supports IPv6).
If ever this changes, IPv6 support in NetSurf should "just work" (much
like it already does on other platforms).
J.
1. https://www.riscos.info/index.php/UnixLib
_______________________________________________
netsurf-dev mailing list -- netsurf-dev@netsurf-browser.org
To unsubscribe send an email to netsurf-dev-leave@netsurf-browser.org
> Hi devs,
>
> Is there a plan to support IPv6 on RISC OS, now the RISC OS Developments
> TCP/IP stack (Internet V7) is commonly available?
Not to my knowledge, no. Note that NetSurf itself doesn't care about
Internet Protocol versions and has long supported IPv6 literals in URIs.
Both libcurl and libcares have supported IPv6 for years -- even when
built for RISC OS.
However, none of this is likely to work if the platform runtime doesn't
understand IPv6 (or does, but not in the same way as the underlying
Internet stack). In the case of NetSurf, the platform runtime in
question is UnixLib[1] and, as far as I know, it does not know anything
about the ROD TCP/IP stack (or, indeed, any RISC OS Internet stack that
supports IPv6).
If ever this changes, IPv6 support in NetSurf should "just work" (much
like it already does on other platforms).
J.
1. https://www.riscos.info/index.php/UnixLib
_______________________________________________
netsurf-dev mailing list -- netsurf-dev@netsurf-browser.org
To unsubscribe send an email to netsurf-dev-leave@netsurf-browser.org
Monday, 13 March 2023
IPv6 support on RISC OS
Hi devs,
Is there a plan to support IPv6 on RISC OS, now the RISC OS Developments
TCP/IP stack (Internet V7) is commonly available?
David
_______________________________________________
netsurf-dev mailing list -- netsurf-dev@netsurf-browser.org
To unsubscribe send an email to netsurf-dev-leave@netsurf-browser.org
Is there a plan to support IPv6 on RISC OS, now the RISC OS Developments
TCP/IP stack (Internet V7) is commonly available?
David
_______________________________________________
netsurf-dev mailing list -- netsurf-dev@netsurf-browser.org
To unsubscribe send an email to netsurf-dev-leave@netsurf-browser.org
Friday, 10 March 2023
Re: [Rpcemu] Network Printing from RPCEmu
In article <8cbe6e825a.jbilton@jbilton.stjohnsarc.org.uk>,
John Bilton <jbilton@freeuk.com> wrote:
> Hello,
> I am using v0.94 of RPCEmu on a Windows 10 machine
> to emulate RiscOS v4.02. It works well and I can
> access websites from RiscOS using !Netsurf v3.10.
> I need to be able to access a network printer on
> the host network (say at address 192.168.1.15) and
> have not yet been able to achieve that. Printing
> via PDFPrint, transferring the file through hostfs,
> then using a Windows host machine to print the file
> on the network printer is far too slow, although
> it does work.
> I was hoping to be able to use the network printer
> directly with a RiscOS driver such as RemotePrinterFS.
> The script 'RemotePrinterFS#proto=LPD;address=192.
> 168.1.15;sendfirst=controlfile:' works well from
> native RiscOS machines to the network printer.
> Is there any way this could be achieved on emulated
> RiscOS machines, using RPCEmu? I had wondered if the
> recent addition of port forwarding to RPCEmu might
> be the answer, but I cannot find any instructions on
> its use and comments from user groups seem to suggest
> that its principal use is to facilitate the hosting
> of a RiscOS website server under RPCEmu. A very useful
> purpose, but the ability to print files quickly is
> more important from my viewpoint.
> Any suggestions would be much appreciated.
> Many thanks, John Bilton
John,
All the computers in this house are LAN connected to a couple of printers,
the most used one being a HP Laserjet 2055dn
One of my many emulated RISC OS installs is on a RPCEmu 0.9.4 running RISC
OS 5.29, this connects and prints perfectly okay to the HP LJ.
I use JetDirect to facilitate the connection with all my emulated RISC OS
installs.
VRPC-DL and RPCEmu running various version of RISC OS.
In the RPCEmu Printer manager 1.90 and in the connection dialogue window
(Shift + Adjust click) I have "JetDirectFS:192.168.0.16" (Sans quotes)
which is obviously the address of the LJ printer.
Dave
--
Dave Triffid
_______________________________________________
RPCEmu mailing list
RPCEmu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
John Bilton <jbilton@freeuk.com> wrote:
> Hello,
> I am using v0.94 of RPCEmu on a Windows 10 machine
> to emulate RiscOS v4.02. It works well and I can
> access websites from RiscOS using !Netsurf v3.10.
> I need to be able to access a network printer on
> the host network (say at address 192.168.1.15) and
> have not yet been able to achieve that. Printing
> via PDFPrint, transferring the file through hostfs,
> then using a Windows host machine to print the file
> on the network printer is far too slow, although
> it does work.
> I was hoping to be able to use the network printer
> directly with a RiscOS driver such as RemotePrinterFS.
> The script 'RemotePrinterFS#proto=LPD;address=192.
> 168.1.15;sendfirst=controlfile:' works well from
> native RiscOS machines to the network printer.
> Is there any way this could be achieved on emulated
> RiscOS machines, using RPCEmu? I had wondered if the
> recent addition of port forwarding to RPCEmu might
> be the answer, but I cannot find any instructions on
> its use and comments from user groups seem to suggest
> that its principal use is to facilitate the hosting
> of a RiscOS website server under RPCEmu. A very useful
> purpose, but the ability to print files quickly is
> more important from my viewpoint.
> Any suggestions would be much appreciated.
> Many thanks, John Bilton
John,
All the computers in this house are LAN connected to a couple of printers,
the most used one being a HP Laserjet 2055dn
One of my many emulated RISC OS installs is on a RPCEmu 0.9.4 running RISC
OS 5.29, this connects and prints perfectly okay to the HP LJ.
I use JetDirect to facilitate the connection with all my emulated RISC OS
installs.
VRPC-DL and RPCEmu running various version of RISC OS.
In the RPCEmu Printer manager 1.90 and in the connection dialogue window
(Shift + Adjust click) I have "JetDirectFS:192.168.0.16" (Sans quotes)
which is obviously the address of the LJ printer.
Dave
--
Dave Triffid
_______________________________________________
RPCEmu mailing list
RPCEmu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
Thursday, 9 March 2023
[Rpcemu] Network Printing from RPCEmu
Hello,
I am using v0.94 of RPCEmu on a Windows 10 machine
to emulate RiscOS v4.02. It works well and I can
access websites from RiscOS using !Netsurf v3.10.
I need to be able to access a network printer on
the host network (say at address 192.168.1.15) and
have not yet been able to achieve that. Printing
via PDFPrint, transferring the file through hostfs,
then using a Windows host machine to print the file
on the network printer is far too slow, although
it does work.
I was hoping to be able to use the network printer
directly with a RiscOS driver such as RemotePrinterFS.
The script 'RemotePrinterFS#proto=LPD;address=192.
168.1.15;sendfirst=controlfile:' works well from
native RiscOS machines to the network printer.
Is there any way this could be achieved on emulated
RiscOS machines, using RPCEmu? I had wondered if the
recent addition of port forwarding to RPCEmu might
be the answer, but I cannot find any instructions on
its use and comments from user groups seem to suggest
that its principal use is to facilitate the hosting
of a RiscOS website server under RPCEmu. A very useful
purpose, but the ability to print files quickly is
more important from my viewpoint.
Any suggestions would be much appreciated.
Many thanks, John Bilton
This e-mail message and accompanying data is confidential and for use by the addressee only. If you are not the intended recipient, you must not use, disclose, copy or forward this transmission. Please return the message to the sender by replying to it and then delete the message and accompanying data from your computer.
_______________________________________________
RPCEmu mailing list
RPCEmu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
I am using v0.94 of RPCEmu on a Windows 10 machine
to emulate RiscOS v4.02. It works well and I can
access websites from RiscOS using !Netsurf v3.10.
I need to be able to access a network printer on
the host network (say at address 192.168.1.15) and
have not yet been able to achieve that. Printing
via PDFPrint, transferring the file through hostfs,
then using a Windows host machine to print the file
on the network printer is far too slow, although
it does work.
I was hoping to be able to use the network printer
directly with a RiscOS driver such as RemotePrinterFS.
The script 'RemotePrinterFS#proto=LPD;address=192.
168.1.15;sendfirst=controlfile:' works well from
native RiscOS machines to the network printer.
Is there any way this could be achieved on emulated
RiscOS machines, using RPCEmu? I had wondered if the
recent addition of port forwarding to RPCEmu might
be the answer, but I cannot find any instructions on
its use and comments from user groups seem to suggest
that its principal use is to facilitate the hosting
of a RiscOS website server under RPCEmu. A very useful
purpose, but the ability to print files quickly is
more important from my viewpoint.
Any suggestions would be much appreciated.
Many thanks, John Bilton
This e-mail message and accompanying data is confidential and for use by the addressee only. If you are not the intended recipient, you must not use, disclose, copy or forward this transmission. Please return the message to the sender by replying to it and then delete the message and accompanying data from your computer.
_______________________________________________
RPCEmu mailing list
RPCEmu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
Subscribe to:
Posts (Atom)