XYplorer Beta Club

Using XY 8.80.0014 in Win 7 x64, I'm hitting an issue that I never had in XP. Here's what's going on:


When doing file management on a network share (with files between 1-2 GB in size), here's what I'm used to in XP:

I drag a file that exists on that network share into a sub-folder on that same drive - so the file is simply being moved on that remote machine. The very first file I drag - *AFTER* I finish the drag action - takes about five seconds before the file is moved. This is normal, because if you haven't been interacting with that network drive, the two machines need to re-establish security credentials. After that, I can continue drag-moving files, and the actions will be performed immediately with no delay.


Now, on Windows 7 x64 (connected to the same remote machine, which hasn't changed), here's what happens:

I *try* to drag a file to perform the same type of move operation. However, the file doesn't visually move, the mouse cursor doesn't change - nothing is registered at all. XY becomes non-responsive. After 5-10 seconds, XY returns to being responsive, and the file *may* have moved to wherever I let go of the mouse (even though there was no visual sign that a move operation was being done). If it didn't go anywhere, this next time I try to move that first file, XY visually responds to the action and the file is moved properly.

But, when I go to drag the next file, but the exact same problem occurs again. XY gives no sign that I am doing a move operation and becomes non-responsive. I let go of the mouse in the same area, to make sure the file doesn't move where I don't intend it to. After about 5 seconds, XY becomes responsive again, and *now* I can perform the move normally. This happens for every single file.


I don't know how much of this is Windows 7 throwing a wrench in the works, but I can tell you that I don't have that problem when using windows explorer to perform the same action.

Did you maybe disable WOW64 redirection?

Can you do the move using other means than dragging, e.g. with menu Edit / Move To...?

admin wrote:Did you maybe disable WOW64 redirection?

Can you do the move using other means than dragging, e.g. with menu Edit / Move To...?

WOW64 Redirection is definitely not disabled.

As for the other means, that's a good question. I'll give it a shot and let you know. But keep in mind that it's not that the moves aren't possible by dragging - it's just a labored process given how XY is behaving.

Something else to keep in mind, which I recently discovered, is that it's not 100% of the time. For what it's worth, I usually encounter this issue after I've just copied files to that remote share. (I don't normally need to move files around unless I've just copied new files there, so I haven't worked that much in other circumstances)

I had the chance to try the Edit/Move To scenario. What happened is that the command was able to come up without delay, and I was able to select the destination folder without problems. However, once I clicked "Move", it took about five seconds for the file to dissappear, during which time XY was non-responsive. So, in other words, no go.

As we're on the topic of dealing with remote shares, I have also noticed that if I lose connection with a remote share, XY becomes non-responsive and is unable to close. I can't even kill the process. I can load another instance of XY, but within seconds it becomes non-responsive as well. And again, I am unable to kill the process. I have no choice but to reboot.

I don't know how much of this is Win 7 and therefore, how much influence you have over this unfortunate behavior. I also don't know if the changes you made in 8.80.0027 will help with this or not, but I thought I'd mention it.

Mesh wrote:I had the chance to try the Edit/Move To scenario. What happened is that the command was able to come up without delay, and I was able to select the destination folder without problems. However, once I clicked "Move", it took about five seconds for the file to dissappear, during which time XY was non-responsive. So, in other words, no go.

As we're on the topic of dealing with remote shares, I have also noticed that if I lose connection with a remote share, XY becomes non-responsive and is unable to close. I can't even kill the process. I can load another instance of XY, but within seconds it becomes non-responsive as well. And again, I am unable to kill the process. I have no choice but to reboot.

I don't know how much of this is Win 7 and therefore, how much influence you have over this unfortunate behavior. I also don't know if the changes you made in 8.80.0027 will help with this or not, but I thought I'd mention it.

8.80.0027 did not change anything regarding remote shares.

You say you move files between 1-2 GB in size, this will take a while over the network. Probably Explorer takes the same time, but uses a background thread, and hence shows no freeze. Threaded copy jobs are planned for a later version for XYplorer, so I expect this will also solve your problem.

admin wrote:
8.80.0027 did not change anything regarding remote shares.

You say you move files between 1-2 GB in size, this will take a while over the network. Probably Explorer takes the same time, but uses a background thread, and hence shows no freeze. Threaded copy jobs are planned for a later version for XYplorer, so I expect this will also solve your problem.

