Open Type Font and all Type 1 Fonts Error

I've attached exports from my XP SP3 system that relate directly to the *.otf and *.ttf file types.  Rename it as a *.reg file if you intend to Merge or Import it to your Registry.  I have split it into 3 sections separated by a remarked-out line:

; ----------------------------

Top section relates to *.otf
Middle section relates to *.ttf
Bottom section is common to both because it is the Class Identifier specified by the ..\shellex\IconHandler key in both cases.

Note also that I have added remarked out lines that show the actual paths where the exported *.reg files contain REG_EXPAND_SZ values, and therefore show as =hex(2): ones that aren't decipherable as standard paths.

Your *.reg file contains standard REG_SZ (String) Values.  I'm not sure if this is important, and that's why I included the remarked out paths so you can compare yours.

I believe that the *.reg file you used may have been intended for a Win98 system that doesn't use REG_EXPAND_SZ values.  That could be the reason it was screwed up before you sorted it out.

Bill,
You were correct the other reg file was from a win98. I cured it the TTF messup by upgrading the paths to fontviewer.

Here is where I am at now. I just merged your file with my registry.

I am still at square one. I can go to a directory with TTF files and view them, but when I go to a directory with OTF files it errors with the same old error.

If I go directly to the fonts directory under WINDOWS I can view both TTF and OTF with no issue, but when I move an OTF into the fonts directory it appears to allow the move and even warns me that it is goign to delete the old font, but after the move the font does not function and errors out when you try to view it.

The only thing that has changed with the registry merge is the OTF fonts outside the fonts directory no longer have an "O" icon, they have the generic Windows icon.

Hmmm.

I checked this on my system.  After copying ARIAL.TTF from C:\Windows\Fonts to a non-system folder, it opens with the preview in FontView just fine and the file retains the "O" icon.

Permissions maybe?
Right-Click > Properties > security tab.
Are any of the "Deny" boxes checked?

What happens if, after you have copied out one of the fonts to a neutral folder, you Shift - Right-Click > Open With > and browse to C:\Windows\System32\FontView.exe

It may not allow you to do this if you have a "NoOpenWith" String Value in the key:
[HKEY_CLASSES_ROOT\Applications\fontview.exe]
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Applications\fontview.exe]
and it is set to any value other than Zero.  Mine is blank, ie. "NoOpenWith" has no Data Value as it appears in regedit, and it exports as this:
"NoOpenWith"=""

Create a shortcut to FontView.exe in a non-system folder and drag/drop a copy of a font from that same folder onto it to see if it opens.

See what happens if you try to (re)register fontext.dll:

regsvr32 /i fontext.dll

This DLL seems to relate primarily to the properties of the Fonts folder and with installing/uninstalling Fonts, and I'm not even sure if it is a self-registerable DLL, but it shouldn't write any values to the registry that wouldn't already be there if it was.

I've uploaded another *.reg file as a *.txt file.  It's commented to explain what I understand of the usage for each of the 3 main keys, and I have completely remarked out each line in the bottom section because the values COULD cause problems being somehow related to Code Pages or Language settings.

It may simply be telling Fontview to load the font preview in English as:
"The quick brown fox jumps over the lazy dog" rather than:
"Le renard brun rapide saute par-dessus le chien paresseux"
or
"El zorro marrón rápido salta sobre el perro perezoso".

Thank you for such accurate translations, http://babelfish.yahoo.com  :-)

I'll need to think about this one some more, but I'll also need to catch some sleep.  I'll count foxes jumping over lazy dogs while I nod off thinking about this.  Maybe other experts may have some clues in the meantime.

Whoops, getting too tired there.  Here's the file.

I took some screenshots of my Folder Options > File Types dialogs for the TTF and OTF types.  The command lines for the "Open" and "Print" actions are the same for TTF and OTF, as are the DDE fields.

The one thing I note of both when opened for editing is that there is no associated icon for each.  I don't know why, but if you click the "Change Icon" button to see if there is an icon set (and perhaps just not showing), it shows an error "Windows cannot find the file %1".  The icon for the fonts is obviously set elsewhere in the Shell settings.

Permissions maybe?
Right-Click > Properties > security tab.
Are any of the "Deny" boxes checked?

I am signed in as Admin and could not find any security tab

What happens if, after you have copied out one of the fonts to a neutral folder, you Shift - Right-Click > Open With > and browse to C:\Windows\System32\FontView.exe

