This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Windows7 broke DRIVELETTER:/path on cmdline of non-cygwin exe


A user has just replaced their WindowsXP computer with a
Windows7 computer and installed cygwin on it. The Windows
XP computer also had cygwin on it.

One use we have for cygwin (apart from openssh) is the
ability to write bash aliases and functions in ~/.bashrc to
launch various programmes that are executed by a non-cygwin

The command lines contain directory paths like "F:/import"
which the non-cygwin python programme can interpret.

On the Windows XP computer, this works. On the Windows 7
computer, after entering the command line and pressing
enter, nothing happens until we press Ctrl-C to terminate
it. Adding debug output to the very start of the programme
emits nothing. It's as though the programme itself hasn't
started running yet at all.

If I replace the "F:/import" with "/cygdrive/f/import" then
the programme is able to execute (and emit debug output) but
it then terminates when it is unable to locate a file
relative to the given path (presumably because /cygdrive/f
isn't a real directory to a non-cygwin programme).

Both computers have the same cygwin dll (1.7.11 epoch 19)
but the packages on the Windows XP computer are older.

Does anyone know what I can do to get this working again? I
tried searching the list archive for cygdrive and driveletter
but couldn't find anything relevant.

I've attached the unaltered output of cygcheck -s -v -r for
both computers.


Attachment: cygcheck-svr-winxp.out
Description: Text document

Attachment: cygcheck-svr-win7.out
Description: Text document

Problem reports:
Unsubscribe info:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]