Network drives w/ and w/o assigned label

I don't know if it is a bug, but Opus doesn't "recognize" drives that have no drive letter assigned. If I want to move files within the same drive Opus always copies the files instead of moving them (Drag'n'Drop).

Example network drive with assigned drive letter:

X:\Test\File.exe to X:\ ---> moving operation

Example network drive without drive letter:

\PC\Drive\Test\File.exe to [b]\PC\Drive[/b] ---> always copying operation

I don't like to use x-driveletters for all my network drives. Any solution?

Regards,
Sasa

I've filed a report to GPSoft. As far as I can tell it only occurs when:

  1. You're accessing the share via a UNC path, not a mapped drive letter.

and

  1. You're moving items into the root of the share. Moving things into a subdirectory beneath the share seems to work fine.

Is that consistent with what you see? Let me know if I should add or change any details in my report.

Hello Nudel,

yes and right, only root-dirs, moving within subdirs working fine.

Maybe my "NAS-Problem" will also be solved (can't delete dirs if they're not empty, EVERY other Filemanager work).

Thanks.

I don't know if there are fixes in that area. It is best to talk to GPSoft directly about that. It's likely that the issue is tied to something unique about the way your NAS device works so you might be asked to run a debug version of Opus or use some monitoring tools to see what's going on if GPSoft can't reproduce the problem on the hardware they have available. (If you're lucky the NAS manufacturer might loan GPSoft a device to try to repro the problem with, but that's never guaranteed.)

Check your NAS has the latest firmware/drivers, too. It could be a bug on its side that has since been fixed.

It might be worth having a look at what Process Monitor reports Opus (and other programs) doing when you delete directories from the NAS. That might reveal what Opus does differently and where the operation fails.

I feel the need to rant. None of the quote below will help solve your problem, which I hope can be fixed, but it might make it easier to understand why there's a problem which only seems to affect Opus.

[quote="Nudel Rant"]It seems that NAS devices vary greatly in how they handle less commonly used features, something which has tripped up the Windows developers in one example (which has meant we'll be stuck forever with the slow method of reading directories):

blogs.msdn.com/oldnewthing/archi ... 73160.aspx
blogs.msdn.com/oldnewthing/archi ... 64809.aspx

That problem turns out to affect many NAS devices from different vendors. I've experienced a bunch of other problems, too.

The Samba-based NAS devices are usually lax at sending change notifications because they detect changes by polling, sometimes every few minutes(!), if at all (!!). (I gather this is improving in newer Sambas, if you use the right Unix/Linux filesystem and the right patches and...)

Some NAS devices don't support Unicode (including some Samba-based ones, if they use the wrong build/version of Samba).

The LinkSys NSLU2 that I bought had all of these problems and also had such a cripplingly slow processor that it couldn't read/write data anywhere near as fast as the network and USB2 drives allowed... (That thing is now sitting in a drawer with other electronic junk. Could make a nice embedded Linux web server, but next to useless at the job it was sold to do...)

I'm sure there are some good NAS devices (I know Jon has used one that he said worked well, though I don't know the make/model) but it seems there are a lot of bad ones, too. I decided it was easier to build low-powered Windows boxes to get SMB network drives, rather than find a good embedded solution!

None of which helps much, but it's good to rant. :slight_smile:[/quote]

Thanks Nudel. I have two "Synology Diskstation 106" incl. latest FW (great device, very fast and lots of stuff included). The problem occurs on both devices.

They have a great forum (similar to this), but no one uses DOpus :cry: (btw Opus never appears in tests and german special-magazines, only TC & Co. :question: )

I'll monitor the file-operations next days.

The problem is caused by some NAS devices returning incorrect result codes or error codes for the RemoveDirectory() function.

If you'd like to help us fix it, please download the small test program from gpsoft.com.au/files/TestNASDelete.zip and run it. It will prompt you to select a folder on a NAS device to attempt deleting. Make sure you pick a non-empty folder so the delete fails, and then report back what the result code/error code are. Thanks!

Thanks Jon, I'll report in a few hours when I'm back home...

Edit: Here it is...

RemoveDirectory \NAS1\Download\Testfolder returned 0 Error code 2.

Folder "Testfolder" included one exe-file. Also same report when a driveletter is assigned to "Download" (= X:\Testfolder).

Regards,
Sasa

Sasa,

Thanks for this!

We've made a test version of Opus for you. Could you email me directly (direct email to me - greg@gpso... ) please and I'll give you details of where to access it and what to do.

[quote="greg"]Sasa,

Thanks for this!

We've made a test version of Opus for you. Could you email me directly (direct email to me - greg@gpso... ) please and I'll give you details of where to access it and what to do.[/quote]

Sent a mail to you via mailbutton...