View Single Post
Old 29th January 2016, 20:19   #2900  |  Link
Sir Didymus
Registered User
 
Join Date: Mar 2004
Location: Italy
Posts: 953
Ok. Just checked. The issue is in the code of BM.

There is one single line of code where the problem originates.

One new function has been introduced, from the release 1.4 up to the latest 1.6, which is most possibly responsible for the reported odd behaviours. This function (in the WinApi) is the "GetFileAttributes". In the BM code it is used to check the destination folder against the constant 0x10 "FILE_ATTRIBUTE_DIRECTORY". All other results from this test currently trigger the reported BatchMux ERROR. I am quite sure (now, after deepening the matter) that encrypted directories - 0x4000 "FILE_ATTRIBUTE_ENCRYPTED", mounted volumes, network drives and possibly other legit directories in the user's file system are wrongly interpreted as invalid directories.

I will do some testing during the week end and report back to you...

Stay tuned, and in the meanwhile, please proceed as suggested by manolito - downgrade to BM release 1.3, or by MrC - just use a plain directory under the C: volume...

Cheers,
SD

Last edited by Sir Didymus; 29th January 2016 at 23:08. Reason: Detailing...
Sir Didymus is offline   Reply With Quote