Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-ID:	<3C4C1E0B.4050009@syntrex.com>
Date:	Mon, 21 Jan 2002 14:56:27 +0100
From:	Pavel Tsekov <ptsekov AT syntrex DOT com>
User-Agent:	Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20011126 Netscape6/6.2.1
X-Accept-Language:	en-us
MIME-Version:	1.0
To:	Tim <tjbynum AT swbell DOT net>
CC:	cygwin AT cygwin DOT com
Subject:	Re: DLL And Visual Basic
References:	<007401c1a1dc$86c1a800$fa34fea9 AT rineco DOT com>

Tim wrote:

> Ok, I've gotten a little further in my endeavors and am stumped again.
> Actually this is pretty much where I was stumped in the beginning, but I
> have made some moderate headway.
> 
> I have successfully created a dl that can be called (successfully mind you)
> from Visual Basic, but unfortunately only once.  ;-)  Any attempt to run the
> app again without first shutting it down will result in the following:
> VB6 caused an invalid page fault in
> module CYGWIN1.DLL at 0177:610066e2.


[snip]


> 
> What am I missing here?  Am I doing something wrong, or is this what I'm in
> for?
> 
> I also had to copy /usr/bin/cygwin1.dll to \windows\system in order to even
> attempt to use the newly created DLL.


Don't do this! Instead add the path to your cygwin1.dll to the PATH 
environment variable.



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -