frmurrw Posted December 27, 2007 Posted December 27, 2007 I am currently using an unattend process using the old method of batch files. This process is working very well for me so I don't want to change to one of the newer methods that are listed. The current process has a total of 6 batch files, one is called by cmdlines.txt and the remainder are part of the [GuiRunOnce]. Batch files as follows:[cmdlines.txt]0PreGui.bat[GuiRunOnce]1applications.cmd2main_batch.cmd3additionalsettings.cmd4cleanup.cmddelete.batThis works great but when changes are required I must update 7 different server builds. So what I did was created a folder structure for each network. Placed all network specific settings into appropriate subfolder. I then created a menu batch file called 3networksettings.bat and replaced 3additionalsettings.cmd in the GuiRunOnce. During the unattended installation it brings up 3networksettings.bat but when I select the approprite network it says n1.bat is unrecognized. All other options state the same error. I can run the batch (3networksetting.bat) without issue outside of the unattend process. When I quit 3networksettings.bat via menu choice 8 it moves to the next file in the [GuiRunOnce]Any help would be greatly appreciated.TIAMurph(3networksettings.bat ) CLS@echo offColor 3ftitle Choose NetworkECHO.@ECHO OFF:StartSET MyInput=IF NOT '%1'=='' GOTO QUIT_MENUECHO Select the corresponding number for server you want to build!!.ECHO 1. Network1ECHO 2. Network2ECHO 3. Network3ECHO 4. Network4ECHO 5. Network5ECHO 6. Network6ECHO 7. Network7ECHO - - - - -ECHO 8. QuitSET /P Input=Please choose an option:IF %Input% == 8 GOTO QUITIF %Input% == 7 GOTO Network7IF %Input% == 6 GOTO Network6IF %Input% == 5 GOTO Network5IF %Input% == 4 GOTO Network4IF %Input% == 3 GOTO Network3IF %Input% == 2 GOTO Network2IF %Input% == 1 GOTO Network1:Network7n7.batGOTO Start:Network6n6.batGOTO Start:Network5n5.batGOTO Start:Network4n4.batGOTO Start:Network3n3.batGOTO Start:Network2n2.batGOTO Start:Network1n1.batGOTO Start:QUIT_MENUExit
Yzöwl Posted December 28, 2007 Posted December 28, 2007 Try usingCALL n1.batAlso please try to use CMD extensions for scripts intended for use with the Windows NT command interpreter.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now