«

What is the preferred method of executing .bat or .exe via ASPs

Yes, sorry. I have tried to ways so far:
1. ASPEXEC
2. WSH

ASPEXEC was *MUCH* faster. I guess it depends on what the EXE is doing
too, but the WSH timed out & the ASPEXEC fires almost immidiately, and
returns without having to wait for the exe to complete.

Curt_C [MVP] wrote:

> Just for clarification you do mean to execute it on the SERVER correct?
> Look here http://www.darkfalz.com/1100/
>

WSH doesn't have to wait for return either.

http://msdn.microsoft.com/library/en...l/wsMthRun.asp

Ray at work

"Dave Karmens" <> wrote in message
news:eBaxhq#...
> Yes, sorry. I have tried to ways so far:
> 1. ASPEXEC
> 2. WSH
>
> ASPEXEC was *MUCH* faster. I guess it depends on what the EXE is doing
> too, but the WSH timed out & the ASPEXEC fires almost immidiately, and
> returns without having to wait for the exe to complete.
>
> Curt_C [MVP] wrote:
>
> > Just for clarification you do mean to execute it on the SERVER correct?
> > Look here http://www.darkfalz.com/1100/
> >

Hmmm.... for some reason then WSH timed out while executing, and ASPEXEC
fired right away and returned.

Ray at <%=sLocation%> [MVP] wrote:

> WSH doesn't have to wait for return either.
>
> http://msdn.microsoft.com/library/en...l/wsMthRun.asp
>
> Ray at work
>
> "Dave Karmens" <> wrote in message
> news:eBaxhq#...
>
>>Yes, sorry. I have tried to ways so far:
>>1. ASPEXEC
>>2. WSH
>>
>>ASPEXEC was *MUCH* faster. I guess it depends on what the EXE is doing
>>too, but the WSH timed out & the ASPEXEC fires almost immidiately, and
>>returns without having to wait for the exe to complete.
>>
>>Curt_C [MVP] wrote:
>>
>>
>>>Just for clarification you do mean to execute it on the SERVER correct?
>>>Look here http://www.darkfalz.com/1100/
>>>
>
>
>

sorry ray, I should have read that article before replying I know
what the problem was ..

[bWaitOnReturn] was set to true :S

Ray at <%=sLocation%> [MVP] wrote:

> WSH doesn't have to wait for return either.
>
> http://msdn.microsoft.com/library/en...l/wsMthRun.asp
>
> Ray at work
>
> "Dave Karmens" <> wrote in message
> news:eBaxhq#...
>
>>Yes, sorry. I have tried to ways so far:
>>1. ASPEXEC
>>2. WSH
>>
>>ASPEXEC was *MUCH* faster. I guess it depends on what the EXE is doing
>>too, but the WSH timed out & the ASPEXEC fires almost immidiately, and
>>returns without having to wait for the exe to complete.
>>
>>Curt_C [MVP] wrote:
>>
>>
>>>Just for clarification you do mean to execute it on the SERVER correct?
>>>Look here http://www.darkfalz.com/1100/
>>>
>
>
>

Yeah, read man!

Ray at work

"Dave Karmens" <> wrote in message
news:ebSAHC$...
> sorry ray, I should have read that article before replying I know
> what the problem was ..
>
> [bWaitOnReturn] was set to true :S
>
> Ray at <%=sLocation%> [MVP] wrote:
>
> > WSH doesn't have to wait for return either.
> >
> > http://msdn.microsoft.com/library/en...l/wsMthRun.asp
> >
> > Ray at work
> >
> > "Dave Karmens" <> wrote in message
> > news:eBaxhq#...
> >
> >>Yes, sorry. I have tried to ways so far:
> >>1. ASPEXEC
> >>2. WSH
> >>
> >>ASPEXEC was *MUCH* faster. I guess it depends on what the EXE is doing
> >>too, but the WSH timed out & the ASPEXEC fires almost immidiately, and
> >>returns without having to wait for the exe to complete.
> >>
> >>Curt_C [MVP] wrote:
> >>
> >>
> >>>Just for clarification you do mean to execute it on the SERVER correct?
> >>>Look here http://www.darkfalz.com/1100/
> >>>
> >
> >
> >