> No, that means that the batch file is invoked, not the command. What
> happens when you open a cmd.exe window and type "c:\cygwin\cygwin.bat"?
I tried all the permutations of those actions. Nothing.
> > But invoking bash by double-clicking cygwin.bat, is not any different
> > from manually st
I hope this won't end up as a double post. I posted it with attachments, but
didn't see it come through nor bounce. So here goes again:
> You have to understand that the reason
> I focused on all the stuff about foreign packages on the system / in the
> path is because that kind of thing turns out
> Having the GnuWin32 tools in your path could be a source of confusion,
> so I wouldn't recommend that. But it appears that your cygwin bin
> directory is first in the path and so the cygwin versions should be
> found.
Stripped it from the PATH. No change.
> But do note - by default \cygwin\bi
> You are on extremely shakey ground with this. Having more than one copy
> of cygwin1.dll on your system is a VERY bad idea unless you know exactly
> what you're doing. I strongly recommend that you stick to official
> Cygwin packages. If you must use something packaged by a third party,
> then
> You are running non-Cygwin programs in a Cygwin tty (because you have
> 'tty' in $CYGWIN.) Non-Cygwin programs do not know what a Cygwin tty
> is, and think they are writing to a pipe. This causes the output to be
> buffered, so you only see output in large chunks when the buffer fills
> enough
After installing OpenSSHD, CopSSH or just the latest cygwin setup, I cannot
get any console output at the Windows command prompt (cmd.exe).
What I'm doing:
- Start the console with "C:\WINDOWS\system32\cmd.exe"
- CD to the cygwin installation directory ("C:\Program Files\OpenSSH",
"C:\Program File
6 matches
Mail list logo
