Broken "Invalid font resource" marking symlinks as corrupt [Closed]
Posted: Mon May 10, 2021 5:19 am
I seem to remember this from some time back. For some reason, Maintype is claiming that 100's of my fonts are corrupt and have a bad magic number. The bad magic number is (213C7379) which corresponds to the first 4 letters of
a Windows <!symlink>.
I've seen apps not understand windows desktop links, but everything that opens files follows windows symlink
codes that appeared about 10-15 years ago on Windows 7, maybe were on Vista before that.
Unfortunately, the fact that Maintype detect these as "corrupt font files" that it wants to delete is a bit scary since I
know other applications use them "just fine".
I have my fonts installed in more than one location due to different application (and OS) needs.
is there a fix or patch for this problem? Both the main font and the symlink are in valid locations (needed in
each location). I've never seen any application have to do anything special since all of the OS-calls automatically follow
the links..
Ideas?
Thanks!
Astara
a Windows <!symlink>.
I've seen apps not understand windows desktop links, but everything that opens files follows windows symlink
codes that appeared about 10-15 years ago on Windows 7, maybe were on Vista before that.
Unfortunately, the fact that Maintype detect these as "corrupt font files" that it wants to delete is a bit scary since I
know other applications use them "just fine".
I have my fonts installed in more than one location due to different application (and OS) needs.
is there a fix or patch for this problem? Both the main font and the symlink are in valid locations (needed in
each location). I've never seen any application have to do anything special since all of the OS-calls automatically follow
the links..
Ideas?
Thanks!
Astara