Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!samsung!olivea!mintaka!bloom-beacon!eru!hagbard!sunic!mcsun!ukc!pyrltd!pyra.co.uk!pjr From: pjr@pyra.co.uk (Peter Ruczynski) Newsgroups: comp.windows.ms.programmer Subject: Re: .FNT -> .FON Message-ID: <671963535.AA18915@flaccid> Date: 18 Apr 91 08:32:15 GMT References: <16640@chaph.usc.edu> <1991Apr17.140221.9285@athena.mit.edu> Sender: news@pyra.co.uk (News system) Reply-To: pjr@pyra.co.uk (Peter Ruczynski) Organization: Pyramid Technology Ltd, Farnborough, ENGLAND Lines: 47 In article <1991Apr17.140221.9285@athena.mit.edu> mmshah@athena.mit.edu (Milan M Shah) writes: >In article <16640@chaph.usc.edu> nagamati@aludra.usc.edu (Romklau Nagamati) writes: >>Hi Netlanders, >> >>I'm wondering whether anyone have play around with .FON file??? I'm trying >>to create a .FON file by using SDK Fonteditor to create a .FNT file. Then, >>create a dummy stub in assembly, link, and RC. >> >>I'm doing exactly what is in Chapter 18 of the SDK Guide to Programming, but >>I got the message "LINK error: L2049 no segments defined" when linking. Yeah, I had the same problem! >Nothing personal, but, Oh god, here we go again. How does one put this in the >FAQ? FLAME ON There is no need for this. Most people don't have time to read news, so questions do get repeated. It's a fact of life! As you say, perhaps this is one that needs to be put into the 'Frequently asked questions' category. (Do we have a Frequently asked questions monthly posting? I must say I haven't seen one) FLAME OFF >The above LINK error is a bug in link. The fix is to run exehdr /r on the >.exe file, and then run rc on it. The explanation I have is that link >incorrectly detects an error, and marks the resulting .exe file with some kind >of error bit, even though the rest of the exe file is ok. Exehdr /r will >reset this "error bit", after which rc will work just fine. Yes, but the fontmanager still does not recognise the .fon file as a valid .fon file. The only current (known) solution is to build a dll and use AddFontResource() with the name of your dll. (Unless, of course, someone from Microsoft would care to enlighten a few very frustrated programmers :-) >Milan Pete. -- -w--------- Pyramid Technology U.K. Peter Ruczynski ---www------- Pyramid House #include -----wwwww----- Farnborough pjr@pyra.co.uk -------wwwwwww--- Hants GU14 7PL England. Wot no funny comment :-)