I am using FoxFire in our company and in one of our offices, the user now goes to the reports menu to fire up FoxFire and it no longer loads because it complains that not all of the fonts are available to run FoxFire (ver 3+).

Since I have the source code, I found out that the checking is being done by a .prg called FFChkFnt and further digging found out that it checks for Arial and FoxFont. I sent the user out a quick program to query what AFONT() was returning and FoxFont was not in the list. I then had the user manually install FoxFont into their fonts folder (via. the "Install Font" menu option of that folder) to see if that would help. It didn't. For some reason, the font is no longer being recognized by their system. This is an install that is about 2 years old (the FoxFire.app part anyhow, the rest I update regularly) and so it just "stopped working".

Looking at the source code, I have a couple of questions (apart from how to solve this):

1) There are notes their by Andy Neil that it seemed he was finding instances himself where his checking code failed. I wonder if there is an update to FFChkFnt.prg and also FFWinFnt.prg. My source has a date stamp of 09/27/96 but header in file says 08/22/95. Maybe there are some Win95/98 anomalies that have been accomodated since then.

(FFWinFnt.prg is used to install the font if it is not found - it obviously is also failing because it should be called if the check fails - my test code that I sent out for the user to run had a modified version of FFChkFnt in it which captured what it was finding to memvars that I then captured to file and had the user send back and it said that FFWinFnt should have been called.)

2) Does anyone know if AFONT() is gathering information from the Fonts folder or is it getting info out of the registry and/or out of Win.ini. Maybe I can insert something in Win.ini that helps this.

Albert