RE: Error: procedure entry point in cygwin1.dll

RE: Error: procedure entry point in cygwin1.dll

[Orrigo, Giampaolo .]

Here another one:

QVTNet 5.1.2 (QPC Software, www.qpc.com) ships with cygwin1.dll version
1.3.5 and with cygz.dll

> On Sat, Dec 06, 2003 at 07:24:29PM -0500, Jack Tanner wrote:
> >Rasjid Wilcox wrote:
> >>C:\>dir /s > filelist.txt
> >>C:\>start wordpad filelist.txt
> >>
> >>Do an edit/find for 'cygwin1.dll'.  See if you have more than one.  (In 
> >>case the Windows find file missed it for some reason.)
> >
> >Better:
> >
> >dir cygwin1.dll /s /a /b
> >
> >/a will catch cygwin1.dll even if it should be marked as a hidden or 
> >system file, and /b will optimize the output format (one line per file).
> 
> What's wrong with using the Windows Find/Search utility?
> 
> >Off topic: I just tried that on my machine and I found that CDRDAO ships 
> >a cygwin1.dll with their Windows build (I have version 1.1.7). If 
> >someone is in the habit of slapping wrists for that sort of thing, 
> >there's your cue.
> 
> I need a better cue than that.  Where did you get the binary?

Re: Error: procedure entry point in cygwin1.dll

[Christopher Faylor]

On Sat, Dec 06, 2003 at 08:07:35PM -0500, Orrigo, Giampaolo . wrote:
>Here another one:
>
>QVTNet 5.1.2 (QPC Software, www.qpc.com) ships with cygwin1.dll version
>1.3.5 and with cygz.dll

And no source...?

cgf

Re: Error: procedure entry point in cygwin1.dll

[Christopher Faylor]

