RunOnceEx from cd doesn't start

[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

[Alex123]

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

[WwTIPPYwW]

Alex - are you testing by burning cds or making images and testing in VMWare or Virtual PC?

Do the later one and you don't waste so many blanks.

[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.

[GreenMachine]

All sounds too wierd for me ... I still believe

• CMDLINES.TXT should be in, and ONLY in, $OEM$, which is at the root of the CD. (CD install.) (Duplicate, identical files is not a technically sound solution, especialy on a machine that has not yet been FUBARed)
  
• .\ should preceed any file names for files in that directory, though it does not always appear to be "needed"
  

Also, don't be confused between \, .\, and ..\

\ = Root of current drive

.\ = Current directory

..\ = Parent directory ("up one level")

[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