Xref: utzoo comp.lang.c:6434 comp.sys.ibm.pc:10575
Path: utzoo!mnetor!uunet!husc6!bbn!rochester!cornell!uw-beaver!mit-eddie!rutgers!mtune!westmark!dave
From: dave@westmark.UUCP (Dave Levenson)
Newsgroups: comp.lang.c,comp.sys.ibm.pc
Subject: Re: QC problems
Message-ID: <351@westmark.UUCP>
Date: 5 Jan 88 21:34:22 GMT
References: <3790@rosevax.Rosemount.COM>
Organization: Westmark, Inc., Warren, NJ, USA
Lines: 26
Keywords: MS, QC

In article <3790@rosevax.Rosemount.COM>, richw@rosevax.Rosemount.COM (Rich Wagenknecht) writes:
...
> I just can't understand
> how my software could run under QC but not as a stand alone executable.
> Has anyone else experienced anything similar?

	This sounds properly frustrating!  I suggest looking for
code that is position-dependent (under QC, you're running at a
different place in memory, aren't you?).

	Another possibility is that QC has left your memory in a
different initial state than MS-DOS does when you run your .exe
directly from command.com.  Perhaps you have an uninitialized
variable somewhere?

	You mentioned that your application makes use of graphics. 
Does QC leave the video subsystem in a different initial state than
MS-DOS does?  Is your program assuming something about its initial
environment?

	Compile it with /Zi and see how far codeview gets with it.
-- 
Dave Levenson
Westmark, Inc.		The man in the Mooney.
Warren, NJ USA
{rutgers | clyde | mtune | ihnp4}!westmark!dave