Hi All,

This time there is no poll. As you might remember in May we had a tie and #125 was selected by additional round. This left #140 (Wanderer: Changing the disk label does not work) for June.

As usual I'll post fix in this thread when ready.

These latest fixes make Wanderer more functional and more like Workbench, thank you for the great work!

Glad you find them useful

Hi All,

Here are fixed for bug #140:

[url]https://axrt.org/development/Wanderer.20240621.i386-aros.zip[/url]

I tested them with renaming RAM Disk, but hopefully they also work with renaming disk drivers. Let me know.

Thank you Deadwood

Thank you Deadwood, as soon as I get home I'll do all the necessary tests, now I'm going to the sea, it's 40 degrees in my region!

[quote name=deadwood post=5671]@deadwood - Hi All,

Here are fixed for bug #140:

[url]https://axrt.org/development/Wanderer.20240621.i386-aros.zip[/url]

I tested them with renaming RAM Disk, but hopefully they also work with renaming disk drivers. Let me know.[/quote]
Perfect deadwood, I successfully renamed both AROS and FAT32 formatted volumes.

Ok, thanks for tests. I'll wait for a day or two for any other tests and then close the bug report.

With this bug fix, an old bug has returned on Wanderer, it is not possible to move 'overwrite' a file.

Can you find back a reference when this bug was supposed to be fixed? I can't find anything about it in bug tracker as well as in commit history in the repository.

I think you have solved [url=https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=1142&rowstart=140&pid=2864][b]HERE[/b][/url] the problem! post #158

But as said without the Bug 140 correction the problem does not exist

Strangely, deleting the 'Bug 140' update only worked once!

I also noticed that if from Wanderer prefs one chooses Copy instead of Move, the copy is made successfully, so it could be the Move command that does not allow copying.

Excuse me for asking, but how many people are involved in the development of AROS? One person, one team?

As for the system itself it is currently only me. Kalamatee, Mazze and Neil seem to be taking some time off but I hope they will be back at some point. Apart from the system itself you have distribution maintainers and 3rd party developers of course.

[quote name=deadwood post=5694]@deadwood - As for the system itself it is currently only me. Kalamatee, Mazze and Neil seem to be taking some time off but I hope they will be back at some point. Apart from the system itself you have distribution maintainers and 3rd party developers of course.[/quote]
Uffs, too much work for one person, fixed the problems for Hollywood, Hollywood Designer and the pluggins with problems will be a imposible work.

@AMIGASYSTEM

I checked the codes and this problem is there from at least release 20201110 - it has never been addressed before. The problem you linked to (post #158) was something slightly different an relating to SFS only.

Currently the move codes in Wanderer are written in such a way that if there is a file with same name in target directory, the move operation will abort.

Here is enhancement report for this topic:

https://github.com/deadwood2/AROS/issues/147