You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please read the FAQ and check existing issues before creating a new issue.
What steps will reproduce the problem?
1. i kept the 4 files provided by you in the cygwin folder.
2. opened cygwin and tried to run the cygterm
3. It opened but hanged, and nothing works.
What is the expected result? What happens instead?
PutTTYcyg version:20091228
Cygwin version:2.573.24
Windows version: windows xp
If you are experiencing performance issues, do you have a multi-core system
or multiple CPUs? no
Do you have any firewall software installed? yes
Please attach your PuTTY configuration. Use this Windows command to create
putty.reg:
REG EXPORT HKEY_CURRENT_USER\Software\SimonTatham\PuTTY putty.reg
Please provide any additional information below.
Original issue reported on code.google.com by blackbug...@gmail.com on 20 Sep 2010 at 7:59
The text was updated successfully, but these errors were encountered:
I'm not able to duplicate this. Without more information (hung how? What do
you see?) I can't go further.
It could be your firewall software preventing putty.exe and cthelper.exe from
communicating.
It could be a problem with your Cygwin installation. Have you checked for
multiple copies of cygwin1.dll on your system?
It might be a problem with your bash setup. Have you tried running a program
other than 'bash' or temporarily removing your .bash_profile and .bashrc files?
Original comment by medgar123 on 29 Oct 2010 at 12:10
Double check you extracted the files from the zip file before running them.
Check out the attachment I've added. If you see what the arrow is pointing to,
you haven't extracted the files. Click it, put the files somewhere then close
the window. Go to where you extracted the files and run them from there.
Original comment by pricech...@gmail.com on 22 Nov 2010 at 2:21
Original issue reported on code.google.com by
blackbug...@gmail.com
on 20 Sep 2010 at 7:59The text was updated successfully, but these errors were encountered: