Re: [LegacyUG] Problem with V8.0.0.602 and V8.0.0.604
Chris, On your initial problem. Something is going on with your computer. Legacy 8 runs fine under Windows 10 without any compatibility settings. Without finding out what that is, you'll likely have problems with Legacy 9 as well. On not upgrading to Legacy 9 until the problems are all sorted. Legacy 9 already has less problems than Legacy 8 in the areas they share. There are some problems in new features but most people aren't encountering them just as most people aren't encountering the many bugs in Legacy 8, some of which have been fixed in 9 now but not in 8. Wanting a transfer of data between programs and online trees etc without loss is just not going to happen. Different programs and different online trees have differing features - that's why they exist. It's the differences that lead people to prefer one over the other. It's remarkable that the old Gedcom standard with a few tweaks does such a good job but even from Legacy to the same version of Legacy via Gedcom loses a few things, most visible is that SourceWriter sources are converted to Basic. Cathy Legacy Tester Chris Hill <mailto:chris.hill.11he...@gmail.com> Tuesday, 11 July 2017 3:59 AM Having been a committee member for the design and implementation of the EDI standards in Europe, in the mid 1980-1990s, I am well aware of the issues of getting a standard format. We ended up with a lot of optional records that most people ignored or did not need, and equally with the issue of a business decided that he did want them and insisted that you provide them. Hopefully, we will get to a basic structure which everyone will support and with only a few, if any, non-mandatory fields. Regards Chris *From:*LegacyUserGroup [mailto:legacyusergroup-boun...@legacyusers.com] *On Behalf Of *Michael Feldman *Sent:* 10 July 2017 20:22 *To:* Legacy User Group <legacyusergroup@legacyusers.com> *Subject:* Re: [LegacyUG] Problem with V8.0.0.602 and V8.0.0.604 Hi all, Chris Hill wrote: [snip] A worthy ideal overall, but "no exceptions" is unlikely to happen in practice. The computing world is filled with technical standards of one kind or another; anyone who works in, or near, a standards committee know this is like herding cats. And even after a standard is adopted, some cats will wander off in their own direction anyway (which is why standards are always revised periodically, to bring exceptions into the fold, then the process starts again). It's human nature (and, often, business nature as well). [ASIDE] The evolution of character-set standards is a good example. I think the discussion here of the em-dash problems is a manifestation of this. "Back in the day" (the fifties), a character was represented as six bits. Of course this limited the total number of characters to 64, which is why the early computers printed everything as UPPER CASE -- no room for lower case in the character set. In recent decades, we've gone to 7 bits, 8 bits, and beyond, to try to accommodate all countries' alphabets and now, even, emojis. Google "number of bits in an emoji" for character-set fun and games. [back to GEDCOM] It'll be interesting to see what FHISO comes up with... Just my $0.02.:-) Mike Feldman Michael Feldman <mailto:mfeld...@gwu.edu> Tuesday, 11 July 2017 3:22 AM Hi all, Chris Hill wrote: [snip] A worthy ideal overall, but "no exceptions" is unlikely to happen in practice. The computing world is filled with technical standards of one kind or another; anyone who works in, or near, a standards committee know this is like herding cats. And even after a standard is adopted, some cats will wander off in their own direction anyway (which is why standards are always revised periodically, to bring exceptions into the fold, then the process starts again). It's human nature (and, often, business nature as well). [ASIDE] The evolution of character-set standards is a good example. I think the discussion here of the em-dash problems is a manifestation of this. "Back in the day" (the fifties), a character was represented as six bits. Of course this limited the total number of characters to 64, which is why the early computers printed everything as UPPER CASE -- no room for lower case in the character set. In recent decades, we've gone to 7 bits, 8 bits, and beyond, to try to accommodate all countries' alphabets and now, even, emojis. Google "number of bits in an emoji" for character-set fun and games. [back to GEDCOM] It'll be interesting to see what FHISO comes up with... Just my $0.02.:-) Mike Feldman Chris Hill <mailto:chris.hill.11he...@gmail.com> Tuesday, 11 July 2017 2:54 AM In theory, if everyone assumes that the GEDCOM is a standardised format. Unfortunately, it is not, and was released in 1996 for the 5.5.1 version. There was a XML version designed in 2002 which never went anywhere. Look at http
Re: [LegacyUG] Problem with V8.0.0.602 and V8.0.0.604
Hi all, Chris Hill wrote: [snip] The Family History Information Standards Organisation (FHISO) was started in 2012 and has just released its very first draft standards for public comment, at the end of June. Something that I need to review. Hopefully, if we can get everyone supporting a single standard, with no exceptions, we will then be able to transfer data with no loss. A worthy ideal overall, but "no exceptions" is unlikely to happen in practice. The computing world is filled with technical standards of one kind or another; anyone who works in, or near, a standards committee know this is like herding cats. And even after a standard is adopted, some cats will wander off in their own direction anyway (which is why standards are always revised periodically, to bring exceptions into the fold, then the process starts again). It's human nature (and, often, business nature as well). [ASIDE] The evolution of character-set standards is a good example. I think the discussion here of the em-dash problems is a manifestation of this. "Back in the day" (the fifties), a character was represented as six bits. Of course this limited the total number of characters to 64, which is why the early computers printed everything as UPPER CASE -- no room for lower case in the character set. In recent decades, we've gone to 7 bits, 8 bits, and beyond, to try to accommodate all countries' alphabets and now, even, emojis. Google "number of bits in an emoji" for character-set fun and games. [back to GEDCOM] It'll be interesting to see what FHISO comes up with... Just my $0.02.:-) Mike Feldman -- LegacyUserGroup mailing list LegacyUserGroup@legacyusers.com To manage your subscription and unsubscribe http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com Archives at: http://www.mail-archive.com/legacyusergroup@legacyusers.com/
Re: [LegacyUG] Problem with V8.0.0.602 and V8.0.0.604
I agree with you. Some of us are happy with 8 and shouldn't have to change. And yes I agree they are adding to many dodads to the program, in my opinion it makes it more unstable. Yes I have issues with 8. Purchased 9 but delayed installing it for same reason. What is the rush! Sent from my iPad > On Jul 10, 2017, at 11:08 AM, Gene Wheeler <bridge...@gmail.com> wrote: > > That just seems to introduce another set of issues! I've purchased v.9, but > am holding off using it until the problems all get cleared up. I think LFT is > maybe getting too complicated to design and use all the new features. IMHO, > they should continue to support v.8 for those of us who would rather have a > solid, reliable tool and still offer v.9 to those who have more patience to > deal with it's issues and can't wait to use the new features. > > Can 8 and 9 run side-by-side on the same machine? If so, one could use v.8 as > the preferred version, and still run v.9 to learn its intricacies before > adopting it to replace v.8. > > Gene > >> On Mon, Jul 10, 2017 at 10:47 AM, ROBERT A SUDDATH <rasudd...@msn.com> wrote: >> you nee dto upgrade to latest versions!! >> >> >> Bob Suddath >> rasudd...@msn.com >> denversuddaths.homestead.com >> >> >> From: LegacyUserGroup <legacyusergroup-boun...@legacyusers.com> on behalf of >> Chris Hill <chris.hill.11he...@gmail.com> >> Sent: Monday, July 10, 2017 8:35 AM >> To: LegacyUserGroup@LegacyUsers.com >> Subject: [LegacyUG] Problem with V8.0.0.602 and V8.0.0.604 >> >> This is for information. >> >> I am running Legacy 8 on a Win 7 64bit Ultimate, fully updated by Microsoft >> and running the Symantec Norton Anti-Virus. >> >> About a month ago it got updated to V8.0.0.602. That then likes to display a >> prompt about upgrading to Legacy 9. Hit Close to ship out and you get a >> Run-Tine Error 75 message and the program closes. Eventually resolved that >> as a program combability issue, having raised it as an formal issue and got >> pointed at the collection of possible causes. >> >> I have now been updated to V8.0.0.604 and the same issue occurred. This time >> I completely removed and reinstalled, and still got the same issue. Ran the >> program compatibility checks and Windows decided that it needed to be in >> mode Windows XP (SP2) and it now works. >> >> But Legacy 8 came out in 2013, so it should have been compatible to Win >> Vista, Win 7, Win 8 and Win 8.1. To my knowledge, it is only the .602 and >> .604 versions that have this issue – certainly I have seen no issues with >> previous versions. So what have Legacy developers changed for these versions >> to make then incompatible or have they forgotten to tell the installer to >> make them needing to be in Win XP SP2. The other alternative is that I am up >> to date on Microsoft .NET to level 4.6, and have 4.7 waiting for >> installation. >> >> Regards >> >> Chris >> >> >> >> -- >> >> LegacyUserGroup mailing list >> LegacyUserGroup@legacyusers.com >> To manage your subscription and unsubscribe >> http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com >> Archives at: >> http://www.mail-archive.com/legacyusergroup@legacyusers.com/ >> > > -- > > LegacyUserGroup mailing list > LegacyUserGroup@legacyusers.com > To manage your subscription and unsubscribe > http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com > Archives at: > http://www.mail-archive.com/legacyusergroup@legacyusers.com/ -- LegacyUserGroup mailing list LegacyUserGroup@legacyusers.com To manage your subscription and unsubscribe http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com Archives at: http://www.mail-archive.com/legacyusergroup@legacyusers.com/
Re: [LegacyUG] Problem with V8.0.0.602 and V8.0.0.604
Chris, I thought that the GEDCOM format was supposed to help transfer your data from one program to another with the basic information traveling. I moved from Family Roots, to Personal Ancestral File, to Ancestral Quest with no problems in the past. Leonard - __ ___ Leonard J. McCown, Irving, Texas -- McCown Family History 217 West 14th Street, Irving, Texas 75060-5903 972-254-7952 <mailto:leon...@mccown.org> leon...@mccown.org -- <http://www.mccown.org> http://www.mccown.org People will not look forward to posterity who never look backward to their ancestors. -- Edmund Burke, 1790 __ ___ From: LegacyUserGroup [mailto:legacyusergroup-boun...@legacyusers.com] On Behalf Of Chris Hill Sent: Monday, July 10, 2017 11:18 AM To: 'Legacy User Group' <legacyusergroup@legacyusers.com> Subject: Re: [LegacyUG] Problem with V8.0.0.602 and V8.0.0.604 That is a different question. I think I would find the hashtags useful, and possibly a couple of the other additions, but most of them are, to me, pointless. The one thing that I do want, and will never get, is a standardised interface API between the different genealogy programs and the online systems, so that we can accurately and easily transfer information with no loss. Regards Chris -- LegacyUserGroup mailing list LegacyUserGroup@legacyusers.com To manage your subscription and unsubscribe http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com Archives at: http://www.mail-archive.com/legacyusergroup@legacyusers.com/
Re: [LegacyUG] Problem with V8.0.0.602 and V8.0.0.604
Hi Gene, If you hold off using v9 until ALL the issues are resolved then you may never get to use it. I have been using v9 since the day it was released and have had no more issues than with v8. Legacy has been quick to respond to any problems and, I’m sure, will continue to do so. You can run v8 & v9 side by side. V9 overwrites the v8 files (without warning) so make a copy of all the v8 files first, install v9, then rename the v8 files. V9 is not compatible with v8 so running them side-by-side is really not practical as they will two separate, non-compatible, databases. I kept the option to run v8 as I still help others who haven’t (didn’t) upgrade but I have never had to go back to it. Just make the switch to v9. Bob Austen From: LegacyUserGroup [mailto:legacyusergroup-boun...@legacyusers.com] On Behalf Of Gene Wheeler Sent: Monday, July 10, 2017 9:09 AM To: Legacy User Group Subject: Re: [LegacyUG] Problem with V8.0.0.602 and V8.0.0.604 That just seems to introduce another set of issues! I've purchased v.9, but am holding off using it until the problems all get cleared up. I think LFT is maybe getting too complicated to design and use all the new features. IMHO, they should continue to support v.8 for those of us who would rather have a solid, reliable tool and still offer v.9 to those who have more patience to deal with it's issues and can't wait to use the new features. Can 8 and 9 run side-by-side on the same machine? If so, one could use v.8 as the preferred version, and still run v.9 to learn its intricacies before adopting it to replace v.8. Gene On Mon, Jul 10, 2017 at 10:47 AM, ROBERT A SUDDATH <rasudd...@msn.com> wrote: you nee dto upgrade to latest versions!! Bob Suddath rasudd...@msn.com denversuddaths.homestead.com _ From: LegacyUserGroup <legacyusergroup-boun...@legacyusers.com> on behalf of Chris Hill <chris.hill.11he...@gmail.com> Sent: Monday, July 10, 2017 8:35 AM To: LegacyUserGroup@LegacyUsers.com Subject: [LegacyUG] Problem with V8.0.0.602 and V8.0.0.604 This is for information. I am running Legacy 8 on a Win 7 64bit Ultimate, fully updated by Microsoft and running the Symantec Norton Anti-Virus. About a month ago it got updated to V8.0.0.602. That then likes to display a prompt about upgrading to Legacy 9. Hit Close to ship out and you get a Run-Tine Error 75 message and the program closes. Eventually resolved that as a program combability issue, having raised it as an formal issue and got pointed at the collection of possible causes. I have now been updated to V8.0.0.604 and the same issue occurred. This time I completely removed and reinstalled, and still got the same issue. Ran the program compatibility checks and Windows decided that it needed to be in mode Windows XP (SP2) and it now works. But Legacy 8 came out in 2013, so it should have been compatible to Win Vista, Win 7, Win 8 and Win 8.1. To my knowledge, it is only the .602 and .604 versions that have this issue – certainly I have seen no issues with previous versions. So what have Legacy developers changed for these versions to make then incompatible or have they forgotten to tell the installer to make them needing to be in Win XP SP2. The other alternative is that I am up to date on Microsoft .NET to level 4.6, and have 4.7 waiting for installation. Regards Chris -- LegacyUserGroup mailing list LegacyUserGroup@legacyusers.com To manage your subscription and unsubscribe http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com Archives at: http://www.mail-archive.com/legacyusergroup@legacyusers.com/ -- LegacyUserGroup mailing list LegacyUserGroup@legacyusers.com To manage your subscription and unsubscribe http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com Archives at: http://www.mail-archive.com/legacyusergroup@legacyusers.com/
Re: [LegacyUG] Problem with V8.0.0.602 and V8.0.0.604
That is a different question. I think I would find the hashtags useful, and possibly a couple of the other additions, but most of them are, to me, pointless. The one thing that I do want, and will never get, is a standardised interface API between the different genealogy programs and the online systems, so that we can accurately and easily transfer information with no loss. Regards Chris From: LegacyUserGroup [mailto:legacyusergroup-boun...@legacyusers.com] On Behalf Of ROBERT A SUDDATH Sent: 10 July 2017 16:47 To: Legacy User Group <LegacyUserGroup@LegacyUsers.com> Subject: Re: [LegacyUG] Problem with V8.0.0.602 and V8.0.0.604 you nee dto upgrade to latest versions!! Bob Suddath rasudd...@msn.com <mailto:rasudd...@msn.com> denversuddaths.homestead.com _ From: LegacyUserGroup <legacyusergroup-boun...@legacyusers.com <mailto:legacyusergroup-boun...@legacyusers.com> > on behalf of Chris Hill <chris.hill.11he...@gmail.com <mailto:chris.hill.11he...@gmail.com> > Sent: Monday, July 10, 2017 8:35 AM To: LegacyUserGroup@LegacyUsers.com <mailto:LegacyUserGroup@LegacyUsers.com> Subject: [LegacyUG] Problem with V8.0.0.602 and V8.0.0.604 This is for information. I am running Legacy 8 on a Win 7 64bit Ultimate, fully updated by Microsoft and running the Symantec Norton Anti-Virus. About a month ago it got updated to V8.0.0.602. That then likes to display a prompt about upgrading to Legacy 9. Hit Close to ship out and you get a Run-Tine Error 75 message and the program closes. Eventually resolved that as a program combability issue, having raised it as an formal issue and got pointed at the collection of possible causes. I have now been updated to V8.0.0.604 and the same issue occurred. This time I completely removed and reinstalled, and still got the same issue. Ran the program compatibility checks and Windows decided that it needed to be in mode Windows XP (SP2) and it now works. But Legacy 8 came out in 2013, so it should have been compatible to Win Vista, Win 7, Win 8 and Win 8.1. To my knowledge, it is only the .602 and .604 versions that have this issue - certainly I have seen no issues with previous versions. So what have Legacy developers changed for these versions to make then incompatible or have they forgotten to tell the installer to make them needing to be in Win XP SP2. The other alternative is that I am up to date on Microsoft .NET to level 4.6, and have 4.7 waiting for installation. Regards Chris -- LegacyUserGroup mailing list LegacyUserGroup@legacyusers.com To manage your subscription and unsubscribe http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com Archives at: http://www.mail-archive.com/legacyusergroup@legacyusers.com/
Re: [LegacyUG] Problem with V8.0.0.602 and V8.0.0.604
That just seems to introduce another set of issues! I've purchased v.9, but am holding off using it until the problems all get cleared up. I think LFT is maybe getting too complicated to design and use all the new features. IMHO, they should continue to support v.8 for those of us who would rather have a solid, reliable tool and still offer v.9 to those who have more patience to deal with it's issues and can't wait to use the new features. Can 8 and 9 run side-by-side on the same machine? If so, one could use v.8 as the preferred version, and still run v.9 to learn its intricacies before adopting it to replace v.8. Gene On Mon, Jul 10, 2017 at 10:47 AM, ROBERT A SUDDATH <rasudd...@msn.com> wrote: > you nee dto upgrade to latest versions!! > > > Bob Suddath > rasudd...@msn.com > denversuddaths.homestead.com > > > -- > *From:* LegacyUserGroup <legacyusergroup-boun...@legacyusers.com> on > behalf of Chris Hill <chris.hill.11he...@gmail.com> > *Sent:* Monday, July 10, 2017 8:35 AM > *To:* LegacyUserGroup@LegacyUsers.com > *Subject:* [LegacyUG] Problem with V8.0.0.602 and V8.0.0.604 > > > This is for information. > > > > I am running Legacy 8 on a Win 7 64bit Ultimate, fully updated by > Microsoft and running the Symantec Norton Anti-Virus. > > > > About a month ago it got updated to V8.0.0.602. That then likes to display > a prompt about upgrading to Legacy 9. Hit Close to ship out and you get a > *Run-Tine > Error 75* message and the program closes. Eventually resolved that as a > program combability issue, having raised it as an formal issue and got > pointed at the collection of possible causes. > > > > I have now been updated to V8.0.0.604 and the same issue occurred. This > time I completely removed and reinstalled, and still got the same issue. > Ran the program compatibility checks and Windows decided that it needed to > be in mode *Windows XP (SP2)* and it now works. > > > > But Legacy 8 came out in 2013, so it should have been compatible to Win > Vista, Win 7, Win 8 and Win 8.1. To my knowledge, it is only the .602 and > .604 versions that have this issue – certainly I have seen no issues with > previous versions. So what have Legacy developers changed for these > versions to make then incompatible or have they forgotten to tell the > installer to make them needing to be in Win XP SP2. The other alternative > is that I am up to date on Microsoft .NET to level 4.6, and have 4.7 > waiting for installation. > > > > Regards > > > > Chris > > > > > > -- > > LegacyUserGroup mailing list > LegacyUserGroup@legacyusers.com > To manage your subscription and unsubscribe http://legacyusers.com/ > mailman/listinfo/legacyusergroup_legacyusers.com > Archives at: > http://www.mail-archive.com/legacyusergroup@legacyusers.com/ > > -- LegacyUserGroup mailing list LegacyUserGroup@legacyusers.com To manage your subscription and unsubscribe http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com Archives at: http://www.mail-archive.com/legacyusergroup@legacyusers.com/
Re: [LegacyUG] Problem with V8.0.0.602 and V8.0.0.604
you nee dto upgrade to latest versions!! Bob Suddath rasudd...@msn.com denversuddaths.homestead.com From: LegacyUserGroup <legacyusergroup-boun...@legacyusers.com> on behalf of Chris Hill <chris.hill.11he...@gmail.com> Sent: Monday, July 10, 2017 8:35 AM To: LegacyUserGroup@LegacyUsers.com Subject: [LegacyUG] Problem with V8.0.0.602 and V8.0.0.604 This is for information. I am running Legacy 8 on a Win 7 64bit Ultimate, fully updated by Microsoft and running the Symantec Norton Anti-Virus. About a month ago it got updated to V8.0.0.602. That then likes to display a prompt about upgrading to Legacy 9. Hit Close to ship out and you get a Run-Tine Error 75 message and the program closes. Eventually resolved that as a program combability issue, having raised it as an formal issue and got pointed at the collection of possible causes. I have now been updated to V8.0.0.604 and the same issue occurred. This time I completely removed and reinstalled, and still got the same issue. Ran the program compatibility checks and Windows decided that it needed to be in mode Windows XP (SP2) and it now works. But Legacy 8 came out in 2013, so it should have been compatible to Win Vista, Win 7, Win 8 and Win 8.1. To my knowledge, it is only the .602 and .604 versions that have this issue – certainly I have seen no issues with previous versions. So what have Legacy developers changed for these versions to make then incompatible or have they forgotten to tell the installer to make them needing to be in Win XP SP2. The other alternative is that I am up to date on Microsoft .NET to level 4.6, and have 4.7 waiting for installation. Regards Chris -- LegacyUserGroup mailing list LegacyUserGroup@legacyusers.com To manage your subscription and unsubscribe http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com Archives at: http://www.mail-archive.com/legacyusergroup@legacyusers.com/
[LegacyUG] Problem with V8.0.0.602 and V8.0.0.604
This is for information. I am running Legacy 8 on a Win 7 64bit Ultimate, fully updated by Microsoft and running the Symantec Norton Anti-Virus. About a month ago it got updated to V8.0.0.602. That then likes to display a prompt about upgrading to Legacy 9. Hit Close to ship out and you get a Run-Tine Error 75 message and the program closes. Eventually resolved that as a program combability issue, having raised it as an formal issue and got pointed at the collection of possible causes. I have now been updated to V8.0.0.604 and the same issue occurred. This time I completely removed and reinstalled, and still got the same issue. Ran the program compatibility checks and Windows decided that it needed to be in mode Windows XP (SP2) and it now works. But Legacy 8 came out in 2013, so it should have been compatible to Win Vista, Win 7, Win 8 and Win 8.1. To my knowledge, it is only the .602 and .604 versions that have this issue - certainly I have seen no issues with previous versions. So what have Legacy developers changed for these versions to make then incompatible or have they forgotten to tell the installer to make them needing to be in Win XP SP2. The other alternative is that I am up to date on Microsoft .NET to level 4.6, and have 4.7 waiting for installation. Regards Chris -- LegacyUserGroup mailing list LegacyUserGroup@legacyusers.com To manage your subscription and unsubscribe http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com Archives at: http://www.mail-archive.com/legacyusergroup@legacyusers.com/
