Yes, I can confirm this problem. th. Jens Fleinert wrote: > zip backup > Have mentioned this b4, have meantime tried every trick in my EDB > vocabolary, same result. > > I rename old zip file, backup works fine first and 2nd time, but 3rd > time onwards I get the error 160..... > Rgds > Jens Fleinert

Carol Miller wrote: > > I have been installing CFTW upgrades over the top of one another since the > original version 1. I have never had a problem. Did not have a problem > with 2.29X either. It installed and runs great. I have never tried > uninstalling the old version first. Maybe thats the trouble. > > Carol Miller > -- Thats the way I have been upgrading also and have had no trouble either Roy...

I also have not had any problem with the upgrage to 2.29x.. A thought that sites are being used for the download ?? Roy

>I rename old zip file, backup works fine first and 2nd time, but 3rd >time onwards I get the error 160. Further there is no way to stop the >exit window, but accept that no backup is made. Add a "cancel" option, >then at leasst I could provide a new alternative name to the backup.zip >file. I hopefully can find this bug. Have recieved some details from another user and when I get time will try to hunt it down. >Photo file names >Earlier I also mentioned the problem with the photo files. They are >created in various formats, but all under Windows, why do you then have >to change the file reading format and restricting it to MSdos limits. I know I am behind time. Trying to catch up, but not an easy fix. Long file names will be allowed in next major Ver 3. release but still a long ways away. Ira ---------------------------------------------------------- Ira J. Lund Cumberland Family Software, Clarksville, Tennessee, USA Genealogy Software for Beginners and Professionals E-mail: ira.lund@cf-software.com http://www.cf-software.com

Yes, I probably should have changed htis with each version. It was one of those little things that was easy to overlook. Will see if I can change this. Ira At 03:35 PM 2/28/98 +0000, you wrote: >The first lines of a CFTW gedcom export file look like this for all >versions from 2.00 to 2.29: > >0 HEAD >1 SOUR CFTREE >2 VERS CFTREE 2.0 Windows > >Will it not be better to write the exact version number - for example: > >"2 VERS CFTREE 2.29 Windows"? > >There are a lot of changes made from version 2.00 to 2.29 - and some >of them certainly affects the gedcom export file - the date change in >2.08 for example. Therefore it might be of some importance for the >receiver of a gedcom file to know exactly which version made the file. >Of course it is easy to fix this line in a text editor just after you >have made the file - but a lot of people are not familiar with that - >and might experience problems with opening large files.That is the >reason the version line is in the gedcom file - isn't it? > >Sigurd Eliassen >Norway > ---------------------------------------------------------- Ira J. Lund Cumberland Family Software, Clarksville, Tennessee, USA Genealogy Software for Beginners and Professionals E-mail: ira.lund@cf-software.com http://www.cf-software.com

Hello Ira zip backup Have mentioned this b4, have meantime tried every trick in my EDB vocabolary, same result. I rename old zip file, backup works fine first and 2nd time, but 3rd time onwards I get the error 160. Further there is no way to stop the exit window, but accept that no backup is made. Add a "cancel" option, then at leasst I could provide a new alternative name to the backup.zip file. Photo file names Earlier I also mentioned the problem with the photo files. They are created in various formats, but all under Windows, why do you then have to change the file reading format and restricting it to MSdos limits. It creates a lot of "name cum number files" and apparently your system also have difficulty in identifying same properly, some were suddenly mixed ?? - any chance of chagnging this into windows file format enabling long file names. Rgds Jens Fleinert

Ira, you have my full support on this subject! Reidar Stromsoe Norway -----Original Message----- From: Ira J. Lund <ira.lund@cf-software.com> To: CFT-WIN-L@rootsweb.com <CFT-WIN-L@rootsweb.com> Date: 28. februar 1998 16:11 Subject: Re: Dates >At 08:39 AM 2/27/98 -0500, you wrote: >>Ever since the date format was changed in 2.08 I have tried in vain to get >>a revision which would solve the problems indicated by Michael and David >>and my own use of dates, too. > >Don't mean to ignore everyone on this issue, but per my previous note I'm >afraid that I am going to go the direction indicated for Ver 3. There are >several incompatible issues here. First we need the date field to be >"calculatable" - a true date that can be used to calculate from. In Ver 3 >(UCC date) the date is so well formatted that it can even re-order dates >properly even when they are in different calendar systems! This IS the >direction I am going. I feel this to be so important that I am afraid I >have turned a deaf ear to your requests. Anything that is NOT a standard >type date should go into the notes...

