Alex123

Well, my cmdlines.txt file never was placed out of $OEM$. The one that was placed out of there was RunOnceEx.cmd, and that was because the parameter .\ in cmdlines.txt. Now, I was understanding .\ meant one level up, not curren directory. That's why I made a copy of RunOnceEx.cmd alongside $OEM$. And the strangest thing is that it didn't fail. Now, according to what GreenMachine just explained if .\ means current directory, then I don't understand why RunOnceEx didn't start when was left alone inside $OEM$ without the copy of itself outside $OEM$, but it did work when a copy of it was left outside. Weird. Alex123

Well, I am testing burning cd's and since they are not too expensive I don't mind. However is worth to take a look of Virtual PC. Probably I'll do soon.

Hi people following this thread. As I explained before, I am testing my unattended installation in a PC which at the beginning worked ok with the normal method of RunOnceEx. Then I tried to do the same but this time running everything from the cd as explained in the guide Running RunOnceEx from CD. At that point and after making sure everything was correct, I found out my RunOnceEx process not running. That's why I started this thread asking for help and got an answer saying the parameter .\ has to be placed in cmdlines.txt like this: [COMMANDS] ".\RunOnceEx.cmd" That solved the problem. However I decided to change the order of the program installation in my RunOnceEx.cmd. That was all what I did, modify this file and strangely next time I tested it didn't pick RunOnceEx in the test. I was told .\ means backing up one level which is that, cmdlines.txt, according with the description above is looking one level up for RunOnceEx instead of looking in the default location, $OEM$, if it was without the .\. It is weird I know, but that solved the problem in the prior test even knowing RunOnceEx.cmd was not up on level but inside $OEM$ folder alongside with cmdlines.txt. I tested twice the installation with the cmdlines.txt and RunOnceEx files running inside the same folder $OEM$ but failed again. Strange behavior because it worked in the test I did when RunOnceEx wasn't modified to change the program installation order, even if it was supposed to look for RunOnceEx one level up, out of $OEM$ with the parameter .\ in cmdlines.txt. Then my next question was if in one scenario with the .\ parameter it worked and after only modifying RunOnceEx it didn't, if placing RunOnceEx.cmd up one level (.\) out of $OEM$ it was going to work. So in case cmlines.txt looks for RunOnceEx.cmd either inside or outside $OEM$ it can't miss it. I did that, left everything exactly as it was when it failed but only copy and paste RunOnceEx.cmd out of $OEM$ and tested again. It worked this time. But certainly I don't know what was what happened. Could be that cmdlines.txt picked the one that was out of $OEM$ because of the parameter .\, and that's why it didn't fail one mor time. But if it was the case I am wondering if I get rid of the parameter .\ and leave only RunOnceEx.cmd inside $OEM$ it will work. Well this is a little strange and I got my CD working, but certainly I will definitively burn another copy with the last propossed setting and will let you know how it behaved. However I am not sure what could affect the fact that sometimes the RunOnceEx process is picked up, and other times it is not. I hope my testing helps others understanding this process and saves time for all. Alex123

Let me add something else to this thread. I just created a second cd with the hotfixes first and Norton Antivirus last in the RunOnceEx.cmd. That was all that was changed, the order in which the programs are placed in RunOnceEx.cmd. However this time it wasn't picked up even with the CMDLINES.TXT with the leading .\ parameter. I am wondering what could have happened. Is it dependant on the pc mood? Because nothing else was changed. The cmdlines.txt file is in the $OEM$ folder alongside with the RunOnceEx.cmd file. As I am understanding, the parameter .\ calls one level up. Which means it called RunonceEx.cmd not inside $OEM$ but alongside with it. That's why I say it must be dependant in the pc mood. Exactly the same set up with the only difference of the order in which the programs were placed in RunOnceEx. Now I am thinking, if it is dependant on what pc you are working on, wouldn't a fix to this be, placing a copy of RunOnceEx.cmd alongside with $OEM$ and leaving one inside it. That way cmdlines.txt will pick any of them without possibility of missing it. What do you think? Alex123

Thanks WwTIPPYwW. Good suggestion. I will order things based on your recommendation. It's good to see how everyday something new is learned. Thanks to all. Alex123

I second what GreenMacnine says. My file was placed in the correct folder $OEM$

A suggestion to the mods. It should be highlighted on the guide to make RunOnceEx from CD that if it fails to call RunOnceEx.cmd during installation, the leading .\ must be placed in the cmdlines.txt file like this. [COMMANDS] ".\RunOnceEx.cmd" Hope this help others. Alex123.

GREEEAAT! That trick solved the issue. Now it is running as it should. Thanks for your help homiebrah.

Thanks. But let me clear this to myself. When I was running RunOnceEx with the original method, I didn't have to add the ".\" in cmdlines.txt and it worked properly. So, I am assuming it is only needed when used the alternative method of running all software from cd. As you could see I only run RunOnceEx from there, but if I decide to run any other thing from there then I have to add the ".\" before all commands. Am I right? Right now I am in the middle of running the process with the tip you shared with me. Minute 19 and counting.... I will post back with the results. Thanks for all your help. Alex123

So, that means that it didn't work for you either when left as shown above? After you added .\ did it fix the problem? Thanks for the reply. I will give it a try. Alex123

