Re: [Rpcemu] Network setup question
On 7 Mar 2013, Dave Symes d...@triffid.co.uk wrote:
In article fd735f2853.old_coaster@old_coaster.yahoo.co.uk,
Tony Moore old_coas...@yahoo.co.uk wrote:
On 6 Mar 2013, Dave Symes d...@triffid.co.uk wrote:
Next question relates to ShareFS.
All my machines have names attached to their IP address, and those
names show up in the ShareFS Menu-Show discs window on any RO
Sys that's running, however, even though RPCEmu has a name
(Blackfan) attached to its address, it doesn't present as the
given differentiating name, but presents as HardDisc4 everywhere.
I believe that the IP address is not relevant to ShareFS. If the
disc which you are sharing has its icon on the iconbar, Menu Share
etc will create a ShareFS share, with the same name as the disc.
This doesn't work with HostFS because there is no iconbar Menu. In
this case, you need an obey file, ShareFS_setup, in boot Tasks,
containing something like
ShareFSWindow 1 { null: }
ShareFSIcon aaa
Share HostFS:$ bbb
where aaa is the name of a remote disc displayed on the local
iconbar, and bbb is the name allocated to the HostFS share, to be
displayed on a remote iconbar. The first line ensures ShareFS
transfer reliability.
Thanks for the thought Tony, though it doesn't appear to be correct.
:-(
You need to read the small-print :)
I already have in Tasks an Obey Shares setup file.
It contains:
ShareFSWindow 1 { null: }
ShareFSIcon Public
(That gives me just a single icon on every RO install, including
RPCEmu, from which I use the menu to select which RO share I want to
activate, as I don't want them all auto mounted, as that would be a
lot of Iconbar real estate gone.) It also give Me and She a single
directory, common over all the machines into which we can put stuff
for the other person.
Here, *ShareFSIcon Public adds an icon to the iconbar, from which I can
mount any of the available ShareFS shares, but there is no Public
directory on this machine. Do you have an actual Public directory - and
if so, where? - or is it a device for accessing the ShareFS shares?
If I add to that as you note above, two things happen.
1) I get an error message Filing system or path HostFS not present.
The *Share HostFS line may appear in the ShareFS setup file, _only_ if
HostFS is present in the system, ie RPCEmu. The setup file for RPCEmu
cannot be the same as for the real RiscPCs.
2) I then still get the HardDisc4 icon as the FS link to the Emu
machine. Obviously...
You could change the name of your RPCEmu ADFS drive but, if you wish to
retain the current generic name, try including a line in the ShareFS
setup file (for the RPCEmu machine only)
*Share ADFS::HardDisc4.$ Blackfan
where Blackfan is your name for the share (as below)
The interesting bit is... With just my plain two line Obey, if all the
Real RPCs are running they all show the names assigned to them in
Hosts... There's nowhere else they are given a name.
That I cannot understand. Here, the Hosts names, and ShareFS names,
differ. Maybe someone else can shed some light?
Of course with the exception of the RPCEmu install which shows as
HardDisc4 instead of its Host name of Blackfan (Which is also the Host
name of the Win machine)
[snip VRPC]
I don't have VRPC, so cannot comment.
My brain hurts...
Not the only one!
Tony
___
Rpcemu mailing list
Rpcemu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
Re: [Rpcemu] Network setup question
In article 8cc4b62853.old_coaster@old_coaster.yahoo.co.uk,
Tony Moore old_coas...@yahoo.co.uk wrote:
On 7 Mar 2013, Dave Symes d...@triffid.co.uk wrote:
In article fd735f2853.old_coaster@old_coaster.yahoo.co.uk,
Tony Moore old_coas...@yahoo.co.uk wrote:
On 6 Mar 2013, Dave Symes d...@triffid.co.uk wrote:
Next question relates to ShareFS.
All my machines have names attached to their IP address, and those
names show up in the ShareFS Menu-Show discs window on any RO
Sys that's running, however, even though RPCEmu has a name
(Blackfan) attached to its address, it doesn't present as the
given differentiating name, but presents as HardDisc4 everywhere.
I believe that the IP address is not relevant to ShareFS. If the
disc which you are sharing has its icon on the iconbar, Menu Share
etc will create a ShareFS share, with the same name as the disc.
This doesn't work with HostFS because there is no iconbar Menu. In
this case, you need an obey file, ShareFS_setup, in boot Tasks,
containing something like
ShareFSWindow 1 { null: }
ShareFSIcon aaa
Share HostFS:$ bbb
where aaa is the name of a remote disc displayed on the local
iconbar, and bbb is the name allocated to the HostFS share, to be
displayed on a remote iconbar. The first line ensures ShareFS
transfer reliability.
Thanks for the thought Tony, though it doesn't appear to be correct.
:-(
You need to read the small-print :)
Sorry, Have I missed something?
I already have in Tasks an Obey Shares setup file.
It contains:
ShareFSWindow 1 { null: }
ShareFSIcon Public
(That gives me just a single icon on every RO install, including
RPCEmu, from which I use the menu to select which RO share I want to
activate, as I don't want them all auto mounted, as that would be a
lot of Iconbar real estate gone.) It also give Me and She a single
directory, common over all the machines into which we can put stuff
for the other person.
Here, *ShareFSIcon Public adds an icon to the iconbar, from which I can
mount any of the available ShareFS shares, but there is no Public
directory on this machine. Do you have an actual Public directory - and
if so, where? - or is it a device for accessing the ShareFS shares?
It's actually a $.Directory on these machines.
If I add to that as you note above, two things happen.
1) I get an error message Filing system or path HostFS not present.
The *Share HostFS line may appear in the ShareFS setup file, _only_ if
HostFS is present in the system, ie RPCEmu. The setup file for RPCEmu
cannot be the same as for the real RiscPCs.
Sorry, don't understand that?
2) I then still get the HardDisc4 icon as the FS link to the Emu
machine. Obviously...
You could change the name of your RPCEmu ADFS drive but, if you wish to
retain the current generic name, try including a line in the ShareFS
setup file (for the RPCEmu machine only)
*Share ADFS::HardDisc4.$ Blackfan
where Blackfan is your name for the share (as below)
Yes that does work, but I'm still getting a HardDisc4 share as well in the
Shares window.
Dave
--
Dave Triffid
___
Rpcemu mailing list
Rpcemu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
Re: [Rpcemu] Network setup question
On 7 Mar 2013, Dave Symes d...@triffid.co.uk wrote: In article 8cc4b62853.old_coaster@old_coaster.yahoo.co.uk, Tony Moore old_coas...@yahoo.co.uk wrote: On 7 Mar 2013, Dave Symes d...@triffid.co.uk wrote: [snip] Here, *ShareFSIcon Public adds an icon to the iconbar, from which I can mount any of the available ShareFS shares, but there is no Public directory on this machine. Do you have an actual Public directory - and if so, where? - or is it a device for accessing the ShareFS shares? It's actually a $.Directory on these machines. Having created a Public directory in the root of my RiscPC, the ShareFS Public icon remains greyed-out, and a select click on it does nothing. However, *share ADFS::ide.$.Public Public causes a share to be created, the Public icon is no longer greyed-out, and a select click on it opens the Public directory. The Public directory, on the RiscPC, can also then be accessed from RPCEmu. If you are using the Public directory as a container, accessed from any machine, I believe that the _active_ Public directory exists on only one machine, and the other machines access its ShareFS share. Try opening each Public directory, via the _filer_, and compare their contents. It seems likely that only one of them will have actual content and, lurking in the boot of that machine, will be a *share ... Public instruction. Locate should find it. If I add to that as you note above, two things happen. 1) I get an error message Filing system or path HostFS not present. The *Share HostFS line may appear in the ShareFS setup file, _only_ if HostFS is present in the system, ie RPCEmu. The setup file for RPCEmu cannot be the same as for the real RiscPCs. Sorry, don't understand that? If you wish to share the HostFS of RPCEmu, the ShareFS setup file, in RPCEmu boot, could include *Share HostFS:$ Emu_HFS (or whatever). HostFS is not present in a real RiscPC, so the ShareFS setup file, in the RiscPC boot, should not refer to HostFS. 2) I then still get the HardDisc4 icon as the FS link to the Emu machine. Obviously... You could change the name of your RPCEmu ADFS drive but, if you wish to retain the current generic name, try including a line in the ShareFS setup file (for the RPCEmu machine only) *Share ADFS::HardDisc4.$ Blackfan where Blackfan is your name for the share (as below) Yes that does work, but I'm still getting a HardDisc4 share as well in the Shares window. The HardDisc4 share must have been created - it couldn't just happen. Try searching the RPCEmu !Boot, using Locate, to find files containing the word Share Tony ___ Rpcemu mailing list Rpcemu@riscos.info http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
Re: [Rpcemu] Network setup question
Settings Reduce CPU usage It makes a big difference to the availability of the CPU, for other Windows tasks. Tony I think that depends on the underlying system: on this quad-core i7 3.4GHz machine, RPCEmu seldom exceeds 15% processor usage, i.e., a little over half of one core. I've tried the 'Reduce CPU usage' option, but can't say I've noticed any benefit on the Windows side. OTH, activating it definitely buggers up !Rhapsody's sound rendition, so I generally leave it turned off. George RPCEmu089/402, Win7 64-bit. -- george greenfield ___ Rpcemu mailing list Rpcemu@riscos.info http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
Re: [Rpcemu] Network setup question
In article dd7a1c2853.old_coaster@old_coaster.yahoo.co.uk, Tony Moore old_coas...@yahoo.co.uk wrote: On 6 Mar 2013, Dave Symes d...@triffid.co.uk wrote: [Snippy] One question though. cpu-idle = 1 on your setup, on mine it's = 0 (obviously yours is On mine is Off) but in real terms what does it mean? Settings Reduce CPU usage It makes a big difference to the availability of the CPU, for other Windows tasks. Tony Ah I see. As it's installed on a 3GHz multicore machine, I guess it won't make much difference. Thanks for the info. There was a bug related to that setting in a version of Emu, has it been fixed. Dave Aside... I discovered a short while ago that creating the bridge made a total FU of my (Lot of) use of Uniserver, sending stuff from SARPC Win and particularly Firefox, and also Copy/Pasting between the machines. Creating the bridge wiped out all my manual settings, but of course I wasn't aware that DHCP had been engaged, and couldn't fathom why it was all FU. Obviously now all reconfigured manually so that Uniserver can once again serve. D. -- Dave Triffid ___ Rpcemu mailing list Rpcemu@riscos.info http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
Re: [Rpcemu] Network setup question
On 6 Mar 2013, george greenfield george.greenfi...@tiscali.co.uk wrote: Settings Reduce CPU usage It makes a big difference to the availability of the CPU, for other Windows tasks. Tony I think that depends on the underlying system: on this quad-core i7 3.4GHz machine, RPCEmu seldom exceeds 15% processor usage, i.e., a little over half of one core. I've tried the 'Reduce CPU usage' option, but can't say I've noticed any benefit on the Windows side. You're right, of course. My system is a more modest dual-core, 1.6GHz. On that, the CPU usage varies from 60% (cpu-idle off), to less than 10% (cpu-idle on). Obviously, this depends on what RPCEmu is actually doing. OTH, activating it definitely buggers up !Rhapsody's sound rendition, so I generally leave it turned off. A different matter, but clearly a good reason to turn it off! Tony ___ Rpcemu mailing list Rpcemu@riscos.info http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
Re: [Rpcemu] Network setup question
On 6 Mar 2013, Dave Symes d...@triffid.co.uk wrote: In article dd7a1c2853.old_coaster@old_coaster.yahoo.co.uk, Tony Moore old_coas...@yahoo.co.uk wrote: [snip] Settings Reduce CPU usage [snip] There was a bug related to that setting in a version of Emu, has it been fixed. I seem to remember problems being reported, but I've no idea if they related to a bug, nor whether it may have been fixed. No problem here, using RPCEmu089 and RO439/519/620 on Win7 32bit. Tony ___ Rpcemu mailing list Rpcemu@riscos.info http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
Re: [Rpcemu] Network setup question
Next question relates to ShareFS. All my machines have names attached to their IP address, and those names show up in the ShareFS Menu-Show discs window on any RO Sys that's running, however, even though RPCEmu has a name (DBF) attached to its address, it doesn't present as the given differentiating name, but presents as HardDisc4 everywhere. I'm out of ideas... Any thoughts please? Thanks Dave -- Dave Triffid ___ Rpcemu mailing list Rpcemu@riscos.info http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
Re: [Rpcemu] Network setup question
On 5 Mar 2013, Dave Symes d...@triffid.co.uk wrote: RPCEmu 0.8.9. running on Win 7 Pro (As Administrator). [snip] On RO 6.20 yes well! The AppleTalk module wouldn't stay dead... But I've now sorted that with an early Obey file. The simplest way of ensuring that AppleTalk is not loaded is to add the line X Unplug AppleTalk to te file !Boot.Resources.!Internet.!Run at new line 42, where several other modules are unplugged. It is also essential to comment-out line 65, of the same file, which seeks to RMLoad AppleTalk And... The ...!System.310.Modules.Network now contains EtherRPCEm Correct. But the problem appears to be just where to put the AutoSense directory on a 6.20 OS While it does work in the (notes) advised place in RO 4.39, in 6.20 Boot.RO430Hook.Res.Configure.!NetSetup.!IFSetup.AutoSense this doesn't work Here the BASIC program is at !Boot.RO440Hook.Res.Configure.!NetSetup.!IFSetup.AutoSense.EtherRPCEm and the Boot Configuration-Network configuration Interfaces remains stubbornly without a RPCEmu option. OK here, with the above settings. Tony ___ Rpcemu mailing list Rpcemu@riscos.info http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
Re: [Rpcemu] Network setup question
In article 8097d12753.old_coaster@old_coaster.yahoo.co.uk, Tony Moore old_coas...@yahoo.co.uk wrote: On 5 Mar 2013, Dave Symes d...@triffid.co.uk wrote: RPCEmu 0.8.9. running on Win 7 Pro (As Administrator). [snip] On RO 6.20 yes well! The AppleTalk module wouldn't stay dead... But I've now sorted that with an early Obey file. The simplest way of ensuring that AppleTalk is not loaded is to add the line X Unplug AppleTalk to te file !Boot.Resources.!Internet.!Run at new line 42, where several other modules are unplugged. Mmnnn! not thought of doing it that way, I've gone the route of an obey file run during the early part of the !Boot sequence, but yours is a better option methinks. It is also essential to comment-out line 65, of the same file, which seeks to RMLoad AppleTalk Yup! that was done, I still have the notes from when we played with this problem in the past with 4.39 And... The ...!System.310.Modules.Network now contains EtherRPCEm Correct. But the problem appears to be just where to put the AutoSense directory on a 6.20 OS While it does work in the (notes) advised place in RO 4.39, in 6.20 Boot.RO430Hook.Res.Configure.!NetSetup.!IFSetup.AutoSense this doesn't work Here the BASIC program is at !Boot.RO440Hook.Res.Configure.!NetSetup.!IFSetup.AutoSense.EtherRPCEm Ah indeedy, that seems to be the place and I now have networking on the Emu 6.20 and the Boot Configuration-Network configuration Interfaces remains stubbornly without a RPCEmu option. OK here, with the above settings. Tony Thanks Dave -- Dave Triffid ___ Rpcemu mailing list Rpcemu@riscos.info http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
Re: [Rpcemu] Network setup question
In article 5327dac7ddd...@triffid.co.uk, Dave Symes d...@triffid.co.uk wrote: Ah indeedy, that seems to be the place and I now have networking on the Emu 6.20 Still one remaining problem though. The Bridge on the PC W7 Pro remains okay, but after a reboot the RPCEmu has lost it's config to the bridge and I have to re-set it every time. (RPCEmu toolbar menu Networking). Is there a bug here, or is there some way to make it persist after a boot? Dave -- Dave Triffid ___ Rpcemu mailing list Rpcemu@riscos.info http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
Re: [Rpcemu] Network setup question
On 5 Mar 2013, Dave Symes d...@triffid.co.uk wrote: In article 8097d12753.old_coaster@old_coaster.yahoo.co.uk, Tony Moore old_coas...@yahoo.co.uk wrote: [snip] The simplest way of ensuring that AppleTalk is not loaded is to add the line X Unplug AppleTalk to te file !Boot.Resources.!Internet.!Run at new line 42, where several other modules are unplugged. Mmnnn! not thought of doing it that way, I've gone the route of an obey file run during the early part of the !Boot sequence, but yours is a better option methinks. Originally Frank de Bruijn's idea. Tony ___ Rpcemu mailing list Rpcemu@riscos.info http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
Re: [Rpcemu] Network setup question
On 5 Mar 2013, Dave Symes d...@triffid.co.uk wrote: In article 5327dac7ddd...@triffid.co.uk, Dave Symes d...@triffid.co.uk wrote: Ah indeedy, that seems to be the place and I now have networking on the Emu 6.20 Still one remaining problem though. The Bridge on the PC W7 Pro remains okay, but after a reboot the RPCEmu has lost it's config to the bridge and I have to re-set it every time. (RPCEmu toolbar menu Networking). Is there a bug here, or is there some way to make it persist after a boot? Try setting the values in Program Files\RPCEmu\rpc.cfg to bridgename = rpcemu mouse_twobutton = 0 network_type = ethernetbridging mouse_following = 1 cdrom_type = 0 cdrom_enabled = 0 refresh_rate = 60 stretch_mode = 1 sound_enabled = 1 vram_size = 2 cpu_type = SA110 mem_size = 128 cpu_idle = 1 I suspect that you may have mem_size 128, which can cause problems. Tony ___ Rpcemu mailing list Rpcemu@riscos.info http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
Re: [Rpcemu] Network setup question
In article 8c98e32753.old_coaster@old_coaster.yahoo.co.uk, Tony Moore old_coas...@yahoo.co.uk wrote: On 5 Mar 2013, Dave Symes d...@triffid.co.uk wrote: In article 5327dac7ddd...@triffid.co.uk, Dave Symes d...@triffid.co.uk wrote: Ah indeedy, that seems to be the place and I now have networking on the Emu 6.20 Still one remaining problem though. The Bridge on the PC W7 Pro remains okay, but after a reboot the RPCEmu has lost it's config to the bridge and I have to re-set it every time. (RPCEmu toolbar menu Networking). Is there a bug here, or is there some way to make it persist after a boot? Try setting the values in Program Files\RPCEmu\rpc.cfg to bridgename = rpcemu mouse_twobutton = 0 network_type = ethernetbridging mouse_following = 1 cdrom_type = 0 cdrom_enabled = 0 refresh_rate = 60 stretch_mode = 1 sound_enabled = 1 vram_size = 2 cpu_type = SA110 mem_size = 128 cpu_idle = 1 I suspect that you may have mem_size 128, which can cause problems. Tony Thanks for the above note Tony. New day, Wednesday, upon cold boot of the whole system, everything now seems to be working/networking okay. Most of the values here are the same, and as I'm aware of the 128 problems... (Also on VRPC) that's what it's always been set at. One question though. cpu-idle = 1 on your setup, on mine it's = 0 (obviously yours is On mine is Off) but in real terms what does it mean? Thanks Dave -- Dave Triffid ___ Rpcemu mailing list Rpcemu@riscos.info http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
Re: [Rpcemu] Network setup question
In article 5327dd41d9d...@triffid.co.uk, Dave Symes d...@triffid.co.uk wrote: In article 5327dac7ddd...@triffid.co.uk, Dave Symes d...@triffid.co.uk wrote: Ah indeedy, that seems to be the place and I now have networking on the Emu 6.20 Still one remaining problem though. The Bridge on the PC W7 Pro remains okay, but after a reboot the RPCEmu has lost it's config to the bridge and I have to re-set it every time. (RPCEmu toolbar menu Networking). Is there a bug here, or is there some way to make it persist after a boot? Dave Just to round off, as I mentioned in my reply to Tony... New day and a cold boot, the Emu networking is still active, so yesterdays niggle was undoubtedly just a glitch at my end. Dave -- Dave Triffid ___ Rpcemu mailing list Rpcemu@riscos.info http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
Re: [Rpcemu] Network setup question
On Thu, Feb 28, 2013 at 06:20:28AM +, Dave Symes wrote: The question: It says in the Networking info (Windows side) that because XP doesn't have a native TAP driver, one needs to be installed, and that's what happened some while back when I did get RPCEmu networking on an XP install. Does Win-7 Pro have its own TAP driver, if so, does it obviate installing an additional TAP driver? All versions of windows need the tap driver installed, I'll tweak the docs. Peter -- Peter Howkins peter.howk...@marutan.net ___ Rpcemu mailing list Rpcemu@riscos.info http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
Re: [Rpcemu] Network setup question
In article 20130228103957.ga9...@spod.org, Peter Howkins rpcemu.howk...@marutan.net wrote: On Thu, Feb 28, 2013 at 06:20:28AM +, Dave Symes wrote: The question: It says in the Networking info (Windows side) that because XP doesn't have a native TAP driver, one needs to be installed, and that's what happened some while back when I did get RPCEmu networking on an XP install. Does Win-7 Pro have its own TAP driver, if so, does it obviate installing an additional TAP driver? All versions of windows need the tap driver installed, I'll tweak the docs. Peter Thank Tony and Peter. Dave -- Dave Triffid ___ Rpcemu mailing list Rpcemu@riscos.info http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
