Running batch file from NetWare login script

I have windows XP clients connecting to a NetWare 4.11
server using Microsoft's Client for NetWare services. All
my drive mappings work but I cannot get my batch files to
run that I use to push out updates.
Example:

#Command.com c/Z:\SavUpd.bat

will not execute when my clients logs in.

Any help would be appreciated.

Bruce

Did you see my reply to your other, earlier post?

bruce wrote:
> I have windows XP clients connecting to a NetWare 4.11
> server using Microsoft's Client for NetWare services. All
> my drive mappings work but I cannot get my batch files to
> run that I use to push out updates.
> Example:
>
> #Command.com c/Z:\SavUpd.bat
>
> will not execute when my clients logs in.
>
> Any help would be appreciated.
>
> Bruce

>-----Original Message-----
>Did you see my reply to your other, earlier post?
>
>bruce wrote:
>> I have windows XP clients connecting to a NetWare 4.11
>> server using Microsoft's Client for NetWare services.
All
>> my drive mappings work but I cannot get my batch files
to
>> run that I use to push out updates.
>> Example:
>>
>> #Command.com c/Z:\SavUpd.bat
>>
>> will not execute when my clients logs in.
>>
>> Any help would be appreciated.
>>
>> Bruce
>
>
>.
>Yes. Not an option. Need to figure out a way to do this.

bruce wrote:
>> -----Original Message-----
>> Did you see my reply to your other, earlier post?
>>
>> bruce wrote:
>>> I have windows XP clients connecting to a NetWare 4.11
>>> server using Microsoft's Client for NetWare services. All
>>> my drive mappings work but I cannot get my batch files to
>>> run that I use to push out updates.
>>> Example:
>>>
>>> #Command.com c/Z:\SavUpd.bat
>>>
>>> will not execute when my clients logs in.
>>>
>>> Any help would be appreciated.
>>>
>>> Bruce
>>
>>
>> .
>> Yes. Not an option. Need to figure out a way to do this.

OK - that was supposed to be a gentle hint not to multipost (crosspost when
needed, instead) - most people sub to multiple groups, and that way everyone
can follow the thread & not duplicate others' work. :-)

Just noticed that you've got command.com in there - try cmd.exe instead.

>-----Original Message-----
>bruce wrote:
>>> -----Original Message-----
>>> Did you see my reply to your other, earlier post?
>>>
>>> bruce wrote:
>>>> I have windows XP clients connecting to a NetWare 4.11
>>>> server using Microsoft's Client for NetWare services.
All
>>>> my drive mappings work but I cannot get my batch
files to
>>>> run that I use to push out updates.
>>>> Example:
>>>>
>>>> #Command.com c/Z:\SavUpd.bat
>>>>
>>>> will not execute when my clients logs in.
>>>>
>>>> Any help would be appreciated.
>>>>
>>>> Bruce
>>>
>>>
>>> .
>>> Yes. Not an option. Need to figure out a way to do
this.
>
>OK - that was supposed to be a gentle hint not to
multipost (crosspost when
>needed, instead) - most people sub to multiple groups,
and that way everyone
>can follow the thread & not duplicate others' work. :-)
>
>Just noticed that you've got command.com in there - try
cmd.exe instead.
>
I have tried the following versions of my command:

#Command.com c/Z:\SavUpd.bat
#cmd.exe c/Z:\SavUpd.bat
#cmd c/Z:\SavUpd.bat

None of the above works.

I have even tried to put #CMD as my first line of my batch
file according to the following link:

http://www.microsoft.com/resources/d...ion/windows/xp
/all/proddocs/en-us/tab16_utilities.mspx

and this does not work either.

In the first part of my login script I have the following
line:

Map S4 := C:\WIndows\System32\command

This maps a search drive to command. I have tried to
switch this to read:

Map S4 := C:\WIndows\System32\cmd (also cmd.exe)

This does not work either.

