RPCEmu and USB

It is the RISC OS Direct version from the bundle and normal networking (Not the bridging version).

So you’re using the ‘Network Address Translation’ option in Settings-Networking (as opposed to Ethernet Bridging)?
I’m using NAT here.

So with that thought in mind, I reverted the OS to a 5.27 of March 2020

So you stepped back 7 months of development releases as opposed to trying the recent 5.29 beta?

No one with a successful trial has answered your question:

What versions of RO 5.nn are you guys using?

Where the answer may be: “5.29 with the matching HD4”

So you stepped back 7 months of development releases…

Indeed I did, because I’ve been going through things step by step. :-)

And yes I have tried 5.29 beta, but absolutely no change… Same error message.

Next solution please?

Thanks
Dave

And yes I have tried 5.29 beta, but absolutely no change…

With matching updated boot etc (the harddisc4 stuff)? It isn’t always just the OS that changes, sometimes the resources do as well.

Of course I haven’t done anything with the Harddisc 4 stuff yet.

I’m going to revert this install back to 5.28 As I don’t want to end up with a FU on my in use one… Then when I can find some more time to waste, I’ll set up a 5.29 version and yes the HD4 stuff.

Dave

Back in the days I had many versions of RO installed to play with, on both VRPC and RPCEmu 4.20, 4.39, 6.20, 5.nn, but these days I’ve lost interest in playing, I just want an OS that works.

D.

Well Rick what a chuckle.
A copy of the working RPCEmu, then applied both the 5.29b and HD4Stuff updates and ran it.

The RPCEmu did run. :-)

This time the LM connection was a total failure, in that nothing connected, not even the drives that had previously connected…

Ping! Checked and the Network Hosts no longer contained the additional ip data required to find anything.

Put that back in and we had some order, but of course as per usual, LM98 would not connect with memory stick(s) F.
“Connection down”.

‘Enuff’ Playing for today, I must get back to work.

Dave

Just a very outside chance: I don’t suppose there is a space in the share’s name?

Just a very outside chance: I don’t suppose there is a space in the share’s name?

I think everyone sticks to visible alphanumeric. Even Windows to Windows users get bitten by the alternative.

Dave, for your next ‘play’ session :-):
Are you running AV software on the PC, and if so, could it be blocking RPCEmu’s access to the F: drive?

George beat me to the question re AV software, “Connection Down” tends to mean it cannot see the resource, nothing really to do with RISC OS version. Its not seeing the Windows resource. A couple of things to try is use the PC’s IP address as the server name – this helps checks if its the server name as the issue. Also double check you have only typed F for the Share name and nothing else within LanMan98. Recheck the Share permission the F: drive and double check that the Windows share is actually called F and nothing else. I know you say you have checked this but recheck its easy to miss an error.

I think everyone sticks to visible alphanumeric.

I vaguely remember being screwed by Windows years ago because there was a space in the overall name of something that prevented it from being shared. The space was inserted and enforced by Windows; it wasn’t part of the leafname. Please forgive the vagueness – it was a long time ago and I’m no longer a Windows user, thankfully.

Good thoughts folks, so I’ll finish off what I’m doing, have a bit o’ lunch, (Watch Bargain Hunt) (well it’s what us old folks do lunch time) ;-)

Then I’ll check out all the above suggestions to make sure.

Thanks
Dave

Laters…

DH.

There is no space after the F in the share.
The LM98 disk config is:

Server: blackfan
Share: F
User: Everyone

GTG.

The only active AV I have on the machine is Windows Security (Formerly Windown defender) and as that’s tied in with the Windows Firewall… See reply lower down.

CH.

Using the IP address is something I’ve tried in the past, and again now, it produces an error message:

WimpError ** from LanMan98 Filer
Error : &00000000
Message: Session refused (NetBIOS name not present)

Yes there is only an F and no after space.

And with regard to the Win side Share checking, lordy I’ve done that so many times, but I’ll do it again.

F:\ Shared.

In Permissions, “Allow” has all three items ticked for the “Everyone” User.

And finally… Even though there already was an entry… I’ve been into the Windows Firewall and set a new allow entry that points explicitly at this particular RPCEmu .exe

No change in the end result though. :-)

Thanks

Dave

With one of my Win10 boxes I’ve had to include the IP address with the server name, so if blackfan’s IP is 192.168.123.100 set the LM98 config to:
Server: blackfan<192.168.123.100>

