New version of filesysbox for AROS

[Amiwell]

yes I know but you have not explained how to solve the problem

[AMIGASYSTEM]

No one has asked me until now, salass00's Mountlist is also correct for Windows, the problem you encounter is only for sharing on Windows.

With Windows you can share one folder or all folders of the "Public" user.

On Windows what is important is to enable sharing (Network and Sharing Center).


I enclose my Mountlists:

Handler = L:smb2-handler
StackSize = 65536
Priority = 5
GlobVec = -1
Startup =

"smb://UserPC:password@192.168.x.x./Public"
or
"smb://UserPC:password@Name-PC/Public"


"smb://UserPC:password@192.168.x.x/Folder name to share"
or
"smb://UserPC:password@Name-PC/Folder name to share"


At Tooltypes Icon:
ACTIVATE=1


Se vuoi puoi postare il mio commento su Amigapage, se qualcuno ha bisogno di altre info in italiano può contattarmi su Amiganews sulla news dedicata a SMB2

[Amiwell]

ok thank you Carlo

[AMIGASYSTEM]

Excellent "SMB2" on AROS One x86, also works perfectly by VMWare, this I would say is good news and a nice convenience.

As you can see from the screenshot I shared, both a Win10 folder, and the User "Public" with all its folders

[Amiwell]

I shared the folder C: on Windows 10 but from Aros does not see it with your settings maybe it's the firewall

[AMIGASYSTEM]

As I said, you have to enable "all" shares and give all permissions to folders.

[Amiwell]

okay thanks!

[AMIGASYSTEM]

If I have time and if requested I can add a detailed post in Italian on amiganews, in this way I also please other Italian users who have asked me.

[paolone]

After several days of successful use of SMB2 filesystem, I can pinpoint these:


In its startup sequence, Icaros Desktop mounts whatever it finds in DEVS:DOSDrivers with these lines:

Automount >NIL:
Mount >NIL: "DEVS:DOSDrivers/~((.#?)|(#?.info))"
I noticed the syntax slightly changed in recent AROS builds by Deadwood:

Automount >NIL:
Mount >NIL: "DEVS:DOSDrivers/~((.#?)|(#?.info)|(#?.dbg))"
but I guess it only adds the chance to mount something with a .dbg extension.


- If I create a SMB2 dev file with ACTIVATE=1, at next reboot I still need to access the share some way to see it 'mounted' and shown by Wanderer or Magellan. Shouldn't file managers show them automatically? This happens with both ACTIVATE=1 in the file, or in icon's tooltypes, or both.


- If I move the dev file and its icon to WBStartup, as others already pointed out, I effectively get the shares mounted at startup, and correctly shown by Wanderer and Magellan.


- if I DON'T put ACTIVATE=1 anywhere, the smb share can be mounted simply by accessing it, for instance with a DIR command. I guess this should be the correct behavior.


- Although SMB2 shares get mounted correctly almost every time, some times I get some weird result. For instance, shares can get unavailable with no reason after a while. I can access them but no file is shown. It also happened I could save a JPG image TO a share, but couldn't read it aftewrwards (the file didn't get recognized as a JPG and Magellan proposed me to sniff it). This until the next reboot, then the file could be read with no issue.
 

[AMIGASYSTEM]

Yes Paolo if you don't use ACTIVATE=1, you have to proceed manually, same thing if you use ACTIVATE=1 but the DosDrivers is located In Storage, here as on Amiga you can mount by typing SMB2: followed by enter, or create the mount buttons on Dopus4.

Regarding the oddity of a failed mount, this may depend on:

- Connection delay, in this case the Mounting through the DOSDriver arrives late and then you will no longer have the share mounting, it could be solved by disassembling/reassembling the DosDriver.

This problem can be avoided if in the Tooltypes of the icon we add a certain delay, better the maximum possible, in this case we will have more time available for assembly.

- Another reason why the Mounting of the DOSDriver fails, is when the shared folder or network drive is used by other app.

- I also add that if the assembly fails, you have to do a cold restart, a hot restart could keep the "assembly error" memorized

For a good sharing with Windows I recommend to create the Network Drive, this way Windows at each reboot will mount the drive automatically available in  Windows Explorer, other advice is to have a short name for Windows, otherwise on AROS you will have a volume name too long.

I for example named my PC simply "Win" and the network drive Share, and on AROS I will have the shared volume with the name Wim-Share, see screenshot

See screenshot.



------  Italiano  --------


Si Paolo se non utilizzi ACTIVATE=1, bisogna procedere manualmente, stessa cosa se si usa ACTIVATE=1 ma il DosDrivers si trova In Storage, qui come su Amiga si può montare digitando SMB2: seguito da un invio, oppure creare i bottone di montaggio su Dopus4.

Riguardo le stranezze di un montaggio non andato a buon fine, questo può dipendere:

- Ritardo della connessione, in questo caso il Montaggio attraverso il DOSDriver arriva in ritardo e quindi non si avrà più il montaggio della condivisione, si potrebbe risolvere smontando/rimontando il DosDriver.

Questo problema può essere evitato se nel Tooltypes dell'icona aggiungiamo un certo ritardo, meglio il massimo possibile, in questo caso si avrà più tempo disponibile per il montaggio.

