Bug 2570 - cygwin version of rsync produces "Fatal exception 0E in VXD IFSMGR(04)" on Windows 98 SE
Summary: cygwin version of rsync produces "Fatal exception 0E in VXD IFSMGR(04)" on Wi...
Alias: None
Product: rsync
Classification: Unclassified
Component: core (show other bugs)
Version: 2.6.3
Hardware: x86 Windows 98
: P3 normal (vote)
Target Milestone: ---
Assignee: Wayne Davison
QA Contact: Rsync QA Contact
Depends on:
Reported: 2005-04-02 21:47 UTC by Dan F
Modified: 2006-02-02 15:55 UTC (History)
0 users

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Dan F 2005-04-02 21:47:45 UTC
Command line:

rsync -v -c -r -t --delete --progress "/cygdrive/c/my documents" "/cygdrive/d/my

/cygdrive/c is my main drive, /cygdrive/d is an Iomega Zip drive.

On the second file, I get a blue screen with the fatal exception mentioned in
the summary.

Output in the cygwin window:


dfrankow@computer /cygdrive/c/My Documents/sysadmin
$ rsync -v -c -r -t --delete --progress "/cygdrive/c/my documents"
"/cygdrive/d/my documents"
building file list ... 
2179 files to consider
my documents/
my documents/.emacs
        7815 100%    0.00kB/s    0:00:00  (1, 0.1% of 2179)
my documents/Bertha.doc
       32768  32%  507.94kB/s    0:00:00
rsync error: received SIGUSR1 or SIGINT (code 20) at

dfrankow@computer /cygdrive/c/My Documents/sysadmin

dfrankow@computer /cygdrive/c/My Documents/sysadmin
$ rsync: writefd_unbuffered failed to write 106 bytes: phase "unknown"
[generator]: Invalid argument (22)
rsync error: error in rsync protocol data stream (code 12) at


Probably this is a Cygwin problem and not an rsync problem, but I do only see it
with rsync.

$ rsync --version
rsync  version 2.6.3  protocol version 28
Copyright (C) 1996-2004 by Andrew Tridgell and others

I found this web page that I thought might be related:


I tried unchecking the "Disconnect" checkbox as instructed, rebooting of course.
 It didn't change anything.
Comment 1 Dan F 2005-04-02 21:48:09 UTC
Oops, report my hardware and platform.
Comment 2 Dan F 2005-04-02 21:50:30 UTC
Forgot: just to let you know, after the blue screen I hit a space to return, and
the rsync just hangs.  Then I hit control-C and that's when I see

rsync error: received SIGUSR1 or SIGINT (code 20) at ...
Comment 3 Wayne Davison 2005-05-23 13:09:21 UTC
Did you report this to the Cygwin folks?  If so, any word back yet?
Comment 4 Dan F 2005-05-25 20:07:04 UTC
I am sorry, I did not.  I'm not sure where to report it.  If you know, I'd be
willing to forward it.
Comment 5 Wayne Davison 2006-02-02 15:55:27 UTC
I hope you googled for the cygwin mailing lists on your own instead of waiting for a slow reply from me.  If not, here is where you can access the cygwin mailing lists:


I'm going to resolve this as "LATER" since this doesn't appear to be a bug in rsync, and this is what I'm using to mean "the bug is outside of rsync, so evaluate the outside fix at a later date".