Accessing smb v2 and v3 shares with ShareView

Another new version available (v0.05) here.

The URL linked above is correct, but it is incorrect in the Help file, where it lacks “/vfp” in the path.

This could usefully be corrected!

The URL linked above is correct, but it is incorrect in the Help file, where it lacks “/vfp” in the path.

Thanks. Both urls now point to the latest version.

I happened to try copying a file called dimmer/c (which is part of a project with DOS-style file names; created in a Windows IDE under Wine under Ubuntu). What arrived was a directory named c, and a file within it named dimmer, both with date and time at which the copy took place.

At some point it will be better to change from an application to a filing system, like LanMan and LanMan98. Do you have plans to do so?

Another new version (v0.06) available here.

New in this version,

The title bar of the main window shows the current share and path name.
Files are sorted by file name.

I happened to try copying a file called dimmer/c (which is part of a project with DOS-style file names; created in a Windows IDE under Wine under Ubuntu). What arrived was a directory named c, and a file within it named dimmer, both with date and time at which the copy took place.

There are still quite a few bugs in the path name translation. Hopefully fixed soon. Thanks.

At some point it will be better to change from an application to a filing system, like LanMan and LanMan98. Do you have plans to do so?

Wasn’t planning to. Not something I’d be capable of. Next up are similar front ends for libssh2 (a gui sftp) and libzip (a gui create and extract zip files with modern compression). Separate apps or maybe one combined one.

Another new version of ShareView (v0.07 alpha) available here.

New in this verison,

Added ‘Refresh’, ‘Open Parent’ and ‘Display’ (sort by file name or date) menu options.

Strange… the new version gives a new error when I try to access the PC with the very same entries as before:
Failed to create/open directory (no such file or directory). OpenDir failed with (0xc0000034) STATUS_OBJECT_NAME_NOT_FOUND.

Strange… the new version gives a new error when I try to access the PC with the very same entries as before:
Failed to create/open directory (no such file or directory). OpenDir failed with (0xc0000034) STATUS_OBJECT_NAME_NOT_FOUND.

Are you able to navigate to the folder if you open the Share with ‘Path’ empty.

Yes, when I leave Path empty, it opens one of the many subdirectories.

Yes, when I leave Path empty, it opens one of the many subdirectories.

What happens when you double click on the folder that gave the ‘OPendir failed’ error.

There’s no folder to click on. The path that I entered was the root of the D drive, but ShareView didn’t open a filer window. The filer window that it does open when I leave the path empty is ‘Documents’ – a subdirectory of the subdirectory ‘Paul’ on that D drive.

What folder does the share you are opening map to? Seems like it is mapped to your user folder and not the root of the d drive.

The path that I entered was the root of the D drive,

Windows doesn’t like sharing the root of a drive, so it’s possible that the permissions on the root are more restrictive than elsewhere.

Windows doesn’t like sharing the root of a drive, so it’s possible that the permissions on the root are more restrictive than elsewhere.

By default if your machine is not joined to a Domain remote access (remote UAC) is blocked to admin shares e.g. C$, ADMIN$ etc. At least on Windows 10 & 11.

What folder does the share you are opening map to? Seems like it is mapped to your user folder and not the root of the d drive.

No, it’s exactly as I described: it opens a subdirectory of a subdirectory of the D drive.

Windows doesn’t like sharing the root of a drive, so it’s possible that the permissions on the root are more restrictive than elsewhere.

Perhaps, but the former ShareView accessed it without problem (as does LanMan since years).

No, it’s exactly as I described: it opens a subdirectory of a subdirectory of the D drive.

It’s the share that governs what the initial folder is. What folder have you shared on your D drive. The path you enter has to be a folder that exists in the root of the share. You can’t enter a path outside of the folder the share points to.

I’ve shared the entire D drive. In the previous version I entered D as the path, which is the share name of the D drive, and that worked. One would presume that when you leave the Path empty, it would open the Current Directory instead. But that one differs completely from what it actually opens now.

What does the window title show.

If I set the share name to d and leave the path blank I get ‘ShareList – d:/’.

Thousand apologies Chris. A night of healthy sleep reveals that I somehow managed to mix up some entries. The speed of my decay is worrying. But your program works fine!

As a new RISCO OS user, I am just getting my bearings around the system, bear with me.

To get started merge the !Boot folder included in the zip file. Then edit the file – done.

!Boot.Choices.smb2.user/txt.
This maps passwords to user names – I tried looking for the file but cannot find it.

Upon rebooting the Pi, I get this message when I click on the Shareview icon: File System Timer Mod Not Found?

Any ideas and thank you.

File System Timer Mod Not Found?

TimerMod is here, at the bottom of the page.

Hi David, thanks for the link.

My understanding of Risc OS is iimited at the moment.

I clicked on the Timer Mod file and the app is loading fine now.

I started off a test to my NAS box with my credentials, connection refused, I wonder if this the case of firewall blocking access, I will need to check.

Just a question on indvidual module files itself.

I think you don’t just double click on the timer mod file to start the module,

I think you have meant to put the module file into a specific location so that Risc OS loads the module file automatically, is that correct?

Thank you.

I think you have meant to put the module file into a specific location so that Risc OS loads the module file automatically

Modules, that are not application specific, should be in !Boot.!System. !System contains numbered directories which represent the minimum version, *100, of RISC OS the module can run on.

TimerMod should go in 310 to be this :-

!Boot.Resources.!System.310.Modules.TimerMod