I've been running the 64-bit version of Windows 7 RC since June.
It's been quite painless on the whole.
One wrinkle that I ran into was with some batchfiles which
launch applications in %ProgramFiles% (normally C:\Program Files).
Due to the magic WOW64 redirector, 32-bit applications
are actually installed into %ProgramFiles(x86)%—normally C:\Program Files (x86)—instead of %ProgramFiles%.
This is transparent to the 32-bit applications,
which think they're running in %ProgramFiles% (C:\Program Files).
However, the cmd.exe shell is 64-bit
(unless you make a special effort to run the 32-bit cmd.exe in SysWOW64),
so batchfiles see the 64-bit %ProgramFiles% which contains 64-bit applications.
Hence, a batchfile that launches an installed 32-bit application on Win64
must use %ProgramFiles(x86)%, not %ProgramFiles%.
It sounds …continue.
I've made some significant changes to my Python Batchfile Wrapper.
The main virtue of this wrapper is that it finds python.exe and
invokes it on the associated Python script,
ensuring that input redirection works.
I've also adapted py2bat to work with my wrapper.
I'm calling my version py2cmd.
Here's my latest batch file, which is shorter than its predecessor.
To use it, place it in the same directory as the Python script
you want to run and give it the same basename;
i.e., d:\some\path or other\example.cmd
will run d:\some\path or other\example.py.
for %%i in (cmd bat exe) do (
for %%j in (python.%%i) do …continue.
I've been getting into Python lately. One problem that I've encountered
under Windows, is that input redirection doesn't work if you use
the .py file association to run the script; e.g.:
C:\> foo.py < input.txt
There's a well-known input redirection bug. The fix is to explicitly use
python.exe to run the script.
A related problem for me was that stdin was opened as a text file,
not a binary file, so \r bytes were being discarded from binary input
files. The fix is to run python.exe -u (unbuffered binary input and
I didn't want to hardcode the path to python.exe in a batch file,
so I came up with the …continue.
I'm a command-line dinosaur.
Vim (Vi IMproved) is my favorite text editor.
And I write quite a few little batch files.
Here are a few useful tricks that work with cmd.exe on Windows XP.
Sometimes I want to create a file whose name includes the current date and time.
By combining the magic %DATE% and %TIME% environment variables,
with for /f and a little bit of string substitution,
I can create that filename.
REM "Tue 06/14/2005" -> "06/14/2005"
for /f "tokens=2" %%i in ("%DATE%") do set MDY=%%i
REM "06/14/2005" -> "2005-06-14"
for /f "delims=/ tokens=1,2,3" %%i in …continue.