how to convert .ttf to .fnt for use with DOS font driver












1















I have a DOS program M10_SCR.COM that loads as a TSR and allows the use of fonts. it does work with its own basic built-in fonts, so now I am trying to convert .ttf fonts into .fnt so I have more fonts to choose from.



there are instructions on how to convert .ttf to .fnt with FontForge at



https://stackoverflow.com/questions/24529369/how-to-convert-ttf-to-fnt-with-fontforge



I did successfully convert a .ttf font to .fnt, although it fails to load with M10_SCR. there were many options in FontForge that may be the cause of failure.



when running M10_SCR.COM with the converted font, it gives an error:



Error - wrong external font file size!



to troubleshoot, I tried loading one of M10_SCR's built-in fonts into FontForge. it gives these errors:



[dialog box: Bad magic number]
This does not appear to be a Windows FNT or FON file



[dialog box: Couldn't open font]
8x16FONT.FNT is not a known format (or uses features of that format fontforge does not support, or is so badly corrupted as to be unreadable)



I can't find any .fnt fonts on the internet to try with M10_SCR for troubleshooting.



why wouldn't a converted font work? how can I find out what the difference is? how can I get this to work?










share|improve this question







New contributor




Fyodor is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





















  • Out of curiosity: what size is a .fnt file that the utility will accept?

    – Tommy
    4 hours ago











  • since it emulates the video card's ROM character table, the characters must be the same size as those, therefore some multiple of 256 bytes. there are three ROM tables: 8x8, 8x14, and 8x16 (character sizes). therefore acceptable filesizes are 2048, 3584 and 4096 bytes.

    – Fyodor
    1 hour ago
















1















I have a DOS program M10_SCR.COM that loads as a TSR and allows the use of fonts. it does work with its own basic built-in fonts, so now I am trying to convert .ttf fonts into .fnt so I have more fonts to choose from.



there are instructions on how to convert .ttf to .fnt with FontForge at



https://stackoverflow.com/questions/24529369/how-to-convert-ttf-to-fnt-with-fontforge



I did successfully convert a .ttf font to .fnt, although it fails to load with M10_SCR. there were many options in FontForge that may be the cause of failure.



when running M10_SCR.COM with the converted font, it gives an error:



Error - wrong external font file size!



to troubleshoot, I tried loading one of M10_SCR's built-in fonts into FontForge. it gives these errors:



[dialog box: Bad magic number]
This does not appear to be a Windows FNT or FON file



[dialog box: Couldn't open font]
8x16FONT.FNT is not a known format (or uses features of that format fontforge does not support, or is so badly corrupted as to be unreadable)



I can't find any .fnt fonts on the internet to try with M10_SCR for troubleshooting.



why wouldn't a converted font work? how can I find out what the difference is? how can I get this to work?










share|improve this question







New contributor




Fyodor is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





















  • Out of curiosity: what size is a .fnt file that the utility will accept?

    – Tommy
    4 hours ago











  • since it emulates the video card's ROM character table, the characters must be the same size as those, therefore some multiple of 256 bytes. there are three ROM tables: 8x8, 8x14, and 8x16 (character sizes). therefore acceptable filesizes are 2048, 3584 and 4096 bytes.

    – Fyodor
    1 hour ago














1












1








1








I have a DOS program M10_SCR.COM that loads as a TSR and allows the use of fonts. it does work with its own basic built-in fonts, so now I am trying to convert .ttf fonts into .fnt so I have more fonts to choose from.



there are instructions on how to convert .ttf to .fnt with FontForge at



https://stackoverflow.com/questions/24529369/how-to-convert-ttf-to-fnt-with-fontforge



I did successfully convert a .ttf font to .fnt, although it fails to load with M10_SCR. there were many options in FontForge that may be the cause of failure.



when running M10_SCR.COM with the converted font, it gives an error:



Error - wrong external font file size!



to troubleshoot, I tried loading one of M10_SCR's built-in fonts into FontForge. it gives these errors:



[dialog box: Bad magic number]
This does not appear to be a Windows FNT or FON file



[dialog box: Couldn't open font]
8x16FONT.FNT is not a known format (or uses features of that format fontforge does not support, or is so badly corrupted as to be unreadable)



I can't find any .fnt fonts on the internet to try with M10_SCR for troubleshooting.



why wouldn't a converted font work? how can I find out what the difference is? how can I get this to work?










share|improve this question







New contributor




Fyodor is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.












I have a DOS program M10_SCR.COM that loads as a TSR and allows the use of fonts. it does work with its own basic built-in fonts, so now I am trying to convert .ttf fonts into .fnt so I have more fonts to choose from.



there are instructions on how to convert .ttf to .fnt with FontForge at



https://stackoverflow.com/questions/24529369/how-to-convert-ttf-to-fnt-with-fontforge



I did successfully convert a .ttf font to .fnt, although it fails to load with M10_SCR. there were many options in FontForge that may be the cause of failure.



when running M10_SCR.COM with the converted font, it gives an error:



Error - wrong external font file size!



to troubleshoot, I tried loading one of M10_SCR's built-in fonts into FontForge. it gives these errors:



[dialog box: Bad magic number]
This does not appear to be a Windows FNT or FON file



[dialog box: Couldn't open font]
8x16FONT.FNT is not a known format (or uses features of that format fontforge does not support, or is so badly corrupted as to be unreadable)



I can't find any .fnt fonts on the internet to try with M10_SCR for troubleshooting.



why wouldn't a converted font work? how can I find out what the difference is? how can I get this to work?







ms-dos font






share|improve this question







New contributor




Fyodor is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











share|improve this question







New contributor




Fyodor is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this question




share|improve this question






New contributor




Fyodor is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked 6 hours ago









FyodorFyodor

61




61




New contributor




Fyodor is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





Fyodor is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






Fyodor is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.













  • Out of curiosity: what size is a .fnt file that the utility will accept?

    – Tommy
    4 hours ago











  • since it emulates the video card's ROM character table, the characters must be the same size as those, therefore some multiple of 256 bytes. there are three ROM tables: 8x8, 8x14, and 8x16 (character sizes). therefore acceptable filesizes are 2048, 3584 and 4096 bytes.

    – Fyodor
    1 hour ago



















  • Out of curiosity: what size is a .fnt file that the utility will accept?

    – Tommy
    4 hours ago











  • since it emulates the video card's ROM character table, the characters must be the same size as those, therefore some multiple of 256 bytes. there are three ROM tables: 8x8, 8x14, and 8x16 (character sizes). therefore acceptable filesizes are 2048, 3584 and 4096 bytes.

    – Fyodor
    1 hour ago

















Out of curiosity: what size is a .fnt file that the utility will accept?

– Tommy
4 hours ago





Out of curiosity: what size is a .fnt file that the utility will accept?

– Tommy
4 hours ago













since it emulates the video card's ROM character table, the characters must be the same size as those, therefore some multiple of 256 bytes. there are three ROM tables: 8x8, 8x14, and 8x16 (character sizes). therefore acceptable filesizes are 2048, 3584 and 4096 bytes.

– Fyodor
1 hour ago





since it emulates the video card's ROM character table, the characters must be the same size as those, therefore some multiple of 256 bytes. there are three ROM tables: 8x8, 8x14, and 8x16 (character sizes). therefore acceptable filesizes are 2048, 3584 and 4096 bytes.

– Fyodor
1 hour ago










2 Answers
2






active

oldest

votes


















3














This is Morozov’s screen driver, available e.g. from SimtelNet archives. It uses a fairly typical font format for EGA/VGA fonts, namely a dump of the in-memory font data as loaded for the character generator in an EGA or VGA graphics adapter: 256 characters each formed of 8 to 16 bytes (depending on the number of lines in the font), each byte encoding a line of a character — so the font files’ size is always a multiple of 256, 2048 bytes for small fonts (as used in 80×50 mode on VGA), 3584 bytes for 14-line EGA fonts, 4096 bytes for 16-line VGA fonts... This doesn’t match any of the .FNT formats available in other environments, such as Windows. I’m not sure whether there are any conversion tools available to produce appropriate fonts from TrueType fonts or other such formats; I don’t remember there being any in the 90s.



Fonts for tools such as this were usually hand-drawn using dedicated font editing tools such as PC Magazine’s FONTEDIT, or Oliver Fromme’s CAFE (my two personal favourites, which are unfortunately hard to get a hold of nowadays — I’ll update this if I find them). You’ll find a number of fonts to try out, and font editing tools, in SimtelNet’s “screen” directory; look through the index for details. I wrote a font-loading tool which supports a variety of formats, loadfont, although since it’s not a TSR it’s not as versatile as Morozov’s screen driver.






share|improve this answer


























  • that is what it is and where I got got it from. the Simtelnet "screen" directory has FNTCOL15.ZIP and I just tried it, they do work with M10_SCR however most are simply character sets for different languages, few are en-us.

    – Fyodor
    48 mins ago













  • next step would be to use those as examples of what format is required, then use something like FontForge to convert .ttf into that specific style of .fnt format,. suggestions?

    – Fyodor
    46 mins ago













  • one thing I notice is that these aren't .FNT they are .F08, .F14 and .F16 and looking again ye olde Win98 CD has .FON

    – Fyodor
    39 mins ago











  • one thing I notice is that these aren't .FNT they are .F08, .F14 and .F16 and are indeed 2048/3584/4096 bytes. looking again at ye olde Win98 CD it has .FON which don't work and are different filesizes too.

    – Fyodor
    33 mins ago



















2














I suspect that what you're dealing with here is two different file formats that happen to use the same filename extension, of ".fnt". There has never been any mechanism to control the use of filename extensions on DOS or Windows, except for market pressure, and .fnt is a very obvious choice for fonts.




  • Windows .fnt is pretty much obsolete, but it could contain vector or raster glyphs.


  • Metagraphics .fnt is a bitmap format that certainly isn't the same as the Windows format, and probably isn't the one used by M10_SCR, since it seems designed for fonts of higher resolution than MS-DOS INT10 usually deals with.


  • M10_SCR [.fnt] seems to be something else.



I can't find much about M10_SCR on the net, but it's a minimum of 22 years old, quite possibly considerably older. Windows' use of particular filename extensions wasn't considered significant by many DOS programmers in the late eighties and early nineties, since Windows didn't have much market share until the advent of Windows 3.0 in 1990, and didn't become dominant in the PC market until the mid-nineties.






share|improve this answer


























  • it's from March 1992

    – Fyodor
    1 hour ago











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "648"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});






Fyodor is a new contributor. Be nice, and check out our Code of Conduct.










draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fretrocomputing.stackexchange.com%2fquestions%2f9212%2fhow-to-convert-ttf-to-fnt-for-use-with-dos-font-driver%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























2 Answers
2






active

oldest

votes








2 Answers
2






active

oldest

votes









active

oldest

votes






active

oldest

votes









3














This is Morozov’s screen driver, available e.g. from SimtelNet archives. It uses a fairly typical font format for EGA/VGA fonts, namely a dump of the in-memory font data as loaded for the character generator in an EGA or VGA graphics adapter: 256 characters each formed of 8 to 16 bytes (depending on the number of lines in the font), each byte encoding a line of a character — so the font files’ size is always a multiple of 256, 2048 bytes for small fonts (as used in 80×50 mode on VGA), 3584 bytes for 14-line EGA fonts, 4096 bytes for 16-line VGA fonts... This doesn’t match any of the .FNT formats available in other environments, such as Windows. I’m not sure whether there are any conversion tools available to produce appropriate fonts from TrueType fonts or other such formats; I don’t remember there being any in the 90s.



Fonts for tools such as this were usually hand-drawn using dedicated font editing tools such as PC Magazine’s FONTEDIT, or Oliver Fromme’s CAFE (my two personal favourites, which are unfortunately hard to get a hold of nowadays — I’ll update this if I find them). You’ll find a number of fonts to try out, and font editing tools, in SimtelNet’s “screen” directory; look through the index for details. I wrote a font-loading tool which supports a variety of formats, loadfont, although since it’s not a TSR it’s not as versatile as Morozov’s screen driver.






share|improve this answer


























  • that is what it is and where I got got it from. the Simtelnet "screen" directory has FNTCOL15.ZIP and I just tried it, they do work with M10_SCR however most are simply character sets for different languages, few are en-us.

    – Fyodor
    48 mins ago













  • next step would be to use those as examples of what format is required, then use something like FontForge to convert .ttf into that specific style of .fnt format,. suggestions?

    – Fyodor
    46 mins ago













  • one thing I notice is that these aren't .FNT they are .F08, .F14 and .F16 and looking again ye olde Win98 CD has .FON

    – Fyodor
    39 mins ago











  • one thing I notice is that these aren't .FNT they are .F08, .F14 and .F16 and are indeed 2048/3584/4096 bytes. looking again at ye olde Win98 CD it has .FON which don't work and are different filesizes too.

    – Fyodor
    33 mins ago
















3














This is Morozov’s screen driver, available e.g. from SimtelNet archives. It uses a fairly typical font format for EGA/VGA fonts, namely a dump of the in-memory font data as loaded for the character generator in an EGA or VGA graphics adapter: 256 characters each formed of 8 to 16 bytes (depending on the number of lines in the font), each byte encoding a line of a character — so the font files’ size is always a multiple of 256, 2048 bytes for small fonts (as used in 80×50 mode on VGA), 3584 bytes for 14-line EGA fonts, 4096 bytes for 16-line VGA fonts... This doesn’t match any of the .FNT formats available in other environments, such as Windows. I’m not sure whether there are any conversion tools available to produce appropriate fonts from TrueType fonts or other such formats; I don’t remember there being any in the 90s.



Fonts for tools such as this were usually hand-drawn using dedicated font editing tools such as PC Magazine’s FONTEDIT, or Oliver Fromme’s CAFE (my two personal favourites, which are unfortunately hard to get a hold of nowadays — I’ll update this if I find them). You’ll find a number of fonts to try out, and font editing tools, in SimtelNet’s “screen” directory; look through the index for details. I wrote a font-loading tool which supports a variety of formats, loadfont, although since it’s not a TSR it’s not as versatile as Morozov’s screen driver.






share|improve this answer


























  • that is what it is and where I got got it from. the Simtelnet "screen" directory has FNTCOL15.ZIP and I just tried it, they do work with M10_SCR however most are simply character sets for different languages, few are en-us.

    – Fyodor
    48 mins ago













  • next step would be to use those as examples of what format is required, then use something like FontForge to convert .ttf into that specific style of .fnt format,. suggestions?

    – Fyodor
    46 mins ago













  • one thing I notice is that these aren't .FNT they are .F08, .F14 and .F16 and looking again ye olde Win98 CD has .FON

    – Fyodor
    39 mins ago











  • one thing I notice is that these aren't .FNT they are .F08, .F14 and .F16 and are indeed 2048/3584/4096 bytes. looking again at ye olde Win98 CD it has .FON which don't work and are different filesizes too.

    – Fyodor
    33 mins ago














3












3








3







This is Morozov’s screen driver, available e.g. from SimtelNet archives. It uses a fairly typical font format for EGA/VGA fonts, namely a dump of the in-memory font data as loaded for the character generator in an EGA or VGA graphics adapter: 256 characters each formed of 8 to 16 bytes (depending on the number of lines in the font), each byte encoding a line of a character — so the font files’ size is always a multiple of 256, 2048 bytes for small fonts (as used in 80×50 mode on VGA), 3584 bytes for 14-line EGA fonts, 4096 bytes for 16-line VGA fonts... This doesn’t match any of the .FNT formats available in other environments, such as Windows. I’m not sure whether there are any conversion tools available to produce appropriate fonts from TrueType fonts or other such formats; I don’t remember there being any in the 90s.



Fonts for tools such as this were usually hand-drawn using dedicated font editing tools such as PC Magazine’s FONTEDIT, or Oliver Fromme’s CAFE (my two personal favourites, which are unfortunately hard to get a hold of nowadays — I’ll update this if I find them). You’ll find a number of fonts to try out, and font editing tools, in SimtelNet’s “screen” directory; look through the index for details. I wrote a font-loading tool which supports a variety of formats, loadfont, although since it’s not a TSR it’s not as versatile as Morozov’s screen driver.






share|improve this answer















This is Morozov’s screen driver, available e.g. from SimtelNet archives. It uses a fairly typical font format for EGA/VGA fonts, namely a dump of the in-memory font data as loaded for the character generator in an EGA or VGA graphics adapter: 256 characters each formed of 8 to 16 bytes (depending on the number of lines in the font), each byte encoding a line of a character — so the font files’ size is always a multiple of 256, 2048 bytes for small fonts (as used in 80×50 mode on VGA), 3584 bytes for 14-line EGA fonts, 4096 bytes for 16-line VGA fonts... This doesn’t match any of the .FNT formats available in other environments, such as Windows. I’m not sure whether there are any conversion tools available to produce appropriate fonts from TrueType fonts or other such formats; I don’t remember there being any in the 90s.



Fonts for tools such as this were usually hand-drawn using dedicated font editing tools such as PC Magazine’s FONTEDIT, or Oliver Fromme’s CAFE (my two personal favourites, which are unfortunately hard to get a hold of nowadays — I’ll update this if I find them). You’ll find a number of fonts to try out, and font editing tools, in SimtelNet’s “screen” directory; look through the index for details. I wrote a font-loading tool which supports a variety of formats, loadfont, although since it’s not a TSR it’s not as versatile as Morozov’s screen driver.







share|improve this answer














share|improve this answer



share|improve this answer








edited 3 hours ago

























answered 3 hours ago









Stephen KittStephen Kitt

38k8154166




38k8154166













  • that is what it is and where I got got it from. the Simtelnet "screen" directory has FNTCOL15.ZIP and I just tried it, they do work with M10_SCR however most are simply character sets for different languages, few are en-us.

    – Fyodor
    48 mins ago













  • next step would be to use those as examples of what format is required, then use something like FontForge to convert .ttf into that specific style of .fnt format,. suggestions?

    – Fyodor
    46 mins ago













  • one thing I notice is that these aren't .FNT they are .F08, .F14 and .F16 and looking again ye olde Win98 CD has .FON

    – Fyodor
    39 mins ago











  • one thing I notice is that these aren't .FNT they are .F08, .F14 and .F16 and are indeed 2048/3584/4096 bytes. looking again at ye olde Win98 CD it has .FON which don't work and are different filesizes too.

    – Fyodor
    33 mins ago



















  • that is what it is and where I got got it from. the Simtelnet "screen" directory has FNTCOL15.ZIP and I just tried it, they do work with M10_SCR however most are simply character sets for different languages, few are en-us.

    – Fyodor
    48 mins ago













  • next step would be to use those as examples of what format is required, then use something like FontForge to convert .ttf into that specific style of .fnt format,. suggestions?

    – Fyodor
    46 mins ago













  • one thing I notice is that these aren't .FNT they are .F08, .F14 and .F16 and looking again ye olde Win98 CD has .FON

    – Fyodor
    39 mins ago











  • one thing I notice is that these aren't .FNT they are .F08, .F14 and .F16 and are indeed 2048/3584/4096 bytes. looking again at ye olde Win98 CD it has .FON which don't work and are different filesizes too.

    – Fyodor
    33 mins ago

















that is what it is and where I got got it from. the Simtelnet "screen" directory has FNTCOL15.ZIP and I just tried it, they do work with M10_SCR however most are simply character sets for different languages, few are en-us.

– Fyodor
48 mins ago







that is what it is and where I got got it from. the Simtelnet "screen" directory has FNTCOL15.ZIP and I just tried it, they do work with M10_SCR however most are simply character sets for different languages, few are en-us.

– Fyodor
48 mins ago















next step would be to use those as examples of what format is required, then use something like FontForge to convert .ttf into that specific style of .fnt format,. suggestions?

– Fyodor
46 mins ago







next step would be to use those as examples of what format is required, then use something like FontForge to convert .ttf into that specific style of .fnt format,. suggestions?

– Fyodor
46 mins ago















one thing I notice is that these aren't .FNT they are .F08, .F14 and .F16 and looking again ye olde Win98 CD has .FON

– Fyodor
39 mins ago





one thing I notice is that these aren't .FNT they are .F08, .F14 and .F16 and looking again ye olde Win98 CD has .FON

– Fyodor
39 mins ago













one thing I notice is that these aren't .FNT they are .F08, .F14 and .F16 and are indeed 2048/3584/4096 bytes. looking again at ye olde Win98 CD it has .FON which don't work and are different filesizes too.

– Fyodor
33 mins ago





one thing I notice is that these aren't .FNT they are .F08, .F14 and .F16 and are indeed 2048/3584/4096 bytes. looking again at ye olde Win98 CD it has .FON which don't work and are different filesizes too.

– Fyodor
33 mins ago











2














I suspect that what you're dealing with here is two different file formats that happen to use the same filename extension, of ".fnt". There has never been any mechanism to control the use of filename extensions on DOS or Windows, except for market pressure, and .fnt is a very obvious choice for fonts.




  • Windows .fnt is pretty much obsolete, but it could contain vector or raster glyphs.


  • Metagraphics .fnt is a bitmap format that certainly isn't the same as the Windows format, and probably isn't the one used by M10_SCR, since it seems designed for fonts of higher resolution than MS-DOS INT10 usually deals with.


  • M10_SCR [.fnt] seems to be something else.



I can't find much about M10_SCR on the net, but it's a minimum of 22 years old, quite possibly considerably older. Windows' use of particular filename extensions wasn't considered significant by many DOS programmers in the late eighties and early nineties, since Windows didn't have much market share until the advent of Windows 3.0 in 1990, and didn't become dominant in the PC market until the mid-nineties.






share|improve this answer


























  • it's from March 1992

    – Fyodor
    1 hour ago
















2














I suspect that what you're dealing with here is two different file formats that happen to use the same filename extension, of ".fnt". There has never been any mechanism to control the use of filename extensions on DOS or Windows, except for market pressure, and .fnt is a very obvious choice for fonts.




  • Windows .fnt is pretty much obsolete, but it could contain vector or raster glyphs.


  • Metagraphics .fnt is a bitmap format that certainly isn't the same as the Windows format, and probably isn't the one used by M10_SCR, since it seems designed for fonts of higher resolution than MS-DOS INT10 usually deals with.


  • M10_SCR [.fnt] seems to be something else.



I can't find much about M10_SCR on the net, but it's a minimum of 22 years old, quite possibly considerably older. Windows' use of particular filename extensions wasn't considered significant by many DOS programmers in the late eighties and early nineties, since Windows didn't have much market share until the advent of Windows 3.0 in 1990, and didn't become dominant in the PC market until the mid-nineties.






share|improve this answer


























  • it's from March 1992

    – Fyodor
    1 hour ago














2












2








2







I suspect that what you're dealing with here is two different file formats that happen to use the same filename extension, of ".fnt". There has never been any mechanism to control the use of filename extensions on DOS or Windows, except for market pressure, and .fnt is a very obvious choice for fonts.




  • Windows .fnt is pretty much obsolete, but it could contain vector or raster glyphs.


  • Metagraphics .fnt is a bitmap format that certainly isn't the same as the Windows format, and probably isn't the one used by M10_SCR, since it seems designed for fonts of higher resolution than MS-DOS INT10 usually deals with.


  • M10_SCR [.fnt] seems to be something else.



I can't find much about M10_SCR on the net, but it's a minimum of 22 years old, quite possibly considerably older. Windows' use of particular filename extensions wasn't considered significant by many DOS programmers in the late eighties and early nineties, since Windows didn't have much market share until the advent of Windows 3.0 in 1990, and didn't become dominant in the PC market until the mid-nineties.






share|improve this answer















I suspect that what you're dealing with here is two different file formats that happen to use the same filename extension, of ".fnt". There has never been any mechanism to control the use of filename extensions on DOS or Windows, except for market pressure, and .fnt is a very obvious choice for fonts.




  • Windows .fnt is pretty much obsolete, but it could contain vector or raster glyphs.


  • Metagraphics .fnt is a bitmap format that certainly isn't the same as the Windows format, and probably isn't the one used by M10_SCR, since it seems designed for fonts of higher resolution than MS-DOS INT10 usually deals with.


  • M10_SCR [.fnt] seems to be something else.



I can't find much about M10_SCR on the net, but it's a minimum of 22 years old, quite possibly considerably older. Windows' use of particular filename extensions wasn't considered significant by many DOS programmers in the late eighties and early nineties, since Windows didn't have much market share until the advent of Windows 3.0 in 1990, and didn't become dominant in the PC market until the mid-nineties.







share|improve this answer














share|improve this answer



share|improve this answer








edited 5 hours ago

























answered 5 hours ago









John DallmanJohn Dallman

2,601614




2,601614













  • it's from March 1992

    – Fyodor
    1 hour ago



















  • it's from March 1992

    – Fyodor
    1 hour ago

















it's from March 1992

– Fyodor
1 hour ago





it's from March 1992

– Fyodor
1 hour ago










Fyodor is a new contributor. Be nice, and check out our Code of Conduct.










draft saved

draft discarded


















Fyodor is a new contributor. Be nice, and check out our Code of Conduct.













Fyodor is a new contributor. Be nice, and check out our Code of Conduct.












Fyodor is a new contributor. Be nice, and check out our Code of Conduct.
















Thanks for contributing an answer to Retrocomputing Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fretrocomputing.stackexchange.com%2fquestions%2f9212%2fhow-to-convert-ttf-to-fnt-for-use-with-dos-font-driver%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Plaza Victoria

Brian Clough

Cáceres