From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: getting cancelsynchronous IO error when starting mintty.exe from Windows XP desktop shortcut
Date: Fri, 29 Jul 2016 10:39:00 -0000 [thread overview]
Message-ID: <20160729073756.GJ26311@calimero.vinschen.de> (raw)
In-Reply-To: <579A7BA7.1080408@towo.net>
[-- Attachment #1: Type: text/plain, Size: 1053 bytes --]
On Jul 28 23:39, Thomas Wolff wrote:
> Am 28.07.2016 um 22:30 schrieb Warren Young:
> > On Jul 27, 2016, at 10:00 PM, prabhakar gupta <gupta_prabhakar@hotmail.com> wrote:
> > > After getting the "installation cocmpleted" message I double clicked on the MINTTY.EXE shortcut and go the following error:
> > > "The procedure entry point cancelsynchronousio could not be located in the dynamic link libraryKERNEL32.DLL”.
> > Indeed, that Windows API function does not exist on XP:
> >
> > https://msdn.microsoft.com/library/windows/desktop/aa363794.aspx
> >
> > Does this not show that the Cygwin DLL is trying to call it?
> I've tested mintty 2.4.2 on cygwin 2.5.2 on Windows XP and it works fine
> here.
CancelSynchronousIo is dynamically loaded by the Cygwin DLL up to version
2.5.2. If loading fails, the DLL falls back to other, somewhat unsafe
code on pre-Vista.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-07-29 7:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-28 7:09 prabhakar gupta
2016-07-28 13:09 ` Douglas Coup
2016-07-28 13:14 ` Corinna Vinschen
2016-07-28 21:39 ` Warren Young
2016-07-29 7:38 ` Thomas Wolff
2016-07-29 10:39 ` Corinna Vinschen [this message]
2016-09-01 14:14 ` Fjor
2016-09-01 14:46 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160729073756.GJ26311@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).