It fails with a less than helpful message. "There was a problem with the transfer. Please try again or contact support for assistance".
Well it is, was, advanced as a beta. I guess I'm spoiled with Google's betas that are better than Microsoft's finished products.
And what is wrong with error messages that had a simple number.
I remember the IBM mainframe days when I had to code user errors like "IEZFJOHN001 – CVT not found! Big problem. Operator notify issue a type one alert!". A friend of mine reported that "my" error message was actually triggered during a system upgrade. Other system utilities either failed silently or caused OC4s and OC6s. My friend was able to tell the staff that he knew the anal retentive who wrote that code.
Hey, when I was a baby programmer, I didn't want a screw up on my watch. If the CVT wasn't where it was supposed to be then I didn't want to get blamed for losing it.
As I recollect, that program had 11 different error conditions. All equally improbable. But, I was conscientious and an uber nerd those days!
My friend actually won a bet on it. They didn't have the source code for it, and many other utilities. He bet that he could have the source code in hand in less than an hour after he called me. I had to hustle to find it in my garage. I was able to offer him either a listing or punch cards. Come to think of it I don't the he ever sent me my half of the six pack.
Now, does anyone need some logical character manipulation Fortran subroutines? How about some assembler reentrant routines to do time sync?
Ahhh, those were the days when I had "real" skills.
Reinke Faces Life 