Note that the InfoZIP "WiZ" program is distributed as a single file
wiz401xN.exe
which is a "self-extracting archive".
To unpack it, you just put this file in an otherwise empty
directory, and launch it, either by double-clicking on its name
or icon under Windows Explorer, or else by typing its name at the
MS-DOS prompt. It should unpack itself and create a number of
files, including the application wiz.exe
.
Launching wiz.exe
will bring up a screen that you
can use to unzip GED2HTML.
There are help files distributed with "WiZ" that you can read if it
is not clear how to use it.
To unpack GED2HTML, launch your unzip program and specify the filename
ged2html.zip
as the file to be unpacked.
Alternatively, you could try double-clicking directly on
ged2html.zip
and when the system asks you what application
you would like to associate with files with extension .zip
you can specify your unzip program.
In either case, once GED2HTML is unpacked, you should have a number
of files in the folder with the GED2HTML.ZIP.
Among the files you now have are the following executables:
The file GED2HTML.EXE is the Windows user interface for GED2HTML, and it is what you should use to launch the program. This user interface simply collects your options in a dialog box, and then starts G2H.EXE, which is the "back-end" program that does all the real work. Since (unlike previous versions of GED2HTML) all the options understood by G2H.EXE can now be accessed via the GED2HTML.EXE interface, there is probably no need for you ever to run G2H.EXE directly. However, please note that for proper operation, GED2HTML.EXE has to be able to find G2H.EXE, and thus either both must reside in the same directory or else you will have to modify properties settings for GED2HTML.EXE so that it starts in the directory where G2H.EXE is located, or use some other Windows trickery to arrange that GED2HTML.EXE can find and launch G2H.EXE.
As your GEDCOM is processed, you will see various progress messages output in the console window. First the GEDCOM is read, then the individuals are sorted and index files are output, then sources and notes files are output, then the individuals are resorted, and finally the individuals files are created. When processing has finished, you will see the message "Processing complete". Under Windows 95/98/NT you should press ENTER to close the console window. Under Windows 3.1 the word FINISHED will appear in the lower left-hand corner of the window, and you will have to close the console window using the system menu.
By default, the HTML files produced by GED2HTML are placed in a subdirectory "HTML" of the directory from which it was started. You may peruse the files with your Web browser to verify that they are OK. Good starting points are the files "PERSONS.HTM" and "SURNAMES.HTM" (under Windows 95/98/NT, "persons.html" and "surnames.html").
Exactly how long it will take to process your GEDCOM is primarily dependent on whether you have enough RAM on your system for the size GEDCOM you are attempting to process. Roughly speaking, this generally amounts to about one megabyte of RAM per thousand individuals in your GEDCOM. Thus, a 10,000-individual GEDCOM could be processed comfortably in 10MB of RAM. In this case, the program will spend most of its time generating the output files, rather than reading the input data. As the ratio of individuals to RAM approaches one megabyte of RAM per two thousand individuals, the program will become slower and slower at reading in the GEDCOM file, and will make extensive use of the disk. In this case, during certain phases of program execution where the individuals are sorted, it may appear that the program is "hung". Most likely it isn't; rather, it is just busy trying to shuffle your data back and forth between disk and RAM. It is probably not feasible to process a GEDCOM if there are more than three thousand individuals per megabyte of RAM.
Copyright © 1995-2000 Eugene W. Stark. All rights reserved.