Re: External command with arguments (WinXP): cmd /c problem
Hm, this is strange, the windows shell cmd (not vim!) has problems with the following: cmd.exe /c C:\Programme\Microsoft Office\Office10\OUTLOOK.EXE /a c:\Dokumente und Einstellungen\hofjoa41\Eigene Dateien\test.txt - C:\Programme\Microsoft not found If I use the command above directly at the shell *without* the cmd /c part it works properly! I think I will ask also at alt.msdos.batch.nt if cmd /c has a special problem. Joachim ### This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange. For more information, connect to http://www.f-secure.com/
Re: External command with arguments (WinXP): cmd /c problem
[EMAIL PROTECTED] wrote: Hm, this is strange, the windows shell cmd (not vim!) has problems with the following: cmd.exe /c C:\Programme\Microsoft Office\Office10\OUTLOOK.EXE /a c:\Dokumente und Einstellungen\hofjoa41\Eigene Dateien\test.txt - C:\Programme\Microsoft not found If I use the command above directly at the shell *without* the cmd /c part it works properly! I think I will ask also at alt.msdos.batch.nt if cmd /c has a special problem. Joachim ### This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange. For more information, connect to http://www.f-secure.com/ If you replace Microsoft Office by its 8.3 equivalent (MICROS~1 or similar) you can leave out the quotes around it and it will still work OK, because there won't be spaces then, to be mistaken for separators. Best regards, Tony. -- 10.0 times 0.1 is hardly ever 1.0.
Re: External command with arguments (WinXP): cmd /c problem
Hi Joachim! This seems to correlate with the space in the directory name. Try C:\Programme\Microsoft\ Office\Office10\OUTLOOK.EXE Regards, Doc Hm, this is strange, the windows shell cmd (not vim!) has problems with the following: cmd.exe /c C:\Programme\Microsoft Office\Office10\OUTLOOK.EXE /a c:\Dokumente und Einstellungen\hofjoa41\Eigene Dateien\test.txt - C:\Programme\Microsoft not found If I use the command above directly at the shell *without* the cmd /c part it works properly! I think I will ask also at alt.msdos.batch.nt if cmd /c has a special problem. Joachim ### This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange. For more information, connect to http://www.f-secure.com/
Re: External command with arguments (WinXP): cmd /c problem
A.J.Mechelynck wrote: [EMAIL PROTECTED] wrote: Hm, this is strange, the windows shell cmd (not vim!) has problems with the following: cmd.exe /c C:\Programme\Microsoft Office\Office10\OUTLOOK.EXE /a c:\Dokumente und Einstellungen\hofjoa41\Eigene Dateien\test.txt - C:\Programme\Microsoft not found If I use the command above directly at the shell *without* the cmd /c part it works properly! I think I will ask also at alt.msdos.batch.nt if cmd /c has a special problem. Joachim ### This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange. For more information, connect to http://www.f-secure.com/ If you replace Microsoft Office by its 8.3 equivalent (MICROS~1 or similar) you can leave out the quotes around it and it will still work OK, because there won't be spaces then, to be mistaken for separators. Best regards, Tony. I've also encountered this problem many times since I often call cmd with /c in my scripts or programs. The answer to this problem may be strange, but at least I found one thing: if the path of the executable contains no space, don't quote it. However, if the path does contain a space, and the problem still arises, I don't know what to do.