Bruce wrote:
>> -----Original Message-----
>> bruce wrote:
>>>> -----Original Message-----
>>>> Did you see my reply to your other, earlier post?
>>>>
>>>> bruce wrote:
>>>>> I have windows XP clients connecting to a NetWare 4.11
>>>>> server using Microsoft's Client for NetWare services. All
>>>>> my drive mappings work but I cannot get my batch
> files to
>>>>> run that I use to push out updates.
>>>>> Example:
>>>>>
>>>>> #Command.com c/Z:\SavUpd.bat
>>>>>
>>>>> will not execute when my clients logs in.
>>>>>
>>>>> Any help would be appreciated.
>>>>>
>>>>> Bruce
>>>>
>>>>
>>>> .
>>>> Yes. Not an option. Need to figure out a way to do this.
>>
>> OK - that was supposed to be a gentle hint not to multipost
>> (crosspost when needed, instead) - most people sub to multiple
>> groups,
> and that way everyone
>> can follow the thread & not duplicate others' work. :-)
>>
>> Just noticed that you've got command.com in there - try cmd.exe
>> instead.
>>
> I have tried the following versions of my command:
>
> #Command.com c/Z:\SavUpd.bat
> #cmd.exe c/Z:\SavUpd.bat
> #cmd c/Z:\SavUpd.bat
>
> None of the above works.
>
> I have even tried to put #CMD as my first line of my batch
> file according to the following link:
>
> http://www.microsoft.com/resources/d...ion/windows/xp
> /all/proddocs/en-us/tab16_utilities.mspx
>
> and this does not work either.
>
> In the first part of my login script I have the following
> line:
>
> Map S4 := C:\WIndows\System32\command
>
> This maps a search drive to command. I have tried to
> switch this to read:
>
> Map S4 := C:\WIndows\System32\cmd (also cmd.exe)
>
> This does not work either.

I haven't worked with Netware or Netware scripts for ages, sorry. Have you
checked in a Netware group for more help? This really sounds likemore of an
issue with the script syntax to me.

>-----Original Message-----
>Bruce wrote:
>>> -----Original Message-----
>>> bruce wrote:
>>>>> -----Original Message-----
>>>>> Did you see my reply to your other, earlier post?
>>>>>
>>>>> bruce wrote:
>>>>>> I have windows XP clients connecting to a NetWare
4.11
>>>>>> server using Microsoft's Client for NetWare
services. All
>>>>>> my drive mappings work but I cannot get my batch
>> files to
>>>>>> run that I use to push out updates.
>>>>>> Example:
>>>>>>
>>>>>> #Command.com c/Z:\SavUpd.bat
>>>>>>
>>>>>> will not execute when my clients logs in.
>>>>>>
>>>>>> Any help would be appreciated.
>>>>>>
>>>>>> Bruce
>>>>>
>>>>>
>>>>> .
>>>>> Yes. Not an option. Need to figure out a way to do
this.
>>>
>>> OK - that was supposed to be a gentle hint not to
multipost
>>> (crosspost when needed, instead) - most people sub to
multiple
>>> groups,
>> and that way everyone
>>> can follow the thread & not duplicate others' work. :-)
>>>
>>> Just noticed that you've got command.com in there -
try cmd.exe
>>> instead.
>>>
>> I have tried the following versions of my command:
>>
>> #Command.com c/Z:\SavUpd.bat
>> #cmd.exe c/Z:\SavUpd.bat
>> #cmd c/Z:\SavUpd.bat
>>
>> None of the above works.
>>
>> I have even tried to put #CMD as my first line of my
batch
>> file according to the following link:
>>
>>
http://www.microsoft.com/resources/d...ion/windows/xp
>> /all/proddocs/en-us/tab16_utilities.mspx
>>
>> and this does not work either.
>>
>> In the first part of my login script I have the
following
>> line:
>>
>> Map S4 := C:\WIndows\System32\command
>>
>> This maps a search drive to command. I have tried to
>> switch this to read:
>>
>> Map S4 := C:\WIndows\System32\cmd (also cmd.exe)
>>
>> This does not work either.
>
>I haven't worked with Netware or Netware scripts for
ages, sorry. Have you
>checked in a Netware group for more help? This really
sounds likemore of an
>issue with the script syntax to me.
>
>
>.
>Nobody at Novell has been able to help me either. I am
just wondering if I really need the #Command or #Cmd
command. I wonder if I just used the following syntax:

# Z:\SavUpd.bat

If that would work. Do I really need to invoke the dos
shell?

