Kill processes for Old APP (Urgent)

[Ricardo]

Hi,
I am creating batch files from Visual Basic to use compact tools like pkzip
and so on. However, for each batch created I got a winoldap process in the
work list, if that processes are not killed then the system crash at all.
My question, is there some way to identify the processes and then kill them?,
or somebody have any other idea to solve the problem?

Platform: Win 98, Visual Basic 6.0 (SP4)

Any help will be highly appreciated.

[Jon Oliver]

"Ricardo" <Rimezah@hotmail.com> wrote in message
news:3c613bad$1@10.1.10.29...

> I am creating batch files from Visual Basic to use compact
tools like pkzip
> and so on. However, for each batch created I got a winoldap
process in the
> work list, if that processes are not killed then the system
crash at all.

> My question, is there some way to identify the processes and
then kill them?,
> or somebody have any other idea to solve the problem?

How are you running your batch files? There should be a way to
execute them without leaving the interpreter behind.

[Jon Oliver]

"Ricardo" <Rimezah@hotmail.com> wrote in message
news:3c613bad$1@10.1.10.29...

> I am creating batch files from Visual Basic to use compact
tools like pkzip
> and so on. However, for each batch created I got a winoldap
process in the
> work list, if that processes are not killed then the system
crash at all.

> My question, is there some way to identify the processes and
then kill them?,
> or somebody have any other idea to solve the problem?

How are you running your batch files? There should be a way to
execute them without leaving the interpreter behind.

[Ricardo]

"Jon Oliver" <joliver@no.spam.maam.com> wrote:
>"Ricardo" <Rimezah@hotmail.com> wrote in message
>news:3c613bad$1@10.1.10.29...
>
>> I am creating batch files from Visual Basic to use compact
>tools like pkzip
>> and so on. However, for each batch created I got a winoldap
>process in the
>> work list, if that processes are not killed then the system
>crash at all.
>
>> My question, is there some way to identify the processes and
>then kill them?,
>> or somebody have any other idea to solve the problem?
>
>How are you running your batch files? There should be a way to
>execute them without leaving the interpreter behind.
>
Jon,
Sorry I'm not really sure if I understood your question. but the way I'm
running the batch is as follow:

vSalida = Shell(Comando, vbHide)
Where comando have the instructions to execute like Pkzip, copy and so on...Hope
this gives you the idea of my problem. Thanks in advance..

[Ricardo]

"Jon Oliver" <joliver@no.spam.maam.com> wrote:
>"Ricardo" <Rimezah@hotmail.com> wrote in message
>news:3c613bad$1@10.1.10.29...
>
>> I am creating batch files from Visual Basic to use compact
>tools like pkzip
>> and so on. However, for each batch created I got a winoldap
>process in the
>> work list, if that processes are not killed then the system
>crash at all.
>
>> My question, is there some way to identify the processes and
>then kill them?,
>> or somebody have any other idea to solve the problem?
>
>How are you running your batch files? There should be a way to
>execute them without leaving the interpreter behind.
>
Jon,
Sorry I'm not really sure if I understood your question. but the way I'm
running the batch is as follow:

vSalida = Shell(Comando, vbHide)
Where comando have the instructions to execute like Pkzip, copy and so on...Hope
this gives you the idea of my problem. Thanks in advance..

[Jon Oliver]

"Ricardo" <Rimezah@hotmail.com> wrote in message
news:3c615ffa$1@10.1.10.29...
>
> "Jon Oliver" <joliver@no.spam.maam.com> wrote:
> >"Ricardo" <Rimezah@hotmail.com> wrote in message
> >news:3c613bad$1@10.1.10.29...
> >
> >> I am creating batch files from Visual Basic to use compact
> >tools like pkzip
> >> and so on. However, for each batch created I got a winoldap
> >process in the
> >> work list, if that processes are not killed then the system
> >crash at all.
> >
> >> My question, is there some way to identify the processes
and
> >then kill them?,
> >> or somebody have any other idea to solve the problem?
> >
> >How are you running your batch files? There should be a way
to
> >execute them without leaving the interpreter behind.
> >
> Jon,
> Sorry I'm not really sure if I understood your question. but
the way I'm
> running the batch is as follow:
>
> vSalida = Shell(Comando, vbHide)
> Where comando have the instructions to execute like Pkzip,
copy and so on...Hope
> this gives you the idea of my problem. Thanks in advance..

