XYplorer Beta Club

kiku wrote:

So, can anybody using Vista SP1 confirm that copying large files is much faster when using XY's "Backup" than when using XY's "Copy" (which is outsourcing the job to the Shell)?

I cannot confirm that "Backup" is much faster than "Copy"
File: 700MB avi movie

1) copy: 41.2s
2) reboot
3) backup: 41s
4) immediate copy (no reboot): 16.9s
5) immediate backup (no reboot): 16.8s

Vista Home Premium 32-bit SP1
In all cases XYplorer completely freezes.
I wonder if it could have something to do with copy progress feedback or something: http://www.eggheadcafe.com/software/asp ... s-pro.aspx

Ok, thanks!

No, I currently do not use copy progress feedback. But I will later, so it's good to know.

Just as a FYI, I've installed Vista Service Pack 2 a few moments ago and the problem with copying remains. If anyone has a Windows 7 machine running, it'd be great to test the "copying situation" there.

I have the same problem on the Windows 7 RC 64-bit.

I have not yet seen any case where file operations (copying/moving/deleting) do _not_ cause XYplorer to freeze. As long as the file operation dialog is processing data, XYplorer is frozen. However, it will unfreeze if the dialog pauses and waits for input, but as soon as you answer the question it will freeze again.

I hope that this might be useful.

Thanks all, it's on my list.

Hello,

Any news regarding this issue? Now that DP is a reallity what about a new challenge?

kind regards

kiku wrote:Now that DP is a reallity what about a new challenge?

Well, I think DP still is a new babe that needs a bit more work before it's ready to ship out via 8.0 so you may have to wait a bit yet...but that's only my $.02.

This Vista sp1 file copy issue still occurs in Vista sp2. But it seems that in Windows 7 the problem has been solved!

I succesfully copied a 10 gb large file in XYplorer (which is using SHFileOperation for this) without the problem that the file/copy window is freezing. Anyone else who has Windows 7 installed that can confirm this that this Vista "bug" is fixed?

ugus wrote:This Vista sp1 file copy issue still occurs in Vista sp2. But it seems that in Windows 7 the problem has been solved!

Hey, good to hear!

This means that the problem of freezing while copying is only present within Windows Vista. Was the reason for having XY's own file operations because Vista people have been having issues? I fear that the audience for Vista is/will be smaller than XP + Win 7 combined, so file operations are put on the backburner while those who have Vista and will stick to it after Win 7 is retail will continue to experience problems as we do now

zer0 wrote:This means that the problem of freezing while copying is only present within Windows Vista. Was the reason for having XY's own file operations because Vista people have been having issues? I fear that the audience for Vista is/will be smaller than XP + Win 7 combined, so file operations are put on the backburner while those who have Vista and will stick to it after Win 7 is retail will continue to experience problems as we do now

Don,
Couldn't you anyway change the copy routines to use CopyFileEx API instead of using SHFileOperation or at least make a config setting where you can switch to CopyFileEx. I realize it's a lot coding but otherwise there are many Windows Vista users that cannot use the copy routines fully and that is a really big drawback...

ugus wrote:

zer0 wrote:This means that the problem of freezing while copying is only present within Windows Vista. Was the reason for having XY's own file operations because Vista people have been having issues? I fear that the audience for Vista is/will be smaller than XP + Win 7 combined, so file operations are put on the backburner while those who have Vista and will stick to it after Win 7 is retail will continue to experience problems as we do now

Don,
Couldn't you anyway change the copy routines to use CopyFileEx API instead of using SHFileOperation or at least make a config setting where you can switch to CopyFileEx. I realize it's a lot coding but otherwise there are many Windows Vista users that cannot use the copy routines fully and that is a really big drawback...

Well, it's on my list and I'm going to do it, not only to workaround a Vista bug, but for lots of other reasons (e.g. a good progress dialog...). But one thing after the other...

admin wrote:

ugus wrote:

zer0 wrote:This means that the problem of freezing while copying is only present within Windows Vista. Was the reason for having XY's own file operations because Vista people have been having issues? I fear that the audience for Vista is/will be smaller than XP + Win 7 combined, so file operations are put on the backburner while those who have Vista and will stick to it after Win 7 is retail will continue to experience problems as we do now

Don,
Couldn't you anyway change the copy routines to use CopyFileEx API instead of using SHFileOperation or at least make a config setting where you can switch to CopyFileEx. I realize it's a lot coding but otherwise there are many Windows Vista users that cannot use the copy routines fully and that is a really big drawback...

Well, it's on my list and I'm going to do it, not only to workaround a Vista bug, but for lots of other reasons (e.g. a good progress dialog...). But one thing after the other...

Sounds good

I'm not a programmer myself but it seems that the SHFileOperation is deprecated in Windows Vista, use IFileOperation Interface instead.

http://msdn.microsoft.com/en-us/library ... S.85).aspx

http://blogs.sevensteps.com/2008/06/shf ... under.html
http://blogs.sevensteps.com/2008/06/shf ... h-boy.html

Hope it helps.

Yes, I know. But I'd be crazy to implement Vista's IFileOperation and inviting all those known and unknown Vista bugs into my app. I will very probably use good old CopyFileEx.

admin wrote:Yes, I know. But I'd be crazy to implement Vista's IFileOperation and inviting all those known and unknown Vista bugs into my app. I will very probably use good old CopyFileEx.

Ok. But isn't it strange that it worked for ugus in Windows7 while some people reported that the issue remained?!?

Personally, I will upgrade to Windows7 64-bit when it's available, but would like to see this fixed rather soon than later