Bill, Where is the location of Legacy ? C:\Legacy ? And how large is the folder of photo's \Legacy\Pictures ? I didn't think about it, but I wonder how many photos are attached overall. I only did a few from the sample.fdb file. I also failed to ask, how big is your database ?
If you cannot open Legacy with your family File, Navigate to the folder where the sample.fdb is and double click. That will open Legacy with the sample.fdb C:\Legacy\Data Tim Rosenlof Utah, USA On 6/1/2012 11:23 AM, Tim Rosenlöf wrote: > On 6/1/2012 10:03 AM, William (Bill) R. Linhart wrote: >> To Tim, thank you for your testing efforts. >> >> I wish my Legacy ran like your Legacy with big images. What was your >> computer configuration for your test? > Netbook. Two years old. Asus, 1.66GHz Processor, 1GB RAM, 140GB Hard > Drive, 52GB Free > >> What do you suspect might be giving at least two users trouble with >> Legacy picture gallery? > I don't have any Idea. You saw my test though. Try to load the > sample.fdb file that should be in your \Legacy\Data folder and see if is > still having trouble > >> How can we determine what might be the cause? I hope you can help me >> wipe away the "tears" somehow. > Accept my Apology. I get a bit possessive of Legacy. You mentioned your > ctrl/alt/del processes, and see no other items running that may also be > taking resources ? > >> Vivian and I have the same problem. We both think our computers run >> fine otherwise. I believe we are both running Win 7 in at least 4 GB >> of RAM. I believe Vivian has 6 GB RAM. We both have a lot of disk >> space. >> >> I have run my testing with no other applications loaded. I created a >> new Legacy file that is nearly empty to run my testing on Legacy >> picture gallery to ensure it is not something in my family file. I >> have De-fragged my hard drive. I turned off anti-virus. I have a >> ticket open and followed the steps Sherry suggested. > That would be my action is to turn off my anti-virus for testing. If you > could send me personally [email protected] a snapshot of your task > manager with only the 'processes'. > >> I felt very frustrated when Sherry told me to re-size my pictures down >> to around 200 KB to get Legacy working. Your answer seems to suggest >> that Legacy should work fine with large images. >> >> I understand your assertion that this is not a defect in Legacy. At >> least it is not a defect you can repeat on your test configuration. >> Something is different between our installations of Legacy. I wish >> mine ran like yours. I would be delighted. > I'm sure you would be delighted. >> What we do know is that it happens to at least two Legacy customers. >> We don't know why. I am sure there are others who gave up before >> even letting you know there was some trouble. I would like to see my >> Legacy work like your Legacy installation. >> >> --- >> >> To Graham: It is not simply a slow down, in my opinion. Slow downs >> come to an end when the process has run its course. Slow downs can >> take seconds or a few minutes to come to a conclusion. But, they do >> come to a conclusion gracefully. >> >> This is a never-ending process with no conclusion. On my machine the >> process consumes 35% of my CPU (2 GHz intel) for 40+ minutes. > Unacceptable. > Try just to load the sample.fdb and see what happens > >> Then I >> closed it. Then the CPU goes to zero. That is a programming loop of >> some kind. In Vivian's case she had to reboot her machine I believe >> to recover. >> >> I have supplied a list of all running processes on my CPU to Sherry so >> tech support could review where the CPU is being used in my system. >> It shows that 25 of the 35% is consumed by Legacy and it is pinned as >> the top CPU consuming process during my testing. That list is a >> snapshot taken after 40 minutes of waiting with the CPU usage stuck at >> 35% while I patiently watched my Legacy picture gallery screen blink >> again and again. Title bar flashes "not responding" periodically. It >> looks like a repeating cycle that never seems to end until I click the >> CLOSE button. Then it eventually closes the Legacy picture gallery >> and the CPU usage goes to zero. Everything seems to return to >> normal. >> >> Bill >> > Tim Rosenlof 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 Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