It may not allow you to do this if you have a "NoOpenWith" String Value in the key:
[HKEY_CLASSES_ROOT\Applications\fontview.exe]
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Applications\fontview.exe]
and it is set to any value other than Zero. Mine is blank, ie. "NoOpenWith" has no Data Value as it appears in regedit, and it exports as this:
"NoOpenWith"=""

Did this and the OTF font that was moved from the fonts directory did not have the OTF extension. Upon moving it, the extension was TTF and it opened fine. I also moved a original copy (from Linotype) of the OTF font with the OTF extension into that same directory and it would error when I tried to open it.

Create a shortcut to FontView.exe in a non-system folder and drag/drop a copy of a font from that same folder onto it to see if it opens.

Nope did not work.

See what happens if you try to (re)register fontext.dll:

regsvr32 /i fontext.dll

This DLL seems to relate primarily to the properties of the Fonts folder and with installing/uninstalling Fonts, and I'm not even sure if it is a self-registerable DLL, but it shouldn't write any values to the registry that wouldn't already be there if it was.

Errored out:
fontext.dll was loaded but the DLLinstall point could not be found. The file could not be registered.

I've uploaded another *.reg file as a *.txt file. It's commented to explain what I understand of the usage for each of the 3 main keys, and I have completely remarked out each line in the bottom section because the values COULD cause problems being somehow related to Code Pages or Language settings.

This returned the icon back for the OTF fonts that are NOT in the fonts directory.

From what I can see when you install an OTF font windows takes it and somehow transforms it into a TTF font that is placed in the fonts directory. Just so you know I have confirmed these OTF fonts are functionable. I have the orignal ones that worked at the begining of the year and have performed a hard install of some of them into CS2 Photoshop. Bypassing the Windows font system is an option Adobe put in their CS system. They function flawlessly.

One thing I was think was maybe the versions of fontext.dll and fontview.exe are not jiving. Here are the versions I have:

fontview: 5.1.2600.5512

fontext: 5.1.2600.5512

Just spoke with a tech friend and he said that some TTF fonts appear to Windows to be OTF fonts, but still have the TTF extension.

Bill,

Any more ideas?

Hi Gman4u

You should find that ALL OpenType TrueType fonts in the C:\Windows\Fonts folder will be *.TTF ones, but you should find *.OTF files in other folders.

You see, the OpenType font format was developed jointly by Microsoft and Adobe.  OpenType fonts may contain either TrueType or PostScript outlines.  Fonts containing TrueType outlines may have either *.OTF or *.TTF file extensions.  Microsoft seems to have retained use of the *.TTF file extension for their OpenType fonts, but has added the "O" icon:
C:\Windows\Fonts\*.ttf
while Adobe applications install their own *.OTF fonts to the application's own program folder, eg:
C:\Program Files\Adobe\Reader 8.0\Resource\Font\*.otf

FontView.exe should be able to preview both the *.ttf and *.otf versions of OpenType fonts.  I have the same version of FontView.exe and Fontext.dll on this WinXP SP3 system, so that's not the problem.

I'm afraid that I have run out of ideas.  I'm sorry, but I really don't know what else to suggest.

Gman4u,

You don't happen to have an ATI graphics card in your machine, do you?

There have been some problems noted with OTF fonts and ATI drivers in XP.

Also, check and make sure you have these files in C:\Windows\System32\
atmfd.dll - version: 5.1.2.225
atmlib.dll - version: 5.1.2.225

These are Adobe Type Manager (hence the atm*.dll) files which help manage Type 1 and Open Type fonts in XP.

Cheers,
LHerrou

Asus EN7900GS/2DHT/256M GeForce 7900 GS PCI Express 256MB DDR3 Video Card w/Dual-DVI & HDTV-Out

Nice setup - and that's NVIDIA, not ATI.

What about the files I mentioned?

atmfb.dll is version 5.1.2.226

That's a typo, right, it's atmfd.dll? and what about atmlib.dll, also version: 5.1.2.225?

Yes typo. LOL

atmlib is version 5.1.2.226

Both are 5.1.2.226 not 5.1.2.225

Hmm. XP SP3 installed maybe? Can you roll back?

XP SP3 was installed because the OTF fonts quit working. I can tell you the fonts were functioning fine about 4 months ago.

