Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!sdd.hp.com!wuarchive!uunet!zephyr.ens.tek.com!tektronix!reed!intelhf!ichips!iwarp.intel.com!pdxgate!eecs!mwizard
From: mwizard@eecs.cs.pdx.edu (Craig Nelson)
Newsgroups: comp.windows.ms.programmer
Subject: BC++ Classes having duplicate execution problem'
Message-ID: <2739@pdxgate.UUCP>
Date: 25 May 91 22:35:55 GMT
Sender: news@pdxgate.UUCP
Lines: 31

Hope this is the right group to post this to.  Just got BC++ about
a week ago, and it's a real kick.  I also received some two weeks
before a copy of Borland Language Express, in which several rather
general windows classes are listed.   I used these classes to write
a couple of do-nothing test programs, and here's where things get a
little weird.

	Call the first program hello1, the second hello2. Both are
seperate windows programs using the same class library (which is NOT
in a DLL).  I execute hello1, and all is well.   Then I execute hello2,
and again, all is well.  Now, if I execute hello2, then try to execute
hello1, I get another copy of hello2 on the screen.  Another interesting
point.  If I load hello2, then load TDW, then attempt to load hello1 in
the debugger it won't load.  Says somthings about an error loading file.
Now if I then quit the running version of hello2, then reload the debugger,
then ask to load hello1 in the debugger, it works and all is fine.

My question is simple.  How does Windows start up the same program from an
entirely different executable, with only the linked libraries in common ?
Better question: Why ???.  One more question:  Anyone got a solution to
this problem ?

Just occured to me that many might not have the code in BLXpress to look
over and ponder this problem.  Since it's available via Borlands download
BBS, I don't think they'd mind me giving it to all who would like it.

Thanks for any help you can give me.

Cheers

Craig.