Hi All

Does anyone know of a set of instructions for getting a RISC OS machine
talking and sharing files with :

1. A Windoz 11 machine
2. A Linux based machine.

I recently updated Uniprint, but found that the instructions largely
relate to a Windoze 7 Machine.( Which is when I last did this sort of set
up!

Any help would be appreciated. As an aside my new machine is dual boot,
and I am hoping to use the Linux side more than the PC side. Linux has
moved on a lot since I last played with it when Paul Beverley was still
master of Archive!

John


--
_________________________________________
| University of Glos. Blighting Longlevens.
| mailto:john@jpeachey.co.uk
_______________________| http://www.jpeachey.co.uk

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

In message <c12d71545c.john@user.orpheusmail.co.uk>
J Peachey <john@jpeachey.co.uk> wrote:

Hi All

Does anyone know of a set of instructions for getting a RISC OS machine talking and sharing files with :

1. A Windoz 11 machine
2. A Linux based machine.

I recently updated Uniprint, but found that the instructions largely
relate to a Windoze 7 Machine.( Which is when I last did this sort of set
up!

It is basically the same setup on Windows 11 as Windows 7 for Uniprint.

I use LanMan98 v2.08 (free) to connect my RISC OS computers to Windows 11.

Any help would be appreciated. As an aside my new machine is dual boot,
and I am hoping to use the Linux side more than the PC side. Linux has
moved on a lot since I last played with it when Paul Beverley was still master of Archive!

Can't advise on Linux really. although I think you might need Sunfish on
the RISC OS side of things to talk to Linux for files

--
Chris Hughes

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

On 2025-08-30, Chris Hughes <news13@noonehere.co.uk> wrote:

In message <c12d71545c.john@user.orpheusmail.co.uk>
J Peachey <john@jpeachey.co.uk> wrote:

Does anyone know of a set of instructions for getting a RISC OS machine
talking and sharing files with :

1. A Windoz 11 machine

Windows, maybe?

2. A Linux based machine.

I wrote this up in the second WROCC Guide To Networking many years ago,
and am not aware that it has changed much since then.

https://www.wrocc.org.uk/newsletter

NFS Server on the Linux box, plus an NFS client on the RISC OS side.

Can't advise on Linux really. although I think you might need Sunfish on
the RISC OS side of things to talk to Linux for files

Or use Samba on the Linux side and LanManFS (or LanMan98 if you really
must) on the RISC OS side.

These days I tend to use the SMB option (Samba + LanManFS) because I've
seen some unexplained and unreproducible file corruption when writing
*large* files to Sunfish using streams (OPENOUT followed by lots of
BPUT#, followed by CLOSE#). I can't say that this is definitely Sunfish,
but as the need to make the Linux box in question accessible to Windows
as well as RISC OS forced the use of Samba, I took the opportunity to
switch to LanManFS on RISC OS and keep an eye on the situation. The type
of corruption being seen was hard to explain from a simple malfunction of
the code in the application doing the writing.

There's also an NFS option in recent Omniclient installations on
RISC OS 5, which works well as an alternative to Sunfish with some
limitations.

--
Steve Fryatt - Leeds, England

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

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

In article <c12d71545c.john@user.orpheusmail.co.uk>,
J Peachey <john@jpeachey.co.uk> wrote:

Hi All

Does anyone know of a set of instructions for getting a RISC OS
machine talking and sharing files with :

1. A Windoz 11 machine
2. A Linux based machine.

It depends. When you say share files with windoze and linux, do you
mean riscos files or PC/NAS/linux files?

I ask because LM98 is excellent for transferring riscos files to and
from a PC/NAS etc. that only use 7 bit characters. BUT !! if you wish
to look at say a music library stored on a NAS then IMHO LM98 is next
to useless. I have found many commonly used utf-8 codes that not only
don't display anything within a file name but many prevent the file
being visible at all. LM98 can't tell the difference between a small
letter a with an acute (C3 A1) and a space (C2 A0), they both return
&A0 in LM98. (Codes in brackets are utf-8.)

On the other hand, Sunfish can be used in a "no conversion mode"
which seems to give the direct UTF-8 codes from a NAS and/or a PC. I
find this a god send, your milage may vary.

To use Sunfish with a PC you need an NFS server installed on the
windoze PC. I've had great success with the haneWIN NFS server. It's
about £23. There is a free server but that is less solid IMHO.

The only issue I have with Sunfish is the front end, it's grim and
patience testing but once you get there Sunfish is King, in my
opinion of course.

OKay LM98, you asked for it...

Connecting with Lanman98 to a W10 or W11 computer. =================================================

Check PC network connection is set to Private !!!!

2). Make sure 'SMB1 Server' is running on the computer.
Control Panel
Programs and features
On LHS - Turn windows features on or off
Slide down the new window..
SMB 1.0 /CIFS File Sharing Support-
SMB 1.0 /CIFS Server = ticked. ------------------------------------------------

3). Control Panel - Network and Sharing Centre.
Change Advanced Sharing Settings.

Private
=======
Turn on network discovery.
Turn on file and printer sharing.

Guest or Public
===============
Turn off network discovery + auto setup.
Turn off file and printer sharing.

All Networks
============
Turn off Public folder sharing.
Set: 128 bit encryption. (works fine for Lanman98)

If the PC has no password at log in then..
Set: Turn off Password Protected Sharing.

If you need a password to use the PC then..
Set: Turn on Password Protected Sharing.

The above works fine W7 to W11 with or without password. ----------------------------------------

4). Make sure the PC thinks it is connected to a private network
and not a public network.


