MHz

Within $OEM$ directory as usual. Having a $OEM$ folder will not break anything. It is using the Winnt.sif sections that loses your F6 option.

Try it over a network. It may depend on your setup to what issues may arise. Running it at Cmdlines.txt means your running as system rather then an account so RunAsSet is perhaps no requirement, if it was anyway. You can only fix problems that come your way, not the ones that do not exist yet. The scripts are flexible to small changes if needed.

You can use Cmdlines.txt. Windows setup will search for Cmdlines.txt existance whether you are using Winnt.sif or not. You can then XCopy your files over to the HDD or just install from CD. Several lines could replace the Winnt.sif method of OEMPreInstall.

Repartition will delete any partitions of the first drive and will format the first drive. AutoPartition setting is irrelevent once Repartition is used.

This works fine. Running the Netfx.msi instead of Install.exe failed for my attempts which made it complain to run Install.exe first.

From Ref.chm: Perhaps if you remove the leading backslashes then it may work ok.

If you expand PP then PP is fine. error message that it can't find the setupskype.exe file. is different to SkypeSetup.exe you have in your script?

You may want to look at FileTargets. Edit: Total Copy actually is the one I was thinking of.

SET FULLPATH=%cdrom%\SETUP\SOFT\Realalt REG ADD %KEY%\025 /V 3 /D "\"%FULLPATH%\realalt144.exe\" /silent /LoadInf=\"%FULLPATH%\realalt.ini\"" /f SET FULLPATH=%cdrom%\SETUP\SOFT\Quickalt REG ADD %KEY%\025 /V 4 /D "\"%FULLPATH%\quickalt163.exe\" /silent /LoadInf=\"%FULLPATH%\qtalt.ini\"" /f This goes into the registry fine.

Not sure of your backslash concept, but it is not a standard concept unless you forgot to add the leading period. Just remove the backslashes as not needed. Winnt.sif is irrelevent to Cmdlines.txt operation. It could be totally missing and Cmdlines.txt will still execute. PowerDVD will not install unless Cmdlines.txt works? Is this a CD (or network) setup? No current information displayed shows the problem of Cmdlines.txt not executing. If Cmdlines.txt is not in the correct spot then it will not execute. Perhaps your should show your directory structure if possible.

As cluberti has mentioned. Network install - only 1 $OEM$ folder inside I386 folder. I386\$OEM$ CD Install - only 1 $OEM$ folder beside I386 folder. I386 $OEM$ Anything different must be specified in the answer file.

Cmdlines.txt normally resides within $OEM$ folder. $OEM$ folder is inline with the I386 folder. Cmdlines.txt should start with the line below. [COMMANDS] If that is not helpful then you may need to supply some details of your setting arrangement.

This is like giving a blind answer to a blind question. A correct solution cannot be given upon a 1 line question that describes perhaps close to nothing.

If that is the Call command of the command interpreter, then you should only need to use it for calling a batch file from another or use it to call a label within the batch file. Luckily the command interpreter may overlook the mistake, but it does not mean that you should use it. Most commandline tools will open a command interpreter if needed. Those few that do not, you can just execute another command interpreter by using "%Comspec% /c " or "CMD /c ". The /c puts the command interpreter into commandline mode so you can pass your command to it directly. Defrag will open the command interpreter when executed directly.

If your invoke RunOnceEx to run at Cmdlines.txt stage, rather then allowing it to run at first logon, then running at T12 + installing Apps for the other 18 mins would give you your 30 minutes before the finish of Windows setup.

[Unattended] OemPreinstall = Yes This setting needs to be in your Winnt.sif for the special folder contents of $OEM$ to be copied over at the end of textmode setup.

Try this. It should use the full address for the source file. copy /y "%~dp0CUSTOM.DIC" "%APPDATA%\Microsoft\Proof" If it fails then you may need to add a pause in the script to find out what the error returned is.

I use nothing but AutoIt. It can do quite very much anything. Some detail is here of my current setup. I started with RunOnceEx but now run an AutoIt script from Cmdlines.txt that makes the RunOnceEx concept seem too basic and look retro. Most of my AutoIt scripts use a silent install method, then automated if it needs to be. I do not have a list that is added to registry. All the software is installed in sequence from a selected folder by executing each AutoIt script in that folder by searching for it. Each software install is logged for exitcode and time taken. No third party command line tools are used as AutoIt can manage it all. Identify Installer in CMenu can create AutoIt installation scripts very quick. My method is easy, but I am quite experienced with AutoIt. Only those who try to learn AutoIt are the people who will gain everything from it. It is a very powerful basic language indeed.

My Oobe is in $OEM$\$$\System32\oobe and works fine for user creation. Automatic updates can be handled in your Winnt.sif.

