From: Vince Rice <vrice@solidrocksystems.com>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: CancelSynchronousIo could not be located in the dynamic link library KERNEL32.dll
Date: Mon, 24 Oct 2016 21:07:00 -0000 [thread overview]
Message-ID: <62B2E535-90D5-459A-AFB7-D70D87CA4FC3@solidrocksystems.com> (raw)
In-Reply-To: <580E28B7.7000009@gmail.com>
> On Oct 24, 2016, at 10:28 AM, Keith Williams <keith.dev.uk@gmail.com> wrote:
>
> I've read the FAQ. I feel the matter isn't resolved and I haven't been able to use Cywin/XP for a while/
>
> Has anyone tried installing Cygwin on Windows XP? The installation doesn't work because the applications seem to be linked with newer Windows run-time libs. Bash and dash do not work for example, they're looking for the missing kernel call, CancelSynchronousIo.
>
> I don't seem able to go back to a working system from the upgrade, and a new installation doesn't work.
>
> Given that 32bit Windows 7 and Vista have been around for years, why was it decided to drop support for Windows XP? Presumably, there's nothing much to be gained by doing this.
XP support was dropped in 2.6. If you upgraded to 2.6.x on XP, you didn’t read the release notes very well.
> I uploaded a new Cygwin release 2.6.0-1.
>
> Please note that this release won't work on Windows XP and Windows
> Server 2003 or 2003 R2. At least Windows Vista or Windows Server 2008
> are required.
Google “cygwin time machine”; it may get you what you need.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2016-10-24 15:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-24 15:47 Keith Williams
2016-10-24 21:07 ` Vince Rice [this message]
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=62B2E535-90D5-459A-AFB7-D70D87CA4FC3@solidrocksystems.com \
--to=vrice@solidrocksystems.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).