This update file supersedes the wgnupdt2.zip. You do not need the wgnupdt2.zip file if you install this file. You still need to add the update called wgnupdt1.zip before installing this wgnupdt3.zip file.
It is very important that you take the time to read the read me files associated with the updates of this program. You should be aware there are problems with running virtually every program in the PC/Windows world. If you do not read the read me files there will be a time that you may encounter a problem that is described there, and there will be fixes for that that you will not know about. Unfortunately every program has bugs. I hope this update will take care of most of the problems that you may have experienced with the last update.
What's New:
A special note about VB based applications. Unfortunately, Visual Basic based applications, with as little as one tiny error in the program code can cause the whole program to crash. That is what was happening with the GEDCOM import problem. The problem related to one single tiny program mistake that took the program down. You should also realize that after any crash of any Visual Basic application you should restart your computer or you may experience unpredictable results.
This update fixes the GEDCOM import problem that causes the program to crash whenever it encounters the problem that generates the message "Illegal Function Call". The GEDCOM import option has actually been down-graded. I was in the middle of an update to this section to make it more extensible when someone reported a show stopper bug somewhere else. I mistakenly thought I was further along in the update of this section of the program than I actually was. I created the update and placed it onto the internet before I should have. I appologize. The wingen.exe file found in the wgnupdt1.zip file has a useable GEDCOM import facility. I basically removed my changes to this to complete this update. Again, I am sorry. I thought I had the problems worked out.
This update also includes the missing vbdb300.dll file. Included in this are also many miscellaneous fixes. One notable update is to the Individual Listing. It is now possible to perform searches in other ways, not only by lastname, firstname, middle name. It allows for searches based on any string sequence. This means that if you have someone named "Tupper, Emily" you can type in "Emily" and the listing will be searched for her. Also, you can search based on dates. You can search for someone, say who was born on 02 Mar 1876. The program will find the match and highlight it if that date of birth has been entered for a family member. Additionally, you can now search next and search previous. If another match is found it will become highlighted. You can also choose to order the individual in Descending order rather then Ascending order only (see the help topic on the Individual Listing). A problem related to having the child form open and then attempting to open the Records form has been fixed. The problem with the Indivdiual Listing where the Listing had the Count Indicator visible and you attempted to minimize the listing caused an error that caused the program to crash. This has been fixed.
NOTE: Included in this file is the vbdb300.dll file that was missing from the previous updates. The file in the previous release was misnamed by me. It was my fault and I take full responsibility. The file has been included here to make up for that. If you are in need of the 95k of disk space that the vbdb30.dll file takes you can delete it from your Windows Genealogy 2.xxx directory.
SYSTEM REQUIREMENTS:
Windows Genealogy 2.xxx requires at least a 386SX-25 with 4MB of RAM and 12MB disk space to install. Although this is the case, it is recommended that you use at least a 386DX-33 with at least 8MB of RAM. It will run in as little as 4MB of RAM but it is not recommended. Windows Genealogy 2.xxx was tested in as little as 4MB of RAM and has been tested on a 386SX-25. In situations such as this, it is obvious that it is not going to purr like the devil playing a violin. You have to understand that even with a swapfile it will run slowly. I believe this is the case with most programs running in only 4MB of RAM.
The recommended configuration is as follows:
486DX-33 (or better) with 8MB RAM (or more) running on a
200MB hard drive (or better)
with at least 12MB disk space free (more if you want to do anything after the install <g>).
I highly recommend that you increase your video resolution to 1024x768 to truly take advantage of the program.
General Notes about Potential Problems:
If you get a message that the ctl3dv2.dll has not been installed properly you should remove the file called ctl3dv2.dll from your Windows Genealogy directory. You can remove it either by deleting it or by renaming it.
If you get the message "Path not found" you probably have an older version of one of the custom controls that Windows Genealogy uses. You can find out exactly which ones by first getting a directory listing of the *.vbx files (dir *.vbx) and then examine your system for an older version of these files. You must keep the version of the file that I provided (or you can use a more recent one). If you find a more recent one, then let me know and I'll examine the possibility of including it/them into the next Windows Genealogy update.
A SPECIAL NOTE about share.exe (or vshare.386). Share.exe (or vshare.386) is required by the program if you are running Windows 3.1. If you are running Work Group For Windows 3.11 or Windows 3.11 and you have vshare.386 loaded via your system.ini file you do not need share.exe. If you do not have vshare.386 loaded you MUST install share.exe via your autoexec.bat file (or via your config.sys in version 6.xx of DOS). There are instructions in the wingen.hlp file under installation that explains this in further detail.
Please read the installation topic in the wingen.hlp file for information about Windows 95 and Windows NT 3.51 (with or without the Windows 95 Preview Interface for Windows NT 3.51).
As of this update I am taking the program out of beta and considering it to be the final release. I am doing this because I feel it is stable enough to be released in this manner. This is not to say that the program does not still contain errors. I believe that most of the show stoppers have been removed. I will, within the next month, update to version 2.1 (no guarantees here). Any individual that registers the program prior to the 2.1 release can register the program for $45.00 (the old registration fee). This will include the benefits of having free updates to the next three official releases. When Release 2.1 is finalized and placed on the internet it will fulfill the first official Update of the program. This last statement is only of use to those who registered version 1.0 of the program. It means that these individuals are still entitled to 2 additional free updates. This notice also is placed here to indicate that after 2.1 of the program has been released there will be no longer the benefit of three free updates. This means that if you purchase an update of greater then 2.1 you will not be entitled to the three free updates. You may still be entitled to updates and maintentance releases free of charge but you are no longer entitled to the three free guaranteed updates.
