Enable Autorun in Ext_Rom in new kitchen?

[docjones]

Is there a way to enable the autorun in the new kitchen? I can't seem to find anything for it anywhere, and I have a few extra large programs automatically install from there. Right now, I just manually kick off autorun.exe and it processes the config.txt for me, but I would like for those items to run automatically right after first boot like a stock rom does.

[verizonguy]

 
[HKEY_LOCAL_MACHINE\Comm]
“AutoRunFlag”=dword:1

[docjones]

Thanks for the reply, VerizonGuy. I set this registry setting in an OEM in my kitchen with guid ffffffff-ffff-ffff-ffff-ffffffffffff but it seems that some event that runs later shifts the setting back. Presumably, I need to set it to 0, but apparently, it's always set to 1 in the kitchen no matter what I do.

I found the following info on xda-dev that further complemented your reply:
http://forum.xda-developers.com/showthread.php?t=301365

[verizonguy]

It is advisable to use a valid guid, and if necessary, only modify the first set to f's to get it to run at the end.

As for the 0/1, you have it backwards. It is a boolean switch where 0 == off && 1 == on. So, to autorun, you want the switch "on" (1).

In order to successfully run from your exented rom, you also need to define AutoRun & AutoRunCFG...sooo after you flash your rom, open a registry editor and navigate to [HKEY_LOCAL_MACHINE\Comm]
Make sure the AutoRun is set to \Extended_Rom\autorun.exe
Make sure the AutoRunCFG is set to your config text file, usually \Extended_Rom\config.txt.
Next make sure you actually have an autorun.exe and that you have modified config.txt to have autorun run the cabs you want run.

[docjones]

Thanks for setting me on the path, Verizonguy! I had all of those details right, but apparently I needed to leave a blank line at the end of my RGU. I found this out from the note at the top of the RGU created by OEMizer. Originally, I made that RGU from scratch a long time ago. Oemizer is a good tool, as it not only gave the option to put f's at the beginning of the guid, but also created new files for me to just cut/paste into. I like it.

Thanks again!

If any one searching for this info is interested, this is the code I used in my RGU(Don't forget the blank line at the end!):
[HKEY_LOCAL_MACHINE\Comm]
"AutoRunFlag"=dword:1
"AutoRunType"=dword:1
"AutoRunCFG"="\\Extended_ROM\\config.txt"
"AutoRun"="\\Extended_ROM\\autorun.exe"

[gguruusa]

Originally Posted by docjones

Thanks for setting me on the path, Verizonguy! I had all of those details right, but apparently I needed to leave a blank line at the end of my RGU.

One of these days I'll get around to making BuildOS compensate for that requirement...

[docjones]

Every element of this kitchen is fantastic and it's a great tool for making our phones even better. I appreciate the efforts of everyone involved in it, as well as the users on this site. In this particular case, it was very handy just to have that comment box at the top of the created RGU file. It was also nice to get such a useful reply from Verizonguy so quickly. Hopefully this will help someone in the future if they need to use the ext_rom.

[verizonguy]

Originally Posted by gguruusa

One of these days I'll get around to making BuildOS compensate for that requirement...

Would it be easy to make buildos add a blank line to the rgus?

We could reverse and build a new rgucomp if we have to.

[colonel]

I suggest using tautoinstall.

[tiermann]

Tier Autoinstall is also available in the kitchen. It searches for cab files in \Storage Card, \Storage Card\Boot, Ext_ROM, and \Windows, then it gives you a checklist to choose which ones you want to install. It rewrites the config.txt (leaving other lines besides cabs intact) and then runs autorun to install them.

You can use your own custom config.txt just by dropping it in the Patches folder.