"Calculating time remaining..."

[Guest]

I just copied a 77kb PDF file from my Vista (Business) machine to a USB drive.

The file-copy dialogue spent about 15 seconds "Calculating time remaining,"
and then copied the 77kb file in a flash.

I've noticed this same behavior when moving files over my network to and
from my XP and Mac. The Vista dialogue box pops up. It churns away for a
while as it is "calculating time remaining." Then it sporadically transfers
some bits. It never transfers smoothly. It's always in fits and starts. It
seems to take file transfers over my LAN a lot longer between the Vista
machine and the others than just between the XP machine and Mac.

Also, when I just FTP to the Mac from the Vista machine, the file transfer
is fast and smooth.

Is there some configuration somewhere that's causing Vista to choke while
moving files?

 

[philo]

The file-copy dialogue spent about 15 seconds "Calculating time remaining,"
and then copied the 77kb file in a flash.

I've noticed this same behavior when moving files over my network to and
from my XP and Mac. The Vista dialogue box pops up. It churns away for a
while as it is "calculating time remaining." Then it sporadically transfers
some bits. It never transfers smoothly. It's always in fits and starts. It
seems to take file transfers over my LAN a lot longer between the Vista
machine and the others than just between the XP machine and Mac.

Also, when I just FTP to the Mac from the Vista machine, the file transfer
is fast and smooth.

Is there some configuration somewhere that's causing Vista to choke while
moving files?

There is certainly some owful bug in Vista.
When I tried to delete my windows.old folder it took al least 10
minutes...that was insane!

I tried it from the command line...no errors were issued...
yet windows.old was still there! Absurd!

 

[Steve Thackery]

There's a fix available from Microsoft, but they won't release it unless you
specifically ask for it because they say it hasn't been thoroughly tested
yet.

But, the main point is that it is a known bug and is being worked on.

Steve

 

[Julian]

There's a fix available from Microsoft, but they won't release it unless
you specifically ask for it because they say it hasn't been thoroughly
tested yet.

Uh!

Won't release something not thoroughly tested!!!

A new policy?

 

[Rock]

There's a fix available from Microsoft, but they won't release it unless
you specifically ask for it because they say it hasn't been thoroughly
tested yet.

But, the main point is that it is a known bug and is being worked on.

Isn't that for a specific situation, involving copying files over a network?
It 's not for stand alone systems.

 

[Rock]

I just copied a 77kb PDF file from my Vista (Business) machine to a USB
drive.

The file-copy dialogue spent about 15 seconds "Calculating time
remaining,"
and then copied the 77kb file in a flash.

I've noticed this same behavior when moving files over my network to and
from my XP and Mac. The Vista dialogue box pops up. It churns away for a
while as it is "calculating time remaining." Then it sporadically
transfers
some bits. It never transfers smoothly. It's always in fits and starts. It
seems to take file transfers over my LAN a lot longer between the Vista
machine and the others than just between the XP machine and Mac.

Also, when I just FTP to the Mac from the Vista machine, the file transfer
is fast and smooth.

Is there some configuration somewhere that's causing Vista to choke while
moving files?

There is nothing you can set to change this. This behavior has been seen
and bugged through the beta. I have not seen any clear explanation for it.

 

[Adam Albright]

Isn't that for a specific situation, involving copying files over a network?
It 's not for stand alone systems.

Try the hotfix and see what happens. At least 4 or 5 people reported
here they did try the hotfix I linked to, posted on a non Microsoft
site, and they all reported the same result I got, much faster copying
and moving of files and it isn't limited to network transfers like
Microsoft pretends.

For the record, Microsoft has a long checked history of being aware of
problems and having the arrogance of knowning a fix and refusing to
give it to customers unless they beg. This is yet another example of
that odd behavior.

 

[Non-entity]

There is nothing you can set to change this. This behavior has been seen
and bugged through the beta. I have not seen any clear explanation for
it.

Is Microsoft such a lofty organization that you couldn't ASK? I try to keep
quiet in this forum and learn by reading - but I only gain more distaste for
Vista and it's years of development when I experience things like this.
Perhaps you could find out if this will be one of the fixes in SP1?

I can't ask since I don't want to open a "support case" for an obvious
blunder and waste hours talking to "support" - lowly users of MS software
are now reduced to paying some big bucks for the honor to "talk to
Microsoft" (or the contractor you happen to get).

Yes, I'm old, and remember when it was possible to have some great
discussions with the real programmers and developers on the CompuServe MS
fora.

It's not a big deal - that's for sure - it's just "something stupid" that
should have been fixed prior to release.

Bill Halvorsen

 

[Adam Albright]

There is nothing you can set to change this. This behavior has been seen
and bugged through the beta. I have not seen any clear explanation for it.

That's because you don't want to learn.

http://www.cs.auckland.ac.nz/~pgut001/pubs/vista_cost.html

 

[Rock]

Is Microsoft such a lofty organization that you couldn't ASK? I try to
keep quiet in this forum and learn by reading - but I only gain more
distaste for Vista and it's years of development when I experience things
like this. Perhaps you could find out if this will be one of the fixes in
SP1?

I can't ask since I don't want to open a "support case" for an obvious
blunder and waste hours talking to "support" - lowly users of MS software
are now reduced to paying some big bucks for the honor to "talk to
Microsoft" (or the contractor you happen to get).

Yes, I'm old, and remember when it was possible to have some great
discussions with the real programmers and developers on the CompuServe MS
fora.

It's not a big deal - that's for sure - it's just "something stupid" that
should have been fixed prior to release.

I'm not sure what you mean. That who couldn't ask? I am just a user like
you, I'm not an MS employee. As I said the issue was brought up many times
in the TechBeta, by many testers, and I saw no clear explanation why this
happens.