1. Win XP handling of command_line function
- Posted by Dick Holmes <d.holmes at aristoslogic.com>
Jan 25, 2007
-
Last edited Jan 26, 2007
When I run a program in a DOS window as: xx.exw a b and call command_line in
xx, the returned sequence only contains the interpreter name and the
program name. If I run: c:\EUPHORIA\BIN\exw.exe xx.exw a b the returned
sequence includes the command line parameters as specified.
I believe this used to work without specifying the interpreter when I was
using Win 2K. Now that I'm on Win XP I'm wondering if there is either an
OS issue or a Euphoria issue....
Thanks!
Dick Holmes
2. Re: Win XP handling of command_line function
Dick Holmes wrote:
>
> When I run a program in a DOS window as: xx.exw a b and call command_line in
> xx, the returned sequence only contains the interpreter name and the
> program name. If I run: c:\EUPHORIA\BIN\exw.exe xx.exw a b the returned
> sequence includes the command line parameters as specified.
>
> I believe this used to work without specifying the interpreter when I was
> using Win 2K. Now that I'm on Win XP I'm wondering if there is either an
> OS issue or a Euphoria issue....
>
> Thanks!
Hi Dick
Check this registry entry (for exw files) in regedit.
HKEY_CLASSES_ROOT\EUWinApp\shell\open\command
It should contain a REG_SZ value:
"C:\EUPHORIA\BIN\EXW.EXE" "%1" %*
(or wherever EXW.EXE is located).
I am using Win2k as well, but it should be the same for WinXP. I had the same
problem on an XP machine at one stage and had to add the %*. I'm not sure where
the incorrect value came from, but I suspect it was using "Open With" at some
stage.
Gary
