YAVR - Yet Another Vista Rant
-
Good choice. If you didn't let the rest of us in on the fun you might be the target instead.
Today's lesson is brought to you by the word "niggardly". Remember kids, don't attribute to racism what can be explained by Scandinavian language roots. -- Robert Royall
dan neely wrote:
you might be the target instead
No good deed goes unpunished :((
Cheers, Vıkram.
"if abusing me makes you a credible then i better give u the chance which didnt get in real" - Adnan Siddiqi.
-
Being that I don't use Vista this is only a guess... but IMHO his problem has nothing to do with "shadow copies" and more to do with Vista's Explorer not doing an automatic refresh after a file operation. No? In each case, Explorer performed the correct operation but simply failed to reflect the change until a manual F5.
That would make sense. :) good old refresh. :)
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb) John Andrew Holmes "It is well to remember that the entire universe, with one trifling exception, is composed of others."
-
It sounds to me like vista actually did exactly what you wanted it to do (managed the files in exactly the way you told it to). Yes, the need-manual-refresh bug is annoying in vista (I had to update one of my uninstallers to manually refresh the desktop as the last step because the icon still showed) but it is VERY minor in the grand scheme of things. But your rant of "cant reliably manage my files" is simply false and misleading. I'll accept "cant reliably automaticly refresh the screen" but the file management worked as intended in your situation.
I'm not sure having to manually refresh is very minor. Sure, when compared to all of the other failings of this OS (from what I've heard), I guess you could say that, but I view an automatic refresh after modifying a folder's contents as a requirement. Considering that many, less aware users don't even know about View->Refresh (F5). How do they deal with this situation? It sounds like one more, in a long line of serious screw-ups. BTW, I picked up a free copy of Vista Ultimate 32bit at an MSDN Event yesterday, so I'll finally install it and have a chance to see what it's really like :). -Justin
-
dan neely wrote:
you might be the target instead
No good deed goes unpunished :((
Cheers, Vıkram.
"if abusing me makes you a credible then i better give u the chance which didnt get in real" - Adnan Siddiqi.
-
It's probably been mentioned before, but I just saw this the other day. My wife bought a Vista laptop, and I try not to use it. But the other day I was helping her with something and suddenly Update popped up a dialog saying it was going to shut down the computer in three minutes and there was nothing I could do about it. (The options for postponing and such were disabled.) I pulled up Task Manager and killed the process, but after a minute (or so) it popped back up and continued counting down as if I hadn't. :mad:
I assume your wife is running a non admin account. You need to log in with local admin rights to change that from the default or override it as a home user. IIRC it's stored as a group policy. At work you need domain admin rights or a heavy cluebat. :doh:
Today's lesson is brought to you by the word "niggardly". Remember kids, don't attribute to racism what can be explained by Scandinavian language roots. -- Robert Royall
-
I assume your wife is running a non admin account. You need to log in with local admin rights to change that from the default or override it as a home user. IIRC it's stored as a group policy. At work you need domain admin rights or a heavy cluebat. :doh:
Today's lesson is brought to you by the word "niggardly". Remember kids, don't attribute to racism what can be explained by Scandinavian language roots. -- Robert Royall
dan neely wrote:
I assume your wife is running a non admin account.
Correct.
dan neely wrote:
You need to log in with local admin rights to change that from the default or override it as a home user.
OK, I have admin right on it, how do I go about setting that for her? Hmmm... could I have done a "switch user" to my profile and postponed the shut down? :confused:
-
dan neely wrote:
I assume your wife is running a non admin account.
Correct.
dan neely wrote:
You need to log in with local admin rights to change that from the default or override it as a home user.
OK, I have admin right on it, how do I go about setting that for her? Hmmm... could I have done a "switch user" to my profile and postponed the shut down? :confused:
Not sure. I did it about 18 mo ago and lost my bookmarks around the same time, IIRC shortly after. If you can't turn anything up googling let me know and i'll go digging through some older stuff and see if I can't find it afterall.
Today's lesson is brought to you by the word "niggardly". Remember kids, don't attribute to racism what can be explained by Scandinavian language roots. -- Robert Royall
-
JazzJackRabbit wrote:
So I try to delete files in the original location. Sorry, can't do that because files do not exist. What? Burned by my previous experiences I do F5 again, no files in original location.
I believe there was a bug that was fixed (at least for the most part because I don't see it on my Vista system anymore) in Vista SP1. Did you put SP1 on your Vista box? If not, you might want to think about it. Just a thought.
Mike Poz
-
It sounds to me like vista actually did exactly what you wanted it to do (managed the files in exactly the way you told it to). Yes, the need-manual-refresh bug is annoying in vista (I had to update one of my uninstallers to manually refresh the desktop as the last step because the icon still showed) but it is VERY minor in the grand scheme of things. But your rant of "cant reliably manage my files" is simply false and misleading. I'll accept "cant reliably automaticly refresh the screen" but the file management worked as intended in your situation.
You're right in a sense that Vista did do what I told it to do. However, it is still a problem because it makes me waste my time double checking results of my action. I try to keep an eye on anything out of the ordinary that might indicate a problem, for example when compiling I glance through warning messages for anything unusual which in the past have saved me lots of time troubleshooting, I do the same with everything else including working with files. If I see something that might indicate a problem, I always investigate. This stupid behavior a) elevates my blood pressure because it makes me think something is wrong with the system/files and b) makes me waste my time making sure everything is alright. When I read about Windows 7, I get cranky because I bet many of these small bugs and annoyances will make it into Windows 7, yet instead of fixing them MS prefers to devote its resources to touch input aka surface, which is absolutely pointless considering that even by 2010 98% of the users will still be using plain old mouse and keyboard.
-
You're right in a sense that Vista did do what I told it to do. However, it is still a problem because it makes me waste my time double checking results of my action. I try to keep an eye on anything out of the ordinary that might indicate a problem, for example when compiling I glance through warning messages for anything unusual which in the past have saved me lots of time troubleshooting, I do the same with everything else including working with files. If I see something that might indicate a problem, I always investigate. This stupid behavior a) elevates my blood pressure because it makes me think something is wrong with the system/files and b) makes me waste my time making sure everything is alright. When I read about Windows 7, I get cranky because I bet many of these small bugs and annoyances will make it into Windows 7, yet instead of fixing them MS prefers to devote its resources to touch input aka surface, which is absolutely pointless considering that even by 2010 98% of the users will still be using plain old mouse and keyboard.
So do you still lookup every single error in the MSDN help when you are compiling code to see what could possibly be wrong? Or do you have some/most of them memorized and know exactly what to look for and howto fix them? Sure, this instance of the bug was annoying when I first encountered it too, but the next time I encountered it, I hit F5 and never put a second thought to it. At that point, and every time thereafter (which hasn't been many), it is a VERY minor thing. Just something you learn in your every day dealings with software. Hell, I'm sure you've told a user of your own software howto work around a bug before and asked them to be patient until you can get some time to work on that section of the code again. How can you expect different of anyone else?