SMB2FS OS3 port

[Fairdinkem]

Got it working - never mind.

[CCRider]

Originally Posted by Fairdinkem

Got it working - never mind.

Would you ming doing a step by step tutorial about connecting a Mac and an A1200?

My setup is pretty much identical to yours, but I couldn't get it to work.

Connecting the Amiga to the internet wasn't an issue. It's something SMB-related that I'm struggling...

[Fairdinkem]

@CCRider

On the Mac under file sharing click on options to make sure sharing files over SMB is checked and a account is also checked.

On the Amiga in SYS:Storage/DOSDrivers I made a duplicate of a DOSDriver and edited it with a text editor to add in the mount list info given on the first page of this thread by the author. I also make sure the properties of the DOSDrivers Icon are using the default to C:Mount and in tool types the command Activate=1 is entered in and that the priority is set to 5 and ensure enough stacksize is available.

For the following command in the DOSDriver if you are using roadshow which I am I find I have to identify the "mypc" portion by the macs IP address given in the file sharing section of settings on you mac followed by the forward slash and the name of your shared folder.

Startup = "smb://myuser: password123@mypc/myshare"

Hope this makes sense and is helpful.

[Firestone]

I got a strange thing to report...
I've used SMB2FS for a couple of months now on my A1200.

Tonight, I tried to install it on my A3000, but was unable to read the share on my TrueNas core server for unknown reasons.

I made the dosdriver identical to the A1200 setup, same stacksize, same username password, same share, and populated the hosts file in the tcp ip stack with the name of the server. Ping is all good.

So in the shell I did "mount truenas:". It will return the prompt after a second or so. And then, if I try to "cd truenas:", workbench will pop a requester saying
"No disk present in device TRUENAS"

Snoopdos does not give anything unusual.

Both machines run AmigaOS3.2, but there is a key difference between them:

The A1200 contains a Blizzard 1230IV
The A3000 contains a Cyberstorm MKII 060

Bot machines chose the 020-version of smb2-handler during install.

My last attempt was to swap the 020-version with the 000-version of the smb2-handler, and then suddenly everything works fine on the A3000!

Are there any known issues with the 020-version when used on a 060 CPU?

EDIT: Tested with version 53.4 (from Aminet)

[BSzili]

None that I know of. On a related note, I added an error requester to the handler which is now available in version 53.5. It should help to diagnose why it can't connect to a share, silent failures like yours are no more. It's currently up on GitHub, and it should be available on Aminet too in a day or so.

[Firestone]

Allright. Tried the latest version for Github now.
It will throw a requester saying the following on the 020-version:

smb_connect_share failed.
Session setup failed with (0xc0000006d) STATUS_LOGON_FAILURE

68000-version in the new archive works just fine.

[nogginthenog]

I've been running the 020 version of SMB2FS on a A4000 Cyberstorm MKII 060 for ages.

Fantastic bit of software.

[Firestone]

Originally Posted by nogginthenog

I've been running the 020 version of SMB2FS on a A4000 Cyberstorm MKII 060 for ages.
Fantastic bit of software.

I know! I love it! ... and this is the strangest thing in the world.
What version of smb handler are you running?

[nogginthenog]

Originally Posted by Firestone

I know! I love it! ... and this is the strangest thing in the world.
What version of smb handler are you running?

Latest from Aminet (there is a slightly newer version on the github page).
I've copied 100s of Mbs of data without issues.

My server is a Debian Linux box.

I have a X-Surf 100 card connected to an old router which is configured as a wireless gateway to my main router. The only issue is the old router takes longer to boot/connect than my Amiga

[AMIGASYSTEM]

Originally Posted by Thorham

Found a possible issue. When you don't use the mounted share for some time (didn't time it, but over five minutes), it stops working.

Settings related perhaps?

However, it is not 5 Minutes, but more than 10, and it happens "only" when you do not use sharing.

There is a small remedy, which is to create other DOSDrivers example: SMB3, SMB4, SMB5 etc..., it is not necessary to change anything, as soon as a connection stops working, run one of the other DOSDrivers, and a new share will appear on the workbench

[itsmedoofer]

Not sure what changed guys but tried again with the version on Git and I now have working shares, this was with mount files that had previously apparently failed?! Happy camper, thanks for your efforts guys really appreciate!!

[BSzili]

That's good to hear! You can always check out the releasenotes in the archive to see what's new.
Version 53.5 is now also available on Aminet. This is identical to the 53.5 released on GitHub a few days ago, so if you already have that there's no need to update.

[AMIGASYSTEM]

Preview tested SMB2-GUI for AROS x86 and 68K for Amiga and AROS 68k (will be posted soon on aminet by Yannick Buchy), the GUI works perfectly on OS 3.9, 3.2, AROS One x86 and AROS One 68k, allows you to create the Mountlist (SMB2) and mount it via special tabs.

The generated mountlis is washed out in Storage/DosDrivers, and reused later when needed in mounts, either through an appropriate Icon or from some Menu or Dock Bar.

The mountlist can also be moved to Devs/DosDrivers, but in my opinion it is not recommended; on some systems, mountlis started early before connection will fail and cannot be remounted later.


https://eab.abime.net/attachment.php...3&d=1683143817

[BSzili]

Very cool! A few suggestions for the UI:

• there's no need to expose GlobVec to the user, it should always be -1
• consider using the USER and PASSWORD arguments, so the reserved characters (e.g. : ; @) can be used in passwords
• an option to set the VOLUME argument would be nice for custom names

[AMIGASYSTEM]

Thanks BSzili the GUI was my request to Yannick Buchy who kindly created it based on my requests, I will inform the developer ti this request of yours

Regarding the first 5 values Handler, Stacksize, Priority Glowvec, Activate, they are already preset in the GUI, there is no need for the user to add them, but if you want you can change them.

Also if you noticed my shared "Share" is a volume (network drive)

[BSzili]

What I meant was: GlobVec should never ever be changed by the user, so it can be dangerous to expose it like this in the GUI, where it can be easily be changed from -1.

[AMIGASYSTEM]

Ok, the developer has been informed of your request and will include your reports in the next release.

BSzili I have successfully tested SMB2 with OS 3.9, 3.2, AROS x86 and AROS 68k, no problems detected.

However, I have encountered problems with OS 4.1, I don't know if it depends on WinUAE but if I mount the mountList (the same one used on OS3 and AROS) on OS 4.1 it doesn't work.

SMB2 seems to be mounted quietly, however if I try to access the SMB2 volume I get error, see screenshot !

[BSzili]

I haven't tried it on OS4, but jugding from the error it doesn't even get to connecting to the share. Snoopy might be able to help you find what fails.

[AMIGASYSTEM]

I updated amb2-handler to version 53.5, and now the error has changed, see screenshot.

I specify that the same mountlist (SMB2) works perfectly on AROS x86/68k and OS3

[tomcat666]

Thank you BSZili - working like a charm on real A1200 with pistorm32. Everything perfect.

As always your ports are flawless.

Slowly we are getting to a very 21st century usable state amiga 68k
We need a semi-modern web browser and a SSH terminal client and we are basically there.