Freeze during copying on Vista 32-bit

[reg]

You've got it the wrong way around. Vista had major file copying problems before SP1. Just do a search on google - you will see that it was one of the most talked about bugs before SP1 arrived and fixed it. I intentionally waited until SP1 so that I wouldn't have the file copying problems.

I believe that in discounting the Vista user base, you are shooting yourself in the foot.

[serendipity]

You've got it the wrong way around. Vista had major file copying problems before SP1. Just do a search on google - you will see that it was one of the most talked about bugs before SP1 arrived and fixed it. I intentionally waited until SP1 so that I wouldn't have the file copying problems.
I believe that in discounting the Vista user base, you are shooting yourself in the foot.

Yup thats right, but you missed one previous post and one important point. What Don now wants to do is create XY's own copy routine so that anything MS does or anyone else does, does not affect the way XY works. In other words, when XY's own copy method will solve all future copy problems why invest on some short-term solution which will be abandoned anyway? And anyway after fixing this whats the guarantee that MS will not release something tomorrow which will break copy thing again?
So please be patient until XY has its own copier routine.

[ivan]

It's not the correct way to put it. Copying worked perfectly under Vista 32 SP0 just like under XP. Now Microsoft brings SP1 and copying gets a freeze issue. Whose bug is that, huh?
I have XYcopy on my list since long and I will do it when the time has come -- because it is good, not because MS has created another problem that developers have to find workarounds for.

I think the correct way to put it would be this:
a) Copying worked OK using WE and Vista 32-bit RTM and it worked OK with XY.
b) Copying works even better than before using WE and Vista 32-bit SP1 but doesn't work 100% with XY.

Since MS have improved copying with SP1 and I haven't heard of significant problems affecting other applications then I doubt it's something they'd look into with SP2. Anyway, assuming and hoping that they would is a long shot.

As much as some of us (on ALL OS's) have been looking forward to DP, and I'm not a Vista user, I'm wondering if it might be worthwhile attempting to address the Copy issue first? I have no idea of what effort/time it would take compared to DP, but I'm just trying to think of it from a marketing POV...Yes, DP would get you more customers but they would then still have issues with copy so thus my thought to hold DP till 8.0 or so.

I would like to echo your opinion. Introducing something radical like DP in 8.0 without solving the Copy issue first is compounding the problem and therefore making it worse. The more customers join XY universe the more chance there is that they will be using Vista 32-bit and as such they are vulnerable to the problem.

Yup thats right, but you missed one previous post and one important point. What Don now wants to do is create XY's own copy routine so that anything MS does or anyone else does, does not affect the way XY works. In other words, when XY's own copy method will solve all future copy problems why invest on some short-term solution which will be abandoned anyway? And anyway after fixing this whats the guarantee that MS will not release something tomorrow which will break copy thing again?
So please be patient until XY has its own copier routine.

And right now is the perfect time to do something about it. Admittedly, there aren't as many Vista users as there are XP ones, but that's exactly why Don should make the most of Vista 32-bit users that are present so we can help iron things out. After all, we are the ones who are having this major issue so we would be more than happy to help.

[admin]

It's not the correct way to put it. Copying worked perfectly under Vista 32 SP0 just like under XP. Now Microsoft brings SP1 and copying gets a freeze issue. Whose bug is that, huh?
I have XYcopy on my list since long and I will do it when the time has come -- because it is good, not because MS has created another problem that developers have to find workarounds for.

I think the correct way to put it would be this:
a) Copying worked OK using WE and Vista 32-bit RTM and it worked OK with XY.
b) Copying works even better than before using WE and Vista 32-bit SP1 but doesn't work 100% with XY.

Since MS have improved copying with SP1 and I haven't heard of significant problems affecting other applications then I doubt it's something they'd look into with SP2. Anyway, assuming and hoping that they would is a long shot.

