more 7 issues

when i run choice i get a message saying to get compatible program. So I
tried kixtart but when i try to run a command it opens a cmd window
without running the command. the start command does this too. What can i
use to replace these?

thanks,
i've edited the bat file to support the format but when I try to run the
bat file i get the termws.bat is not recognised as the name of cndlet.

On 14/11/2010 05:21, Carlos wrote:
> Jason,
> I am not sure if I understand your post correctly, but wouldn't
> Windows 7 Powershell fit you?
> Carlos
> On 13 nov, 01:18, Jason<jal...@hotmail.com> wrote:
>> when i run choice i get a message saying to get compatible program. So I
>> tried kixtart but when i try to run a command it opens a cmd window
>> without running the command. the start command does this too. What can i
>> use to replace these?
>

i had to edit the line because the format is different and I had to add
".\ to the filename.
On 14/11/2010 14:20, Jason wrote:
> thanks,
> i've edited the bat file to support the format but when I try to run the
> bat file i get the termws.bat is not recognised as the name of cndlet.
>
> On 14/11/2010 05:21, Carlos wrote:
>> Jason,
>> I am not sure if I understand your post correctly, but wouldn't
>> Windows 7 Powershell fit you?
>> Carlos
>> On 13 nov, 01:18, Jason<jal...@hotmail.com> wrote:
>>> when i run choice i get a message saying to get compatible program. So I
>>> tried kixtart but when i try to run a command it opens a cmd window
>>> without running the command. the start command does this too. What can i
>>> use to replace these?
>>
>

Windows PowerShell does not include the current directory in the execution
path. This is by design, and for the same reasons that UNIX and Linux
don't-- there is the potential for a security issue. Therefore, if you need
to execute a program that isn't on your normal PATH ($envath in PowerShell
speak), you have to expicitly include the current directory by preceeding
the program name with the path to it. Hence the need for ".\" before it.

If all you are trying to do is run a batch file (.BAT), you might find it
simpler and easier to simply open a command window (CMD.EXE) and run the
batch file from there. Of course, Windows PowerShell gives you far more
capabilities and is clearly the future of Windows command line and
scripting, so you may well prefer to expend the extra effort to start
getting comfortable in it.

--
Charlie.
http://msmvps.com/blogs/Russel


"Jason" <> wrote in message
news:ibne44$9qq$...
>i had to edit the line because the format is different and I had to add ".\
>to the filename.
> On 14/11/2010 14:20, Jason wrote:
>> thanks,
>> i've edited the bat file to support the format but when I try to run the
>> bat file i get the termws.bat is not recognised as the name of cndlet.
>>
>> On 14/11/2010 05:21, Carlos wrote:
>>> Jason,
>>> I am not sure if I understand your post correctly, but wouldn't
>>> Windows 7 Powershell fit you?
>>> Carlos
>>> On 13 nov, 01:18, Jason<jal...@hotmail.com> wrote:
>>>> when i run choice i get a message saying to get compatible program. So
>>>> I
>>>> tried kixtart but when i try to run a command it opens a cmd window
>>>> without running the command. the start command does this too. What can
>>>> i
>>>> use to replace these?
>>>
>>
>

cmd doesn't work - i get error saying i need a compatible program. Plus
if i was to open cmd first i would do the process manually.
On 15/11/2010 04:12, Charlie Russel-MVP wrote:
> Windows PowerShell does not include the current directory in the
> execution path. This is by design, and for the same reasons that UNIX
> and Linux don't-- there is the potential for a security issue.
> Therefore, if you need to execute a program that isn't on your normal
> PATH ($envath in PowerShell speak), you have to expicitly include the
> current directory by preceeding the program name with the path to it.
> Hence the need for ".\" before it.
>
> If all you are trying to do is run a batch file (.BAT), you might find
> it simpler and easier to simply open a command window (CMD.EXE) and run
> the batch file from there. Of course, Windows PowerShell gives you far
> more capabilities and is clearly the future of Windows command line and
> scripting, so you may well prefer to expend the extra effort to start
> getting comfortable in it.
>

yes
On 15/11/2010 02:19, Carlos wrote:
> Jason,
> Is it working now?
> Carlos
> On 13 nov, 22:30, Jason<jal...@hotmail.com> wrote:
>> i had to edit the line because the format is different and I had to add
>> ".\ to the filename.
>> On 14/11/2010 14:20, Jason wrote:
>>
>>
>>
>>> thanks,DEL Lines