Calling one script from another

[Morris, Lamar]

I have a simple script that copies over some files from a mapped network
drive to the local drive, and calls another script from the local
directory that I just copied over, which essentially makes the OS very
secure. The problem I keep running in to is that the original script
that calls the second script and when it finishes it gets a device
error. Is there a way to make the original script go ahead and die so
that the secondary script doesn't try to go back to the first script.
Any help would be appreciated.

 

1st script.

 

xcopy /s /e /v
\\dsks66\prodw\W2K3Baseline\rel5220\cd_src\x86\std\SEC\*.* C:\SEC\*.*

sleep 3

echo.

echo.

c:

cd\

cd SEC

echo.

echo.

call c:\sec\secbaseline.bat

 

 

 

Regards

Lamar Morris

Texas Instruments - IT Operations - Windows Server Team

* <mailto:LamarMorris@...>  email: LamarMorris@... - *office:
214-567-7169

* <mailto:searun@...>  team email: wst@... - *mobile:
214-882-4187

*web: <http://wst.itg.ti.com/> http://wst.itg.ti.com/
<http://wst.itg.ti.com/>

 

 



[Non-text portions of this message have been removed]

[Morris, Lamar]

Thanks.

 

Lamar

 

________________________________

From: batchworld@... [mailto:batchworld@...] On
Behalf Of foxidrive
Sent: Thursday, April 03, 2008 11:08 AM
To: batchworld@...
Subject: Re: [BATCH WORLD] Calling one script from another

 

On Thu, 3 Apr 2008 09:38:47 -0500, "Morris, Lamar" <LamarMorris@...
<mailto:LamarMorris%40ti.com> >
wrote:

>I have a simple script that copies over some files from a mapped
network

>drive to the local drive, and calls another script from the local
>directory that I just copied over, which essentially makes the OS very
>secure. The problem I keep running in to is that the original script
>that calls the second script and when it finishes it gets a device
>error. Is there a way to make the original script go ahead and die so
>that the secondary script doesn't try to go back to the first script.
>Any help would be appreciated.
>
>
>
>1st script.
>
>
>
>xcopy /s /e /v
>\\dsks66\prodw\W2K3Baseline\rel5220\cd_src\x86\std\SEC\*.* C:\SEC\*.*
>
>sleep 3
>
>echo.
>
>echo.
>
>c:
>
>cd\
>
>cd SEC
>
>echo.
>
>echo.
>
>call c:\sec\secbaseline.bat

Just remove the CALL keyword and it will not return to the first script.

 



[Non-text portions of this message have been removed]

[Morris, Lamar]

I was locked in to yesteryear when you had to call a batch file from a
batch file.

 

Lamar

 

________________________________

From: batchworld@... [mailto:batchworld@...] On
Behalf Of foxidrive
Sent: Thursday, April 03, 2008 11:08 AM
To: batchworld@...
Subject: Re: [BATCH WORLD] Calling one script from another

 

On Thu, 3 Apr 2008 09:38:47 -0500, "Morris, Lamar" <LamarMorris@...
<mailto:LamarMorris%40ti.com> >
wrote:

>I have a simple script that copies over some files from a mapped
network

>drive to the local drive, and calls another script from the local
>directory that I just copied over, which essentially makes the OS very
>secure. The problem I keep running in to is that the original script
>that calls the second script and when it finishes it gets a device
>error. Is there a way to make the original script go ahead and die so
>that the secondary script doesn't try to go back to the first script.
>Any help would be appreciated.
>
>
>
>1st script.
>
>
>
>xcopy /s /e /v
>\\dsks66\prodw\W2K3Baseline\rel5220\cd_src\x86\std\SEC\*.* C:\SEC\*.*
>
>sleep 3
>
>echo.
>
>echo.
>
>c:
>
>cd\
>
>cd SEC
>
>echo.
>
>echo.
>
>call c:\sec\secbaseline.bat

Just remove the CALL keyword and it will not return to the first script.

 



[Non-text portions of this message have been removed]

[foxidrive-7]

On Thu, 3 Apr 2008 09:38:47 -0500, "Morris, Lamar" <LamarMorris@...>
wrote:

>I have a simple script that copies over some files from a mapped network
>drive to the local drive, and calls another script from the local
>directory that I just copied over, which essentially makes the OS very
>secure. The problem I keep running in to is that the original script
>that calls the second script and when it finishes it gets a device
>error. Is there a way to make the original script go ahead and die so
>that the secondary script doesn't try to go back to the first script.
>Any help would be appreciated.
>
>
>
>1st script.
>
>
>
>xcopy /s /e /v
>\\dsks66\prodw\W2K3Baseline\rel5220\cd_src\x86\std\SEC\*.* C:\SEC\*.*
>
>sleep 3
>
>echo.
>
>echo.
>
>c:
>
>cd\
>
>cd SEC
>
>echo.
>
>echo.
>
>call c:\sec\secbaseline.bat

Just remove the CALL keyword and it will not return to the first script.