G'day folks, bit of advice please.

Aside from ticking ShareFS 'On' in RISC OS Networking, is there any other configuring required to get RISC OS computers to communicate over a LAN?

Assume all the computers are fully network configured, both LAN and WAN.
As it now stands, sometimes they'll communicate with each other, sometimes
not.

Thanks
Dave

--

Dave Triffid

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

In article <5a748190d0dave@triffid.co.uk>, Dave <dave@triffid.co.uk>
wrote:

G'day folks, bit of advice please.

Aside from ticking ShareFS 'On' in RISC OS Networking, is there any
other configuring required to get RISC OS computers to communicate
over a LAN?

Assume all the computers are fully network configured, both LAN and
WAN. As it now stands, sometimes they'll communicate with each
other, sometimes not.

I'm not aware of any ShareFS options in Boot.Configuration > Network
but you might like to try this:

Create an Obeyfile with the single instruction

Share <disc name>

give it a name (example myshare) and drag in Boot.Tasks

For example on my ARMX6 I have an Obeyfile in Boot.Tasks containing...

Share SCSI::SSD

Richard

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

In article <5a748190d0dave@triffid.co.uk>,
Dave <dave@triffid.co.uk> wrote:

G'day folks, bit of advice please.

Aside from ticking ShareFS 'On' in RISC OS Networking, is there any
other configuring required to get RISC OS computers to communicate
over a LAN?

Assume all the computers are fully network configured, both LAN and
WAN. As it now stands, sometimes they'll communicate with each
other, sometimes not.

When copying material from one VRPC to another VRPC on the same
network, occasionally the receiving ShareFS doesn't show the supplying
one. But I find that there's sometimes a time lag, and if I wait a few
seconds the source computer shows up.

But from experience of your questions, Dave, I've probably given the
wrong answer as usual. 8-)

Michael Harding
Rev. Preb. M.D. Harding riscos@mdharding.org.uk

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

In article <5a74ae20a4cvjazz@waitrose.com>,
Chris Newman <cvjazz@waitrose.com> wrote:

In article <5a748190d0dave@triffid.co.uk>, Dave <dave@triffid.co.uk>
wrote:

G'day folks, bit of advice please.

Aside from ticking ShareFS 'On' in RISC OS Networking, is there any
other configuring required to get RISC OS computers to communicate over
a LAN?

Assume all the computers are fully network configured, both LAN and
WAN. As it now stands, sometimes they'll communicate with each other, sometimes not.

See Bernard Veasey's networking tips at...

https://www.bapfish.org.uk/networking.htm

Very useful article.

I must proof read before I send.

--
Chris Newman

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

In article <5a748190d0dave@triffid.co.uk>, Dave <dave@triffid.co.uk>
wrote:

G'day folks, bit of advice please.

Aside from ticking ShareFS 'On' in RISC OS Networking, is there any
other configuring required to get RISC OS computers to communicate over
a LAN?

Assume all the computers are fully network configured, both LAN and
WAN. As it now stands, sometimes they'll communicate with each other, sometimes not.

See bernardveasey's networking tips at...

https://www.bapfish.org.uk/networking.htm


Very useful article.

--
Chris Newman

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

In message <5a748190d0dave@triffid.co.uk>
Dave <dave@triffid.co.uk> wrote:

G'day folks, bit of advice please.

Aside from ticking ShareFS 'On' in RISC OS Networking, is there any other configuring required to get RISC OS computers to communicate over a LAN?

Assume all the computers are fully network configured, both LAN and WAN.
As it now stands, sometimes they'll communicate with each other, sometimes not.

I don't think we know enough yet about the symptoms you're seeing.

Once a pair of drives are communicating, do they continue to do so until
they are powered down?

Do they ever start communicating after initially failing, without any intervention from you?

When you look at the "Resources:$.Discs" window (by clicking on the Discs
icon on the icon bar), for any given drive, is it visible in that window
on all the machines on the LAN?

What sets the discs to be shared? Is it a line in your boot choices
somewhere? If so, does boot ever fail to complete with any other
error(s)?

David

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

In article <5a749e7d69riscos@mdharding.org.uk>,
M Harding <riscos@mdharding.org.uk> wrote:

In article <5a748190d0dave@triffid.co.uk>,
Dave <dave@triffid.co.uk> wrote:

G'day folks, bit of advice please.

Aside from ticking ShareFS 'On' in RISC OS Networking, is there any
other configuring required to get RISC OS computers to communicate
over a LAN?

Assume all the computers are fully network configured, both LAN and
WAN. As it now stands, sometimes they'll communicate with each
other, sometimes not.

When copying material from one VRPC to another VRPC on the same
network, occasionally the receiving ShareFS doesn't show the supplying
one. But I find that there's sometimes a time lag, and if I wait a few seconds the source computer shows up.

But from experience of your questions, Dave, I've probably given the
wrong answer as usual. 8-)