5). Sharing a directory (folder)

Right button click on the folder you wish to share with RISCOS.
Select properties.
In the new Properties window..
Select the Sharing tab.
Click the "Advanced Sharing" button.
In the Advanced Sharing window..
Tick the "Share this folder" tick box.
It then offers a share name the same as the folder
name but you can change that to whatever you like.
Set the share name then click apply.

Click Permissions button, this sets the share permissions.
Give user "Everyone" Full Control.
Click OK in the Permissions window.
Click OK in the Advanced Sharing window.

Now in the Properties window click the Security tab.
This is to set the folder permissions.
Click the Edit button.

In the Permissions window click the Add button.
In the box type: Everyone
Then click Check Names.
Then click OK.
In the permissions window select the
Everyone you've just added.
Tick the allow full control box.
Click OK.
Done !!

You can check the shares offered by the PC.
Run the command prompt and type: net share

This will list shares on the machine.


Lanman98 - the RISCOS end.
==========================

One of the big things here is to tell Lanman98 what
the IP address of the PC is, without that info it
will not be able to connect.

There are two ways to do that:

1. Use the Hosts file at
$.!Boot.Resources.!Internet.files.Hosts
Edit that file and add the IP address and
then the network name of the PC computer.

If you do that then everything on the RISCOS machine
will know the address of the PC including Lanman98.

2. Add the IP address along side the network
name in the Link info for the that connection in
Lanman98 discs.

I don't ever bother with the GUI for setting up share
connections for Lanman98, I just creat a new link file
for it.

Examples link file.

Server: RED << name of PC/NAS on network
Share: mystuff << name of your share on the above.
User: Bob << the user account name.
Password: opensaysme << the password *IF* you use one.


That's it. Don't include the password line if your PC
isn't using passwords and obviously don't include
the << info bits.

Create the file type LM98Link(069) with the above in it.
Obviously the values should be for your PC not mine.

If you have NOT put the IP address of the PC in the Hosts
file then you can add it to the server name in the above
file like this..

Server: RED<192.168.1.36>
Share: mystuff
Etc.


Works great on W11 this week August 2025.


Bob.

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

Hi All,

My sincere thanks to everyone who has answered my request for help,
especially Bob for his blow by blow account, which is just what I needed.

Kind regards
John



In message <5c548b66c5bob@sick-of-spam.invalid>
Bob Latham <bob@sick-of-spam.invalid> wrote:

In article <c12d71545c.john@user.orpheusmail.co.uk>,
J Peachey <john@jpeachey.co.uk> wrote:

Hi All

Does anyone know of a set of instructions for getting a RISC OS
machine talking and sharing files with :

1. A Windoz 11 machine
2. A Linux based machine.

It depends. When you say share files with windoze and linux, do you
mean riscos files or PC/NAS/linux files?

