[quote="Peke"]Sorry, didn't know that.[/quote]I would remove my script's reliance on this, except that it scrapes the forum search results and the Subject is the only field available.... Roll on the day when reporting and tracking are integrated :)

[quote="Peke"]EDIT: Also include Space prefix " [#-----]".[/quote]
OK, will do.

[quote]Also Topic would be much clear as "1511 Failed sync require hundreds Cancel clicks [#10308]" instead of current[/quote]
a) I do think well-formed English is clearer.
b) I believe "Failed sync require[s] hundreds [of] Cancel clicks" is not necessarily true, whereas "Failed sync can require hundreds of Cancel clicks" is.

Sorry, didn't know that. I have also removed version number as it is replicable in 4.1.0.1616 and I didn't tested in 1511 so 1511 is irrelevant for fixing.

EDIT: Also include Space prefix " [#-----]". Also Topic would be much clear as "1511 Failed sync require hundreds Cancel clicks [#10308]" instead of current

Peke, I guess the removal of the version number from the subject of the root post was by you, to make room for the Mantis number. I need these version numbers for my tracking script so I have restored it (crushed the text to make space). In future I'll include [#-----] to reserve sufficient space for the Mantis number.

No problem, this just made me remember to look at documentation of My NAS and see new ACL settings from latest firmware.

Thanks Peke.

Added as http://www.ventismedia.com/mantis/view.php?id=10308

[quote="adrianmarsh"]As each folder could have different ACLs in Windows[/quote]

This is one folder - info added to report. Thanks.

You're trying to sync to a RO device right - so MM can't write to it to update it.
As each folder could have different ACLs in Windows, then MM has to try each one independently (not sure if thats MM's intended design, but would make sense to me).

So, main issue is really, why are you trying to sync with a RO device ?

1) With generic device auto-sync configured for a few hundred tracks in the same folder, click auto-sync
2) Due to the device being read-only, get an error dialog e.g.:
[img]http://img90.imageshack.us/img90/7199/erroroq.png[/img]
3) Click Cancel.

Expected: auto-sync cancels.
Observed: auto-sync fails to cancel, but presents the dialog again, with identical content, requiring another Cancel click, and repeats a few hundred times.

Workaround: use Task Manager to kill the app.

This with Windows 7 Pro 64-bit using Windows Classic theme.

EDIT(TC) Tracked at http://www.ventismedia.com/mantis/view.php?id=10308