🚀 go-pugleaf

In article <BzA2sp.199@newsserver.technet.sg> ipser@solomon.technet.sg (Ed Ipser) writes:
>In article <1gilfkINNjmd@crcnis1.unl.edu> chaddan@cse.unl.edu (Christopher Haddan) writes:
>>rmccown@world.std.com (Bob McCown) writes:
>>
>>>In article ... chaddan@cse.unl.edu (Christopher Haddan) writes:
>>>>8910782@sunvax.sun.ac.za (Roger) writes:
>>>[lots o' stuff deleted...]
>>>>
>>>>Ummmmm, why don't you run in a dos box? That way you have DPMI 
>>>>support w/o 386Max and exec'ing your app is just a click away.
>>
>>>There's a problem with this.  I'm writing a DLL to be called from a VB
>>>program, and it seems once I load the DLL once, until I unload windows
>>>from the machine, it keeps the original copy in memory.
>>
>>This is true, I have encountered the same problem.
>
>So how come I don't encounter this problem under Borland C++? I use the
>ID and I've developed an application and two DLLs on which it depends.
>I can make changes to the DLLs or the the application and then run the
>application and test the results all within the same windows session.
>
>Is the above perhaps a "feature" of MSC++?

Possibly the calling program is not a VBasic program.  You dont have the
ability to 'LoadModule' in VB, so you cant unload it when you're done.
-- 
|  Bob McCown / Mundane - Robur of Roestoc / SCA - Sir Gaath Gazul / NERO  |
|  rmccown@world.std.com                                                   |
|  "'ow d'you know 'e's a king?" "'cause 'e 'asn't got shit all over 'im!  |
|									   |