The first lines of a CFTW gedcom export file look like this for all versions from 2.00 to 2.29: 0 HEAD 1 SOUR CFTREE 2 VERS CFTREE 2.0 Windows Will it not be better to write the exact version number - for example: "2 VERS CFTREE 2.29 Windows"? There are a lot of changes made from version 2.00 to 2.29 - and some of them certainly affects the gedcom export file - the date change in 2.08 for example. Therefore it might be of some importance for the receiver of a gedcom file to know exactly which version made the file. Of course it is easy to fix this line in a text editor just after you have made the file - but a lot of people are not familiar with that - and might experience problems with opening large files.That is the reason the version line is in the gedcom file - isn't it? Sigurd Eliassen Norway

At 08:39 AM 2/27/98 -0500, you wrote: >Ever since the date format was changed in 2.08 I have tried in vain to get >a revision which would solve the problems indicated by Michael and David >and my own use of dates, too. Don't mean to ignore everyone on this issue, but per my previous note I'm afraid that I am going to go the direction indicated for Ver 3. There are several incompatible issues here. First we need the date field to be "calculatable" - a true date that can be used to calculate from. In Ver 3 (UCC date) the date is so well formatted that it can even re-order dates properly even when they are in different calendar systems! This IS the direction I am going. I feel this to be so important that I am afraid I have turned a deaf ear to your requests. Anything that is NOT a standard type date should go into the notes... Or another idea I might do in Ver 3 is add a second field: non-standard date - which would be a free-format non-calcualtable field that would allow entry of anything a user would want to enter. But such a field would never be usable for sorting date orders, or other date calculatons, etc. Ira ---------------------------------------------------------- Ira J. Lund Cumberland Family Software, Clarksville, Tennessee, USA Genealogy Software for Beginners and Professionals E-mail: ira.lund@cf-software.com http://www.cf-software.com

Well, I put "spring of 1991" back before a forced the date to be a fixed tpype format. I would not do that today. I would have put 1991 in the date and then the note might say it was in the spring. In other words, I am trying to force all to put proper dates in the date field. Ver 3 will be even stricter: the date MUST be a valid date (like the UCC accepts) as internally the date will be stored as a series of numbers - day number, month number, year number, cycle number, etc. Ira At 06:34 PM 2/27/98 +1100, you wrote: > >G'day Ira et al, > >I am seem to have a minor annoyance in trying to use "non-standard" dates in >events. > >Here is a quote from the help file on "Event Editor - Standard":- > >Business Startup: Ira Johan Lund started a business in the spring of 1991 at >Clarksville, Montgomery, Tennessee called Cumberland Family Software. > >I have examined the SAMPLE database and this is what appears from the "same" >(?) event:- > >Ira Johan LUND started a business 1991 at Clarksville, Montgomery, Tennessee >called Cumberland Family Software. > >I tried to modify the date used from "1991" to "in the spring of 1991" but >the entry is too long so I created my own "non-standard" date - "late >1950s" - here is the result:- > >Michael CALDER late 1950's AD started playing lawn bowls. > >Not worrying about the grammar it is the "AD" that is the problem. Any >"word" attached to a date in the "date window" will trigger the addition of >AD (or you can choose BC). > >Can we have a "blank" option? so that we can have dates like "early 1856" >"mid 1950s" or even a bigger field to add "in the spring of 1991" <VBG>? > >HURU Mike > ---------------------------------------------------------- Ira J. Lund Cumberland Family Software, Clarksville, Tennessee, USA Genealogy Software for Beginners and Professionals E-mail: ira.lund@cf-software.com http://www.cf-software.com

Ira and all, I too would be interested in a different display (especially without AD, because -well let's be realistc- who can trace his roots until BC?). Wouldn't it be possible to display non-standard dates exactly as they have been entered? If this is not possible for version 2, this would be a wish for version 3. Regards, Ren Hasekamp. ---------- > Van: David Cushing <dcushing@fox.nstn.ca> > Aan: CFT-WIN-L@rootsweb.com > Onderwerp: (Fwd) Dates > Datum: vrijdag 27 februari 1998 13:07 > > Hello Ira and others, I too have been considering requesting more > control of the AD addition to the date with text. I have some user defined > events for which I use the date space to enter a an age, ie 34yrs 6 mo, > and this ends up with AD appended which looks out of place. Therefore I > too request the ability to turn off the BC/AD designation, BUT not at the > expense of loosing the larger screen. > > From: "Michael CALDER" <mcalder@tpgi.com.au> > Subject: Dates > Date: Fri, 27 Feb 1998 18:34:52 +1100 > > G'day Ira et al, > > I am seem to have a minor annoyance in trying to use "non-standard" dates in > events. > > Not worrying about the grammar it is the "AD" that is the problem. Any > "word" attached to a date in the "date window" will trigger the addition of > AD (or you can choose BC). > > Can we have a "blank" option? so that we can have dates like "early 1856" > "mid 1950s" or even a bigger field to add "in the spring of 1991" <VBG>? > > HURU Mike > > >

Ever since the date format was changed in 2.08 I have tried in vain to get a revision which would solve the problems indicated by Michael and David and my own use of dates, too. What I wanted was User-defined Date Modifiers, just as we have User-defined Events. The modifiers could be anything (such as "decade of," "early," "mid-," "late," "in the spring of," and my favorites (which I used prior to 2.08), such as "part of," "most of," "perhaps," "not before," "not after," and especially "at least," as in "John DOE lived at least 1860 at ..." For date calculation purposes I could accept that the modifiers would be ignored by CFTW. I was told to stick with the six modifiers provided (normal, about, before, after, from, between) because they were the only GEDCOM standards, yet we users are allowed to add and modify Standard Events. Delighted, therefore, to see someone else bringing up the subject of date formatting. At 08:07 AM 2/27/98 -0400, you wrote: >Hello Ira and others, I too have been considering requesting more >control of the AD addition to the date with text. I have some user defined >events for which I use the date space to enter an age, ie 34yrs 6 mo, >and this ends up with AD appended which looks out of place. Therefore I >too request the ability to turn off the BC/AD designation, BUT not at the >expense of losing the larger screen. > >From: "Michael CALDER" <mcalder@tpgi.com.au> >Subject: Dates >Date: Fri, 27 Feb 1998 18:34:52 +1100 > >G'day Ira et al, > >I am seem to have a minor annoyance in trying to use "non-standard" dates in >events. > >Not worrying about the grammar it is the "AD" that is the problem. Any >"word" attached to a date in the "date window" will trigger the addition of >AD (or you can choose BC). > >Can we have a "blank" option? so that we can have dates like "early 1856" >"mid 1950s" or even a bigger field to add "in the spring of 1991" <VBG>? > >HURU Mike > > > > ______________________________ | | | EMQUAD International, Ltd. | | P.O. Box 60 | | Great Neck, NY 11022 | | - | | emquad@worldnet.att.net | | http://home.att.net/~emquad | | - | | Consulting Division | | Publishing Division | |______________________________|

Hello Ira and others, I too have been considering requesting more control of the AD addition to the date with text. I have some user defined events for which I use the date space to enter a an age, ie 34yrs 6 mo, and this ends up with AD appended which looks out of place. Therefore I too request the ability to turn off the BC/AD designation, BUT not at the expense of loosing the larger screen. From: "Michael CALDER" <mcalder@tpgi.com.au> Subject: Dates Date: Fri, 27 Feb 1998 18:34:52 +1100 G'day Ira et al, I am seem to have a minor annoyance in trying to use "non-standard" dates in events. Not worrying about the grammar it is the "AD" that is the problem. Any "word" attached to a date in the "date window" will trigger the addition of AD (or you can choose BC). Can we have a "blank" option? so that we can have dates like "early 1856" "mid 1950s" or even a bigger field to add "in the spring of 1991" <VBG>? HURU Mike

G'day Ira et al, I am seem to have a minor annoyance in trying to use "non-standard" dates in events. Here is a quote from the help file on "Event Editor - Standard":- Business Startup: Ira Johan Lund started a business in the spring of 1991 at Clarksville, Montgomery, Tennessee called Cumberland Family Software. I have examined the SAMPLE database and this is what appears from the "same" (?) event:- Ira Johan LUND started a business 1991 at Clarksville, Montgomery, Tennessee called Cumberland Family Software. I tried to modify the date used from "1991" to "in the spring of 1991" but the entry is too long so I created my own "non-standard" date - "late 1950s" - here is the result:- Michael CALDER late 1950's AD started playing lawn bowls. Not worrying about the grammar it is the "AD" that is the problem. Any "word" attached to a date in the "date window" will trigger the addition of AD (or you can choose BC). Can we have a "blank" option? so that we can have dates like "early 1856" "mid 1950s" or even a bigger field to add "in the spring of 1991" <VBG>? HURU Mike

>That is curious. The Cleansweep program also archived >c:\windows\Hsun32.exe, which >seems to be part of an uninstall program. i.e. clicking on this brings up a >menu that >says uninstall must be run with parameters. It may be yours since it has a >garbage >can icon like the one that appeared in the little icon box on installation. Yes, it is mine. But I didn't realize that the install placed it in c:\windows. The uninstall is handled by the install program. Ira ---------------------------------------------------------- Ira J. Lund Cumberland Family Software, Clarksville, Tennessee, USA Genealogy Software for Beginners and Professionals E-mail: ira.lund@cf-software.com http://www.cf-software.com

At 08.18 25-02-98 -0500, Joseph Cain wrote: > ... Both of the backups were flawed in that they would >not unzip using Norton's unzip program. This is nothing new in my opinion. My Norton Commander has never been able to open the ZIP files made by CFTW backup. PKUNZIP has always been able to unpack them correctly. Erik

Good point, but those that had damaged or incorrectly zipped individ.tps files were of the 8.3 variety, whereas I had a couple that unzipped ok which had longer than 8 character names. I routinely use Windows Commander or Norton's zip/unzip functions which allow both the names and extensions to be longer than 8.3. The latter is via Norton's file manager and a right click on a file viewed by Windows explorer will also allow Norton's zip/unzip as an option. I rarely use Windows Explorer though, mostly Windows Commander with its two panel display. From: "George W. Durman" <sgtgeorg@concentric.net> At 01:56 AM 2/26/1998 -0500, you wrote: >If I may step in here.....a suggestion for ALL users who download .ZIP >files from the Internet or Web is to use an UNZIP program that will >preserve Win95 type file names. >I don't know if this has anything to do with unzipping the CFT files, but it >is worth exploring.

If I may step in here.....a suggestion for ALL users who download .ZIP files from the Internet or Web is to use an UNZIP program that will preserve Win95 type file names. That is, MOST ZIP/UNZIP programs will only preserve the typical 8.3 type filenames, e.g. abcdefgh.xxx. Many .ZIP files now downloaded contain expanded file names that MUST be preserved. As an example, I recently downloaded a Desktop Theme program and sever "themes". Using older versions of PKZIP, all the files were expanded in the 8.3 format. Instead of WesternHorse.theme, using an older program will unzip this file as WesternH.the, which will NOT work with the program. During the past few weeks, I have discovered more and more programs that are "zipped" with file names greater than the 8.3 format. If you don't use a Win95-compatible unzipper, you will have problems. I use WinZip for Win95 and it DOES preserve the full names of the files. I don't know if this has anything to do with unzipping the CFT files, but it is worth exploring. SgtGeorge At 08:18 AM 2/25/98 -0500, Joseph Cain wrote: >There was a recent posting suggesting that the problem I was having >in the install of version 2.29 was the prior removal of the earlier >version (whether by Cleansweep or the cft supplied uninstall program). > >To test this I already had 2.27 working again as per an earlier post >except for its inability to be able to restore older zipped backup >files. (These could be read with no problem when unzipped by another >means to the cftw directory). I then installed 2.29 on top of 2.27 >to see if there was any difference. The result was nearly the same. That is, >when it first presented the icon for family tree it was unable to >bring up the program, but had to look for it even though the >Properties/shortcut directed it correctly to the cftw32.exe file. This was >again repaired by looking for the icon, which when found solved that >problem. However, on each load the screen would flash "Fonts were copies to >fonts directory, press ok to continue," followed by another screen that had >the caption: "LUNDS FONTS Installation warning" which read: "The set of >Lunds fonts did not install properly...etc" after which the program loaded >fine. > >I also tested whether it would reload the older databases. This time it >did reload all but two. Both of the backups were flawed in that they would >not unzip using Norton's unzip program. The file that would not unzip was >individ.tps, whose length was 84,480 long on both. The one that cftw >unzipped except for this file was written 2/22/98 during the time I was >testing version 2.29. (I had not intended to replace any of the old files >so this was an error in so doing). The other failure was a database that >was backed up 10/5/97 with whatever version was in use at that time. In >this instance the file appeared in the directory was only 768 bytes long >after the cftw restore. > >Has anyone else had such failures of the backups to reload? I have not had >problems with unzipping such files except in instances where they were >written to defective floppies. These were both written to my other hard drive. > > > >

At 06:18 PM 2/25/1998 -0600, you wrote: > >CFT-Win does not use any other than normal Window DLLs, etc. It only >installs the FOUR LUND fonts to c:\windows\fonts. Otherwise everything else >is in c:\cftw. That is curious. The Cleansweep program also archived c:\windows\Hsun32.exe, which seems to be part of an uninstall program. i.e. clicking on this brings up a menu that says uninstall must be run with parameters. It may be yours since it has a garbage can icon like the one that appeared in the little icon box on installation.

>> Failure of the backup files is scary. It is also interesting that both >> failures involved the same file. It is unlikely that this would be a >> common problem with my hard drive since it occured twice at different >> times months apart. >> >I had the same experience, renaming/deleting the old file did not solve >it, only first time. then I changed the filename in ptions/database/ >setting same result. > >IRA how to resolve this. ?? Test with PKZIP or WinZip. It seems some of anothers users backups were corrupted. But I am not certain it is a general problem as most people can successfully do it. Test making a backup and restore to a secondary database. See if you can get it to work even on the hard drive. Ira ---------------------------------------------------------- Ira J. Lund Cumberland Family Software, Clarksville, Tennessee, USA Genealogy Software for Beginners and Professionals E-mail: ira.lund@cf-software.com http://www.cf-software.com