On Jan 12 11:54, Ismail Donmez wrote:
> On Tue, Jan 12, 2016 at 11:50 AM, Corinna Vinschen
> <corinna-cygwin@cygwin.com> wrote:
> > On Jan 12 11:45, Ismail Donmez wrote:
> >> Hi,
> >>
> >> On Tue, Jan 12, 2016 at 11:28 AM, Corinna Vinschen
> >> <corinna-cygwin@cygwin.com> wrote:
> >> > Hi Ismail,
> >> >
> >> > On Jan 12 10:23, Ismail Donmez wrote:
> >> >> Hi,
> >> >>
> >> >> -0.17 was fine but this release breaks sshd, sshd.log says:
> >> >>
> >> >> 1 [main] sshd 2828 C:\cygwin64\usr\sbin\sshd.exe: *** fatal error - unable
> >> >> to load C:\Windows\system32\ws2_32.dll, Win32 error 1001
> >> >
> >> > What OS?  32 bit, 32 bit under WOW64 or 64 bit?  How do you start sshd?
> >>
> >> Sorry for the brevity of my bug report. This is on Windows 7 SP1
> >> 64-bit with cygwin 64bit.
> >>
> >> > I'm asking because
> >> >
> >> > a) What I did was to revert a piece of code to the same state as in 2.2.1.
> >> >    Does the "prev" version 2.2.1 work for you?
> >>
> >> I am always running cygwin snapshots on this machine and yesterday
> >> -0.17 was working fine. Now I rolled backed to 2.2.1-1 and it works
> >> fine. Went a little bit further and cygwin1-20160109.dll works fine
> >> where-as cygwin1-20160111.dll shows the problem.
> >
> > Still, does 2.2.1 work for you, too?
> 
> Quoting my email "Now I rolled backed to 2.2.1-1 and it works fine."

That's what time pressure does to my reading skills... sorry :}

This is a bit weird.  If 2.2.1 using the same method works, why not
2.4.0-0.18?!?

I tried to workaround this problem by "upgrading" the DLL load
mechanism to use the facilities available since Vista.  In theory
this should work fine for you.  I uploaded a new developer snapshot
to https://cygwin.com/snapshots/  Please give it a try.


Thanks,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat