Respondus 3.0 Equation Editor true type font error
Ye gads...
When I package Respondus 3.0 Equation Editor, no matter what I do I get the error: Respondus Equation Editor requires a newer version of the MT Extra (true type) font that is currently installed... Has anyone had experience with this type of error? When i compare the Windows XP font with the Respondus font, they appear the same (even has the same date of 1999)...
When I package Respondus 3.0 Equation Editor, no matter what I do I get the error: Respondus Equation Editor requires a newer version of the MT Extra (true type) font that is currently installed... Has anyone had experience with this type of error? When i compare the Windows XP font with the Respondus font, they appear the same (even has the same date of 1999)...
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
VikingLoki
18 years ago
I had a similar problem trying to get Access 97 coexisting with Office 2003, but the HATTEN.TTF files were definitely different. The 2003 font was twice the size of 97's font.
I'd make a copy of the font file untouched before the vendor's install and a copy of it after the vendor's install. Then compare the two. Date, time, size, click properties and check version number, even use a file compare utility to see if it's bit-by-bit identical. If they're different, make sure your capture picked up the right file. You may also find that your problem is that Windows Installer is seeing the existing file and determining that it's the same file that's in the MSI, but it isn't. I think setting the Attributes field for that file in the File Table to include a checksum might be able to do the trick. (See http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/setup/file_table.asp)
I'd make a copy of the font file untouched before the vendor's install and a copy of it after the vendor's install. Then compare the two. Date, time, size, click properties and check version number, even use a file compare utility to see if it's bit-by-bit identical. If they're different, make sure your capture picked up the right file. You may also find that your problem is that Windows Installer is seeing the existing file and determining that it's the same file that's in the MSI, but it isn't. I think setting the Attributes field for that file in the File Table to include a checksum might be able to do the trick. (See http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/setup/file_table.asp)
Posted by:
plangton
18 years ago
Hi Rodina00,
Might be worth doing a binary compare on the two files (http://www.fileware.com/download.htm has a tool called fdiff.exe that I use for binary compares from time to time).
Other than that, it could be that the font is meant to have an entry in the registry (see HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts) - try doing a regmon when runing the package to see if it references any keys that it can't find.
Hope that's helped!
Rgds
Paul
Might be worth doing a binary compare on the two files (http://www.fileware.com/download.htm has a tool called fdiff.exe that I use for binary compares from time to time).
Other than that, it could be that the font is meant to have an entry in the registry (see HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts) - try doing a regmon when runing the package to see if it references any keys that it can't find.
Hope that's helped!
Rgds
Paul
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
