Groups | Search | Server Info | Login | Register


Groups > comp.sys.acorn.misc > #21662

Re: Getting RISC OS to talk to other machines

From Bob Latham <bob@sick-of-spam.invalid>
Newsgroups comp.sys.acorn.misc
Subject Re: Getting RISC OS to talk to other machines
Date 2025-08-30 15:48 +0100
Organization None
Message-ID <5c548b66c5bob@sick-of-spam.invalid> (permalink)
References <c12d71545c.john@user.orpheusmail.co.uk>

Show all headers | View raw


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.

Back to comp.sys.acorn.misc | Previous | NextPrevious in thread | Next in thread | Find similar


Thread

Getting RISC OS to talk to other machines J Peachey <john@jpeachey.co.uk> - 2025-08-30 10:15 +0000
  Re: Getting RISC OS to talk to other machines Chris Hughes <news13@noonehere.co.uk> - 2025-08-30 11:30 +0100
    Re: Getting RISC OS to talk to other machines Steve Fryatt <news@stevefryatt.org.uk> - 2025-08-30 12:22 +0100
  Re: Getting RISC OS to talk to other machines Paul Stewart <phorefaux@gmail.com> - 2025-08-30 14:39 +0100
  Re: Getting RISC OS to talk to other machines Bob Latham <bob@sick-of-spam.invalid> - 2025-08-30 15:48 +0100
    Re: Getting RISC OS to talk to other machines J Peachey <john@jpeachey.co.uk> - 2025-08-31 11:15 +0000
      Re: Getting RISC OS to talk to other machines druck <news@druck.org.uk> - 2025-08-31 20:48 +0100
    Re: Getting RISC OS to talk to other machines J Peachey <john@jpeachey.co.uk> - 2025-09-01 16:15 +0000
      Re: Getting RISC OS to talk to other machines Bob Latham <bob@sick-of-spam.invalid> - 2025-09-01 19:31 +0100
        Re: Getting RISC OS to talk to other machines J Peachey <john@jpeachey.co.uk> - 2025-09-02 13:00 +0000
          Re: Getting RISC OS to talk to other machines Bob Latham <bob@sick-of-spam.invalid> - 2025-09-02 15:32 +0100
            Re: Getting RISC OS to talk to other machines J Peachey <john@jpeachey.co.uk> - 2025-09-02 17:15 +0000
            Re: Getting RISC OS to talk to other machines druck <news@druck.org.uk> - 2025-09-02 19:06 +0100
              Re: Getting RISC OS to talk to other machines Bob Latham <bob@sick-of-spam.invalid> - 2025-09-02 20:58 +0100
              Re: Getting RISC OS to talk to other machines Bob Latham <bob@sick-of-spam.invalid> - 2025-09-08 07:11 +0100
                Re: Getting RISC OS to talk to other machines druck <news@druck.org.uk> - 2025-09-10 07:42 +0100

csiph-web