home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.os2.programmer
- Path: sparky!uunet!decwrl!pa.dec.com!nntpd2.cxo.dec.com!dlj.enet.dec.com!jennings
- From: jennings@dlj.enet.dec.com (Dave Jennings -- Digital Equipment Corp.)
- Subject: Re: Problems in DOS boxes with link.exe from Microswift (sic)
- Message-ID: <1992Nov12.134310.12427@nntpd2.cxo.dec.com>
- Sender: usenet@nntpd2.cxo.dec.com (USENET News System)
- Organization: Digital Equipment Corporation
- References: <1992Nov12.103855.1752@jetsun.weitek.COM>
- Distribution: na
- Date: Thu, 12 Nov 1992 15:42:47 GMT
- Lines: 34
-
-
- In article <1992Nov12.103855.1752@jetsun.weitek.COM>, maynard@jetsun.weitek.COM (Michael P. Maynard) writes...
- >I have recently adopted OS/2 2.x as my development platform.
- >I need to use Microsoft's Version 7.0 C/C++ compiler. The
- >compiler compiles, but the linker will not link. If I simply
- >execute the linker from the DOS command line, to wit:
- >
- > c> link
- >
- >OS/2 reports that an access violation occurred at 00010224.
- >I have applied all known patches (thru version 5.31.009) from
- >the Microsoft Developer's CD. At this point I don't know
- >whether link does this under native DOS 5.0 and because of
- >the lack of protection it is overlooked, or whether it is
- >just another buggy software release.
- >
- >This seems like I may have overlooked something, perhaps.
- >It just doesn't seem like invoking link without command
- >line parameters should do this.
- >
- >So, I put to you, anyone ... any ideas ?
- >
- >puzzled,
- >
- >Michael
-
- You need to have the DPMI_? DOS setting in the ENABLED state and not the
- default AUTO state.
-
- Works for me.
-
- ---
- Dave Jennings -- jennings@dlj.enet.dec.com
- ---
-