I agree with everything that Mark has outlined below, and have my setup the same way.
*My* addition. If Legacy is suppose to only be installed to the root, then why doesn't Legacy 'force' you instead of giving you the opportunity to do otherwise. Tim Rosenlof On 11/16/2010 6:46 PM, Mark Wilson wrote: > Jerry, for what it's worth, I've always installed Legacy within the > "Program Files" directory, and NEVER under the root of the drive. > Legacy has always performed well using this setup, in my experience. > > Beginning with the 64-bit Windows versions of XP, Vista, and 7, there > has been two "Program Files" directories, one for 64-bit software and > one for 32-bit software. When running a 64-bit Windows system, there > will be one "Program Files" directory for 64-bit software installation > and one "Program Files (x86)" directory for 32-bit software > installation. If running a 32-bit Windows system, there will be just a > single "Program Files" for all 32-bit software installation. The 32-bit > system will not install 64-bit software, so there is no need for the two > separate directories. > > Then starting with Vista, the security within the operating system was > beefed up. It started to require special "permissions" for some > software to operate properly. This was done to help reduce the > possibility of a rogue program being installed without the knowledge of > the user. Sometimes it even prevents the proper operation of software, > "thinking" that the software is trying to perform some clandestine > operation in the background. > > For the most part, software should be installed and run as intended; > unless that software does not perform as expected. And as you have > undoubtedly noticed, Windows Vista and 7 require "Administrator > Privileges" for many software operations. Here is the work around for > Legacy that I have successfully used with Windows Vista Pro (32-bit) and > Windows 7 Ultimate (64-bit): > > 1) Locate the "Legacy.exe" file within the Legacy installation > directory. (In my case, "C:\Program Files (x86)\Legacy"). > 2) Right-click on the file. Select "Properties." > 3) Click on the "Compatibility" tab. > 4) Towards the bottom of the window, place a check-mark next to "Run > this program as administrator." > 5) Click on the "Apply" button and then the "OK" button. > > This "tweak" has improved the reliability of Legacy, but keep in mind > that it may not work with other programs. This method should NOT be > used on any software that must start during the system boot process! > For some reason, the software is prevented from running at start-up and > must be manually launched after the system has booted. > > If for some reason, you still have problems with Legacy, try this: > 1) Start with the previous steps 1 and 2. > 2) Click on the "Security" tab. > 3) Click on the "Edit" button. > 4) Select (highlight) the line, "Users (ComputerName\Users)." > 5) In the "Permissions for Users" group, place a check-mark in the > "Allow" box for Full Control. > 6) Click on the "Apply" button and then the "OK" button. > > Now... if for some reason you were unable to edit the file's Security > Permissions for the Users account (grayed out), it is because you do not > have ownership of that file (e.g., Legacy.exe). I won't go into the > "how to change ownership" part because it can, in some cases, make it > possible for potential software exploits. And we're more concerned > about overall system security than we are about getting software to run > correctly, right? > > I hope this helps you! > > > Mark Wilson > > > > On 16 Nov 2010 11:28 AM, Jerry wrote: >> Thanks Sherry. I think you hit the nail on the head. I have Windows >> 7 Professional and have Legacy installed to the Program Files on C, not >> directly on C. So, I'm wondering if I go ahead and simply MOVE Legacy >> to be directly under the C drive, if that will work ok? It should, I >> would think, but I'll be sure to back up my files really well before I >> attempt it. Thanks, --Jerry >> >> On 11/16/2010 10:57 AM, Sherry/Support wrote: >>> I've never seen this error message before. Normally an error long will >>> simply be created. >>> >>> If you have WIndows 7 or Windows Vista, you must have Legacy installed >>> to the c:\Legacy folder on your hard drive. It will not run correctly >>> if it's installed to the c:\Program Files folder. >>> >>> Please review the instructions at >>> www.LegacyFamilyTree.com/helpWindows7andVista.asp. >>> >>> Sincerely, >>> Sherry >>> Technical Support >>> Legacy Family Tree >>> >>> >>> >>> On Mon, Nov 15, 2010 at 7:59 PM, Jerry<[email protected]> wrote: >>>> Does anyone know the process of re-creating the appropriate error logs >>>> for Legacy? Somehow mine got deleted or something - I attempted to >>>> just create a blank one with the name Error.log - also tried >>>> Errorlog.txt within the Programs/Legacy directory, but nothing seems to >>>> work. When I do a File Maintenance / Check and Repair, Legacy says my >>>> error log does not exist. -Thanks, --Jerry > > > > Legacy User Group guidelines: > > http://www.LegacyFamilyTree.com/Etiquette.asp > > Archived messages after Nov. 21 2009: > > http://www.mail-archive.com/[email protected]/ > > Archived messages from old mail server - before Nov. 21 2009: > > http://www.mail-archive.com/[email protected]/ > > Online technical support: http://www.LegacyFamilyTree.com/Help.asp > > To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp > > > > Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