Err, also, any changes to your boot.ini file during the period in question? Read this...
http://photo.net/digital-darkroom-forum/00QHie

(if you set your machine to use >3gb RAM, may have issues with ATM's handling of Type 1 and Open Type fonts).

Can you check if you have any Type 1 fonts on your machine, and see if those are working? That may also help narrow things down.

No 3gb switch here.

Just checked and that sucks. None of my Type 1 Adobe fonts are functioning. I did not notice that before.

I just ran a driver updater type program and it is claiming some of my NIVDIA drivers for my motherboard are outdated. I will attempt to update them.

Well, then the next step I would take is a check of all protected files on your system:
Go to Start -> Run and in the Open box, type sfc /scannow, and then click OK.

If files need replacing, you may get prompted to insert your Windows XP disk. Any files upgraded by Service Packs or Hotfixes from M$ will be checked and replaced from the downloaded SP or hotfix, and not the older files from the CD.

Ran sfc/scannow and it appeared to replace a few files from the original cdrom. Nothin has changed, still can't read the Type 1 or OTF fonts.

OK, it appears to either be a registry or a font folder issue. As a next step, download TweakUI (http://www.microsoft.com/windowsxp/Downloads/powertoys/Xppowertoys.mspx) and run the font repair utility:

Launch TweakUI and click the "Repair" link. To the left of the "Repair Now" button, click the pull-down and choose "Repair Font Folder". Click "Repair Now", then "OK" to close the dialog box.

Oh, right, and also go to the Windows font cache file that is located here: C:\Windows\System32\FNTCACHE.DAT and delete it. When you reboot, a new cache will be generated.

Thank you for your help.

Ran TweakUI via, Start, Run. Repaired Font folder (did not seem to do anything). Still having issue.

Well, the only suggestion left in my toolbox is a repair install of Windows XP. This is a big step, I know, but everything else I can think of I've suggested (or you already tried with BillDL's help). It may not be worth it if you can access them via CS2 through your manual addition.

I also have scoured the web looking for other possibilities. It appears that this is a very difficult problem when it occurs, and I haven't found anyone with a solution. (side note: I did see you had posted your question elsewhere as well).

My next step will be to bring in my laptop and regedit on both machines. I will do a locate fo the extension otf and see if there are any differences between the to regsitries on how one machine treats the otf fonts, opens them etc. I did read somewhere that the display driver on a machine with an ATI board gave this problem. Maybe my Nvidia is causing it? My last step before doing anything drastic will be to pop in a different video card and see if that cures it.

Well, double-checking the registry seems to make sense, but you mostly went through that exercise with BillDL. I've never seen a report of this issue with NVidia cards, but can't hurt to give it a try.

This just came in from Linotype:

There is a registry entry that controls the rendering of PostScript outlines. I assume this might be corrupted on your machine. In order to fix this, you would need to do the following:
Start regedit and go to:
»HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Font Drivers«.
I assume that there will be no string called Adobe Type Manager. Create this string, and enter the reference "atmfd.dll".

Best Regards,

Jens Konrad
Linotype GmbH

OK, let us know if that fix works...

Here's the export from my XP registry - you can copy/paste and save this into a .reg file and import it back into your registry.

Windows Registry Editor Version 5.00
 
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Font Drivers]
"Adobe Type Manager"="atmfd.dll"

                                              

1:
2:
3:
4:

Guys/Gals,

I am not ready to just up and reinstall XP over this when it has to ve a simple fix. Someone here has to know the steps that take place when Type1 and CTF fonts are loaded by fontview and see something we missed.

I would like to thank everyone for trying to help me out with this issue. Unfortunately I do not have the time to completely reinstall XP so the problem will remain.

Once again thanks for trying.

Gman4u, I respect your decision to not re-install XP. However, that does appear to be a solution - maybe not for you, given your circumstances, but for others with the same issue. We also provided a tremendous amount of prior suggestions and work-arounds (and I do recognize that none of the worked for you, but that does not mean that they might not help someone else). I therefore believe this thread should stand.

lherrou,
To inform a person that they need to reinstall the OS is a reckless solution considering that it could cause data loss and countless hours of program reinstalling. This in my book is unacceptable and is not a solution. I am sorry but a respectfully disagree with you. The problem at hand is in a connection between XP and the Type 1 fonts. To tell a person the ONLY fix is to reinstall XP is like telling a person with an infected paper-cut that you have to remove their arm and replace it with a new one.

