Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!zaphod.mps.ohio-state.edu!uwm.edu!psuvax1!rutgers!rochester!kodak!atexnet!cvbnet!feds19!jshekhel
From: jshekhel@feds19.prime.com (Jerry Shekhel )
Newsgroups: comp.windows.ms
Subject: Re: 3.0 SDK problems
Message-ID: <682@cvbnetPrime.COM>
Date: 24 Jul 90 15:29:29 GMT
References: <26093@usc.edu>
Sender: postnews@cvbnetPrime.COM
Reply-To: jshekhel@feds19.UUCP (Jerry Shekhel )
Organization: Prime Computervision, Bedford MA
Lines: 22

In article <26093@usc.edu> papa@pollux.usc.edu (Marco Papa) writes:
>
>3.  The major problem is with the 5.10 linker.  It just plain doesn't
>work.  It doesn't seem to be able to pick up ANY of the Windows library
>symbols and tells me that all the ones I use (174) are undefined, and
>then aborts.
>
>Has anybody gotten the 5.10 Linker to work with the 3.0 SDK?
>

Well, believe it or not, there are 2 different linkers on the C 5.1
distribution diskettes.  The installation program copies the Version 3.xx
linker you mentioned.  However, if you look around, you'll find a
Version 5.0x linker on one of the Utilities diskettes.  It comes up
as "Microsoft Segmented-Executable Linker, Version 5.0x", or something
like that.  This one works great with Windows.

>
>-- Marco
>

-- Jerry