Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!chinacat!uudell!twaddle.dell.com!jporter
From: jporter@twaddle.dell.com (Jeff Porter)
Newsgroups: comp.windows.ms.programmer
Subject: Re: Having an EXE and DLL of the same name
Message-ID: <15115@uudell.dell.com>
Date: 13 Feb 91 19:42:24 GMT
References: <7134@hsv3.UUCP> <15097@uudell.dell.com> <1991Feb13.151814.25905@odi.com>
Sender: news@uudell.dell.com
Reply-To: jporter@twaddle.dell.com (Jeff Porter)
Organization: Dell Computer Corp.
Lines: 20

In article <1991Feb13.151814.25905@odi.com>, ed@odi.com (Ed Schwalenberg) writes:
|> In article <15097@uudell.dell.com> jporter@twaddle.dell.com (Jeff Porter) writes:
|>   In article <7134@hsv3.UUCP>, jls@hsv3.UUCP (James Seidman) writes:
|>   |> 
|>   |> I'm probably missing something really obvious here.  I have a program
|>   |> which requires a DLL to go along with it.   I'd like to have them named
|>   |> the same (e.g. XYZPROG.EXE and XYZPROG.DLL).
|> 
|>   Windows only allows either a DLL or EXE with a given name.  It's a
|>   documented feature in the SDK manuals.
|> 
|> Oh, twaddle.  (Sorry, I couldn't resist.)
|> Look at PBRUSH.EXE/PBRUSH.DLL in your Windows directory with EXEHDR.
|> The secret is that the module name of PBRUSH.EXE is actually PBRUSHX.
|> Develop XYZPROG.DLL and XYZPROGX.EXE, then rename the latter to XYZPROG.EXE
|> before execution and you're all set.

That'll teach me to believe what I read!!! :-)

Jeff Porter