Two "experts" have weighed in on this problem the first I found somewhat schooled in XP and the second I found had resorted to doing searches on Google and such for a clue as to why the problem was happening, something I performed myself prior to asking for assistance. It is ridiculous to tell a person that comes along in the future with this issue they need to overhaul their OS to make it go away when NO one knows if that is REALLY the solution or not. It has not been done and I am not here to be the ginnie-pig or sacrificial lamb.

Iherrou, if you wish to perform such drastic measures on your machine, I suggest you drop about $3500 and build the box I am running, set it up with the software I have installed and recreate the problem, then play OS reinstaller. Then goe through the process of reinstalling CS3, about a dozen video and audio editing suites, plus all their pluggins and addons.

It's time to move this up the ladder to the real "Experts" at Maximum PC. Replace the OS is a cop-out, not a solution.

Gman4u,

To save yourself this trouble in the future, you might want to consider using one of the 'Imaging' programs available.

That way the next time you screw up your computer, you can simply re-load the last known good image and be back on your way.

I use "BootIt" on all my computers (and for my customers who are smart enough to agree with me).

Re-loading from image takes about 5-6 minutes, but with your fancy $3,500 box - it might take 6 or 7.

younghv,

Considering missing exotic fonts like the Type 1 fonts that are not funxtioning is not something you would notice on a day to day basis, exactly how would "Imaging" help? The last time I used the fonts was in January. I stand by my commet about it being irresponsable to say, an OS reinstall is the solution.

Vee Mod,

I don't know what youa re seeing on your screen, but I just responded to iherrou and did not start any closing process again.

A repair install, in general, should NOT delete all of your programs and settings. If you go about it properly (image the machine before, use a Slipstreamed CD, backup and save your registry settings), it should simply repair your OS without harming anything else. Now, that's not always the case, especially if you've tinkered with your registry a lot, so imaging the machine beforehand IS important, but I still think it is a reasonable option for you. Note that I did NOT suggest a full wipe and re-install, which is what you seem to think I had suggested.

And I run CS and several other imaging and video editing programs, with many third-party plugins, etc. I do know what a hassle this can be.

lherrou,

"Note that I did NOT suggest a full wipe and re-install, which is what you seem to think I had suggested."

Then I read it wrong and I apologize.

My objection remains, as previously stated in http:/Q_23710967.html#22533001

Wee Mod,

I would likt to place this ina holding pattern please until I can perform the option Iherrou gave me.

By the way, here is one of the better guides that I am aware of for doing an XP Repair Install (younghv might have other suggestions):

http://www.michaelstevenstech.com/XPrepairinstall.htm

Michael Stevens is as good as it gets.
Great advice.

I was facing the same problem. It was very hard to find any informaiton about this problem on the Internet and the posts in this threat were not helpful. If you have XP SP3 installed I found two causes for that problem:

1) A problem with the graphic card driver and XP SP3 (i.e. ATI, NVIDIA)
2) /3GB Switch in the boot.ini file

I found no reference to the problem on the NVIDIA site, but I found a very new driver. I installed it and the problem was gone! All OTF and Type 1 fonts are displayed again and can be used.  

I hope this helps you, too.

Marcus

I had the same issue today as well.  No idea when it broke, but went to use some Post Script and Open Type fonts and got the same issue.

I have three screens, with two video cards. a Dual head GeForce 6800 Ultra (AGP) and a GeForce FX 5200 PCI.

I went and downloaded the latest and greatest drivers (Forceware 178.13), and two things happened:
1. My Post Script and Open Type fonts started working again.
2. I found out that the above version of drivers no longer support the older FX line of GPU's and so I lost the monitor that was connected to it.

Not really happy with that solution, even though I did have my Post Script and Open Type fonts working again I really wanted my system in tact.  I tried playing around with installing the FX's Drivers manually using the inf file, but that didn't work, and so I dove into the archive's of drivers, and found that Forceware 169.21 works with both my GPU's and still allows Post Script and Open Type fonts to open in fontview.

Hope this helps....I know I spent the better part of a day dealing with this, (Boss isn't going to be happy when he ask's "So, how far did we get on this today" and I say, well, remember that font problem I ran into this morning around 8:45 am; well I just fixed it (4:20 pm)"