Session refused (NetBIOS name not present)

Hmm, complaining about the NetBIOS name (it should actually use the DNS/NameServer name)¹

From RPCEmu, in a task window:

gethost blackfan

then use the name that appears in the response in your connection attempt.

¹ That’s where people sometimes need to use a hosts entry or reference the IP

Richard.

Doesn’t make any difference, still fails with the same error message.

“Connection down”

Dave

Steve, gethost blackfan just gets what I already know, so it doesn’t make any difference to the end result.

*gethost blackfan
Hostname: blackfan
Address: 192.168.0.4
type: 2
length: 4

I’m getting confused…

1 That’s where people sometimes need to use a hosts entry or reference the IP ?

Dave

My main confusion is this.

Using LM98 I can connect to other computers and a NAS on the LAN (3+1 NAS) just using their names in the LM98 disk config and obviously having the IP address in the RO Network Hosts file.

But blackfan has multiple SSD drives C. D. and X and they all connect with LM98 okay.

Additionally I have a number of USB SSD Hardrives that connect with LM98 okay just using the assigned letters each one has, like R and M etc… And they obviously don’t have any additional Host entries because they are being served by blackfan which does.

Server: blackfan
Share: R

So why won’t the damn memory stick work?

The server is still blackfan, the USB ports are the same ones used with the USB SSDs the sticks have assigned letters and Sharing is configured.

Shrugs shoulders!

Thanks
Dave

Hostname: blackfan

Most home routers tag a local domain onto the response name, so you get a response like blackfan.home or blackfan.local

For example, the response on this laptop install of RPCEmu to a query¹:

*gethost L82369
Hostname: l82369.home
Address: 192.168.2.85
Type: 2
length 4

IPConfig/all on the laptop in question shows “home” as one element of the DNS suffix search list (the other is, predictably, the corporate domain) – does the response to IPCONFIG/ALL on blackfan show a domain suffix entry?
Is there an entry in the hosts on your RPCEmu setup for blackfan?

¹ It’s my laptop from work, which is a fairly locked down Win10

But blackfan has multiple SSD drives C. D. and X and they all connect with LM98 okay.

Ah, so it isn’t connectivity to the server, it’s the specific share

That has to be permissions on the share (Everybody, you said) or the Drive that is shared.
Lost track on the info:- Is that share accessible from the Windows side of your RPCEmu base machine?

IPCONFIG/ALL

Mnnn! Interesting thoughts Steve.

Shows the following:

Windows IP Configuration

Host Name…………. Blackfan

Primary DNS Suffix….

Node Type…………. Hybrid

IP Routing Enabled…. No

WINS Proxy Enabled…. No

Etc, etc…

In the RPCEmu Networking Hosts file I have the entry for this computer.

192.168.0.4 blackfan

Followed by the other computers & NAS on the LAN.

With regard to your last question, Is the F stick share accessible from the Win side of blackfan, Yes.

When I put the stick in the USB socket I get a Win Filer window for that stick.

Thanks
Dave

If I’ve read and understood the thread adequately, it appears that SSDs can be accessed OK by LM98 but USB sticks can’t.

The difference appears to be that sticks are considered to be removable drives but SSDs aren’t.

But why that should make a difference, I don’t know.

And I apologise if I’m wrong.

it appears SSDs can be accessed OK by LM98 but USB sticks can’t.

You are correct in that understanding of what I’ve written, and while it’s not relevant here as I’m only concerned with RPCEmu, my tests show that on VRPC-DL and even a Real Hardware RISC PC the SSD enclosured Hard drives can be accessed but the memory sticks cannot.

As I understand it from my reading, an SSD in an external USB enclosure is classed as a removable drive.

No worries, in these sort of situations all ideas are welcome.

Thanks
Dave

t appears that SSDs can be accessed OK by LM98 but USB sticks can’t.

That’s not the case here: I can access memory sticks in drive F: via LM98/RPCEmu just fine (see my earlier posts to this thread for details). IMHO DS /should/ be able to do the same: the reason why he can’t is what is causing us to rack our brains, so far fruitlessly!

I have things I must do before I hit the hay this evening… But tomorrow after taking SWMBO shopping I’ll wind up all the computers and try them with the memory stick F and report back afterwards.

Dave