Path: utzoo!attcan!uunet!decwrl!wuarchive!zaphod.mps.ohio-state.edu!rpi!bu.edu!snorkelwacker!bloom-beacon!eru!hagbard!sunic!news.funet.fi!funic!santra!tuura!risto
From: risto@tuura.UUCP (Risto Lankinen)
Newsgroups: comp.windows.ms
Subject: Re: MessageBox problem
Message-ID: <770@tuura.UUCP>
Date: 24 Sep 90 07:17:32 GMT
References: <1990Sep12.043315.10404@Neon.Stanford.EDU> <1990S <767@tuura.UUCP> <7928@milton.u.washington.edu>
Organization: Nokia Data Systems Oy
Lines: 30

efowler@milton.u.washington.edu (Eric Fowler) writes:

>Netlanders:
>	I have been fighting a losing battle with the MSC 5.1 linker for
>several days now.  I have some windows code that compiles, links, and
>executes flawlessly on my computer at work, a standard 386/33 clone. 
>The same code with the same makefile(and the same .rc, .def, .h, and
>.lib's) fails to link on the Epson Equity 386/20 that I have at home. 
>The error returned by the linker is always "Warning:No stack segment",
>followed by:"Unresolved external:", and either 23 or 36 functions.  The

Hi!

This may sound far too trivial to be the solution, but I think it could
be given a try...  There was a problem similar to this which was solved
by making sure that the LINK.EXE was the product's 'own' version, but
not the one which is usually packed with MS-DOS .  Try renaming the
LINK.EXE in the DOS-directory to something else (I'm using LINK!.EXE).

The problem focuses to the functions in the WINDOWS.H probably because
their 'executable' is in import libraries (as opposed to traditional
object libraries), whose packing method the too old a linker cannot
resolve.

Terveisin: Risto Lankinen
-- 
Risto Lankinen / product specialist ***************************************
Nokia Data Systems, Technology Dept *  2                              2   *
THIS SPACE INTENTIONALLY LEFT BLANK * 2 -1 is PRIME!  Now working on 2 +1 *
replies: risto@yj.data.nokia.fi     ***************************************