I have a question about Prefs/Network and OLD smb filesystem.

Where does it save data for SMB shares? I can't remove shares once I have created them. I have once saved a share and no matter how many times I clicked on the REMOVE button, it disappeared form the application list just to respawn exactli where it was when I reset the PC. I have tried looking into AROSTCP files and in ENVARC: with no luck at all.

Paolo "Network Prefs" after you have configured a share generates a DOSDrivers it is named "SMB0"which includes the setting, and at each reboot it is Mounted, that's why you find it, it's probably a Bug, you can still delete the DOSDriver by hand, is located in Storage/DOSDrivers, the file "ServerAutoMounts", in ENV:AROSTCP which indicates the DOSDriver to be mounted, should also be deleted

----- Italiano -----

Paolo "Network Prefs" dopo che hai configurato una condivisione genera un DOSDrivers si nome "SMB0" che include il settaggio, e ad ogni riavvio viene Montato, ecco perchè te lo ritrovi, probabilmente è un Bug, puoi comunque eliminare il DOSDriver a mano, si trova in Storage/DOSDrivers, va anche eliminato il file "ServerAutoMounts" in ENV:AROSTCP che indica il DOSDriver da montare

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

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.
 

Quote from: miker1264 on February 05, 2023, 07:34:10 PM

There are a few changes in the works for Wanderer that are coming from backports from ABIv1 including changes that allow to move or copy items depending on which volume. Also I believe changes were made after that to allow moving, copying, renaming, deleting unassociated icons in Wanderer. I've also noticed that Edit Tooltypes in Icon Information doesn't work at times because of the internal text editor.

These functions are already present on the latest Build D14, and are already part of the upcoming AROS One v2.0

Thanks. I will probably use that version of Wanderer as the base code for development & testing.

This is what I would like the Wanderer Icon Exchange GUI to look like. I made this mockup in a paint program. I do that for all my AROS GUI projects. It makes it easier to take measurements when making the actual user interface.

Now I must research MUI/Zune user interface setup to figure out how to make the mockup into a real program module. Of course the "Dest icon" label on top should be "Srce icon". I missed that little detail. 

It's much easier at the beginning when I have a clear goal.

Nuova versione 1.02 del software "RPN Scientific+"  installata su AROS O

RPN Scientific+ is a scientific, programmer, and statistic, it allows entry in and simultaneously displays values in decimal, hexadecimal,  binary, and time notation.  The programmer functions allow displaying values of Long, Word, and Byte signed or unsigned numbers.  Numbers and basic functions can be entered using the number pad on your keyboard.

The calculator is stack-based with 4 registers.  The stack can be manipulated using the buttons in the upper right of the
calculator.  They function per Forth language counterparts. Various options can be set by toggling the green keys.  For
example, DEG when pressed toggles from angles in degrees to  angles in radians.  The FP button alternates between floating point and integer mode.  Entering in the Hex or Binary display triggers integer mode.  Press FP to return to floating
point.