Finally, I've found a workaround for the condensed Terminal font bug
I use the Terminal font where it should show like this:
https://i.imgur.com/4VKBKLb.png But somehow, ended up like this: https://i.imgur.com/7H02DHy.png This has bugged me for years. And so far, the only workaround I found on the net is a a system restart. But I finally found a consistent method to reproduce the problem: simply log off the use, then relogin. Apparently, the bug applies to Windows Vista and up to Windows 10 before build 1703. My guess is that it has something to do with Windows Desktop Manager which was introduced in Windows Vista. And with that, I found that somehow, the `Terminal Regular` font (i.e. the `VGAOEM.FON` file) got removed from the font list in memory while the font itself is still loaded in memory, on subsequest user login. The workaround fix I've found is to delete the `Terminal Regular` font from the `Fonts` folder. But because it's a system font, it can't be deleted and it'll show an error message. However, it causes the font to be reregistered into the font list in the memory. So, it does what's needed to fix the font. I've made a script to ease the font fix using VBScript. No Administrator rights is required to run it and apply the fix. https://pastebin.com/aQuGNLah |
Finally, I've found a workaround for the condensed Terminal font bug
JJ wrote:
I use the Terminal font where it should show like this: https://i.imgur.com/4VKBKLb.png But somehow, ended up like this: https://i.imgur.com/7H02DHy.png This has bugged me for years. And so far, the only workaround I found on the net is a a system restart. But I finally found a consistent method to reproduce the problem: simply log off the use, then relogin. Apparently, the bug applies to Windows Vista and up to Windows 10 before build 1703. My guess is that it has something to do with Windows Desktop Manager which was introduced in Windows Vista. And with that, I found that somehow, the `Terminal Regular` font (i.e. the `VGAOEM.FON` file) got removed from the font list in memory while the font itself is still loaded in memory, on subsequest user login. The workaround fix I've found is to delete the `Terminal Regular` font from the `Fonts` folder. But because it's a system font, it can't be deleted and it'll show an error message. However, it causes the font to be reregistered into the font list in the memory. So, it does what's needed to fix the font. I've made a script to ease the font fix using VBScript. No Administrator rights is required to run it and apply the fix. https://pastebin.com/aQuGNLah An alternate approach could be to use the "Consolas" font. I have been using this font for many years (since Windows 7) and I particularly like to use the italic style. |
All times are GMT +1. The time now is 10:34 PM. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright © 2004 - 2006 PCbanter
Comments are property of their posters