As much as some of us (on ALL OS's) have been looking forward to DP, and I'm not a Vista user, I'm wondering if it might be worthwhile attempting to address the Copy issue first? I have no idea of what effort/time it would take compared to DP, but I'm just trying to think of it from a marketing POV...Yes, DP would get you more customers but they would then still have issues with copy so thus my thought to hold DP till 8.0 or so.

I would like to echo your opinion. Introducing something radical like DP in 8.0 without solving the Copy issue first is compounding the problem and therefore making it worse. The more customers join XY universe the more chance there is that they will be using Vista 32-bit and as such they are vulnerable to the problem.

Yup thats right, but you missed one previous post and one important point. What Don now wants to do is create XY's own copy routine so that anything MS does or anyone else does, does not affect the way XY works. In other words, when XY's own copy method will solve all future copy problems why invest on some short-term solution which will be abandoned anyway? And anyway after fixing this whats the guarantee that MS will not release something tomorrow which will break copy thing again?
So please be patient until XY has its own copier routine.

And right now is the perfect time to do something about it. Admittedly, there aren't as many Vista users as there are XP ones, but that's exactly why Don should make the most of Vista 32-bit users that are present so we can help iron things out. After all, we are the ones who are having this major issue so we would be more than happy to help.

If it is true that other applications using Shell file copy do not suffer from the same symptom under Vistae 32 SP1 then it's indeed worthwhile to look into this. It might be a very small thing. First thing however is to remove the last "user control" (aka make new address bar), since user controls can be responsible for any kind of surprises.

[JohnM]

Hi guys,

Just to add my 2cents...

I have recently moved (I won't say upgraded) to Vista Home Premium x64 SP1 and this freezing-while-copying problem is still with me.

So for me at least this problem is not just restricted to 32-bit Vista.

Cheers
JohnM

[admin]

Hi guys,

Just to add my 2cents...

I have recently moved (I won't say upgraded) to Vista Home Premium x64 SP1 and this freezing-while-copying problem is still with me.

So for me at least this problem is not just restricted to 32-bit Vista.

Cheers
JohnM

It's the SP1. They hastily rewrote the whole copying stuff and of course made some mistakes.

[kiku]

I can't wait to see this fixed in XYplorer, hopefully before Vista SP2 release...

regards

[reg]

Would be great to know if admin has looked at this and has scoped out the size of the problem. Is this something we can expect to be fixed soon or should we be trying to forget about the lost time between copies?

[admin]

Would be great to know if admin has looked at this and has scoped out the size of the problem. Is this something we can expect to be fixed soon or should we be trying to forget about the lost time between copies?

I'm aware of the demand. But some other things will have to come first. I cannot make any predictions about when I write XYcopy.

[kiku]

I noticed that it's also impossible to cancel the copy operation or it takes a lot of time to stop, so I was wondering if it can be related with the following article:
http://msdn.microsoft.com/en-us/library/aa480216.aspx

I am not a programmer, so I am sorry if I am wasting your time with something that has nothing to do with it

[admin]

I noticed that it's also impossible to cancel the copy operation or it takes a lot of time to stop, so I was wondering if it can be related with the following article:
http://msdn.microsoft.com/en-us/library/aa480216.aspx

I am not a programmer, so I am sorry if I am wasting your time with something that has nothing to do with it

I don't think so since I do not use those API. But who knows what Vista is doing in the background.

[ivan]

Don, I'm sure you haven't forgotten about this but with over a month gone by since there has been a peep, I cannot continue to be silent any more on this issue. Nobody apart from you can wave a magic wand and make it go away. Your commitment to increasing number of features for common folk has made me optimistic that something would happen on this front, but unfortunately this has not been the case.

I realise that you have been very busy with other things, but this IS important and this REALLY needs to be solved. You'd know better than me whether this issue is a complex or a simple one to deal with, but as a Vista user I cannot emphasise hard enough how crucial this is. According to my not-so-scientific poll, most people do use XP but 27% is still quite substantial and cannot be overlooked.

Please try to deal with this as soon as possible and I'm not the only who is asking you to do so. Not sure whether I'd matter to you or not, but I personally can't be 100% behind XYplorer if this is not sorted.

[admin]

I personally can't be 100% behind XYplorer if this is not sorted.

No problem, ivan, just go away and move over to some other file manager.

bye,
don

[graham]

You know Ivan, there are times when some problems as reported are not that easy to resolve. It could be a bug in XY or something (more likely) in Vista. It is difficult to comment specifically but I can assure you that if a solution was within reach then it is not forgotten and implemented asap. I think we take it for granted that Don comes up with solutions and new ideas at such speed but he is very unusual - I am desperately waiting for the new release of Bibble 5 and have waited for about a year, others much longer but the CEO refuses to release software until he is satisfied it is right - that is a virtue and not a fault, so may I suggest you allow Don some space and time - if you can't live with the waiting then buy another file manager but don't expect it to be error free or as dynamic.

[ezhik]

As a new user I think my input my help. I have this file copy bug on Vista 64 SP1, first time I came across it I was copying 68 x 200 Mb files and saw it freeze. I didn't know whether the files were actually being copied or getting lost, so I opened another instance of XY and went to the copy to location and there were my files, the list updating one by one as they were successfully copied. So that's what I do now.

My work around until its fixed? Open a new instance of XY and work with that one until the copying is done, no big deal. Of course you need to have allowed more than one instance in the configuration. Personally I can wait, though I'm sure not everyone will want to use this work around, I hope it will help some.