Yzöwl

Please provide more information, give at least an example of what you are wanting and do try to improve your English. Thank you.

Just as closure to your last little problem, Cmdow.exe was used to hide the cleanup window, perhaps you should unhide it again, using the /VIS switch , at the end of the cleanup.cmd or on the return to the StartXP.cmd.

Okay, I moved the XCOPY command only to keep them together, and hadn't noticed that it was now out of order, but you are correct that the lines are run in order so if you feel you need to re-order them then you should be able to do so. I'd like to explain how CALL works; it navigates to and runs the script, maintaining the variables etc. from the calling script and then returns to it after the called script is ended. The way that it works means that you set the StartXP.cmd to run from your Startup folder on reboot/first login. When it runs it checks that the Windows CD-ROM is still in the drive, if not it should remain in position until next time you reboot/login. when it'll try again. The DEL %0 at the end of StartXP.cmd is the instruction to delete itself and is therefore the last line. This means that only when the script has been fully run to completion will it delete itself. The only reason it is not currently running this command is that control doesn't seem to be returned to it after Cleanup.cmd has completed. (Just to be safe, because you are running it from a global location, you may wish to try replacing DEL %0 with DEL /F %0 or even as a last resort use the /A switch too!). I'm also not sure why the CALL is not working correctly, it should return to the original script when finished. Logically I would assume that the Cleanup.cmd isn't finishing for some reason, but the best way to check that is to insert a pause or message at the end and wait to see if it appears during install. I've no idea about your hanging installer because the correct syntax for the command is to include the quotes, optionally placing a description within them. Finally I'd strongly suggest that you use a Virtual Machine for testing all this stuff out, Microsoft, VMWare and VirtualBox all provide free ones, the latter being my preference. Using these you can create your installs a lot quicker and take snapshots to prevent you having to recover old ground too!

If you are running under an Administrator account you could always extend the line I gave to check for the type of drive too. Mountvol|Find "D:\">Nul&&(FSUtil FSInfo DriveType D:|Find "Fixed Drive">Nul 2>&1&&(<place your command here>))Which could then be reduced due to the nature of the FSUtil command to this single line: FSUtil FSInfo DriveType D:|Find "Fixed Drive">Nul 2>&1&&<place your command here> Not really relevant to the thread but thanks for the reminder to read Martins blog, I haven't seen much of him around here for some time!

To be honest with you I'd forget about wrapping the cmd inside a RARSfx leave it in the same location, (as cleanup.cmd not cleanup.exe), and run it using a call command. I'd also remove unrequired lines from it cleanup.cmd too: RMDIR /Q /S "%UserProfile%\Application Data\Microsoft\Internet Explorer\Quick Launch\Administrative Tools" RMDIR /Q /S "%UserProfile%\Application Data\Microsoft\Internet Explorer\Quick Launch\General Tools" RMDIR /Q /S "%UserProfile%\Application Data\Microsoft\Internet Explorer\Quick Launch\LiteStep" RMDIR /Q /S "%UserProfile%\Application Data\Microsoft\Internet Explorer\Quick Launch\System Tools" RMDIR /Q /S "%UserProfile%\Application Data\Microsoft\Internet Explorer\Quick Launch\TuneUp Utilities 2007" RMDIR /Q /S "%UserProfile%\Application Data\Microsoft\Internet Explorer\Quick Launch\Unlocker"I'd change the first two lines, the last four lines, learn to use switches correctly for the DEL command, learn the switches for XCOPY, learn when COPY can be used instead of XCOPY, learn how to utilize local environment variables in order to condense code and perhaps navigate the directories in order to reduce code too. Then I'd try do reduce all those blank echo'd lines in STARTXP.BAT and finally rename it StartXP.cmd since your OS uses `Windows NT Command Scripts` not `MS-DOS Batch Files`. I've attached something like the above, it's only been done quickly so I've maybe made some stupid mistakes, and not tidied it fully etc. but give it a go! Remember all you need to do is replace %CDROM%\Auto\Cleanup.exe with %CDROM%\Auto\Cleanup.cmd. daladim.7z

Basic Example mountvol|find "D:\">nul&&<place your command here> Depending upon the exact use required, there may be a problem with the above solutions! D: may exist but may be allocated to a non-writable or non-fixed drive! Not the most appropriate of places to be trying to issue a move command to for instance.

It's not an easy task at all, and one which I'll never provide my best code for, there are literally thousands of people looking for good scripts for this and to be honest I'm not willing to provide it freely. It is one of only a few tasks that I decided many years ago not to give freely. There are some very poor NT command, visual basic and java scripts available across the web most of them with a cost thats not worth paying. There are also built-in tools for emptying TIFs and hundreds of free/payware cleanup utilities for both tasks. If you want to try to create your own then I'd suggest VBScript or JScript, and bear in mind that index.dat files should only be removed if a reboot is built in to the scripted process. Good Luck!