Michael Harding
Rev. Preb. M.D. Harding riscos@mdharding.org.uk

You've not given the wrong answer Michael.

In the case in question, sometimes one of the RISC OS installs never shows
up until I reboot all the machines on the LAN.

Dave

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

In article <5a74ae20a4cvjazz@waitrose.com>,
Chris Newman <cvjazz@waitrose.com> wrote:

In article <5a748190d0dave@triffid.co.uk>, Dave <dave@triffid.co.uk>
wrote:

G'day folks, bit of advice please.

Aside from ticking ShareFS 'On' in RISC OS Networking, is there any
other configuring required to get RISC OS computers to communicate over
a LAN?

Assume all the computers are fully network configured, both LAN and
WAN. As it now stands, sometimes they'll communicate with each other, sometimes not.

See bernardveasey's networking tips at...

https://www.bapfish.org.uk/networking.htm

Very useful article.

Yes Chris, I've seen Bernard's article in the past, but it's not really relevant to this ShareFS problem.

But thanks for the thought.

Dave

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

In article <5a7486718fbasura@invalid.addr.uk>,
Richard Ashbery <basura@invalid.addr.uk> wrote:

In article <5a748190d0dave@triffid.co.uk>, Dave <dave@triffid.co.uk>
wrote:

G'day folks, bit of advice please.

Aside from ticking ShareFS 'On' in RISC OS Networking, is there any
other configuring required to get RISC OS computers to communicate
over a LAN?

Assume all the computers are fully network configured, both LAN and
WAN. As it now stands, sometimes they'll communicate with each
other, sometimes not.

I'm not aware of any ShareFS options in Boot.Configuration > Network
but you might like to try this:

Create an Obeyfile with the single instruction

Share <disc name>

give it a name (example myshare) and drag in Boot.Tasks

For example on my ARMX6 I have an Obeyfile in Boot.Tasks containing...

Share SCSI::SSD

Richard

Thank you for that thought Richard,

I do already have a file in Task setup to do that.

Dave

--

Dave Triffid

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

In article <2d69b5745a.DaveMeUK@BeagleBoard-xM>,
David Higton <dave@davehigton.me.uk> wrote:

In message <5a748190d0dave@triffid.co.uk>
Dave <dave@triffid.co.uk> wrote:

G'day folks, bit of advice please.
Aside from ticking ShareFS 'On' in RISC OS Networking, is there any
other configuring required to get RISC OS computers to communicate
over a LAN?

Assume all the computers are fully network configured, both LAN and
WAN. As it now stands, sometimes they'll communicate with each other, sometimes not.

I don't think we know enough yet about the symptoms you're seeing.

Once a pair of drives are communicating, do they continue to do so until
they are powered down?

Do they ever start communicating after initially failing, without any intervention from you?

When you look at the "Resources:$.Discs" window (by clicking on the Discs icon on the icon bar), for any given drive, is it visible in that window
on all the machines on the LAN?

What sets the discs to be shared? Is it a line in your boot choices somewhere? If so, does boot ever fail to complete with any other
error(s)?

David

Thanks for the prompts David, I'll make some time Saturday to revisit the problem and see if I can supply more details.
Thanks

Dave

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 10 Feb, news@triffid.co.uk wrote:

In article <2d69b5745a.DaveMeUK@BeagleBoard-xM>,
David Higton <dave@davehigton.me.uk> wrote:

[Snip]

What sets the discs to be shared? Is it a line in your boot choices somewhere? If so, does boot ever fail to complete with any other
error(s)?

David

Thanks for the prompts David, I'll make some time Saturday to revisit the problem and see if I can supply more details.
Thanks

Dave

Right... I've spent a lot of time/many hours today (Saturday) going
through the VRPC RISC OS installs, and one Hardware SARPC, checking what
was what. :-(

Four of the machines on the LAN in RISC OS mode, including the SARPC, all communicated with each other okay, the fifth RISC OS install was the fly
in the ointment, it would show some Shares but not others, and when it was running, something it was doing would mess up comms between the others,
who without it were usually working okay.

I couldn't fathom out exactly what was going wrong, so I piped out any/all entries in files that might be affecting the fifth machines ShareFS.

There are a few in Tasks.

I wrote in those files what I thought the entries should be, or in some
cases left the entries piped out.

Rebooted the whole kit 'n caboodle, that's all the machines, and all the
RISC OS installs.

Thereafter forwards or backwards (Nb) running the machines, ShareFS worked correctly every time and on all machines.

Again, thanks for the prompt, it got me out of the doldrums to doing some thinking and testing.

Dave


Nb: After the hours of testing,testing... And then switching all the
machine off...
Starting up with machine 1, then adding machine two, then machine 3,4,5 checking the Shares were appearing okay.

Then doing it in reverse. Starting up machine 5 first, then adding machine 4,3,2,1 and checking the Shares were appearing okay.
They were.

And still are...
D.

--

Dave Triffid

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)