This is the list of problems with which we are familiar. You can scan down the page, or click on the title that looks like the problem you are having. The most recently encountered problems are first. If you are having one of the problems that we have fixed, and have a CD older than the date it was fixed, you need an upgrade. See Prices, Licensing, and Upgrade Info.
Windows error message: "This file is potentially harmful"
The Installer Ran Under Windows 7, but the Fonts Don't Show Up
McGraw-Hill Handwriting Doesn't Work
Publisher 2010, 2013 incorrectly substitutes for characters that it thinks are missing in the fonts
Wordpad/Notepad Sometimes Display Cursive Fonts Wrong in Vista
Font is Wrong after LinkLetter in Pagemaker 7
The Installer Doesn't Work with 64-bit Vista or 64-bit Windows 7 Fixed 4/25/09. Upgrade available.
Fonts Disappear After Restart - workaround
LinkLetter Doesn't Work with 64-bit Vista Fixed 4/25/09. Upgrade available.
OpenOffice Problems Mostly Fixed 11/15/08
Older CD cannot be read
Starting Dot in HWT Manuscript Outlines #5 in Wrong Place Fixed October 2007
Installer Problem on Windows Vista Fixed April 2007
Microsoft Office 2007, Problems with Cursive Text Fixed April 2007
Windows 2000 or Windows XP - Error Message About AUTOEXEC.NT
WordPerfect and Quark Express 6.5 Problems
Windows XP - Installer Aborts Fixed April 2007
Windows XP - Installer Does Nothing
Microsoft Word AutoFormatting Problems
Microsoft Word - i Gets Changed to I
Microsoft Word - The First Letter of Every Line Gets Capitalized
Microsoft Word - Can't Get Rules To Extend to the End of the Line
Microsoft Word 2000 and HP Deskjet 952c
Microsoft Works 4.0 and 4.5 Are Missing Some EFI fonts
Microsoft Works 6.0 - Undo Linkletter Does Not Work Fixed December 2001
WordPerfect - Some of the Linked Cursive Text is Gibberish
WordPerfect - Manuscript Fonts Get Changed to Default Font
WordPerfect - Bold Fonts Get Changed
Windows 98 and WordPerfect
WordPerfect 8 Cursive Text Sometimes Becomes Gibberish When Linked
Cursive Fonts and Phonetics Phont in WordPerfect 9, 10 and 11.
Cursive Text Does Not Work With WordPerfect 5 or 6.0
WordPad Doesn't Display or Print Some Sizes
Fonts Don't Show Up in Your Word Processor
Printer Error or PostScript Error
Silly Windows. It is preventing you from installing the fonts and LinkLetter programs you just bought, even logged on as Administrator (which you must be). Here's the solution that customers Toby and Lori most graciously sent us [They were installing the DF fonts series]:
1. Save the zip file onto another computer and unzip it there.
2. Insert a flash drive and move the unzipped folder to the flash drive.
3. Insert the flash drive into the destination computer.
4. Click Start --> Control Panel --> System and Security --> Windows Firewall --> Allow a program through Windows firewall
5. Click "Change Settings" button
6. Click "Allow another Program" button
7. Click "Browse" button
8. Find install_DF file
9. Click "Open" button
10. Move install_DF.exe file from flash drive to desktop
11. Launch install_DF file.
Thanks, Toby and Lori!
This happens when the user hasn't signed on as an Administrator. The installer program tries to install the fonts in the Windows/Fonts directory, but is denied permission to do so. Sign on as Administrator and do the install again.
Alas, the McGraw-Hill installation CDROM is woefully out of date. Please call us at 1-800-806-2155, describe the problem, and we will give you a current CD, no charge(!), in exchange for the non-working CD (so we can verify that you really bought the McGraw Hill program). In addition to actually installing on modern systems, our CD looks prettier.
There is a problem in Publisher 2010 and 2013 such that certain characters we used in our linked cursive become the subject of character or font substitution. Joanna brought the problem to our attention when the ending strokes of letters g, j, y, and z were showing up as florins (fancy f's) after running LinkLetter using the HB Cursive font series. The linked text pastes correctly into Word 2010, but if doesn't even work to copy the text from Word and paste it into Publisher.
We managed to workaround the HB cursive problem for Joanna by including additional codepages when we generated the HB Cursive fonts.
Unfortunately, there are characters in almost all of our linked cursive fonts that don't work correctly with Publisher.
We haven't be able to discover which code pages we need to include to get Publisher to correctly handle the characters for all of our linked cursive fonts. One of the characters for which we haven't been able to avoid substitution is the Greek letter pi. We've even included Greek as one of the codepages for the font, and Publisher still inserts the pi symbol.If you are experiencing problems with our cursive fonts using Publisher, please contact us and we might be able to provide you with a fix.
We have only encountered this problem on a laptop, but that doesn't mean that a desktop display will not have the problem.
Wordpad and Notepad were recoded for Vista and sometimes no longer display our cursive fonts correctly. Symptoms include excessive space for ligatures, rectangles instead of ligatures or letters, or other bizarre display characters. It is caused by very narrow widths defined for some ligation characters in some of our fonts. This narrow width is valid, and worked fine under previous Windows operating systems, but now Vista has arbitrarily decided to "correct" what it thinks is an undisplayable width. Sigh.
Fortunately, this seems to be almost entirely a display problem -- most of the fonts seem to print correctly. The exception to this is the HB font family, which has problems printing under Vista using several different printer drivers in Wordpad especially.
It used to be that users who were having problems with Word were advised to use Wordpad, but now, under Vista, the reverse is true. All our fonts display and print properly using Word 2007.
LinkLetter worked great under Pagemaker 6.5, but now under Pagemaker 7, after running LinkLetter, the font coming back is no longer a handwriting font at all, but something weird like FuturaMdBt. To your great annoyance, since InDesign won't import your older documents properly.
One of our loyal, helpful customers (thanks, Joan!) found a "fix" for this Pagemaker 7 problem. After she installed Acrobat Pro 9, suddenly LinkLetter worked properly again! We at EFI speculate that PM 7 shipped with a buggy Clipboard processor, and Acrobat overwrote that DLL with a functional one.
If your CDROM predates 4/25/09, you have a 16-bit installer, and no 16-bit program runs under Windows 64-bit operating systems. We fixed this on 4/25/09, and an upgrade is now available for it. If you are not using LinkLetter, and your CD is dated September 2004 or later, read the file W_RAWFONTS.TXT in the Windows\Rawfonts folder for instructions. If you don't have a RawFonts folder or need LinkLetter, you need to buy the upgrade. See Prices, Licensing, and Upgrade Info.
You installed the fonts and everything worked fine. That is, until you did a Restart or Shutdown, and then the fonts no longer appear in your Fonts menu. Your Windows Font Cache has gotten confused.
The Windows operating system has a font cache file that is located here:
Delete this file, and restart your system. A new FNTCACHE.DAT file will be created on startup.
Reinstall the fonts after the restart. That should clear up the problem.
True. We found this out 8/28/08, when a friendly teacher called in to say Linkletter didn't work on her new computer. It turns out that 16-bit programs like LinkLetter no longer can be run on the 64-bit Windows computers. We fixed this on 4/25/09, and an upgrade is now available for it.
Our cursive fonts had worked correctly in OpenOffice 1.5, but they changed something in 2.0 and our fonts no longer worked. We resolved the Linkletter problem with our 11/15/08 CD, but there are still a few relatively minor problems remaining. The problems are still there in the most recent version, 3.4.1.
When you relink cursive text with certain letters at the beginning of a paragraph, the letter does not get linked to the letter following it. The letter will also be a much smaller size than the rest of the paragraph. The letters that do not correctly link are not the same in each font family. The easiest way to avoid this problem is to run UndoLinkletter before running LinkLetter on text that had been prevoiusly linked. You'll also have to look at the size of each letter at the beginning of the paragraph.
Two PM fonts (specifically PM48 Cursive Base, Mid, Top and PM23 Cursive Base, Mid, Top) are not recognized by OpenOffice. Its problem is likely that the fonts have commas in their names. The only workaround for this problem is to set the text to a different PM Cursive fonts, link it, and then change it to the font with the comma in its name.
If you have a document with more than one cursive font in it (for example, HWT Cursive and HWT Cursive Outlines), OpenOffice can get confused when you relink or unlink the document. If what you see does not look correct, undo the paste and relink the text for each font separately, or just relink words that you have changed instead of the entire document. Or don't mix fonts.Copying linked text from an OpenOffice document to a document in another word processor might not work well, depending on the font and the actual text. This problem was reported to the OpenOffice people in 2006, and it has not been fixed.
This has happened on both Mac and Windows computers, with a particular batch of CDs from one manufacturer, shipped to our customers in September of 2003.
You put the CD in the drive. You can hear the drive attempting to mount it. You wait and wait for it to show up on your computer. On Windows, if you open My Computer and double-click on the CD drive, My Computer hangs and you have to Ctrl-Alt-Del to end it. to end it.
Three people have called with this problem since early April, 2008. We asked them to mail us the CDs. We had the same problems with their CDs on our computers, and then noticed that all of the "bad" CDs have the same set of numbers stamped on the hub. No manufacturer information, but we now know how to identify the bad ones.
If you think you have one of these bad CDs, please call us. Our master CD for September 2003 is still fine (it is on a CD from a different batch), and we can burn you another copy of the same vintage, for no charge.
You may also upgrade (for the normal price) to our latest CD. The major changes that we have made since September 2003 are:
1. Changed to all of our Linkletter programs to handle enhancements Microsoft made in Word 2004 and Word 2008 on the Mac, and Word 2003 Service Pack 3 and Word 2007 for Windows computers.
2. We bought a new installer program and redid all of our installers to run on Windows Vista.
3. Created universal installers and native mode Linkletter programs for the Intel Mac.
4. Added more DN fonts (French, Spanish, and German Cursive).
5. Added another set of HWT Manuscript fonts with a dotted center line on the three rule variations.
6. Added three new families, DK Cursive (left and right handed slant cursive fonts), Queensland (Australia), and CF (Cursive First, copyright of LITHBTH Publishing).
7. Added one Decorative font (EFI Extra Fancy) and several Specialty fonts (Count Dots, Direct Instruction, Music, and four Prewriting Practice variations).
8. Added four Manuscript Phonics fonts to all our Manuscript families (AB, CCU, DN, FS, GDI, HB, HWT, McD, OZ, Palmer, PM, PT, QM, SSD, SV, and ZB).
9. We redid all of our Linkletter programs in April 2009 to run in Windows 64 bit operating systems.
If you have a CD dated earlier than October 2007, the starting dot on the number 5 in the HWT Manuscript Outlines, Outlines Rules, and Outlines 3 Rules fonts is in the incorrect place. Oops. If it bugs you, please email us with your school name or home address for a free download link to give you the corrected fonts. Please follow the instructions in the ReadMe.txt in the download - you will have to remove the incorrect fonts using the Fonts Control Panel before installing the new ones. *Many Thanks* to OT Vera Johnson for reporting this bug to us.
If you have a CD earlier than 2007, the Windows installers typically abort with a Shadow error message when run on Windows Vista. There is a workaround available on the CD if your CD is dated September 2004 or later. See the paragraph about SW.EXE in the file W_RAWFONTS.TXT in the Windows\Rawfonts folder for instructions.
If you have an older CD (one without the RawFonts folder), email us and we will email SW.EXE and the instructions to you.
We have fixes on our 2007 CD for all but the problem 4 issue in Publisher. If you have an older CD and plan to use any of our cursive fonts with Office 2007, you'll want to upgrade to the newest CD. If you find any new problems, please call us (1-800-806-2155).
There is a minor problem - you can only link about a one page document (like a letter, with many words, not just a short spelling list, at 48 point).
1. The last letter in your document is chopped off.
2. If you try to unlink or relink your already linked cursive text, you will get an error message and the program terminates without relink or unlinking.
3. One some displays, the linked text does not display correctly at some sizes, but it prints correctly.
4. When you relink or unlink text, Publisher substitutes incorrect
characters for three of our ligation characters (joins between
letters). There is nothing we can do about this, and there is
no workaround. The problem is introduced when you paste the text
into the document after the first link. We have filed a problem
report with Microsoft.
Did you get the following message after you double-clicked install.exe?
16-bit MS-DOS Subsystem
path to the program you are trying to run
C:\WINNT\system32\autoexec.nt The system file is not suitable for running MS-DOS and Microsoft Windows applications. Choose 'Close' to terminate the application.
Or did you get a similar error message when you were running Linkletter?
This is a known Microsoft problem, and it is documented on the Microsoft support web site. The probable cause is that your AUTOEXEC.NT file is missing or damaged.
We have a work-around. We put a copy of AUTOEXEC.NT on our CDs, beginning in January of 2005. For information about copying AUTOEXEC.NT from our CD to your computer, see the file Windows\RawFonts\W_RAW_FONTS.TXT.
If you do not have AUTOEXEC.NT on our CD, there should be a
copy in the Windows\Repair folder on your hard drive. But it needs
to be in the Windows\System32 folder. To get it in the System32
1. Open My Computer, and size it so that you can see an empty area on the Desktop.
2. Double-click the local disk C:.
3. Scroll down to the Windows folder, and double-click it.
4. Double-click the Repair folder.
5. Single-click AUTOEXEC.NT, hold the Ctrl key, and drag a copy of AUTOEXEC.NT to your Desktop.
6. In My Computer, click the Back button to get to the Windows folder.
7. Scroll down in the Windows folder until you see the System32 folder.
8. On your Desktop, single-click AUTOEXEC.NT, and drag it to your System32 folder.
If you get a message that your are trying to look in a system
folder or a hidden folder, click whatever choice there is to be
able to view it.
Some programs do not correctly display or print Cursive text when you paste it back into the application after running Linkletter. These are the programs that we know do not work correctly:
Corel Word Perfect 9, 10, and 11. A few of the linked letters are dropped. See Cursive Fonts and Phonetics Phont in WordPerfect 9, 10 and 11 on this web page.
Quark Express 6.5. One of the linked letters gets changed to Y. The affected letter is different depending on which font you are using. For example, in ZB Cursive, it is the letter "u." We have reproduced the problem, but we do not have any way to fix it. Quark Express 7.2 does not have this problem.
The Windows installer (install.exe) is supposed to copy itself from the CD to your hard drive, and then run itself. A few users have had problems with the installer aborting (General Protection Fault) before it runs. All of these problems have occured outside the United States - is there something different about the international version of Windows?
We have an alternate installer (SW.EXE) that seems to avoid these problems. We can email you this installer and tell you how to use it. We have also included this installer on the CDs beginning in September 2004. See the file W_RAW_FONTS.TXT in the WINDOWS Raw Fonts folder on the CD for information about how to use SW.EXE, and how to install individual fonts.
Contact us if you are having this problem, so we can figure out the best way to get your fonts installed.
You have double-clicked install.exe on the CD or a floppy disk. Nothing happens! Try dragging the font family to the desktop and double-click the install.exe that you have just copied.
To "drag" the font family:
- On the CD, double-click Windows. Scroll to the font family that you want to install (such as DN or GDI). Click the folder name, and drag it to the desktop.
- If using a floppy disk, first create a folder on your desktop, with the name of the font family (such as DN or GDI). Select all of the files on your EFI floppy disk (there should be four). Drag the four files into the folder you just created.
There are other workarounds available if you have a CD dated September 2004 or later. See the file W_RAW_FONTS.TXT in the WINDOWS Raw Fonts folder on the CD for information. If it still doesn't work, call us. 1-800-806-2155.
Starting with Word 97, Microsoft introduced a feature called AutoFormat, which automatically changes some of what you type. Unfortunately, this feature causes problems, particularly with our ruled fonts.
If you get underlines instead of blank rules, some words become italic (even though you didn't type them in italic), or words unexpectedly end up bold, you have been done in by this feature.
Because of the problems with blank rules, we added another way to make blank rules starting in August 2003. If you have one of our newer CDs, we suggest that you use the bar character (|, shift backslash, above the Enter or return key on your keyboard) instead of the underscore character (shift minus) for blank rules.
To turn off AutoFormat:
1. On the Format menu, click AutoFormat.
2. Click Options.
3. Click the AutoFormat As You Type tab, and uncheck *Bold* and _italic_ with real formatting and Symbol characters (--) with symbols (-).
4. Click the AutoFormat tab, and uncheck *Bold* and _italic_ with real formatting and Symbol characters (--) with symbols (-).
5. Click OK, close Word, and reopen Word.
If you are still having problems, open Word Help, and read topics dealing with AutoFormat. Or call us. 1-800-806-2155
Every time that you try to type the single letter i, it gets changed to a capital I. You've encountered the Microsoft Word AutoCorrect feature.
To turn it off:
1. On the Format menu, click AutoFormat.
2. Click Options.
3. Click the AutoCorrect tab, and scroll down the left column until you find i (which is replaced by I).
4. Click the i, and click Delete.
You've encountered another Microsoft Word AutoCorrect feature.
To turn it off:
1. On the Format menu, click AutoFormat.
2. Click Options.
3. Click the AutoCorrect tab.
4. Unckeck Capitalize first letter of sentences.
In pre-march 2003 versions, you can only extend the line when you are using a font "with Rules," such as DN Manuscript Arrows Rules or ZB Manuscript Outlines Rules. Delete the space after the last word in the line, hold the shift key, and type the underscore character (on the same key as the minus). In March 2003, we added the vertical bar character to al fonts as a blank rule holder to avoid this problem.
Two customers have reported that their computer freezes when trying to print any of our DN fonts using an HP Deskjet 952c. One was running Windows ME, the other Windows 98.
The good news about this printer is it works fine if you use WordPad instead of Microsoft Word 2000 (Start button, Programs, Accessories).
Even better news is that deleting the font BD Denver eliminated the problem with Microsoft Word for both users.
Microsoft acknowledges a bug with some of our fonts. The following EFI fonts do not show up in the Fonts menu:
Microsoft does not have a solution, but have provided this
1. Open Works
2. Click the "Format" menu, then click "Font and Style"
3. In the Format Font and Style dialog box, type the name of the missing font and enter the size you want (we suggest using at least 24 point as the size).
4. Click OK.
And neither does running Linkletter a second time on the document. As of December 2001, we have a fix for this problem. Call or email us to get the correction.
All versions of WordPerfect have problems with our fonts. Most of the problems occur with cursive fonts.
When you paste the linked cursive text back into WordPerfect 7 or higher, some of it is OK, some is gibberish. The problem is that WordPerfect is interpreting some of the connectors as control characters. Just select all of the text and change it to the desired font and size.
If you have both Manuscript and Cursive fonts in a document, the Manuscript text might get changed to the default font when you run Linkletter or UndoLinkletter. The solution is to not run any manuscript text through LinkLetter, or to change it back to what you really want after running LinkLetter.
WordPerfect doesn't keep the Bold font name when you run LinkLetter or Undo LinkLetter. It links and unlinks the letters correctly, but changes the font name, and makes the text bold. That is, DN Cursive Bold becomes DN Cursive, and the style of the font is changed to Bold. This problem occurs with all of our Bold fonts. It seems than WordPerfect can't handle having Bold as part of the font name.
WordPerfect 7 and a Canon printer has problems similar to WordPad in Windows 95. There are size ranges that cause breaks between letters when using ruled fonts. For example, DN Cursive Arrows Rules at 30 point on our PC is OK, it's bad between 34 and 42, and OK at 44 and higher.
There is a problem with WordPerfect 8 and some of our cursive fonts. The text is gibberish when pasted back after Linkletter. Even though the font named in the font window is the correct one, WordPerfect is actually displaying the text in the default font. The solution is to highlight the text and reselect the font and size.
These version of WordPerfect do special handling with the characters that we have in character positions 0152, 0168, and 0180. The characters in these positions are not the same in all of our fonts.
The cursive characters that have problems are:
DN, NP and VP - v and s
GDI - some letter e
HB - x and w
McD, OZ, PM, PT, ZB - v, x, and w
SSD - Y and J
The Phonetics Phont has even more characters that are problems.
You'll have to look at the PHONETICS.PDF in the SPECIAL.TY folder
on the CD to see what these characters are supposed to be.
Unfortunately, these letters disappear when the cursive text is linked or when you type the alt code for the Phonetics Phont. We told Corel about the problem with WordPerfect 9 in October 2001, and WordPerfect 11 still has the same problem. At this time, you should not use WordPerfect 9, 10, and 11 if you are going to be using cursive text or the Phonetics Phont. If you created your documents using WordPerfect 8, use that version instead.
WordPerfect 5 does not correctly handle RTF format, which is what LinkLetter and UndoLinkletter copy to the clipboard. Try using another word processor. Microsoft Write on Windows 3.1 can handle simple documents, as can WordPad on Windows 95 and higher.
WordPad is the simple word processor that ships with Windows 95, Windows 98, Windows NT, Windows 2000, and WIndows ME. The Windows 95 version has problems with all of our ruled fonts on InkJet printers. The fonts will work fine for some size ranges, and be bad at other sizes. For example, DN Manuscript with Rules on our PC is OK at less than 28 point, does not work correctly at 28 point through 40 point, and is OK above 40 point.
There are two variations to the problem:
1. As you type, each letter goes on a separate line, like you are typing Enter after each letter. Documents that look like this will NOT print correctly.
2. Some of the letters on each line disappear as you type them. They are really there, and will print correctly. If you use Print Preview to look at the document, everything will show up OK.
If you have variation 1, try other sizes until you get one
that works. For those who are having variation 2 problems, try
typing in the corresponding non-ruled font (for example, using
Manuscript Outlines) so you can see what you are typing, and change
to the ruled font to print (Manuscript Outlines Rules).
If you install an EFI Teacher Pack family and the fonts don't show up in your word processor, there could be several reasons:
When using Windows 2000, you must restart the computer after installing the fonts.
Your word processor was open when you installed the fonts. Close and reopen your word processor, and all the new fonts should now be available.
You have "too many" fonts installed on your computer. On the PC, 1000 fonts is definitely too many. But problems can start to occur with about 700 or so. The limit is a function of the length of all of the font names, and probably a few other factors. The solution is to delete some of the fonts that you no longer use.
You are using Works 4.5 or Word 6.0 (not 6.0a or 6.0c). There are known problems in these two products, and the bugs affect the following fonts : DN Cursive, DN Manuscript, HB Cursive, HB Manuscript, McD Cursive, and McD Manuscript. The workaround is the same for both problems. See the Works problem described elsewhere on this page.
This typically happens on an inkjet printer when you are trying
to print a document that has a lot of fonts. The printer doesn't
have enough memory to contain all the fonts. You can either reduce
the number of different fonts that you are using, or try printing
fewer pages at a time.