RunOnceEx x2?

[Denney]

Hey guys. After my RC2 sfc_os.dll problem, I was wondering if it's possible to perform RunOnceEx on 2 boots rather than 1?

To clarify:

After setup finishes and computer boots, I apply the sfc_os.dll reg hack and restart (using RunOnceEx).

When Windows starts the second time, I want it to perform additional tasks (install programs, reg edits etc.).

Can I just add another RunOnceEx.cmd that gets imported at the end of the first boot? I don't think that would work because that would just overwrite the entries it is running now, is that right?

This has probably confused you as much as it has confused me upon reading this.

[MCT]

i think it'd work, ive never done it, try it in vmware & see

good luck

[Denney]

Normally I would do that but the PC I'm on at the moment isn't really capable of running VMWare.

My main PC is being repaired at the moment (waiting for a new mobo+cpu after the last ones broke ) and I want to have a brand new unattended CD ready for when it's fixed.

I could test it on my spare PC but it'd take forever to install (P2-250, 96MB RAM).

[MCT]

ya, it probly would take along time

but, it should work at the end, cause, your done what your doing, so when u reboot. it should be there again 2 install other stuff, just point it 2a different file so your not installing same stuff over & over

good luck

[Denney]

Heh. Yeah I figured as much.

My only question is does Windows delete the original RunOnceEx keys BEFORE or AFTER the last RunOnceEx command is executed? If it is AFTER then the new commands that get added by that last command would be deleted.

I don't know. I guess I'll have to try it out somehow... maybe using this comp... just install 2 small programs or something to test out my theory.

[Denney]

Just tried it... here is what happened:

First RunOnceEx entries were added (001 and 100), then I restarted.

Upon boot, 001 was executed and then 100 (as usual). 100 added the next set of RunOnceEx entries (001, 005, 100).

100 then finished, deleted the new 100 entry (so it deletes them as they go) and then deleted the new TITLE registry key.

Upon restart, the new set of RunOnceEx settings were executed but without a title and without the 100 entry.

So, yes it worked and no it didn't.

I worked in the sense that as long as you don't want a title for the new setup box and you don't have a new entry with the same number as the one that's adding the entries it will work as expected.

[Bâshrat the Sneaky]

When Windows starts the second time, I want it to perform additional tasks (install programs, reg edits etc.).

Can I just add another RunOnceEx.cmd that gets imported at the end of the first boot?

Over here it works...

[XtremeMaC]

why don't u copy the hacked dll into the cd, then just apply the registry hack at 1st logon along with the install of programs?

also I believe u can put a command in runonce after running it for the first time...

[Denney]

@XtremeMaC: With the new sfc_os.dll file, you have to restart before the SFCDisable setting in the registry will take effect.

Windows Setup has a habit of setting that registry entry to "0" when it hits the T-6 minute. Unfortunately, there isn't another option to run anything after that time before setup finishes.

BTW: The hacked file is on the CD.