>-----Original Message-----
>
>>-----Original Message-----
>>Bruce wrote:
>>>> -----Original Message-----
>>>> bruce wrote:
>>>>>> -----Original Message-----
>>>>>> Did you see my reply to your other, earlier post?
>>>>>>
>>>>>> bruce wrote:
>>>>>>> I have windows XP clients connecting to a NetWare
>4.11
>>>>>>> server using Microsoft's Client for NetWare
>services. All
>>>>>>> my drive mappings work but I cannot get my batch
>>> files to
>>>>>>> run that I use to push out updates.
>>>>>>> Example:
>>>>>>>
>>>>>>> #Command.com c/Z:\SavUpd.bat
>>>>>>>
>>>>>>> will not execute when my clients logs in.
>>>>>>>
>>>>>>> Any help would be appreciated.
>>>>>>>
>>>>>>> Bruce
>>>>>>
>>>>>>
>>>>>> .
>>>>>> Yes. Not an option. Need to figure out a way to
do
>this.
>>>>
>>>> OK - that was supposed to be a gentle hint not to
>multipost
>>>> (crosspost when needed, instead) - most people sub to
>multiple
>>>> groups,
>>> and that way everyone
>>>> can follow the thread & not duplicate others' work. :-
)
>>>>
>>>> Just noticed that you've got command.com in there -
>try cmd.exe
>>>> instead.
>>>>
>>> I have tried the following versions of my command:
>>>
>>> #Command.com c/Z:\SavUpd.bat
>>> #cmd.exe c/Z:\SavUpd.bat
>>> #cmd c/Z:\SavUpd.bat
>>>
>>> None of the above works.
>>>
>>> I have even tried to put #CMD as my first line of my
>batch
>>> file according to the following link:
>>>
>>>
>http://www.microsoft.com/resources/d...tion/windows/x
p
>>> /all/proddocs/en-us/tab16_utilities.mspx
>>>
>>> and this does not work either.
>>>
>>> In the first part of my login script I have the
>following
>>> line:
>>>
>>> Map S4 := C:\WIndows\System32\command
>>>
>>> This maps a search drive to command. I have tried to
>>> switch this to read:
>>>
>>> Map S4 := C:\WIndows\System32\cmd (also cmd.exe)
>>>
>>> This does not work either.
>>
>>I haven't worked with Netware or Netware scripts for
>ages, sorry. Have you
>>checked in a Netware group for more help? This really
>sounds likemore of an
>>issue with the script syntax to me.
>>
>>
>>.
>>Nobody at Novell has been able to help me either. I am
>just wondering if I really need the #Command or #Cmd
>command. I wonder if I just used the following syntax:
>
># Z:\SavUpd.bat
>
>If that would work. Do I really need to invoke the dos
>shell?
>.
>Got this to work by using the following command right
after my drive mapping to the Z drive:

# Z:\SavUpd.bat

Later.

Bruce wrote:
>> -----Original Message-----
>>
>>> -----Original Message-----
>>> Bruce wrote:
>>>>> -----Original Message-----
>>>>> bruce wrote:
>>>>>>> -----Original Message-----
>>>>>>> Did you see my reply to your other, earlier post?
>>>>>>>
>>>>>>> bruce wrote:
>>>>>>>> I have windows XP clients connecting to a NetWare 4.11
>>>>>>>> server using Microsoft's Client for NetWare services. All
>>>>>>>> my drive mappings work but I cannot get my batch files to
>>>>>>>> run that I use to push out updates.
>>>>>>>> Example:
>>>>>>>>
>>>>>>>> #Command.com c/Z:\SavUpd.bat
>>>>>>>>
>>>>>>>> will not execute when my clients logs in.
>>>>>>>>
>>>>>>>> Any help would be appreciated.
>>>>>>>>
>>>>>>>> Bruce
>>>>>>>
>>>>>>>
>>>>>>> .
>>>>>>> Yes. Not an option. Need to figure out a way to
> do
>> this.
>>>>>
>>>>> OK - that was supposed to be a gentle hint not to multipost
>>>>> (crosspost when needed, instead) - most people sub to multiple
>>>>> groups,
>>>> and that way everyone
>>>>> can follow the thread & not duplicate others' work. :- )
>>>>>
>>>>> Just noticed that you've got command.com in there - try cmd.exe
>>>>> instead.
>>>>>
>>>> I have tried the following versions of my command:
>>>>
>>>> #Command.com c/Z:\SavUpd.bat
>>>> #cmd.exe c/Z:\SavUpd.bat
>>>> #cmd c/Z:\SavUpd.bat
>>>>
>>>> None of the above works.
>>>>
>>>> I have even tried to put #CMD as my first line of my batch
>>>> file according to the following link:
>>>>
>>>>
>> http://www.microsoft.com/resources/d...tion/windows/x
> p
>>>> /all/proddocs/en-us/tab16_utilities.mspx
>>>>
>>>> and this does not work either.
>>>>
>>>> In the first part of my login script I have the following
>>>> line:
>>>>
>>>> Map S4 := C:\WIndows\System32\command
>>>>
>>>> This maps a search drive to command. I have tried to
>>>> switch this to read:
>>>>
>>>> Map S4 := C:\WIndows\System32\cmd (also cmd.exe)
>>>>
>>>> This does not work either.
>>>
>>> I haven't worked with Netware or Netware scripts for ages, sorry.
>>> Have you checked in a Netware group for more help? This really
>>> sounds likemore of an issue with the script syntax to me.
>>>
>>>
>>> .
>>> Nobody at Novell has been able to help me either. I am
>> just wondering if I really need the #Command or #Cmd
>> command. I wonder if I just used the following syntax:
>>
>> # Z:\SavUpd.bat
>>
>> If that would work. Do I really need to invoke the dos
>> shell?
>> .
>> Got this to work by using the following command right
> after my drive mapping to the Z drive:
>
> # Z:\SavUpd.bat
>
> Later.

Glad you got it working!