It is never 100% sure of success as to running a script while someone is also actively using the computer at the same time. You can increase the chances of success alot by using the Control* functions. Here is a Notepad example using ControlSend() to send directly to the edit control. No need for a window to be active with ControlSend(). $text1 = 'This is a string of text' $text2 = 'Control functions are more reliable to use' Run('Notepad') WinWait('Untitled') WinSetTitle('Untitled', '', 'Notepad 1') WinWait('Notepad 1') Run('Notepad') WinWait('Untitled') WinSetTitle('Untitled', '', 'Notepad 2') WinWait('Notepad 2') Sleep(1000) ControlSend('Notepad 1', '', 'Edit1', $text1) Sleep(1000) ControlSend('Notepad 2', '', 'Edit1', $text2) While WinExists('Notepad 1') And WinExists('Notepad 2') WinActivate('Notepad 1') Sleep(1000) WinActivate('Notepad 2') Sleep(1000) WEnd

Net User to create the user Net LocalGroup to assign where the user should be... Net Group is for a domain... Try it HTH

A general AllUsers template is in @Windows & '\ShellNew\Template.au3' but you should make your own in @UserProfileDir & '\templates' and create a template.au3 in there. Add your own special something in it. My template is currently blank as Scite4AutoIt3 can fill in the information too easy with abbreviations.

Here is my last test in Virtual PC with install timing logs. _.Net_Framework_v1.1sp1.au3 219 seconds _AdAware_Personal_v1.6.au3 9 seconds _Additional_XP_Themes.au3 19 seconds _Advanced_Disk_Catalog_v1.51.au3 4 seconds _AutoIt_v3.1.1.au3 11 seconds _Avast4Home_v4.6.691.au3 19 seconds _BookMark_Master_v3.13.au3 4 seconds _CCleaner_v1.23.160.au3 4 seconds _CDCheck_v3.1.8.au3 2 seconds _Chris_TV_Lite_v4.60.au3 16 seconds _CMenu_v2.0.au3 6 seconds _FFdshow_03.08.2005.au3 13 seconds _FileZilla_v2.2.16.au3 6 seconds _FlashPaste_Lite_v3.2.au3 2 seconds _Foxit_Reader_v1.3.0.930.au3 3 seconds _Free_Download_Manager_v1.9.au3 5 seconds _HideOE_v1.1b1.au3 1 seconds _HtmlHelp_WorkShop_v1.3.au3 12 seconds _Icon_Snatcher_v3.6.1.au3 2 seconds _Inno_Setup_v5.1.5.au3 4 seconds _ISO_Recorder_v2.0.au3 8 seconds _ISTool_v5.1.5.au3 2 seconds _Jane_v1.47.au3 2 seconds _KeePass_v1.03.au3 2 seconds _Maxthon_v1.5.0.au3 13 seconds _Meazure_v2.0.au3 3 seconds _Nvu_v1.0.au3 9 seconds _PatchWise_Free_v3.29r.au3 2 seconds _PDFCreator_v0.81.au3 31 seconds _PhotoFiltre_v6.1.5.au3 5 seconds _Process_Controller_v3.0.au3 2 seconds _PSPad_v4.3.3.au3 5 seconds _RainLendar_v0.21.au3 3 seconds _SciTe4AutoIt3_30.08.05.au3 14 seconds _Spybot_v1.4.au3 4 seconds _SunJava_v1.5.0.05.au3 88 seconds _Talking_Messenger_v3.1.au3 3 seconds _TaskSwitchXP_v2.0.8.au3 2 seconds _tinySpell_v1.3.au3 2 seconds _TortoiseCVS_v1.8.22.au3 6 seconds _WinDowse_v5.1.au3 3 seconds _WinMerge_v2.4.0.au3 4 seconds _WinRAR_v3.50.au3 3 seconds _Xplorer2_lite_v1.3.0.2.au3 3 seconds Total time = 10 minutes and that is lean anount of progams on a cd with custom files and settings added also. These are AutoIt scripts with all the tweaking that would take me hours to do manually installing and configuring. While time maybe lost on creating a unattended cd, you are but prepared for an installation which can be done while you sleep. I don't lose a tweak, or a favorite file or nothing as I keep adding to my project. It is an never finished project as it can be always enhanced on as time goes by. Any task that you may do multiple times with a PC are saved time by scripting methods. Heck, probably why I luv using AutoIt so much. Plos it is an interest.

For keeping a window on top, use: WinSetState('title', 'text', 1) and use 0 on the last parameter to turn it off.

Only good reference to AutoIt is the helpfile included with it. Everybody seems too busy making scripts to stop and write a devoted book for AutoIt. You could check the AutoItWiki for alittle more. There is also a Unattended Wiki here that has installation scripts.