Tweet
Been away from *band for a bit. I noticed that the modern variants are still having the same problem with csrss and fonts.
I can appreciate that there are other fixes and changes that have a higher priority than this, and that some ports use custom bitmap fonts and don't want to use true-type. So here's a super quick, dead easy fix. Will take all of two minutes to implement, no code changes required, and is just as easily implemented on future updates. Ready?
Stop using the same file names for fonts.
That's it, nothing else. Just tag the beginning or end of your font name with something unique, like your variant name and version number. So for QuickBand 2.05b, for example instead of *x*.FON use quick_205b_*x*.FON. Easy-peasy
I would however encourage implementing a better solution to this problem in the long run however as Win32 can become very glitchy when too many fonts are locked into csrss.exe and the only way to free them is a reboot since this is the parent process of the entire OS.
I can appreciate that there are other fixes and changes that have a higher priority than this, and that some ports use custom bitmap fonts and don't want to use true-type. So here's a super quick, dead easy fix. Will take all of two minutes to implement, no code changes required, and is just as easily implemented on future updates. Ready?
Stop using the same file names for fonts.
That's it, nothing else. Just tag the beginning or end of your font name with something unique, like your variant name and version number. So for QuickBand 2.05b, for example instead of *x*.FON use quick_205b_*x*.FON. Easy-peasy
I would however encourage implementing a better solution to this problem in the long run however as Win32 can become very glitchy when too many fonts are locked into csrss.exe and the only way to free them is a reboot since this is the parent process of the entire OS.