Path: utzoo!attcan!uunet!mcsun!unido!gmdzi!strobl
From: strobl@gmdzi.UUCP (Wolfgang Strobl)
Newsgroups: comp.windows.ms
Subject: Re: Zortech C++ classes for Windows
Keywords: windows zortech
Message-ID: <2518@gmdzi.UUCP>
Date: 7 Jun 90 17:19:50 GMT
References: <74771@ccicpg.UUCP> <2510@gmdzi.UUCP> <2513@gmdzi.UUCP> <6629@umd5.umd.edu>
Organization: GMD, Sankt Augustin, F. R. Germany
Lines: 27

brianf@umd5.umd.edu (Brian Farmer) writes:

>	There was an extra link included with MSC 5.1 for use
>	with OS 2 but that didn't get installed if you only 
>	installed for DOS.  I don't remember which disk it is
>	on but the size is about 110k and is called LINK. 

>	You can use this linker just like LINK4 except you need
>	to include the line 'EXETYPE WINDOWS' in your .def files.

I do not have MSC 5.1, but I have IBM C/2 1.1, which is essentially
the same compiler (at least it has excactly the same bugs :)
Its LINK.EXE (107 230 Bytes) has no documented EXETYPE statement
in the Module Definition FIle, but understands it anyway.
I had tried this LINK.EXE before, without the EXETYPE statement.
It is not necessary for producing MS Windows programs. But with this
LINK (instead of the 5.01 LINK4) my virtual member functions do not
work, either. I tried your suggestion anyway. With this statement
included in the .DEF file, the linkage editor produces a .EXE file
of exacly the same length, with only one bit changed (offset 40a,
from B6 to B7). The EXEHDR utility doesn't know this bit, and it
has no noticeable effect.

Does anybody out there have an LINK4 version 5.02 or later? How
old is it (time stamp)? From which SDK version is it?

Wolfgang Strobl