MHz

The fullpath or filename to the script to be executed in the windows folder. You could just use a filename as the script is in the systems path. Example DOS entry to add to registry: Reg Add HKCU\Software\Microsoft\Windows\CurrentVersion\RunOnce /v _FirstLogon /d FirstLogon.cmd /f This will execute FirstLogon.cmd script in the systems path. Don't run the FirstLogon.cmd script from CD as it may not be available latter when you create new accounts and logon into them. This is what I do. I use AutoIt scripts but you can use cmd scripts also. I execute an AutoIt script from Cmdlines.txt, which installs my software and then adds to HKCU\RunOnce the fullpath to another AutoIt script that I copy to the Windows folder. Note: I now have an AutoIt script in the Windows directory (hidden from view) and I have a HKCU\RunOnce entry that will execute the AutoIt script. For each account for which 1st active desktop logon happens, the script in the Windows folder will execute it's set tasks.

The space after .lnk could be removed also that shows in the pictures. ...lnk "

It is still currently the last posted script in the Autoit thread and I do not want to prolong to revise the script for too much longer. The last posted script is the best to my current knowledge unless someone can prove otherwise. For proof of failure, I do need good information to pinpoint any issue with the script. I still have not tested DT4 from Cmdlines.txt yet, which is where I install software from, so that may reveal a revise of the script with an extra window added or something.

Check your PATH variable. Should display a string as such: C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem If your system directory is not in Path, then that can explain your problem.

@muiz What sets the results to be different between these PCs ? Are the window titles the same on these PCs ? Any information could be helpful. Edit: Have updated the posted script with some changes that may help. Since DT4 is sometimes not installing on the reboot for some PCs. I would like to know if the script is starting on reboot (you should see the icon in the systray), or the installation does finish but without result. The updated script will invoke DT4 to execute after reboot, if it does not show the 1st window in 30 seconds as long as the script runs on reboot ok. @RogueSpear Thanks for the nice words. I'm glad you are learning through my scripts. It makes the effort spent more worthwhile.

I add a entry into HKCU\RunOnce from Cmdlines.txt. This is added to HKU\.Default at T-12 so it will run for each account. The script is copied to the Windows directory, hidden and executed there, as from the HKCU\RunOnce (HKU\.Default) entry created. This has been tested to work with existing and newly created accounts.

I notice the Desktop Icon sometimes remains. This is not a script issue as more of a Windows Desktop issue with refreshing. Reboot is not required as simply pressing F5 while on Desktop will make the Icon disappear. It is not a constant refresh problem to be concerned about. You may find a virtual machine install may not refresh ok ? Wizard, may look into handling it.

I have been notified by PM of BandWidth Exceedance of CMenu site. Thanks MtDew12oz for the info. RapidShare Download Link has been added to the 1st post. News: Some options in Identify Installer were not being enabled but are now enabling correctly now in the version upload to RapidShare. Enjoy.

Hi muiz, New Daemon Tools 4.00 script posted. I have troubles trying to reproduce your problem, so it maybe your timed reboot causing the problem. The script should run at RunOnceEx (I assume where you are running it?). You then logon and DT4 will complain of a reboot needed. The script should handle it and reboot 10 seconds after that window (gives everyone time...). It should run DT4 during the next logon to Desktop after reboot. Remove your reboot command from your script and let the DT4 script handle it. Please do not post responses in the AutoIt thread as it is not a devoted DT4 thread. Alert me of any further problems. MHz. If anyone else is experiencing problems, then post here after using the latest script. Thanks. Debug Only Script: _Daemon_Tools_v4.00.html Normal Usage script: AutoIt thread

To strengthen on what tom_vilsack is saying. If your top notch ram is not JEDEC compliant ram, then it could be a compatiblity issue between the motherboard and the ram. Changing the timings of the ram will possibly prove useless if it not compatible with your mobo. Corsair makes some good ram but it goes outside JEDEC standards. I went through a 3 month ordeal to discover the problem and to get it resolved. Had the ram sent away for a month to be tested, but it returned as passed. Matching pair of ram modules yet my mobo could tell them apart! Finally the supplier exchanged it for cheaper Kingston ram which is JEDEC standard and now runs like a dream. Don't kid yourself. Download Memtest86 and test your ram. The quicker you can positively identify the problem, the sooner it will be fixed.

This works fine. You do not see it running but it cleans. REG ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce /V ccleaner /d "\"%programfiles%\ccleaner\ccleaner.exe\" /auto" /f General rule: For each double quote within surrounding double quotes, add a backslash in front of them.

If your not making an ISO first then try CDImage or CDImage Gui as mentioned here. You can then just burn the whole bootable image at once.

Oobeinfo.ini seems limited in non-sysprep...installs that I have tested in the past. Remove the [options] section and just use it to create users. I use Oobeinfo.ini and has not failed for user creation yet.

You assume that this is correct as you think the point of reference is from I386 ? Setup default looks for $OEM$ in the root of a CD so your addressing is perhaps invalid. Just remove that whole line and let setup run with the default.

Is that HKLM Runonce or HKCU RunOnce. Or do you actually run it from HKLM RunOnceEx, like alot of people seem to do? These 3 registry keys run at different times and have different characteristics. HKCU RunOnce runs when the desktop is active and that is when I run a script to cleanup shortcuts...

http://www.msfn.org/board/index.php?showto...58797&hl=iTunes

How can that work? The /qb needs to be after the msi filename.

AutoItInfo Tool A small example

Lots of Information here: Unattended CD/DVD Guide For AutoIt scripts, you will need to have to download AutoIt. Scite4AutoIt3 editor will help if you need a programming editor. It has lots of tools onboard to help to make a successful script. Check the script for any changes needed. The author may have specified instructions. You can then compile the script into an executable, or just use AutoIt3.exe to run the file. AutoIt3.exe "Script.au3" Use a path as required.

An installer just extracts Adaware to the HDD. No runtime, no registry entries... All Users should show for all users. Try this @echo off echo this will copy ad aware's links to the program group echo and the desktop echo. copy /y "%systemdrive%\Install\AdAwareSE\Ad-Aware SE Personal.lnk" "%AllUsersProfile%\Desktop\Ad-Aware SE Personal.lnk" xcopy "%systemdrive%\Install\AdAwareSE\Lavasoft Ad-Aware SE Personal" "%AllUsersProfile%\Start Menu\Programs\Lavasoft Ad-Aware SE Personal" /E /C /I /Q /G /H /y copy /y "%systemdrive%\Install\AdAwareSE\INSTALL.LOG" "%systemdrive%\INSTALL.LOG" copy /y "%systemdrive%\Install\AdAwareSE\INSTALL.LOG" "%systemdrive%\utilities\Lavasoft\Ad-Aware SE Personal\INSTALL.LOG"

I will try and create an automated scripted with AutoIt if needed ?

Google tells me that .Net Framework v2 is KB829019. I do not believe the intregrate switch will work with it. Do you see KB829019 as a 23 Mb download at windows update site?

Some handy info: IEPrivacyKeeper.exe executes after silent install.

Can't? And where do you think the DivX installer is? Chances are that it is extracted and executed from your temp directory. I do this with AutoGordianKnot and Gordianknot in the AutoIt thread. I wait for the temp installer to show it's 1st window, then I hide the window. I then execute the temp installer with silent switches and once done, I just close the process of the 1st temp installer. Setup happily continues... That should work unless of the silent switches problem that BoardBabe has mentioned. I would check myself but that bloated installer is too big for just installing a video codec.

You may want to check the AutoIt thread as I have done it with 1 script.