You're unfair. <rant>
Why don't you put all your stuff in Windows\System32 then? It's a matter of protection, after all. We all were able to put files wherever we wanted, and that does NOT mean it was good. They fixed this (and, btw, this no-write rule is present in Linux as well. Is that a crap OS too? In this case, is there any OS that is NOT crap, from this point of view?) Again, the OS is not tricking YOU, but instead it tries to trick the old shitty applications which dumped all kind of tmp files in C:\. I swear I saw years ago a computer which had literally hundreds of foxpro temporary files in C:\. And it was not a pretty sight at all. As I was saying, the OS is not trying to trick YOU. You are a programmer and supposedly you should have known about the virtualization. It is not OS fault if the programmer doesn't read documentation. Or at least What's New. Imagine some guy moving from Windows 3.1 to Windows 95: "Huh? What is this system32 folder? I didn't put it there, and I don't need no stinking system32!!!! The OS is crappy. I am gonna delete this system32. How they can imagine they know better than me?!!!??!?!" Or imagine your users talking about your application: "Why the hell does this application create a folder in my computer, puts all kind of stuff there and DOESN'T TELL??" I am not a big fan of virtualization, but I believe that for the old apps which tend to write in system-protected areas (and C:\ IS (or at least, it should be) a system protected area, because there are some OS-critical files there), and the original vendor cannot be found to fix this, or the product is out of market, or for whatever reason the application cannot be changed, then the Virtualization is the only way out. Um... there is another way out, disabling virtualization for your application: disable UAC and change shortcut to Run as Administrator. Do this and you're back in 2001. And first worm will tear your computer apart. Good luck. </rant> Bottom line: if one can't handle virtualization, one can get rid of it. But blaming the OS for something that's very well documented but you just happened to not know about it (although google helps a lot) it like driving on the wrong lane and using "I didn't know the rules" as an excuse. > -----Original Message----- > From: [email protected] [mailto:profoxtech- > [email protected]] On Behalf Of Ricardo Aráoz > Sent: Wednesday, July 07, 2010 3:59 PM > To: [email protected] > Subject: Re: Win7 conundrum > > On 07/07/2010 08:19 a.m., Stephen Russell wrote: > > On Tue, Jul 6, 2010 at 11:40 PM,<[email protected]> wrote: > > > >> Don't you just love a crap OS that thinks it knows what you want to > >> do better than you do so it does all kinds of crazy crap? > >> > > ----------------------------------- > > > > You mean that dumping everything into c:\ "root" is a good idea? > > > > How should I know? I'm not your dad. > Nor is the OS. > You are a grown up adult and should be able to do it should you consider > there is a need. Anyway worse than doing it or not, the real crappy thing is > that the OS will trick you into thinking you are doing something you are > really > not doing. That is big daddy saying he'll twist the news a little for your own > good, because we all know big daddy knows better. > > [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
