Uses the Unicode APIs. Version 5.2 is available in English, German, Chinese, Japanese and Korean versions, but the database format is interchangeable between them.
There have been multiple minor-version releases. One tester has 5.2.18.0 (English) and 5.1.12.0 (English) installed on different Windows systems, and can't tell the difference between them.
Wine compatibility Refer to specific test data for information on what works, what does not work, and what was not tested.
Old test results
The test results you have selected are very old and may not represent the current state of Wine.
Selected Test Results (selected in 'Test Results' table below)
What works
Installation works using PAF5AllLangs.exe with no DLL overrides, using the PAF-supplied international unicode font. I unchecked the 'View Getting Started Document Now' box, because Wordpad has not been found during earlier installation attempts.
Open an existing file.
View and navigate in family, pedigree, and individual views.
Open to view 'Edit Individual', 'Edit Marriage', 'Notes', and 'Sources' dialogs.
Export the whole file to GEDCOM using default options.
Close file.
Restart PAF, create a new file, and import GEDCOM into the new file.
'Save As' to a different filename.
Add a new individual/child, unlinked the new child, then linked the child to a different family.
Print pedigree, family group, and individual summary.
Viewed and printed a page from the built-in help viewer.
Restart PAF, view built-in help, and follow hyperlinks.
What does not
Got a hang or crash after canceling a print of a page from the help viewer.
What was not tested
MS core fonts; I stayed with the PAF-supplied font.
Entry of sources and notes.
Exporting partial databases to GEDCOM.
Multimedia.
Other auxiliary functions.
Additional Comments
This application has been platinum with earlier Wine versions. It operates considerably better than silver would seem to imply, but it does not require any DLL overrides, so gold is not appropriate.
While installing PAF, mark the check box labeled International Unicode Font.
If you want to use PAF's help functions with Wine version 1.0.1 (well, actually 0.9.38) or earlier, you should install the MS core fonts. See the appendix for details.
Start PAF by double clicking the _PAF 5_ shortcut on your desktop or by running file drive_c/Program Files/FamilySearch/Paf5/pstart.exe
Appendix:
WINE version 1.0.1 (well, actually, 0.9.29 or later) or later will work if you don't need PAF's help functions.
If you want to create a new WINE prefix directory, run wineprefixcreate. (Newer versions of WINE don't require wineprefixcreate.)
If installing from CD, you can use setup.exe to install. In this case, uncheck the Acrobat reader.
The International Unicode Font is referred to as Andale WT inside PAF. Any relationship between this font and any supported by Bill Gates' company is not obvious.
To install the MS core fonts, download the core font installers from http://sourceforge.net/projects/corefonts. Skip the Word 97 viewer. Run the other 11 *32.exe files.
PAF 5 under Wine on an Intel Mac
PAF 5 works under Wine on an Intel-based Mac using the X11 compatibility layer. It is reported to have the same issues as on Linux. To supply updates, clarifications, corrections, and such to this note, please post comments or email maintainers.
It requires XCode, X11, and fontforge:
XCode and X11 are available on the Mac OS X CDs or on the Apple website. (They are not installed by default on Mac OS X.)
Fontforge can be installed from a pre-built package, or it can be built
from source. If building from source, build as if to run on Linux.
It is recommended to install the unicode font supplied with the All Languages version of PAF.
There have been no reports concerning the use of Darwine, the Quartz driver instead of the X11 driver to remove the X11 requirement, or QEmu to run PAF on a PowerPC Mac.
To make it as easy to start as other Mac programs, it is recommended to make a simple Mac bundle containing a bash script that starts X11 and then starts Wine and the PAF executable.
On May 29, 2011, Clinton Stimpson commented with the following:
But, I would add that my own do-it-yourself build had to have this:
export DYLD_FALLBACK_LIBRARY_PATH=/usr/X11/lib:/usr/lib
The /usr/X11/lib path was for better font support, and /usr/lib was to enable print support in PAF.
Note
This table attempts to describe behavior of the (yellow question mark) help window with recent Wine versions. Please post comments or email maintainers with any corrections or updates.
Wine version
Font/text appearance
Unhandled page faults?
0.9.50 , 0.9.52
text looks fine, even without core fonts
after several help navigation clicks
0.9.53 through 0.9.56
Wine_Gecko does not download
n/a
0.9.57 through 0.9.60
Help text looks fine, even without core fonts.
After more than 9 to 12 help navigation clicks.
0.9.61 through 1.1.1
Help text looks fine.
After any use of the help window.
1.1.2 through 1.1.11
Help text looks fine.
No unhandled page faults seen.
1.1.12 (patched) through 1.1.26
Most chapters show no text.
No unhandled page faults seen.
1.1.28 through 1.1.37
Help text looks fine.
No unhandled page faults seen.
1.1.38
n/a
on first attempt to use help
1.1.39
Help text looks fine.
No unhandled page faults seen.
1.1.40
Help text looks fine.
Unhandled page fault after clicking on a hyperlink.
1.1.41 (patched) through 1.1.44, 1.2-rc1 through 1.2-rc4
Help text looks fine.
No unhandled page faults seen.
1.2-rc5 through 1.2-rc7, 1.2, 1.2.1, 1.2.2, 1.2.3, 1.3.0 through 1.3.3
Most chapters show no text.
No unhandled page faults seen.
1.3.4 through 1.3.6
Help text looks fine
(except graphical items).
No unhandled page faults seen.
1.3.7 through 1.3.11
No text visible in any chapter.
No unhandled page faults seen.
1.3.12 through 1.3.15
Chapters show text until crash.
Unhandled page fault after clicking on four chapter titles.
1.3.16 through 1.3.37
Help text looks fine.
Help viewer exception, wine crash after canceling print, following a few hyperlinks.
1.4-rc1 through 1.4-rc3
Help text looks fine.
Help viewer exception, wine crash after canceling print, following a few hyperlinks.
1.4-rc4 and 1.4-rc5
Help text looks fine until crash.
Unhandled page fault after clicking on several chapter titles. Separate WINE crash after canceling print and following a few hyperlinks.
1.4-4c6, 1.4, 1.4.1, and 1.5.0 through 1.5.28
Help text looks fine.
Help viewer exception, wine crash after canceling print, following a few hyperlinks.
1.5.29, 1.5.30
Help text looks fine.
Help viewer exception, wine crash after printing a page or canceling print.
How it used to work (Jan. 2007 to Sept. 2007)
by Robert Riches on Tuesday February 24th 2009, 21:44
(This comment was restored February 24, 2009 after it was mysteriously deleted.)
(This is an edited version of a comment originally dated January 12, 2007 and originally titled "To run PAF 5.2 under Wine 0.9.29 (or later) (on Mandriva Linux 2007)").
1. Install wine-0.9.29 or later. If you compile Wine from source, you will need fontforge, bison-2.3 (byacc won't work) and libcups2-devel (or equivalent).
2. If you wish to specify the path to the Wine prefix directory to be something other than $HOME/.wine, set environment variable WINEPREFIX. This variable must be set each time you run something from this prefix directory.
3. Run wineprefixcreate to build the prefix area.
4. Install PAF 5.2 from CD /mnt/cdrom/setup.exe or from downloaded PAF5AllLangs.exe or PAF5EnglishSetup.exe. Suggestions: uncheck Acrobat reader, skip viewing 'getting started' document if asked, install PAF international font if asked. (File PAF5AllLangs.exe can be found at ftp.ldscatalog.com/PAF5AllLangs.exe.)
5. Install font(s) by doing either OR both of the following:
1. Install PAF international font (if that was not done in step 4) by running Wine on PAF5Font.exe (from the PAF 5.2 CD.)
2. Download the core font installers from sourceforge.net/projects/corefonts. (You don't need the Word 97 viewer--it probably won't work.) Run all 11 of the *32.exe files.
6. Run PAF with something similar to the following command. (You may want to define an alias for this command.
Suggestion: make a source script that sets the WINEPREFIX environment variable and defines the alias.)
2. Copy the file usp10.dll from a windows installation of PAF into the wine windows directory: c:\\windows\\system32
3. Add c:\\windows\\system32 to the path setting in the wine user config file
4. copy all files from a windows installation of PAF from c:\\Program Files\\FamilySearch\\Paf5 to the corresponding wine windows directory.
5. Open PAF: wine paf5.exe
6. The dialog box asking if you would like the enter key to move to the next field appears without the text and buttons.
7. The "Welcome to PAF" dialog box opens and prompts with options to create new database, open existing, etc. [At this point the original tester experienced a crash that appears to have been a null-pointer dereference. No one ever filed a bug report or otherwise provided more information, so it looks like we've made progress.]