On Tue, Dec 09, 2003 at 08:22:21PM +1100, Rasjid Wilcox wrote:
>On Tuesday 09 December 2003 19:33, Martin Schmid wrote:
>>The Windows XP explorer really seems to have a problem finding files
>>:-(
>
>That has been my experience, and it seems, the experience of a number
>of others on the list.

It's odd that this is the very first time I've heard that XP find doesn't
find files in system directories.  I guess that's one for the FAQ.

cgf

Re: Error: procedure entry point in cygwin1.dll

[Rasjid Wilcox]

On Tuesday 09 December 2003 19:33, Martin Schmid wrote:
> The Windows XP explorer really seems to have a problem finding files :-(

That has been my experience, and it seems, the experience of a number of 
others on the list.

No doubt there is a magic combinaiton of 'tick this box' and 'untick that 
box', and it will all work fine.  And people that already have that magic 
combination will not see any problems.

Personally, I liked Jack Tanners:

dir cygwin1.dll /s /a /b

solution.  Seems guaranteed to work regardless of what options are ticked or 
otherwise.

Cheers,

Rasjid.

-- 
Rasjid Wilcox
Canberra, Australia (UTC +10 hrs)
http://www.openminddev.net

Re: Error: procedure entry point in cygwin1.dll

[Martin Schmid]

Hello Rasjid

Thanks for your tip which was not daft at all, since cygwin was actually
running, I just couldn't start xfree from the cygwin shell.
In fact, the cygwin find utility did find another copy of cygwin1.dll in the
c:\windows folder, and deleting this file did solve the problem. Before
deleting it, I repeated trying to find this file with the Windows XP Explorer.
The first try was searching in C:, which failed to find c:\windows\cygwin1.dll
but found C:\cygwin\cygwin1.dll (sic!), then I tried searching in C:\windows
(without changing anything else), and this time c:\windows\cygwin1.dll was
found.
The Windows XP explorer really seems to have a problem finding files :-(

Cheers, Martin

>On Saturday 06 December 2003 11:02, Rasjid Wilcox wrote:
>> Have you tried using the cygwin find utility instead?
>That has to be one of the daftest things I've ever said on a public
mailling 
>list, since cygwin is not working.  I would suggest the following instead:
>In a cmd shell - 
>C:\>dir /s > filelist.txt
>C:\>start wordpad filelist.txt
>Do an edit/find for 'cygwin1.dll'.  See if you have more than one.  (In
case 
>the Windows find file missed it for some reason.)
>Cheers,
>Rasjid.

-- 
+++ GMX - die erste Adresse für Mail, Message, More +++
Neu: Preissenkung für MMS und FreeMMS! http://www.gmx.net

Re: Error: procedure entry point in cygwin1.dll

[Harold L Hunt II]

Christopher Faylor wrote:

> On Sun, Dec 07, 2003 at 05:31:57PM -0500, Harold L Hunt II wrote:
> 
>>The overall point to be taken home here is that you can't trust the 
>>search facility in XP unless you are prepared to ask people if they have 
>>done things in a very specific way *and* you are prepared to trust their 
>>response to those questions.  It ends up being a huge waste of time when 
>>you could instead run a command-line search and be done with it.
> 
> 
> I'm pretty certain that using the search facility in XP for the purpose
> of searching for duplicate cygwin1.dll's should work just fine.

Again, it might work in this case.  But, I'm talking about reasons for 
using a different approach that works in all cases.  It really doesn't 
matter though.

> Using cygwin's command-line search in a scenario where cygwin doesn't
> work is obviously not going to work and using dir/s is rather laborious
> and error-prone if you have multiple drives.

I guess.

> In the many years of advising people to use GUI utility, I've never
> heard anyone say that they failed to find what they were looking for
> with this method.

Well, many years of prior experience doesn't really matter since I am 
complaining about the broken search functionality in XP, which isn't 
many years old :)  Search did work fine in Windows until XP, but now it 
has a lot of caveats, and I am not good at remembering caveats.

Harold

Re: Error: procedure entry point in cygwin1.dll

[Christopher Faylor]

On Sun, Dec 07, 2003 at 05:31:57PM -0500, Harold L Hunt II wrote:
>The overall point to be taken home here is that you can't trust the 
>search facility in XP unless you are prepared to ask people if they have 
>done things in a very specific way *and* you are prepared to trust their 
>response to those questions.  It ends up being a huge waste of time when 
>you could instead run a command-line search and be done with it.

I'm pretty certain that using the search facility in XP for the purpose
of searching for duplicate cygwin1.dll's should work just fine.

Using cygwin's command-line search in a scenario where cygwin doesn't
work is obviously not going to work and using dir/s is rather laborious
and error-prone if you have multiple drives.

In the many years of advising people to use GUI utility, I've never
heard anyone say that they failed to find what they were looking for
with this method.

cgf

Re: Error: procedure entry point in cygwin1.dll

[Harold L Hunt II]

Jack Tanner wrote:
> Harold L Hunt II wrote:
> 
>> It works fine in Windows 2000, but they broke it horribly in Windows 
>> XP when they "extended" it to ignore certain directories and types of 
>> files.  You have to jump through all sorts of hoops and enable the 
>> indexing service in order to get it to search all files in XP.  So, 
>> the results of the utility cannot be trusted in XP.
> 
> 
> What's wrong with Start, Search, All files and folders, Look in Local 
> Hard Drives? I just tested it on XP SP1, it worked well. Doesn't it get 
> around what you describe if you click "All files and folders" instead of 
> "Pictures, music, or video" or "Documents"?

Nope, doesn't work, at least not in the cases that I use the most, but 
might not be entirely relevant to the discussion at hand.  The case I am 
referring to is when you are searching for text in a file, which is a 
little different than what we are talking about here.  In that case, you 
have to configure the indexing service specially and turn it on in order 
to be able to search through .c and .h files (and all the other files a 
programmer would use) without having Visual Studio .NET installed (which 
I think installs handlers that allow some of these file types to be 
searched.

The overall point to be taken home here is that you can't trust the 
search facility in XP unless you are prepared to ask people if they have 
done things in a very specific way *and* you are prepared to trust their 
response to those questions.  It ends up being a huge waste of time when 
you could instead run a command-line search and be done with it.

Harold

Re: Error: procedure entry point in cygwin1.dll

[Jack Tanner]

Harold L Hunt II wrote:
> It works fine in Windows 2000, but they broke it horribly in Windows XP 
> when they "extended" it to ignore certain directories and types of 
> files.  You have to jump through all sorts of hoops and enable the 
> indexing service in order to get it to search all files in XP.  So, the 
> results of the utility cannot be trusted in XP.

What's wrong with Start, Search, All files and folders, Look in Local 
Hard Drives? I just tested it on XP SP1, it worked well. Doesn't it get 
around what you describe if you click "All files and folders" instead of 
"Pictures, music, or video" or "Documents"?

-JT

Re: Error: procedure entry point in cygwin1.dll

[Jack Tanner]

Christopher Faylor wrote:
> What's wrong with using the Windows Find/Search utility?

Nothing; it's capable of the same thing, but you have to explicitly turn 
on "Show hidden and system files" in Folder Options (in case the dll is 
on the drive, but hidden from view because of attributes). In another 
sense, the Windows Search utility is actually better because you can 
search multiple drives at once, whereas with the CLI, you have to repeat 
the dir command for every drive.

>>Off topic: I just tried that on my machine and I found that CDRDAO ships 
>>a cygwin1.dll with their Windows build (I have version 1.1.7). If 
>>someone is in the habit of slapping wrists for that sort of thing, 
>>there's your cue.
> 
> I need a better cue than that.  Where did you get the binary?

http://cdrdao.sourceforge.net/ is the main site;
http://sourceforge.net/projects/cdrdao/ is the download page where 1.1.7 
is available. The main developer is Andreas Mueller (andreasm at 
users.sourceforge.net), but since it's a SourceForge-hosted project, 
they have a bug db available through the site.

Best,
JT

Re: Error: procedure entry point in cygwin1.dll

[Harold L Hunt II]

Christopher Faylor wrote:
> On Sat, Dec 06, 2003 at 07:24:29PM -0500, Jack Tanner wrote:
> 
>>Rasjid Wilcox wrote:
>>
>>>C:\>dir /s > filelist.txt
>>>C:\>start wordpad filelist.txt
>>>
>>>Do an edit/find for 'cygwin1.dll'.  See if you have more than one.  (In 
>>>case the Windows find file missed it for some reason.)
>>
>>Better:
>>
>>dir cygwin1.dll /s /a /b
>>
>>/a will catch cygwin1.dll even if it should be marked as a hidden or 
>>system file, and /b will optimize the output format (one line per file).
> 
> 
> What's wrong with using the Windows Find/Search utility?

It works fine in Windows 2000, but they broke it horribly in Windows XP 
when they "extended" it to ignore certain directories and types of 
files.  You have to jump through all sorts of hoops and enable the 
indexing service in order to get it to search all files in XP.  So, the 
results of the utility cannot be trusted in XP.

Harold

Re: Error: procedure entry point in cygwin1.dll

[Christopher Faylor]

On Sat, Dec 06, 2003 at 07:24:29PM -0500, Jack Tanner wrote:
>Rasjid Wilcox wrote:
>>C:\>dir /s > filelist.txt
>>C:\>start wordpad filelist.txt
>>
>>Do an edit/find for 'cygwin1.dll'.  See if you have more than one.  (In 
>>case the Windows find file missed it for some reason.)
>
>Better:
>
>dir cygwin1.dll /s /a /b
>
>/a will catch cygwin1.dll even if it should be marked as a hidden or 
>system file, and /b will optimize the output format (one line per file).

What's wrong with using the Windows Find/Search utility?

>Off topic: I just tried that on my machine and I found that CDRDAO ships 
>a cygwin1.dll with their Windows build (I have version 1.1.7). If 
>someone is in the habit of slapping wrists for that sort of thing, 
>there's your cue.

I need a better cue than that.  Where did you get the binary?

Re: Error: procedure entry point in cygwin1.dll

[Jack Tanner]

Rasjid Wilcox wrote:
> C:\>dir /s > filelist.txt
> C:\>start wordpad filelist.txt
> 
> Do an edit/find for 'cygwin1.dll'.  See if you have more than one.  (In case 
> the Windows find file missed it for some reason.)

Better:

dir cygwin1.dll /s /a /b

/a will catch cygwin1.dll even if it should be marked as a hidden or 
system file, and /b will optimize the output format (one line per file).

Off topic: I just tried that on my machine and I found that CDRDAO ships 
a cygwin1.dll with their Windows build (I have version 1.1.7). If 
someone is in the habit of slapping wrists for that sort of thing, 
there's your cue.

Best,
JT

Re: Error: procedure entry point in cygwin1.dll

[Rasjid Wilcox]

On Saturday 06 December 2003 11:02, Rasjid Wilcox wrote:
> Have you tried using the cygwin find utility instead?

That has to be one of the daftest things I've ever said on a public mailling 
list, since cygwin is not working.  I would suggest the following instead:

In a cmd shell - 

C:\>dir /s > filelist.txt
C:\>start wordpad filelist.txt

Do an edit/find for 'cygwin1.dll'.  See if you have more than one.  (In case 
the Windows find file missed it for some reason.)

Cheers,

Rasjid.

-- 
Rasjid Wilcox
Canberra, Australia (UTC +10 hrs)
http://www.openminddev.net

Re: Error: procedure entry point in cygwin1.dll

[Christopher Faylor]

On Sat, Dec 06, 2003 at 11:02:51AM +1100, Rasjid Wilcox wrote:
>On Saturday 06 December 2003 01:58, Christopher Faylor wrote:
>>On Fri, Dec 05, 2003 at 11:37:19AM +0100, Martin Schmid wrote:
>>>I do trust the wisdom of the archives, that's why I checked my whole
>>>hard disk for any other copy of cygwin1.dll, and why I rebooted three
>>>times before posting the message.
>>
>>That would have been an interesting thing to mention in your first
>>problem report.
>>
>>>There definitely must be another reason for the problem.  Any
>>>suggestion?
>>
>>There are no other reasons for the problem.
>
>I am probably displaying my complete ignorance of dll's here, but is it
>possible for this problem to occur even if the second 'cygwin1.dll' as
>been named something different?

No.

Re: Error: procedure entry point in cygwin1.dll

[Rasjid Wilcox]

On Saturday 06 December 2003 01:58, Christopher Faylor wrote:
> On Fri, Dec 05, 2003 at 11:37:19AM +0100, Martin Schmid wrote:
> >I do trust the wisdom of the archives, that's why I checked my whole
> >hard disk for any other copy of cygwin1.dll, and why I rebooted three
> >times before posting the message.
>
> That would have been an interesting thing to mention in your first
> problem report.
>
> >There definitely must be another reason for the problem.  Any
> >suggestion?
>
> There are no other reasons for the problem.

I am probably displaying my complete ignorance of dll's here, but is it 
possible for this problem to occur even if the second 'cygwin1.dll' as been 
named something different?

Also, Martin, I assume that you used the Windows Find Files search funciton.  
Have you tried using the cygwin find utility instead?  I have on occasions 
found the Windows find files search function to skip whole directories for no 
apparent reason.

Cheers,

Rasjid.

-- 
Rasjid Wilcox
Canberra, Australia (UTC +10 hrs)
http://www.openminddev.net

Re: Error: procedure entry point in cygwin1.dll

[Christopher Faylor]

On Fri, Dec 05, 2003 at 11:37:19AM +0100, Martin Schmid wrote:
>I do trust the wisdom of the archives, that's why I checked my whole
>hard disk for any other copy of cygwin1.dll, and why I rebooted three
>times before posting the message.

That would have been an interesting thing to mention in your first
problem report.

>There definitely must be another reason for the problem.  Any
>suggestion?

There are no other reasons for the problem.

Possibly following the guidelines at: http://cygwin.com/problems.html
will provide a clue.

cgf

Re: Error: procedure entry point in cygwin1.dll

[Martin Schmid]

Hello all

Thanks, Christopher, for your answer

I do trust the wisdom of the archives, that's why I checked my whole hard
disk for any other copy of cygwin1.dll, and why I rebooted three times before
posting the message.
There definitely must be another reason for the problem.
Any suggestion?

Martin



On Thu, Dec 04, 2003 at 01:23:38PM +0100, Martin Schmid wrote:
>Hello
>
>I try running xfree/cygwin on a PC with Windows XP. When I try to start
>xfree either directly from the windows explorer with startxwin.bat or from
a
>cygwin bash or csh shell with startxwin.sh, I always get the error:
>
>The procedure entry point __getreent could not be located in the dynamic
>link library cygwin1.dll
>
>I have made a search in previous messages and they most of them suggest
that
>similar errors are usually caused by having several versions of cygwin1.dll
>or an outdated version of this file. However I have only one version of
>cygwin1.dll on my hard disk, the one that came with cygwin 1.5.5-1 which is
>dated
>to 20.09.03 You should trust the wisdom of the archives.  You either have
two versions
of the DLL around, or you need to reboot.  There are no other reasons for
this problem.
--
Please use the resources at cygwin.com rather than sending personal email.
Special for spam email harvesters: send email to aaaspam@sourceware.org
and be permanently blocked from mailing lists at sources.redhat.com

-- 
+++ GMX - die erste Adresse für Mail, Message, More +++
Neu: Preissenkung für MMS und FreeMMS! http://www.gmx.net

Re: Error: procedure entry point in cygwin1.dll

[Christopher Faylor]

On Thu, Dec 04, 2003 at 01:23:38PM +0100, Martin Schmid wrote:
>Hello
>
>I try running xfree/cygwin on a PC with Windows XP. When I try to start
>xfree either directly from the windows explorer with startxwin.bat or from a
>cygwin bash or csh shell with startxwin.sh, I always get the error:
>
>The procedure entry point __getreent could not be located in the dynamic
>link library cygwin1.dll
>
>I have made a search in previous messages and they most of them suggest that
>similar errors are usually caused by having several versions of cygwin1.dll
>or an outdated version of this file. However I have only one version of
>cygwin1.dll on my hard disk, the one that came with cygwin 1.5.5-1 which is
>dated
>to 20.09.03

You should trust the wisdom of the archives.  You either have two versions
of the DLL around, or you need to reboot.  There are no other reasons for
this problem.
--
Please use the resources at cygwin.com rather than sending personal email.
Special for spam email harvesters: send email to aaaspam@sourceware.org
and be permanently blocked from mailing lists at sources.redhat.com

Error: procedure entry point in cygwin1.dll

[Martin Schmid]

Hello

I try running xfree/cygwin on a PC with Windows XP. When I try to start
xfree either directly from the windows explorer with startxwin.bat or from a
cygwin bash or csh shell with startxwin.sh, I always get the error:

The procedure entry point __getreent could not be located in the dynamic
link library cygwin1.dll

I have made a search in previous messages and they most of them suggest that
similar errors are usually caused by having several versions of cygwin1.dll
or an outdated version of this file. However I have only one version of
cygwin1.dll on my hard disk, the one that came with cygwin 1.5.5-1 which is
dated
to 20.09.03

Has anyone another suggestion for the cause of the problem?

Thanks, Martin

-- 
+++ GMX - die erste Adresse für Mail, Message, More +++
Neu: Preissenkung für MMS und FreeMMS! http://www.gmx.net




-- 
+++ GMX - die erste Adresse für Mail, Message, More +++
Neu: Preissenkung für MMS und FreeMMS! http://www.gmx.net