|
My Windows Fonts folder shows an entry called "SerialNumber", but the file name is garbage, the size is zero,
and I can't open it to see what it is. So what is it?
|
 |
|
For starters, it isn't anything to do with The Font Thing! And versions of The Font Thing
from 0.80 (beta 2) onwards will run quite happily even when this Registry corruption is present.
|
 |
|
It seems to be triggered (on certain systems only) by having font smoothing turned on. Another symptom of this
particular combination is that the phantom "SerialNumber" entry will return even if you delete it or use a tool
like TweakUI to repair the Fonts folder. If you turn font smoothing off, this Fonts folder problem will not recur.
|
 |
|
Many thanks to Jay Tomford for spotting this solution.
|
 |
|
When I select the Appearance tab on the Options screen, I get a General Protection Fault along the lines of
"TFT caused a general protection fault in module MACXW4.DRV at xxxx:xxxxxxxx".
|
 |
|
The font viewing colour selection drop-downs on the Appearance tab seem to trigger a problem with
at least some video drivers for graphics card using the ATI RAGE chipset. I'm currently investigating potential
solutions (I want to keep the current drop-downs if possible), but in the meantime avoid the Appearance tab!
|
 |
|
You should also check that you are using the latest approved drivers for your graphics card, and it is often
worthwhile trying the generic drivers from the chipset manufacturer (i.e. ATI) in case they give
a better result than the specific drivers from the graphics card manufacturer.
|
 |
|
When I try to create a new font collection, the program locks up. How can I fix this.
|
 |
|
This can happen if you have a very large number of fonts installed (say 800 or more).
In this scenario, all other functions work including adding fonts to existing collections,
but the New collection function can fail. (By the way, in extreme cases having very large
numbers of fonts installed can cause Windows itself to malfunction. Click
here
for a bit more information.)
|
 |
|
Since the other program functions work normally in this situation, the way to fix the
problem is to reduce the number of installed fonts. Here's one way of doing this, which
moves them elsewhere so you can still use them later:
|
 |
 |
 |
Make (or identify) a folder somewhere on your system for keeping your uninstalled fonts in.
|
 |
 |
 |
On the Installed page, select the fonts that you don't use frequently, then copy them to
the folder from the previous step using the Copy to Folder command (it's on the context
menu and the File menu).
|
 |
 |
 |
Next, uninstall the rarely used fonts from the previous step using the Uninstall command
(it's on the context menu, the File menu, and the main tool bar).
|
 |
|
By default the fonts will be deleted to the Recycle Bin when you uninstall them. Hold
down Shift when choosing the Uninstall command if you want to delete them permanently.
|
 |
 |
 |
Restart your computer.
|
 |
|
This probably isn't strictly necessary but is definitely a good thing to do at this stage,
particularly if the number of installed fonts was high enough as to cause problems in Windows itself.
|
 |
|
Once you've reduced your installed fonts down to a more reasonable number, you should be
able to create new font collections again.
|
 |
|
Many thanks to Dean Maynard of Stingray Web Design for his detective work here!
|
 |
I'm using Windows NT, and the Installed page shows the error
symbol ( ) next to a lot of
my fonts. What's the problem?
|
 |
|
Normally the error symbol means that the font's file couldn't be found, or that it was unreadable.
However the error symbol has also been reported with font files on NTFS partitions where the file
creation date and file modification date were 1601.
|
 |
|
Changing the file's modification date to a "reasonable" value will get rid of the error symbols in
the font list. However if the file creation date is also 1601 you should change it too, since the
font may still misbehave if it's left at 1601.
|
 |
|
You can use the NT 4 Resource Kit's Touch program to change the file modification date.
However you'll need another technique (or program) if you need to change the file creation date as well.
Suitable programs include:
|
 |
 |
 |
TouchPro (shareware) from
JD Design
|
 |
 |
 |
SetFileDate (freeware) from
No-Nonsense Software
(NB: You'll need to change the properties on your Fonts folder first since SetFileDate doesn't show read-only or system folders)
|
 |
|
(PS: If you know of any other good programs for setting NT file dates, let me know so I can update this page!)
|
 |
|
Many thanks to John Gray for figuring this one out.
|