No, it shouldn't take any time at all. Remember, those files are already on the remote drive. I'm simply moving them from one directory to another - on the same remote machine. Once the security credentials are re-established, it should be instantaneous.

Mesh wrote:

admin wrote:
8.80.0027 did not change anything regarding remote shares.

You say you move files between 1-2 GB in size, this will take a while over the network. Probably Explorer takes the same time, but uses a background thread, and hence shows no freeze. Threaded copy jobs are planned for a later version for XYplorer, so I expect this will also solve your problem.

No, it shouldn't take any time at all. Remember, those files are already on the remote drive. I'm simply moving them from one directory to another - on the same remote machine. Once the security credentials are re-established, it should be instantaneous.

I see. It has maybe to do with how the connection was established initially. When you establish the connection using Explorer and then do the file operation using XYplorer -- does this work better?

admin wrote:
I see. It has maybe to do with how the connection was established initially. When you establish the connection using Explorer and then do the file operation using XYplorer -- does this work better?

I'm using the Map Drive command, which I thought was a system action, rather than XY specific. Would that be any different if I did that through Explorer?

Mesh wrote:

admin wrote:
I see. It has maybe to do with how the connection was established initially. When you establish the connection using Explorer and then do the file operation using XYplorer -- does this work better?

I'm using the Map Drive command, which I thought was a system action, rather than XY specific. Would that be any different if I did that through Explorer?

I would not think so, but I would give it a try anyway.

admin wrote:I see. It has maybe to do with how the connection was established initially. When you establish the connection using Explorer and then do the file operation using XYplorer -- does this work better?

There is definitely something going on here - especially in Windows 7 - running Windows 7 32 bit and I have hit at least 4 instances in the last two days where XY simply locks up the entire machine when browsing a network share...the last one was so bad - I had a PDF open...that the entire OS simply locked for minutes and minutes and I had to do a hard reset...in every case XY is the start of the lock and then - well....pain.

Something else I'm noticing. When this happens, and XY freezes for a few seconds - when it comes back, XY momentarily dissappears from the taskbar and reappears all the way on the right - as if it shut down and restarted itself.

I don't know if this helps or not, but I thought I would mention it.

Mesh wrote:Something else I'm noticing. When this happens, and XY freezes for a few seconds - when it comes back, XY momentarily dissappears from the taskbar and reappears all the way on the right - as if it shut down and restarted itself.

I have seen this as well...but only on Win 7....since my switch back to Vista 64 SP2...I have specifically pounding XY thru my network shares to see if it would burp or glitch up....but no amount of switching, opening, closing, creating, deleting, copying, moving...anything on a network location has made the app twitch in any way.

So either there is something switched on in XY 8.80 (but I never have messed with the config except to change font display - everything is stock) that really disagrees with Win 7 or there is an outright bug in here somewhere...again - I never noticed a single issue with this app at all until I switched to Win 7 for a few brief weeks here....

Another piece of information - this same behavior (roughly) occurs when I'm renaming files on a remote share. There are several seconds of non-responsiveness when I rename a file, which makes it a royal pain when I have to rename multiple files. It's useless to try tabbing from one file rename to another, given what XY is doing.

I've had to shift to using Windows Explorer for almost all remote file management, which is somewhat disheartening to say the least.

I maybe wrong, but I don't see my question answered yet:

It has maybe to do with how the connection was established initially. When you establish the connection using Explorer and then do the file operation using XYplorer -- does this work better?

It's the only idea I have at the moment...

Mesh wrote:Another piece of information - this same behavior (roughly) occurs when I'm renaming files on a remote share. There are several seconds of non-responsiveness when I rename a file, which makes it a royal pain when I have to rename multiple files. It's useless to try tabbing from one file rename to another, given what XY is doing.

I've had to shift to using Windows Explorer for almost all remote file management, which is somewhat disheartening to say the least.

Mesh:Are you using Windows 7? Or which OS?

Admin: I am using only XY to hit shares in Vista 64 SP2 and I have no lag or any signs of delay when renaming (single, multiple etc) or any other file operation on a network share. Not sure if Mesh has "remote" share meaning one on a local network or not....