Path: utzoo!utgpu!watserv1!watmath!att!pacbell!pacbell.com!ucsd!swrinde!zaphod.mps.ohio-state.edu!mips!apple!snorkelwacker!bloom-beacon!eru!hagbard!sunic!mcsun!unido!gmdzi!strobl From: strobl@gmdzi.UUCP (Wolfgang Strobl) Newsgroups: comp.windows.ms Subject: Re: WHO, WHAT, WHERE REGARDING: WINDOWS 3.0 Message-ID: <3319@gmdzi.UUCP> Date: 8 Sep 90 20:17:19 GMT References: <8639@orca.wv.tek.com> <26055@cs.yale.edu> Organization: GMD, Sankt Augustin, F. R. Germany Lines: 23 spolsky-joel@cs.yale.edu (Joel Spolsky) writes: >In article <8639@orca.wv.tek.com> mhorne%hss.pdx.com@uunet.uu.net writes: >> - Is there a decent (commercial) developers package available for >> Windows 3.0? If so, where can I obtain it and how much is it? >The Microsoft Software Development Kit is pretty much a must; it is >$500 list (about $350 from mail order shops). Make sure you get >version 3.0! You will also need Microsoft C. It IS possible to use >other C compilers by begging Microsoft for their object file >compatability disk. This does not include Turbo C. I am not quite sure that I understand this. I am using Zortech C++ 2.1 for some time now to create Windows programs which run under Windows 2 and 3, using the 2.1 SDK (the 3.0 SDK hasn't arrived here, yet). I have never heard about an "object file compatibility disk". I simply use the LINK4 from the SDK or some of the OS/2 linkers instead of the BLINK from Zortech and, of course, the SDK libraries. So, please tell me, what is the purpose of this object file compatibility disk? Wolfgang Strobl #include