Newsgroups: comp.windows.ms.programmer
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!think.com!mintaka!bloom-picayune.mit.edu!athena.mit.edu!mmshah
From: mmshah@athena.mit.edu (Milan M Shah)
Subject: Re: .FNT -> .FON
Message-ID: <1991Apr17.140221.9285@athena.mit.edu>
Sender: news@athena.mit.edu (News system)
Organization: Massachusetts Institute of Technology
References: <16640@chaph.usc.edu>
Date: Wed, 17 Apr 91 14:02:21 GMT
Lines: 27

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. 

Nothing personal, but, Oh god, here we go again. How does one put this in the
FAQ?

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.

Alternate fix is to use link4 from SDK 2.10

Milan
.




