Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!usc!ucsd!nosc!logicon.com!trantor.harris-atd.com!trantor!dsampson From: dsampson@x102a.harris-atd.com (sampson david 58163) Newsgroups: comp.windows.ms Subject: Re: 3.0 SDK problems Message-ID: Date: 24 Jul 90 12:28:13 GMT References: <26093@usc.edu> <3543@tuminfo1.lan.informatik.tu-muenchen.dbp.de> Sender: news@trantor.harris-atd.com Organization: Harris Gov't Aerospace Systems Division Lines: 28 In-reply-to: rommel@lan.informatik.tu-muenchen.dbp.de's message of 23 Jul 90 17:20:35 GMT In article <3543@tuminfo1.lan.informatik.tu-muenchen.dbp.de> rommel@lan.informatik.tu-muenchen.dbp.de (Kai-Uwe Rommel) writes: >Hey, look at your C 5.10 distribution disks. You should find there two >copies of LINK.EXE. One is the OLDOLDOLDOLD 3.65 DOS-only linker which >cannot be used to create segmented-executables. The other one is >5.0.17 (or so) and can be used (I do this every day ...) You are ABSOLUTLY correct. It took about three days on the phone with the sdk support people, but this was resolved. When you install MSC 5.1 it doesn't put the sdk compatible linker on your hard drive. The linker that is compatible is on disk 5 (Utilities 1, I think). After copying that file over, everything worked smoothly. The MS people said the linker should be version 5.01.21 or later for the windows 3.0 sdk. David -- ------------------------------------------------------------------------------- David Sampson Harris Corporation dsampson@x102a.ess.harris.com Gov't Aerospace Systems Divison uunet!x102a!dsampson Melbourne, Florida -------------------------------------------------------------------------------