Alexander Schremmer wrote:
Windows tries to execute the cygwin symbolic link and fails.
Correcting your path works (as you said).
One thing about that: I re-installed python (ie upgraded to python
2.3.5) and it did not solve the error. I assume that the python 2.3.5
installer is so well-mannered
Here's some more info on this:
When I use the Win2k feature to search for files, it turns up python.exe
in the \cygwin\bin directory. The file size is shown as 24 bytes.
Mighty small for an executable. The file is hidden. This is evidently
the guy who was caussing the problem.
Why does cygw
On Sat, 09 Apr 2005 11:00:08 -0700, Al Christians wrote:
> I started having some problems running python programs (python 2.3) from
> the Win2k command line. I would get crashes with an NTVDM error.
Windows tries to execute the cygwin symbolic link and fails.
Correcting your path works (as you
I started having some problems running python programs (python 2.3) from
the Win2k command line. I would get crashes with an NTVDM error. Even
just executing python would cause it. I upgraded to python 2.3.5, and
no difference. When I rearranged my path to move cygwin and a bunch of
other s
