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. > > > >