It's clean, kat, and me in the room

On 4/13/2013 8:43 PM, Eliz Hanebury wrote:
> LOL this is why I love these lists; but may I suggest she might never
> have found the problem until it killed her computer if she didn't have
> the LegacyUG.
>
>
>
> Eliz
>
>
> On Sat, Apr 13, 2013 at 9:14 PM, Brian L. Lightfoot
> <[email protected] <mailto:[email protected]>> wrote:
>
>     As others have stated, thank you for giving us the “end of story”.
>     As the multitude of messages piled up all detailing the method of
>     doing clean re-installs of Legacy, not only did you follow the
>     instructions precisely but many other uses that just lurk in the
>     background probably assimilated some good things to know.
>
>     If your Windows system files were that much corrupted, I’m
>     surprised that many other programs didn’t cause the same if not
>     similar errors when they were run. Maybe you would have found out
>     if all your attentions weren’t focused only on getting Legacy
>     running. Thanks for letting us know.
>
>     Good luck in all your endeavors.
>
>     Brian in California
>
>     *From:*BK Ford [mailto:[email protected]
>     <mailto:[email protected]>]
>     *Sent:* Saturday, April 13, 2013 2:26 PM
>     *To:* [email protected]
>     *Subject:* Re: [LegacyUG] Panic!-UPDATE
>
>     Okay, here's the report on the resolution of my Legacy error, for
>     those who wanted to know the "end of the story."
>
>     After the tech support at Milennia saying there was nothing they
>     could do, a couple of people on the group helped me with putting
>     my family file into a format that I could use in FTM (last
>     resort). Great relief to know there was a way I could access my
>     data at least. I am very appreciative of one of our group who took
>     my file and checked it for errors and put it in a GEDCOM format
>     for FTM.
>
>     Others had great suggestions/tips. No matter what I tried, Legacy
>     still could not run. I could not count the times I uninstalled
>     (including files left behind) and reinstalled. (clean reinstall
>     from the web). Every time, same error.
>
>     One person from the group contacted me personally and virtually
>     held my hand through several processes. First, a scan revealed
>     that there was indeed a plethera of problems on my 9-month-old
>     Dell, seemingly resulting from a corrupted Windows update(s).
>     Things had been snow-balling and log-jamming since then. Our first
>     choice was to do a system restore back to a point where all was
>     working well. Unfortunately, my system gave us no options for a
>     restore point that went back far enough. So, then, my Good
>     Samaritan directed me to uninstall all the Windows updates from
>     2013, one at a time. After turning off Auto Updates and completing
>     that process (took me almost all day today), another scan revealed
>     some remaining corruption. However, for the first time since all
>     this mess started, my Legacy program is now running. I could not
>     believe it when it actually did NOT return the error. I'm trying
>     not to worry too much about the remaining corruption that shows up
>     during a scan, because everything seems to be working beautifully
>     right now. Anything else is going to be dumped in the lap of Dell.
>     (And I did remember to turn back on the Windows updates, and so
>     I'm all updated with good files now.)
>
>     So, thanks so much for all the wonderful help. And thanks for all
>     the mentions of sympathy regarding my mother's final days. I have
>     been making many trips to my sister's home, and will be on the
>     road again tomorrow. We know she has days at most, maybe only
>     hours now. She is prepared and is ready to go, though it is always
>     difficult to say goodbye, of course.
>
>     I can now answer genealogy questions from family members whom I
>     will see in the next few days.
>
>     Thanks again, all,
>
>     Barbara
>
>
>
>
>     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
>
>
>
>
> --
> Eliz
> Not Today and Not without a Fight
> (Anon)
>
> For all that has been, thanks.
> For all that will be, yes.
>     (Dag Hammarskjold)
>
>
> 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




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

Reply via email to