I've never installed VFP in anything other than a folder named VFP(#) off the root of my dev system C drive. Not for the cogent reasons w00dy mentions; just because I thought it was totally unnecessary to install it anywhere else and adding c:\vfp9 to my system path involved so much less typing.... You can pick up that folder and plop it down on ay other system and as long as you don't care about seeing it's registered to engineering prototype it's perfectly happy. And there are ways to get around that, too.
-- rk -----Original Message----- From: ProfoxTech <profoxtech-boun...@leafe.com> On Behalf Of Ted Roche Sent: Tuesday, May 4, 2021 3:53 PM To: profoxt...@leafe.com Subject: Re: _framewk,vct is missing or invalid, but it isn't and it's not. Thanks for the insights, wOOdy! I recall installing VFP into its own directories in the distant past, but I haven't done any clean installs on new Windows machines in a long time. This was another developer's machine, and she shares her project with other remote developers and the project files include paths of "c:\Program Files (x86)\" and so forth, so changing them would be a pain in the... neck. But it's great info to know, and now I have some new techniques to debug weird problems. I'd like to tell you that Linux is way easier than this, but it's just as inscrutable in its own way. Issues with SELinux or AppArmor security are just as obscure and difficult to troubleshoot. Stupid computers :) On Tue, May 4, 2021 at 3:10 PM Jürgen Wondzinski <juer...@wondzinski.de> wrote: > As a rule of thumb: FoxPro as a Development system must not get > installed in %Program Files% ! That directory hive is only for Runtime > apps, and such those files are not allowed to write into that folders > (Virus Prevention). > If they need to write program-specific files, those go into %Program Data%. > And: that's a GOOD THING (tm)! > If you insist to install under %program files%, you need to invoke all > permissions on that folder. Since not all programs adhere to those > principles, MS invented that VirtualStore, which is a really clever > way to keep those stupid programs running and stil don't let viruses > get into the secured area. > > Unfortunately, FoxPro is too old for adhering to those Established > Security Rules, that's why you should always install it to a different > non-secured and non-supervised folder (like c:\Develop). See also > http://woody-prolib.blogspot.com/ for installation of VFP9 in a modern > world. > > wOOdy > > > -----Ursprüngliche Nachricht----- > Von: ProFox <profox-boun...@leafe.com> Im Auftrag von Ted Roche > Gesendet: Dienstag, 4. Mai 2021 15:25 > An: profox@leafe.com > Betreff: _framewk,vct is missing or invalid, but it isn't and it's not. > > Rebuilding a project that includes c:\program files (x86)\microsoft > visual foxpro 9\wizards\_framewk.vcx gives the error > > Memo file c:\program files (x86)\microsoft visual foxpro > 9\wizards\_framewk.VCT is missing or invalid. > > But it isn't and it's not. > > I copied both _framewk files from another machine where it works, no > change. > I opened the file exclusively and tried to PACK and get the same > error. I copy the two files to C:\temp and they pack fine, and compile > classlib works there (after I also copied over _framewk.h) but moving > the files back to the above directory and attempting a build project, > rebuild all throws the same error. > > This is a permissions issue with the program files (x86) folder and > I've tried turning off the "Read Only" settings and in the folder > permissions granting Modify and Write to the Users group, but the errors > continue. > > Any suggestions on how to get the Program files (x86) to be read-write > for VFP? Moving the files to the project folder would be my > preference, but it is not my project. > > > --- StripMime Report -- processed MIME parts --- multipart/alternative > text/plain (text body -- kept) > text/html > --- > [excessive quoting removed by server] _______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: https://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: https://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: https://leafe.com/archives This message: https://leafe.com/archives/byMID/CACW6n4v6poLBxgZndenBog-O=_-jl12xtymcadmgtemtxie...@mail.gmail.com ** 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. Report [OT] Abuse: http://leafe.com/reportAbuse/CACW6n4v6poLBxgZndenBog-O=_-jl12xtymcadmgtemtxie...@mail.gmail.com _______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: https://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: https://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: https://leafe.com/archives This message: https://leafe.com/archives/byMID/mwhpr1001mb2144f4b1b70341fc256ce609d2...@mwhpr1001mb2144.namprd10.prod.outlook.com ** 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.
