Bug with mounted drives

Hello,

I upgraded Directory Opus vom 10 to 11. Unfortunaltely there seems to be a big bug in the new version.

I have 3 harddisks in my PC. The first harddsik is C:\ of course. The second harddisk is D:\ but is also mounted to an empty NTFS folder as C:\Users\Reinhold\Daten. The same is with the third harddisk which is E:\ and also mounted as C:\Users\Reinhold\Daten\Bilder II.
Access to D:\ and E:\ works but access to C:\Users\Reinhold\Daten\Bilder II etc. is very buggy.

I can open C:\Users\Reinhold\Daten\Bilder II\2010_2019\2013\Norwegen_JPG Ready\rename_jpg.bat but I can not edit it. But I can edit it when the path is E:\2010_2019\2013\Norwegen_JPG Ready\rename_jpg.bat.
It is the same file only the writing of the path is different. This did not happen in Version 10, in Directory Opus 10 everything worked perfect. I get the error message, saying that the path does not exist.

The same situation is when I right click on a file and click "open with (any program). It works with D:.... but not with C:\Users\Reinhold\Daten....
The same is with properties: Select more than one folder and right click on properties. You get the correct result on D:\ but not on C:\Users\Reinhold\Daten.
The same is with Treesize Free: it works with D:\ but not with C:\Users\Reinhold\Daten\

Of course I tried all these things in Windows Explorer too and there everything works as id should. And also these things worked in Directory Opus 10.x very well.

I hope someone can help me or the programers of Directory Opus can fix this problem.

Best wishes

Reinhold

Which program is the error message coming from? Opus, or the text editor that Opus is launching?

What is the full, exact error message? Does it mention a path?

What happens if you paste this into the Start menu's search/run field?:

notepad "E:\2010_2019\2013\Norwegen_JPG Ready\rename_jpg.bat"

Hi leo,

thanks for looking at my problem.
Here is the error message:

If I paste your line in Start menu notepad starts and loads the batch so I can edit it.

Regards

Reinhold

Hi leo,

could you verify the problem? Will GP fix it?

Best wishes

Reinhold

Please be patient, it's 10am on Monday here, the issue was reported yesterday, and we'll need to configure a machine to try what you've described.

People get used to your fast response times.. o)

I have a similar configuration to RWittich.
I have no problems accessing a different volume (sd-card reader this is) in a ntfs folder on c:\users<username><mountpoint>
A partition from the same volume (drive D:) mounted to c:\users<username><mountpoint2> works as well here.

@rwittich: Which method have you used to mount the drives to folders below C:? There are a few different ways to do it, so it may be important that we try the same one you have used.

Hi leo,

i did it with the windows control panel

In Disk Manager, right-click the partition or volume where you want to assign the mount-point folder path, and then click Change Drive Letter and Paths.
To assign a mount-point folder path, click Add. Click Mount in the following empty NTFS folder, type the path to an empty folder on an NTFS volume, or click Browse to locate it.

Regards

Reinhold

No fix available?

Regards

Reinhold

Please be patient. This is not the only issue in our queue and it hasn't been that long. You have a good workaround for now; just use the other drive letter.

When do you expect the fix?

Regards

Reinhold

That depends how long the things ahead of it in the queue take.

Assuming this is a bug (not confirmed yet), the fix will not be in your hands until we put out the next beta version, which will be contingent on the other fixes that we want to put into the next beta also being finished. So you will just have to be patient.

Every moment I have to spend replying to this thread is just delaying when I will be able to look at your issue.

I think I have re-created what you have described, as shown in the video below, and there were no problems double-clicking text files below the mounted HDD folders to send them to Notepad.

Please watch the video to confirm that I have done things correctly. Maybe I missed an important detail in the setup somewhere.

If I haven't missed anything then I do not think the issue you are seeing is caused by Opus. It could be something to do with file/folder permissions, or which user/account Opus is running under. (If double-clicking works in Explorer but not Opus, check in Task Manager's Process tab that all instances of both dopus.exe and explorer.exe are running under the same account name.)

Hi leo,

thanks again for looking at the problem. But in the video I can not see that you exactly tested what I told you. When I doubleclick a file, I can open it and edit it and so on. There is no problem. But see what I described:

"The same situation is when I right click on a file and click "open with (any program). It works with D:.... but not with C:\Users\Reinhold\Daten...."

The problem exists in DO 11.1 but it exists not in DO 10.x, so I think it comes from DO.

I watched your video a few times and I verified what you did. And I found that the problem really does not occur with a *.txt file. It occurs with *.pdf and all kinds of images like *.jpg and *.psd *.tif etc.
Seems to be a very strange situation.

Regards

Reinhold

Thanks! I've confirmed the problem with the context menu, and have written a fix that should be in the next beta version.

Thanks and have a nice weekend.

Beta3 works perfect.
Thanks

Reinhold

Hello:

I am right-clicking a .mrimg (Macrium Reflect) image file, clicking menu item Explore Image, and get error message "Macrium Reflect - Failed to access". I have DOpus beta 7. In Windows Explorer, I have one "right-click" bold Explore Image menu item, which does not work, and one non-bold Explore Image menu item, which does work. Does not matter if the drive is mounted or not. By "work", I mean that the image file should display its content, namely all the drives, folders and files that I have imaged using Macrium Reflect.

Since Beta 3 worked for rwittich, this must be some other problem. Any ideas?

Hans L

The thread you're replying to is from 3 years ago and so the "beta 3" referred to is a very old version.

Please start a new thread if you have an unrelated issue.

Sorry, Jon, but I though I saw, yesterday, that the last posts were from Feb 23, 2017. Must have misread!

Will start new thread.

Hans L