TOPIC:

Hello koeiekat,

It seems that the FontSets file was corrupted by the update (possibly restart without waiting for the app to terminate).

Here are some steps to fix the problem:

Restore the FontSets file (FindMyFont.fst or FindMyFont.fst.bin in user\AppData\Roaming\FindMyFont\fmfdata) from your backup.

If the above doesn't work, delete the FontSets file. Then start FindMyFont and re-created the font sets as you had them before. If the fonts are the same and in the same folders, the program will use the existing index files. It will show the fontsets as indexed when you add them.

Let me know if this worked.

Thanks. The first suggestion doesn't work, alas, as the back-up was after disaster struck.

I will now try the second suggestion. I hope I do not have to recreate the fontsets from scratch again as that will take many hours. I'll keep you posted.

Yes, I need to recreate all 60 fontsets. That is going to take a long time

koeiekat wrote: Yes, I need to recreate all 60 fontsets. That is going to take a long time

Hi koeiekat,
I suggest to follow the advise of Harris, i.e.
a) Delete the FindMyFont.fst (if it exist) and the FindMyFont.fst.bin
b) Create again your fontsets by choosing the same exact directories as the old ones

In this case Yes, the App. will need some time to count/validate again the font-files of each fontset, but -if the index files are intact- the fontsets will appear indexed and there will be no need to spend time on indexing.

It is the indexing actually which takes a lot of time not the fontset creation itself

May I suggest that in the next release, every time the FindMyFont.fst.bin file is written also a file FindMyFont.fst.bin.BAK is created so that when disaster strikes the BAK file comes to the rescue.