Hi everybody and first of all, thanks to all these great people that dedicates their time to help others. I read before making questions in the forum, but this time I could not see any answer for the question I am about to ask. When trying to migrate the process from regular RunOnceEx to RunOnceEx from CD I am running into an issue. At the time when cmdlines.txt is supposed to be picked up, which I understand is at minute 12, it looks like it is not being picked up. That's my thinking, but could be something else. After rebooting RunOnceEx should be run but it doesn't happen. The OS gets installed but no programs are installed. However something that I tried was to manually execute RunOnceEx.cmd and rebooting, and that way all the programs were installed including the hotfixes that can't be installed through svcpack.inf. My understanding tells me that it should be run automatically after rebooting and login in the first time. I followed all the instructions from the guide on how to create an unattended installation with RunOnceEx from cd. Created a blank CD.txt file and placed it in the right place as indicated. I will include my RunOnceEx.cmd file for you people to review and help me figure out why it is not being picked up. Thanks in advance for any help given. RunOnceEx.cmd cmdow @ /HID @echo off IF EXIST D:\CD.txt set CDROM=D: IF EXIST E:\CD.txt set CDROM=E: IF EXIST F:\CD.txt set CDROM=F: IF EXIST G:\CD.txt set CDROM=G: IF EXIST H:\CD.txt set CDROM=H: IF EXIST I:\CD.txt set CDROM=I: IF EXIST J:\CD.txt set CDROM=J: SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx REG ADD %KEY% /V TITLE /D "Installing Applications" /f REG ADD %KEY%\001 /VE /D "Adobe Acrobat Reader 6" /f REG ADD %KEY%\001 /V 1 /D "%cdrom%\install\Apps\AdobeReader6\AR6.msi /QB" /f REG ADD %KEY%\005 /VE /D "SpyBot Search And Destroy 1.3" /f REG ADD %KEY%\005 /V 1 /D "%cdrom%\install\Apps\spyBSD\spyBSD13.exe /silent /nocancel /taskbarhide /autoclose" /f REG ADD %KEY%\010 /VE /D "Norton Antivirus 2003 Pro" /f REG ADD %KEY%\010 /V 1 /D "%cdrom%\install\Apps\NAV2003\NAV\NAV.msi /QB" /f REG ADD %KEY%\020 /VE /D "MSN Messenger 6.0.0602 Final" /f REG ADD %KEY%\020 /V 1 /D "%cdrom%\install\Apps\MSN\MsnMsgs.msi /QB" /f REG ADD %KEY%\025 /VE /D "Nero Burning ROM 6" /f REG ADD %KEY%\025 /V 1 /D "REGEDIT /S %cdrom%\Install\Apps\nero\register.reg" /f REG ADD %KEY%\025 /V 2 /D "%cdrom%\Install\Apps\Nero\nero6009.exe /silent /noreboot" /f REG ADD %KEY%\030 /VE /D "Installing Hotfixes" /f REG ADD %KEY%\030 /V 1 /D "%cdrom%\install\hotfixes\hotfixes.cmd" /f RunOnceEx is placed inside $OEM$ folder and alongside with it is cmdlines.txt which is: CMDLINES.TXT [COMMANDS] "RunOnceEx.cmd" Here is winnt.sif if needed to be reviewed. WINNT.SIF ;SetupMgrTag [Data] AutoPartition=0 MsDosInitiated="0" UnattendedInstall="Yes" [Unattended] UnattendMode=FullUnattended OemSkipEula=Yes OemPreinstall=Yes TargetPath=\WINDOWS Repartition=No WaitForReboot="No" Autoactivate = No UnattendSwitch="no" [GuiUnattended] AdminPassword=" EncryptedAdminPassword=NO OEMSkipRegional=1 TimeZone=35 OemSkipWelcome=1 [Display] BitsPerPel=32 Xresolution=1024 YResolution=768 Vrefresh=75 [UserData] FullName=" OrgName=" ComputerName=* ProductKey=* [Tapilocation] CountryCode=1 Dialing=Tone [Identification] JoinWorkgroup=* [Networking] InstallDefaultComponents=Yes [Components] msmsgs=off msnexplr=off Thanks again and any help will be appreciated. alex123

Thanks for your feedback. Well, the intallation folder shows a three diferent icons that could be used to initialize the installation process. Setup.exe, launch.exe and ecdc5.msi All of them get me to the same InstallShield Wizard. I also searched for *.iss files in the application folder and nothing is found. I am assuming this is a special application, since it doesn't act like a normal Install shield act. Also, I think I have to design a registry hack to overcome the serial key step. What I think it has to be done is to silently install it with the following command: setup.exe /s /v/qb and then apply the registry key. Let me someone know if I am totally lost. Thank you.

I am new here. Hi everybody. I am not sure if people like Easy CD Creator or what, but I would like to install it. I underustand it is a InstallShield setup, and it needs to create a setup.iss file. I undurstand also I have to run this command: setup.exe -R. It doesn't run from there, so I read it should be used setup.exe /s /v/qb, which installs it, but I am wondering how to manage the serial key. As I said, I am a newbie and willing to learn. Thanks for your help. Alex123