I ask because LM98 is excellent for transferring riscos files to and
from a PC/NAS etc. that only use 7 bit characters. BUT !! if you wish
to look at say a music library stored on a NAS then IMHO LM98 is next
to useless. I have found many commonly used utf-8 codes that not only
don't display anything within a file name but many prevent the file
being visible at all. LM98 can't tell the difference between a small
letter a with an acute (C3 A1) and a space (C2 A0), they both return
&A0 in LM98. (Codes in brackets are utf-8.)

On the other hand, Sunfish can be used in a "no conversion mode"
which seems to give the direct UTF-8 codes from a NAS and/or a PC. I
find this a god send, your milage may vary.

To use Sunfish with a PC you need an NFS server installed on the
windoze PC. I've had great success with the haneWIN NFS server. It's
about £23. There is a free server but that is less solid IMHO.

The only issue I have with Sunfish is the front end, it's grim and
patience testing but once you get there Sunfish is King, in my
opinion of course.

OKay LM98, you asked for it...

Connecting with Lanman98 to a W10 or W11 computer. =================================================

Check PC network connection is set to Private !!!!

2). Make sure 'SMB1 Server' is running on the computer.
Control Panel
Programs and features
On LHS - Turn windows features on or off
Slide down the new window..
SMB 1.0 /CIFS File Sharing Support-
SMB 1.0 /CIFS Server = ticked. ------------------------------------------------

3). Control Panel - Network and Sharing Centre.
Change Advanced Sharing Settings.

Private
=======
Turn on network discovery.
Turn on file and printer sharing.

Guest or Public
===============
Turn off network discovery + auto setup.
Turn off file and printer sharing.

All Networks
============
Turn off Public folder sharing.
Set: 128 bit encryption. (works fine for Lanman98)

If the PC has no password at log in then..
Set: Turn off Password Protected Sharing.

If you need a password to use the PC then..
Set: Turn on Password Protected Sharing.

The above works fine W7 to W11 with or without password. ----------------------------------------

4). Make sure the PC thinks it is connected to a private network
and not a public network.

5). Sharing a directory (folder)

Right button click on the folder you wish to share with RISCOS.
Select properties.
In the new Properties window..
Select the Sharing tab.
Click the "Advanced Sharing" button.
In the Advanced Sharing window..
Tick the "Share this folder" tick box.
It then offers a share name the same as the folder
name but you can change that to whatever you like.
Set the share name then click apply.

Click Permissions button, this sets the share permissions.
Give user "Everyone" Full Control.
Click OK in the Permissions window.
Click OK in the Advanced Sharing window.

Now in the Properties window click the Security tab.
This is to set the folder permissions.
Click the Edit button.

In the Permissions window click the Add button.
In the box type: Everyone
Then click Check Names.
Then click OK.
In the permissions window select the
Everyone you've just added.
Tick the allow full control box.
Click OK.
Done !!

You can check the shares offered by the PC.
Run the command prompt and type: net share

This will list shares on the machine.

Lanman98 - the RISCOS end.
==========================

One of the big things here is to tell Lanman98 what
the IP address of the PC is, without that info it
will not be able to connect.

There are two ways to do that:

1. Use the Hosts file at
$.!Boot.Resources.!Internet.files.Hosts
Edit that file and add the IP address and
then the network name of the PC computer.

If you do that then everything on the RISCOS machine
will know the address of the PC including Lanman98.

2. Add the IP address along side the network
name in the Link info for the that connection in
Lanman98 discs.

I don't ever bother with the GUI for setting up share
connections for Lanman98, I just creat a new link file
for it.

Examples link file.

Server: RED << name of PC/NAS on network
Share: mystuff << name of your share on the above.
User: Bob << the user account name.
Password: opensaysme << the password *IF* you use one.

That's it. Don't include the password line if your PC
isn't using passwords and obviously don't include
the << info bits.

Create the file type LM98Link(069) with the above in it.
Obviously the values should be for your PC not mine.

If you have NOT put the IP address of the PC in the Hosts
file then you can add it to the server name in the above
file like this..

Server: RED<192.168.1.36>
Share: mystuff
Etc.

