File associations in the command line seems broken
- From: Joan <Joan@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 16 Apr 2008 00:55:00 -0700
Hello,
I'm forced to specify the program with which I want to open a file, I cannot
launch files from the command line directly (and rely on the file extension
association)...
I can launch .exe and .bat fine. If I try to open a text file, it fails :
test.txt"The system cannot execute the specified program"
The association is ok in explorer: If I double click on a text file, it will
open it with notepad.
I can also do:
notepad test.txtand this will work, so notepad is found in the path. (it's in \system32
anyway)
Here is the result of associations commands :
assoc .txt..txt=txtfile
ftype txtfiletxtfile=%SystemRoot%\system32\NOTEPAD.EXE %1
So everything looks fine from what I can tell, only I can't launch the file
directly.
It is a major annoyance because we have a bunch of python scripts that rely
on this file association to launch each other from the command line and they
all fail on my machine due to this problem.
Thanks for any idea, insight, pointers...
.
- Follow-Ups:
- Re: File associations in the command line seems broken
- From: Ramesh, MS-MVP
- Re: File associations in the command line seems broken
- From: ju.c
- Re: File associations in the command line seems broken
- Prev by Date: Re: Losing Windows XP Profile Association
- Next by Date: Problem in Windows XP Professional SP3!!!
- Previous by thread: Download trojan horse
- Next by thread: Re: File associations in the command line seems broken
- Index(es):
Relevant Pages
|