I can't tell what's in your Comando variable...

[Jon Oliver]

"Ricardo" <Rimezah@hotmail.com> wrote in message
news:3c615ffa$1@10.1.10.29...
>
> "Jon Oliver" <joliver@no.spam.maam.com> wrote:
> >"Ricardo" <Rimezah@hotmail.com> wrote in message
> >news:3c613bad$1@10.1.10.29...
> >
> >> I am creating batch files from Visual Basic to use compact
> >tools like pkzip
> >> and so on. However, for each batch created I got a winoldap
> >process in the
> >> work list, if that processes are not killed then the system
> >crash at all.
> >
> >> My question, is there some way to identify the processes
and
> >then kill them?,
> >> or somebody have any other idea to solve the problem?
> >
> >How are you running your batch files? There should be a way
to
> >execute them without leaving the interpreter behind.
> >
> Jon,
> Sorry I'm not really sure if I understood your question. but
the way I'm
> running the batch is as follow:
>
> vSalida = Shell(Comando, vbHide)
> Where comando have the instructions to execute like Pkzip,
copy and so on...Hope
> this gives you the idea of my problem. Thanks in advance..

I can't tell what's in your Comando variable...

[Ricardo]

"Jon Oliver" <joliver@no.spam.maam.com> wrote:
>
>"Ricardo" <Rimezah@hotmail.com> wrote in message
>news:3c615ffa$1@10.1.10.29...
>>
>> "Jon Oliver" <joliver@no.spam.maam.com> wrote:
>> >"Ricardo" <Rimezah@hotmail.com> wrote in message
>> >news:3c613bad$1@10.1.10.29...
>> >
>> >> I am creating batch files from Visual Basic to use compact
>> >tools like pkzip
>> >> and so on. However, for each batch created I got a winoldap
>> >process in the
>> >> work list, if that processes are not killed then the system
>> >crash at all.
>> >
>> >> My question, is there some way to identify the processes
>and
>> >then kill them?,
>> >> or somebody have any other idea to solve the problem?
>> >
>> >How are you running your batch files? There should be a way
>to
>> >execute them without leaving the interpreter behind.
>> >
>> Jon,
>> Sorry I'm not really sure if I understood your question. but
>the way I'm
>> running the batch is as follow:
>>
>> vSalida = Shell(Comando, vbHide)
>> Where comando have the instructions to execute like Pkzip,
>copy and so on...Hope
>> this gives you the idea of my problem. Thanks in advance..
>
>I can't tell what's in your Comando variable...

Jon,
Sorry because I didn't specify a deteil the content of comand var, I realized
that this is an important thing to help me.
I tried to put "command /c " expression before bat file and it works fine
it solve my problem.

Thank you very much for you help and time.

[Ricardo]

"Jon Oliver" <joliver@no.spam.maam.com> wrote:
>
>"Ricardo" <Rimezah@hotmail.com> wrote in message
>news:3c615ffa$1@10.1.10.29...
>>
>> "Jon Oliver" <joliver@no.spam.maam.com> wrote:
>> >"Ricardo" <Rimezah@hotmail.com> wrote in message
>> >news:3c613bad$1@10.1.10.29...
>> >
>> >> I am creating batch files from Visual Basic to use compact
>> >tools like pkzip
>> >> and so on. However, for each batch created I got a winoldap
>> >process in the
>> >> work list, if that processes are not killed then the system
>> >crash at all.
>> >
>> >> My question, is there some way to identify the processes
>and
>> >then kill them?,
>> >> or somebody have any other idea to solve the problem?
>> >
>> >How are you running your batch files? There should be a way
>to
>> >execute them without leaving the interpreter behind.
>> >
>> Jon,
>> Sorry I'm not really sure if I understood your question. but
>the way I'm
>> running the batch is as follow:
>>
>> vSalida = Shell(Comando, vbHide)
>> Where comando have the instructions to execute like Pkzip,
>copy and so on...Hope
>> this gives you the idea of my problem. Thanks in advance..
>
>I can't tell what's in your Comando variable...

Jon,
Sorry because I didn't specify a deteil the content of comand var, I realized
that this is an important thing to help me.
I tried to put "command /c " expression before bat file and it works fine
it solve my problem.

Thank you very much for you help and time.