Works great on W11 this week August 2025.

Bob.

--
_________________________________________
| University of Glos. Blighting Longlevens.
| mailto:john@jpeachey.co.uk
_______________________| http://www.jpeachey.co.uk

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

On 31/08/2025 12:15, J Peachey wrote:

Hi All,

My sincere thanks to everyone who has answered my request for help, especially Bob for his blow by blow account, which is just what I needed.

Kind regards
John

[Snip previous posts]

Please thanks us by not quoting posts below your reply.

---druck

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

In message <5c548b66c5bob@sick-of-spam.invalid>
Bob Latham <bob@sick-of-spam.invalid> wrote:

In article <c12d71545c.john@user.orpheusmail.co.uk>,
J Peachey <john@jpeachey.co.uk> wrote:

Hi All

Does anyone know of a set of instructions for getting a RISC OS
machine talking and sharing files with :

1. A Windoz 11 machine
2. A Linux based machine.

[snip]

If you have NOT put the IP address of the PC in the Hosts
file then you can add it to the server name in the above
file like this..

Server: RED<192.168.1.36>
Share: mystuff
Etc.

Works great on W11 this week August 2025.

Bob.

I have made some progress with this. However when trying to connect to the
PC shares, I get timed out while connecting. Any ideas?

I have Uniprint working swapping URLs and the clipboard. So it look like perhaps the firewall might be intervening. Although a quick look seems to
allow file transfers.

Thanks for your help so far.

John


--
_________________________________________
| University of Glos. Blighting Longlevens.
| mailto:john@jpeachey.co.uk
_______________________| http://www.jpeachey.co.uk

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

In article <70e99a555c.john@user.orpheusmail.co.uk>,
J Peachey <john@jpeachey.co.uk> wrote:

I have made some progress with this. However when trying to connect
to the PC shares, I get timed out while connecting. Any ideas?

I have Uniprint working swapping URLs and the clipboard. So it look
like perhaps the firewall might be intervening. Although a quick
look seems to allow file transfers.

Thanks for your help so far.

Do check that your PC thinks it is connected to a Private network and
not a public network !!

On windows 11 Settings - Network and internet
Diagram at top of page says Properties private or public.

Are you using a password on the PC? It has to be a local password not
an on-line microsoft account password !!

Have you changed the permissions for both the share and the folder
you're sharing. Set both to have an "Everyone" user and then in both
cases give "Everyone" Full Control.

Do you have another PC kicking around? Can you try to connect to the
share from another PC ?

Bob.

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

Hi Bob

In message <5c55a77428bob@sick-of-spam.invalid>
Bob Latham <bob@sick-of-spam.invalid> wrote:

In article <70e99a555c.john@user.orpheusmail.co.uk>,
J Peachey <john@jpeachey.co.uk> wrote:

I have made some progress with this. However when trying to connect
to the PC shares, I get timed out while connecting. Any ideas?

I have Uniprint working swapping URLs and the clipboard. So it look
like perhaps the firewall might be intervening. Although a quick
look seems to allow file transfers.

Thanks for your help so far.

Do check that your PC thinks it is connected to a Private network and
not a public network !!

Confirmed that this is a Private Network

On windows 11 Settings - Network and internet
Diagram at top of page says Properties private or public.

Yep

Are you using a password on the PC? It has to be a local password not
an on-line microsoft account password !!

No

Have you changed the permissions for both the share and the folder
you're sharing. Set both to have an "Everyone" user and then in both
cases give "Everyone" Full Control.

Yes

Do you have another PC kicking around? Can you try to connect to the
share from another PC ?

Yes- With a faulty network card, which is why I replaced the machine!

From Net Share I get
Documents C:Users\john\docs
Users C:\users

I can Ping Penguin. which shows I'm using the write pC name.

So, I'm a bit stuck. Perhaps unshare and start again?

John

Bob.

--
_________________________________________
| University of Glos. Blighting Longlevens.
| mailto:john@jpeachey.co.uk
_______________________| http://www.jpeachey.co.uk

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

In article <0e930c565c.john@user.orpheusmail.co.uk>,
J Peachey <john@jpeachey.co.uk> wrote:

Hi Bob

