The rule, "Don't use C:\Program Files to store your DBF's", should be followed because if you don't your program won't work. And that rule didn't come from Microsoft, it came from folks like Doug Hennig figuring out how to cope with the rule that DID come from MS, namely, "We've decided to protect you by making C:\Program Files read-only", with no advance notice.
Steve was obviously referencing the rule that came from MS. The fact that there's always a work-around for any such rule, whether discovered by Doug Hennig or Malwar-0 el-Haxor, is part of the point I was making. Actually, I "figured out" how to "cope" with the MS rule by turning off virtualization in the Local Policies long before Doug published his solution. (I didn't so much "figure it out" as do some research; the Policies are well-documented.)
If I can figure out how to get around it, anybody can. Including evil-doers. That's the point I am making. Not sure I see what distinction you are raising. Ken Dibble www.stic-cil.org _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.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.