If all you want to do is run a cmd script from a RARSfx then here's one I've just done as an example for you. The batch file is extracted to the hardcoded path C:\ and is coded to delete itself after running. I've added an icon since most people do and the comments are visible through the WinRAR GUI. I hope it helps! Just extract the SFX from the attached archive! ThisTest.7z

This one's not free but it's a superb product, Ashampoo Office 2008.

My understanding is that `shutdown -a` will abort a running shutdown procedure. It appears that you are wanting to prevent one from being issued, which is not the same. I would doubt that having a looping abort switch would be an efficient method of stopping a new shutdown procedure from being invoked. Apart from that the commands at the bottom of your batch file will never get issued since the loop will never end. You could to look at opening another console session using a defined windows title which runs the loop, running your commands in the original session ending with a command to close the looping batch using its windows title. You may be able, as jaclaz already suggested, to simply rename shutdown.exe, (after preventing WFP from `fixing` it) but to be honest there's nothing to stop users from pushing the button on the front of the PC anyhow. Also you say install process, what are you installing, it sounds as if you are trying to install something unattendedly for other users which must take some time and over which you'd like to have more control. My suggestion, whether you like it or not, is to have a little faith in your end users, pop up a message letting them know of the install procedure and that switching off will likely render their computer useless.

Another idea is to right-click on your taskbar, uncheck `Lock the Taskbar` goto Toolbars and check Address. Drag it accross the taskbar (or onto the desktop at a suitable size and shape). This is effectively the same as having a run box always available. You can put a web address there and go/enter or for example enter cmd or calc. You'll be surprised how useful it is. As for the %windir% and %systemroot% variables, the former is really only used for legacy purposes for older OS compatibility. %systemroot% is the correct one for modern OS's.

Here is a method you can use as part of your unattended procedure; It uses reg.exe from an NT command script to set the locations for all the PC Users to the same location as the default System Temp. @Echo off&Setlocal Set "LK_=HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Environment" (Set VD_=/t REG_EXPAND_SZ /d "%%%%SystemRoot%%%%\Temp" /f^>Nul) For %%? In (T TE) Do Reg add "%LK_%" /v %%?MP %VD_% Pushd %UserProfile%\..\Default User Reg load HKU\TempHiv NTUSER.DAT>Nul 2>&1||Goto :Eof For %%? In (T TE) Do Reg add HKU\TempHiv\Environment /v %%?MP %VD_% :Un_ Reg unload HKU\TempHiv>Nul 2>&1||Goto Un_Just change SystemRoot for SystemDrive if you prefer the location to be in the root of the drive instead!

It may seem from your end by now that you're being picked on, but this is really for your own good. This post contains no content which is of any real use to anybody but yourself. Some of the bugs are not bugs at all and the rest are personal only to you. When you submit bugs you also need to provide a great deal more information to Microsoft than that which you've provided here. To be honest you wouldn't be able to get much in the way of forum help on these problems with the information you've put forward. If you would like help with these problems then post, in greater detail, what they are in this topic, I'll transfer it to a more appropriate location, (We have a Forum Group specific to Vista which would of course be the most likely to be correct location for your post), to get more reads, and we'll try to help. If you fail to do this within a reasonable amount of time I'll be forced to remove this post along with the others I've recently had to inform you about.

Please read the reply given by jaclaz and treat it as a birthday present, it is an extremely helpful piece of information which from your posts thus far is not warranted. Topic closed!

Note that I said generally and also said that the only sure fire way would be to try it. On occasions when I have it has been. Other things tried too have been using additional copies of the command interpreter in different locations and running a different one for each copy operation.

Simultaneous running commands will generally work quicker than consecutively running ones. Your biggest problem would more likely be with local hard drive head movement and writing to more than one network location at the same time. Trying it is your only sure fire way, but ensure that you play safe and use something like robocopy with its switches for handling verification and/or errors. To do it I would create a master batch file and run my three individual copy batches from it. for example: START "" %comspec% /c docopy1.cmd START "" %comspec% /c docopy2.cmd START "" %comspec% /c docopy3.cmd

This type of generic question will not be answered here, please revise the question with specifics or I'll remove this topic.

After receiving an explanation of the original post, it has been re-written as above and the topic re-opened.

Apart from the file being called svcpack.inf not ini, it would certainly help us if we were to see it, also to install things you usually need to give install switches/files to the installers. It is also evident that you are a new poster here (see the edit tag in your post), so I'll vstrongly suggest that you use the search feature as your first port of call after completing the unattended guide.

Might it be under the heading `A script for doing the Registry edit` where it states `Click here to download setcommand.inf (zipped)`!

Yes, you're correct, I noticed it in your opening post but I wasn't willing to do that for the sake of a couple of updates.

Bear in mind that pointless posts just to increase post count may however be removed. Oh and although this isn't your first post, welcome to the MSFN Forums

That's because you're not using the command correctly, in that case you should be using:cd /d D:\Something

Yes it is!

I don't really know how to verify it. There's nothing relevant in my event viewer and the automatic service has started without problem so far!.Is there something else you'd like me to try in order to verify it?