- Altro motivo per cui fallisce il Montaggio del DOSDriver, è quando la cartella condivisa o l'unità di rete è utilizzata da altra appicazione.

- Inoltre aggiungo che se il montaggio fallisce, bisogna fare un riavvio a freddo, un riavvio a caldo potremme mantenere  memorizzato "l'errore montaggio"

Per una buona condivisione con Windows consiglio di creare l'Unità di Rete, in questo modo Windows ad ogni riavvio monterà l'unità automaticamente disponibile in Explora Risorse, altro consiglio è di avere un nome corto per Windows, altrimenti su AROS si avrà un nome volume troppo lungo.

Io per esempio ho chiamato il mio PC semplicemente "Win" e l'unità di rete Share, e su AROS avrò il volume condiviso con il nome Wim-Share, vedi screenshot

Vedi screenshot

[paolone]

Yes Paolo if you don't use ACTIVATE=1, you have to proceed manually, same thing if you use ACTIVATE=1 but the DosDrivers is located In Storage, here as on Amiga you can mount by typing SMB2: followed by enter, or create the mount buttons on Dopus4.

Ok, but this is not coherent with anything else that happens on the system. If I mount a NTFS hard drive partition at startup, I can see it exposed on Wanderer's desktop. Same if I have a CD in the drive. And I am quite confident it also happened with older network shares using the old SMB device. So why should I manually 'enable' it with a command, or placing shares in WBStartup? And what is the difference if ACTIVATE = 1 gives me the exact same result of no ACTIVATE at all?


Maybe this is the exact behavior it should have, but it is not coherent with anything else.


BTW, I am writing a SMB2 shares 'adder' in LUA, which currently supports creating share links on the fly (eg. in RAM when booting AROS from DVD) and also auto mounting shares by moving the device from devs/DosDrivers to WBStartup. But the best solution would be adding SMB2 filesystem support to prefs/Network (and I haven't the skills to do so).

[Amiwell]

But the best solution would be adding SMB2 filesystem support to prefs/Network (and I haven't the skills to do so).

yes where is a best solution

[AMIGASYSTEM]

But the best solution would be adding SMB2 filesystem support to prefs/Network (and I haven't the skills to do so).

Yes Paolo would be optimal to add SMB2 in Network Prefes, that way the user could add his data and store it in the DOSDrivers.

But beware the DEVS/DOSDRiver the Mountlist is mounted before the connection happens and therefore the mount will fail and never succeed, and consequently you will need to unmount and remount.

Also, those who have a slow connection or network will never be able to connect if started by DEVS/DOSDrivers

With WBstartup you can delay the right amount of time and thus "always" have your Sharing Icon up and running on the Workbench.

Mounting an HD, CD or Floppy does not need a connection, the mounting is immediate, and there is no time to delay.

The difference between ACTIVATE=0 and ACTIVATE=1 has a big difference, with the former you will never have the icon on the Workbench, the latter on the other hand is purposely created to have the device ready right away.

I on OS3 in the DosDrivers do not use any Icon, when I need the peripherals I run the Mountlist from Dopus or from a Shell.

Translated with www.DeepL.com/Translator (free version)



---- Italiano ----

Si Paolo sarebbe ottimale aggiungere SMB2 in Network Prefes, in questo modo l'utente potrebbe aggiungere i suoi dati e memorizzarli nel DOSDrivers.

Ma attenzione il DEVS/DOSDRiver la Mountlist viene montata prima che avvenga la connessione e quindi il montaggio fallirà e non andrà mai a buon fine, e di conseguenza occorrerà smontare e rimontare.

Inoltre chi ha una connessione o una rete lenta non potrà mai connettersi se avviata da DEVS/DOSDRivers

Con WBstartup puoi ritardare il giusto tempo e quindi avere "sempre" la tua Icona della condivisione operativa sul Workbench.

Montare un HD, un CD o un Floppy non ha bisogno di una connessione,  il montaggio è immediato, e non ha tempi da rispettare.

La differenza tra ACTIVATE=0 e ACTIVATE=1 ha una grande differenza, con il primo non avrai mai l'icona sul Workbench, il secondo invece è stato creato di proposito per avere da subitio pronta la periferica.

Io su OS3 nei DosDriver non uso nessuna Icona, quand le periferiche mi servono eseguo la Mountlist da Dopus o da una Shell.

[paolone]

Ok, this makes sense. Thanks for the explanation.

[AMIGASYSTEM]

Paolo, for the same reason SMB0 created by Network Prefs did not work, precisely because it does the Mounting from Storage/DOSDrivers "in advance" of the connection.

Network Prefs and native AROS x86 smb-handler work perfectly, if the mount is done "after the connection"

As you can see from the screenshot, I connected to the Windows Network Unit using Network Prefs


----- Italiano -------

Paolo, per lo stesso motivo SMB0 creato da Network Prefs non funzionava, proprio perchè effettua il Montaggio da Storage/DOSDrivers "in anticipo" rispetto alla connessione.

Network Prefs e  smb-handler nativi AROS x86 funzionano perfettamente, se il montaggio avviene "dopo la connessione"

Come puoi vedere dallo screenshot, mi sono connesso alla Unità di Rete di Windows utilizzando Network Prefs