Curious hourglass behaviour

If you try LanManFS instead of LanMan98 it should tell us if the hourglass is from LanMan98.

I think you’ve found it, Colin. Using LanManFS gives no hourglass for the file comparison with one file read from NAS, whereas using LanMan98 (which I have done for years now) gives the hourglass.

Hi Dave,

If you are testing against a NAS then some NAS drives cause issues with LanMan98 as per the run file entry below.

Could this be flooding the network as ShareFS uses UDP which isn’t exactly stable on heavy network traffic.

Doug

| The following line tells LanMan98 to use raw read requests for speed if the
| server claims to support it. Some NAS, and Windows Vista claim to support
| it, but actually fail to do so. If you have problems with your connections
| comment the following line out to make LanMan98 avoid raw reads in all
| cases.
Set LanMan98$ReadRaw ""

This afternoon I used Omni to connect the three NAS drives. I was very worried when I opened the root directory of one and saw only about half the files and folders that I was expecting!

Quitting Omni and connecting via LanMan98 instead, all of the expected stuff was there. Phew. Big sigh of relief.

So there would still appear to be a major problem with LanMan somewhere.

If you are testing against a NAS then some NAS drives cause issues with LanMan98 as per the run file entry below.

What sort of issues?

I’ll try the ReadRaw change later this evening.

Quitting Omni and connecting via LanMan98 instead, all of the expected stuff was there. Phew. Big sigh of relief.

AIUI Omni is just a front end to various transports including LanManager and it can also be LanMan98. LM98 transfers should I believe be identical through Omni or LM98 standalone. Where you using LanManager or LanMan98 within Omni.

This afternoon I used Omni to connect the three NAS drives. I was very worried when I opened the root directory of one and saw only about half the files and folders that I was expecting!

How recent is the build you’re using? I ask because I could swear I recall a number of changes to the LanManFS that dealt with directory reads from some network shares.

LanManFS 2.62 (04 Aug 2018), RISC OS 5.27 (20-Nov-18).

I presume LanManFS comes with the build of RISC OS, because it’s there in the list of ROMModules. If there’s a separate build available, I’d be happy to try it.

If there’s a separate build available, I’d be happy to try it.

As I recall it was stuff that Colin was doing and the changes may have fallen down the gap in the ROOL sofa. I thought they’d made it in, but it seems not.

Incorrect.

Do you have examples in C or Basic?

When I read again recently the thread that included Colin’s changes, it appeared that they were related to stopping crashes, which is not what I’m seeing.

I get the hourglass appearing (without a percentage), although nothing is single-tasking.

When I read again recently the thread that included Colin’s changes, it appeared that they were related to stopping crashes, which is not what I’m seeing.

It was this bit, following, that had me thinking about Colin’s changes as partial retrieval of directory listings was very much a symptom.

This afternoon I used Omni to connect the three NAS drives. I was very worried when I opened the root directory of one and saw only about half the files and folders that I was expecting!

Incorrect.

Do you have examples in C or Basic?

Yes.

https://www.riscosopen.org/viewer/view/mixed/RiscOS/Sources/Programmer/SMP/Test/

Fantastic. I need to test this :)