Greetings,

I've discovered that 5.25" and 3.5" floppy drive access became broken
as of Cygwin1.dll version 1.7.19-1 (2013-06-05 01:07:23).  I reported
this back in October, but perhaps the message never got through. The
problem persists with the latest version.

I tested by updating all my packages to current as of 2014-05-07, then
simply swapping cygwin1.dll with older versions.

cygwin1.dll 1.7.29-1 (2014-02-09 13:07:01 - LATEST)

$ dd if=/dev/fd1 of=./junk count=1
dd: opening `/dev/fd1': Bad address

cygwin1.dll 1.7.19-1 (2013-06-05 01:07:23)

$ dd if=/dev/fd1 of=./junk count=1
dd: opening `/dev/fd1': Bad address

cygwin1.dll 1.7.18-1 (2013-04-19 01:40:41)

$ dd if=/dev/fd1 of=./junk count=1
1+0 records in
1+0 records out
512 bytes (512 B) copied, 2.83143 s, 0.2 kB/s

In all cases, the drive motor is activated and the light comes on.
Note that the problem manifests identically for both 3.5" floppy
drive (/dev/fd0) and 5.25" floppy drive (/dev/fd1) access.

I'm attaching the release notes for quick reference, and below that, my
cygcheck output as recommended by http://cygwin.com/problems.html.

~ Sean

-------------------------------
http://www.cygwin.com/cygwin-ug-net/ov-new1.7.html

What's new and what changed from 1.7.18 to 1.7.19

 Drop support for Windows 2000 and Windows XP pre-SP3.

 Add support for building a 64 bit version of Cygwin on x86_64 natively.

 Add support for creating native NTFS symlinks starting with Windows
Vista by setting the CYGWIN=winsymlinks:native or
CYGWIN=winsymlinks:nativestrict option.

 Add support for AFS filesystem.

 Preliminary support for mandatory locking via fcntl/flock/lockf, using
Windows locking semantics. New F_LCK_MANDATORY fcntl command.

 New APIs: __b64_ntop, __b64_pton, arc4random, arc4random_addrandom,
arc4random_buf, arc4random_stir, arc4random_uniform.

-------------------------------
cygcheck -s -v -r > cygcheck.out