On 07/07/2010 10:19 a.m., Grigore Dolghin wrote: > You're unfair. >
Usually. > <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?) > If you have the privileges, you can write wherever you want (AFAIK). > 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. > Where do *I* see the files? Where they really are or somewhere else? I wouldn't care the OS allowed me to give *permision* to trick a *particular* program, so long as I see the files in their real place. After all, this program may have an option to change the default saving place and I might want to use that instead of tricking the program. > 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. True. But I will read the W7 docs right after I finish with the Linux docs, the PostgreSql docs, the complete fox docs, python docs, tb docs, mozilla docs, etc.etc. Oh! I forgot about reading and thoroughly understanding the EULA and all the different licences. When I'm done with all that, just then I'll start coding (provided I don't starve first due to lack of incoming money). > 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?!!!??!?!" > Now *this* is unfair. I guess we are two of a kind. :-) > 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??" > Even more! Why does it put files all through the system, and does not give me the privilege to decide where I want the files kept. And then I have to buy third parties soft to erase all the unnecesary or risky (from a security pov) files (IE privacy keeper comes to mind). That's why I usually prefer portable apps in W$. > 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. > I think I read some breaking news last night about some amazingly new technology, they called it "virtual machines". You can have a vm with an old os version and run your legacy apps there. Seems almost magic, does it not? _______________________________________________ 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.