In message <5c55a77428bob@sick-of-spam.invalid>
Bob Latham <bob@sick-of-spam.invalid> wrote:

In article <70e99a555c.john@user.orpheusmail.co.uk>,
J Peachey <john@jpeachey.co.uk> wrote:

Are you using a password on the PC? It has to be a local password
not an on-line microsoft account password !!

No

Okay so therefore:

In advanced network settings...

Private networks
Network Discovery on.
Setup network connected devices automatically - ticked.
File and print sharing on.

Public networks
Network discovery off.
File and print sharing off.

All networks
Public folder sharing off.
File sharing connections 128 bit encrypt.
Pass word protected sharing - OFF !!

Check password is off !!! ^^^^^

-----

Are you sure SMB1 SERVER has been activated?

SMB 1.0/CIFS auto remove - OFF
SMB 1.0/CIFS client - OFF
SMB 1.0/CIFS Server - ON

Please check it.

What do you have in your LM98 connection file for the PC?

Here's mine created last week all 3 lines of it.

Server: DESK-PC2
Share: Home
User: Bob

Make sure the share name is the same as the share name on the PC.
That's the share name not always the same as the folder name.


Try Server: name<192.168.1.x>
But if you say it resolves ok then that may not do it.

Honestly, there's nothing else to it.
Just for testing try turning off the firewall and the virus
protection at the same time.

Yes- With a faulty network card, which is why I replaced the
machine!

From Net Share I get
Documents C:Users\john\docs
Users C:\users

I can Ping Penguin. which shows I'm using the write pC name.

So, I'm a bit stuck. Perhaps unshare and start again?

I'm now reduced to a mistake, or some 3rd tool on the PC doing nasty
things.
What virus protection are you using?



Bob.

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

Hi Bob

In message <5c56156d54bob@sick-of-spam.invalid>
Bob Latham <bob@sick-of-spam.invalid> wrote:

In article <0e930c565c.john@user.orpheusmail.co.uk>,
J Peachey <john@jpeachey.co.uk> wrote:

Hi Bob

In message <5c55a77428bob@sick-of-spam.invalid>
Bob Latham <bob@sick-of-spam.invalid> wrote:

In article <70e99a555c.john@user.orpheusmail.co.uk>,
J Peachey <john@jpeachey.co.uk> wrote:

Are you using a password on the PC? It has to be a local password
not an on-line microsoft account password !!

No

Okay so therefore:

[snip]

I was just preparing some more diagnostic info when, your mention of what
was in the file, sent me looking for it. I couldn't find it so created one based on one of your earlier postings. It didn't work, so I then added the server adress, and that seems to have kick started the process.

I've done a reboot of both machines and it has retained the settings
across the boot (no reason why it shouldn't.. but)

Many thanks for your help and patience, it has been much appreciated.

Kind regards
John

Bob.

--
_________________________________________
| University of Glos. Blighting Longlevens.
| mailto:john@jpeachey.co.uk
_______________________| http://www.jpeachey.co.uk

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

On 02/09/2025 15:32, Bob Latham wrote:

Are you sure SMB1 SERVER has been activated?

SMB 1.0/CIFS auto remove - OFF
SMB 1.0/CIFS client - OFF
SMB 1.0/CIFS Server - ON

I would also recommend that once set up and working, you use the Windows firewall to only allow access to the SMB ports from RISC OS devices' IP addresses. Don't even allow all of your local network in case of
compromised devices such as security cameras or guest's equipment.

---druck

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

In article <1097bmf$llip$1@druck.eternal-september.org>,
druck <news@druck.org.uk> wrote:

On 02/09/2025 15:32, Bob Latham wrote:

Are you sure SMB1 SERVER has been activated?

SMB 1.0/CIFS auto remove - OFF
SMB 1.0/CIFS client - OFF
SMB 1.0/CIFS Server - ON

I would also recommend that once set up and working, you use the
Windows firewall to only allow access to the SMB ports from RISC
OS devices' IP addresses. Don't even allow all of your local
network in case of compromised devices such as security cameras or
guest's equipment.

Good suggestion, thanks Dave.

Mind, I'll bet it will lead to hours of head scratching in the future
- why won't it connect !!

Bob.

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