yashsingh1/xdaforums huggingface dataset:
[Windows Mobile Development and Hacking General] Thoughtscape:
How to cook? Veery basic directions needed

:eek: Hi guys,

I have an HTC Universal WM6 [Jwrightmcps Crossbow ROM Update 2_12_08 WWE] and it is great except for one or two apps I want to delete and some I want to add.

I want to be able to do a hard restart anywhere I am and have it automatically install all my previous settings, etc. The settings at this stage are not important, just the files.

And some from other forums. Basically I have found that I need to:

1. Put desired cab files in cab folder on Storage Card

2. Install said cabs to the Storage Card [Have downloaded WinCE Cab Manager so I can change the default installation directory.

3. Follow this -> http://xdaforums.com/show...0&postcount=19 for loading cabs that require user input.

4. Remember to save my damn contacts so I don't have to keep adding them from my sim lol.

But on this forum [oops forgot the link - saved it as .mht] it says this

- Cook the attached SDAutoRun.exe into \windows

- if AutoRun.exe isn't already in \windows then place a copy there too

- Replace the "RST: Reset" line in config.txt with "EXEC: windows\SDAutoRun.exe"

So you see? What is to "cook the sdautorun into \windows.

I did find a forum that may have helped.. but it was for wm5. Basically it said to copy desired cab into \Extended_Rom\ and rename it to have "default" at the beginning. It also said something about a config.txt file in the extended rom but there is no such thing on wm6 or this rom.

So please help. I will be eternally grateful

Cheers,

Thoughtscape.
[Windows Mobile Development and Hacking General] Sleuth255:
"Calendar" is how to represent "Calendar" in xml. See my example on post 2. I have the exact syntax you're looking for in my today settings.
[Windows Mobile Development and Hacking General] Sleuth255:
@thoughtscape: You have to be a "ROM Chef" to understand. That's why this thread is entitled "ROM Chefs: SdAutoRun gives customization to everybody" ;)

The information you seek is here in various forms. Your best bet is to start in your own device forum. Here is a good starting point:

http://xdaforums.com/forumdisplay.php?f=357

hint: look for a thread named "Hypercore Kitchen".....

If you're not interested in cooking, then you need to wait for a Universal based UC capable ROM. You might want to post in the support thread for your favorite chef and point him here b/c its possible that nobody cooking Universal ROMs even knows about UC yet.
[Windows Mobile Development and Hacking General] Sleuth255:
Got them on the list!
[Windows Mobile Development and Hacking General] anubis.genix:
any news about the autodetecting feature for foreign paths of storage cards?

too bad i can't use it right now :(
[Windows Mobile Development and Hacking General] c_shekhar:
Thanks bro! grateful to you. It worked..
[Windows Mobile Development and Hacking General] Sleuth255:
Next version will feature a registry setting you can cook in to override "Storage Card"

This is the registry setting it will use (kudos to Noonski for finding this):

[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\ SDMemory]

"Folder"="Storage Card"

Let me know if your device has the correct value in this registry entry.
[Windows Mobile Development and Hacking General] MooCan:
Request ?

Hi,

Thanks for this great tool.

I would like to know if it's possible to make a version which could be run from a SD Card and execute the SDConfig.txt from it's current Path ?

Some have multiple device with differents packages for each.

It could be fun to do a structure on an SD with a tree structure and an SDConfig for each Device with all predefined packages and applications for auto installation and customization. All is needed will be to launch the good SDConfig on your SD Card within the good folder depending on your device.

Thanks

Moo

Hoppe I'm clear :)
[Windows Mobile Development and Hacking General] Sleuth255:
@Any Chef who wishes UC would work on a non-WWE ROM

I'm planning on implementing Noonski's idea for determining the Storage Card name, but I need you to verify that this registry setting is correct for non WWE ROMs:

[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\ SDMemory]

is the "Folder" value = the true name of your storage card?
[Windows Mobile Development and Hacking General] Sleuth255:
Your solution is simple (I actually use it myself): Why not keep your separate folders along with the associated SDConfig.txt on your SD card just like you are suggesting. Then just copy the one you need to the root of your sd card before hard resetting your device?

In my case, I have a "Hermes" and a "Kaiser" directory on my storage card, both containing SDConfig.txt + XML customizations specific to the associated device. I have a common Cab directory with all cabs in it. Each SDConfig.txt file chooses the cabs it needs and runs XML based customization from the device specific file location.

So, if I want to flash a new Hermes ROM, I simply copy SDConfig.txt from \Storage Card\Hermes to the root then flash the new os. Likewise for Kaiser.

Piece of cake :)
[Windows Mobile Development and Hacking General] Noonski:
I'll check this at a new MUI collecting translating thread that's been started at ELF Forum.
[Windows Mobile Development and Hacking General] Sleuth255:
Thanks! I've already had verification from anubis.genix that his reg setting is correct for his cardname.

Unless I hear otherwise, I'm gonna start a public beta tomorrow for v2.0:

Good news:

will include the card name logic for non-WWE support

will automatically detect and fix SDConfig.txt formatting errors. Extra/missing spaces, tabs etc are corrected. Only lines with a ':' character in them are passed on to autorun which means that UC ROM flashers can even put comments and blank lines into their SDConfig.txt file now...

Bad news:

It's 500 bytes larger :(

This should clear up a lot of format related problems.
[Windows Mobile Development and Hacking General] MooCan:
Thanks for your answer.

I have too a lot of devices (Hermes, Kaiser, Universal) and find interested if a program could make installation and customization without the need of including it in ROM mastering process as a standalone mode and or could be launch at any time or different time (not specially after a hard reset only) for different purpose or if you miss to insert your SD Card on Hard Reset (that's for me!).

We spend so much time on this little companion (hooo me too) and I'm starting kitchen learning for the kaiser and maybe after for hermes and the others if they are not died before.

Thanks

Moo
[Windows Mobile Development and Hacking General] Sleuth255:
You can run UC any time you like: just set HKLM\comm\SDAutoRunFlag to 0 and tap \windows\SDAutorun.exe.
[Windows Mobile Development and Hacking General] abusalza:
SDAutoRun sign by me:)
[Windows Mobile Development and Hacking General] Sleuth255:
yikes! I wasn't expecting this. Tks! :) Do I need to install any certs?

edit: base signature validated against OEM certs with 100% original code :D damn, nicely done. I'll test it out tomorrow.
[Windows Mobile Development and Hacking General] abusalza:
No need, also for registry "0000101C"=1
[Windows Mobile Development and Hacking General] Sleuth255:
How's the weather on Borneo btw? I've always wanted to go there...
[Windows Mobile Development and Hacking General] abusalza:
Always cloudy and also rained for a last month:D
[Windows Mobile Development and Hacking General] Laurentius26:
Thank you guys,

I asume this is the version 2.0 Sleuth was talking about?
[Windows Mobile Development and Hacking General] Sleuth255:
nope, that's a signed version of the original. I'll have the beta up soon & will PM everybody as well.
[Windows Mobile Development and Hacking General] Sleuth255:
Here's the public beta for SDAutoRun v2.0. Please read this post carefully as I've made it a whole lot easier to test with any SDConfig.txt file you can think of to throw at it.

Changelog

Works with non-WWE ROMs. SDAutoRun uses the registry to determine the default name for the Storage Card now.

Automatically corrects SDConfig.txt formatting errors. Extra/missing tabs, spaces, newline characters etc are corrected before passing to autorun.exe.

New string value "SDAutoRunVersion" created in HKLM\comm contains "2.0". This will help debug SDConfig.txt file issues in the user thread.

abusalza signed it with an EOM cert too (see signed version in attachments) so relaxed security registry settings shouldn't be required

SDAutorun v2.0 should be fully compatible with all SDConfig.txt files created to date. Additionally, there shouldn't be a config file you can throw at it that it won't re-format to the following template:

Commands will left justified into the first 5 characters and space filled

Parameters will be left justified to the 6th character and trailing whitespace will be removed

Lines that don't contain a command will not be passed to autorun. Note: To determine validity, I only check for a ":" in postion 4 or 5 here to allow for future command expansion.

if no valid commands are encountered, then a file containing only "RST: Reset" will be created

Here's how to test:

The attached zip contains two programs. "SDConfigTest.exe" does everything that SDAutorun.exe does except execute autorun. This makes it easy to test sdconfig.txt command combinations:

connect up your device and open activesync explorer

drop SDConfigTest.exe and SDAutoRun.exe into your temp directory

drop your test SDConfig.txt into the root of the Storage Card's folder

using a registry editor on your device, set HKLM\comm\SDAutoRunFlag to 0

now tap on \temp\SDConfigTest.exe. It will appear to do nothing at all but will actually create a new SDConfig.txt file in \windows. Drag this to your desktop to view the results!

If you want to actually run UC, then tap \temp\SDAutoRun.exe instead of \temp\SDConfigTest.exe.

I've tested the peejeebees out of this and have not been able to make it fail. Be sure to try the signed version with normal security settings to make sure its compatible with OEM certs in your device's root store. Note that this doesn't work with my WM6.1 release. However, most everything else (all SPB software) doesn't run either on my ROM with relaxed security settings turned off. Kudos again to abusalza for this! I will release this version officially on March 17th unless something turns up.

Have fun with it! Remember that SDConfigTest.exe is only for format testing and won't be included in the final release. Cooking instructions will remain unchanged. To upgrade your UC capable ROM to v2.0 just put the new SDAutoRun.exe in /windows where v1.0 used to reside and re-cook. I'm planning on just doing an in-line update to my current ROMs.
[Windows Mobile Development and Hacking General] Noonski:
Your to fast.

I also got a verification that this was the same for Italian storage card.. with the reg key and the dutch and german i checked myself.

New toys to play with and reak our little devices.

Also (need to recheck) found a verys low Autorun when i had a SDconfig.txt file in my Cabs folder.

but that might be paranoia.
[Windows Mobile Development and Hacking General] Sleuth255:
testing autorun will be important. While I'm confident that I've correctly coded in formatting rules that are derived from experiences in the user thread, I still need to be sure that autorun works correctly when it processes config files formatted according to those rules. I'd be surprised if this wasn't the case but who knows...

Note: for slowness debugging it is important to verify during a Hard Reset. I've always noticed that Autorun seems to run quicker during customization.

I'm currently rebuilding v3.0Sleuth and will begin autorun tests shortly.

Edit:

autorun tests completed. Autorun runs at its normal speed on my Kaiser. I tested everything but CPY1:, CPY2: and SHOW: using the attached SDConfig.txt file and everything processed normally. You're not gonna believe your eyes when you see how screwed up this file is from a formatting standpoint :eek:

For Kaiser at least, SDAutorun.exe looks good atm.
[Windows Mobile Development and Hacking General] RanDomIze:
UC dont work in My ROM

Hi

I'm trying make a ROm with Uc, but Dont Work

Start the Autorun, and instal, then the Devise go to Softreset and dont go to the SDConfig.txt in the SDCard.

I attach the Cnfig.txt and the SDConfig.txt
[Windows Mobile Development and Hacking General] Sleuth255:
Try the signed version that's now on the first post.
[Windows Mobile Development and Hacking General] abusalza:
SDAutoRun.2.0 signed:)
[Windows Mobile Development and Hacking General] Sleuth255:
You 'da man :) I'm pretty sure you just signed the 3/17 release too as I've been unable to make this fail. We'll see tomorrow after others have played with it ;)

edit: just tested with security off and the signed version is throwing a security warning on WM6.1 (along with just about every other third party software I've installed including the SPB stuff which I thought was signed as well). It's very likely the certs in my pre-release certificate store. What OEM root are your code signing certs linked to?
[Windows Mobile Development and Hacking General] RanDomIze:
Dont Work.

Bdw, The ROM is a WM6.1.

I instaled the SDAutoRun, Nor mal and signed with the same result.

Then i Instaled the SDAutoRunv2.0_signed, and i have make the test.

With the test, i see the SDAutoRun go to the SDCanfig in SDCard, the SDConfig created in \Windoes is the same i have in SDCard.

But dont instal notting, only do the Last Comand the "RST".
[Windows Mobile Development and Hacking General] OMJ:
I am having trouble getting UC to work w/ my ROM. I'm using the latest v2 signed. After flashing, the AutoRun never runs.....if I manually run SDAutoRun.exe, the customization will run, install my 2 cabs & my .xml, but the .xml changes do not stick. I have also tried using your AutoRun.exe, but still nogo. This is on a Vogue, using a 6.1 ROM

attached are my config.txt, SDConfig.txt, and .xml.

thx
[Windows Mobile Development and Hacking General] Sleuth255:
@RanDomIze:

Ok, if SDConfig.txt is created in \windows and its the same as what's on the root of your SD card then it proves that SDAutoRun is running. One thing SDAutoRun does do at the very end is to execute \windows\autorun.exe. If this program isn't in \windows then that is your problem. In Hermes it may be in ExtROM only. If it is in \windows, then it may not understand \storage card paths. In either case, try placing the autorun.exe program that I've included in the post 1 attachements into \windows, then re-cook. That version is from Kaiser and is known to work.

@Itd:

Sounds like you have two issues: You're not locating the correct autorun text file for your vogue and you have a syntax issue in your xml. Try PM'ing one of the Vogue Chefs who got the device running with UC to find the correct config file for the EXEC: to sdautorun. The user thread has links to their support threads in post 1.

As far as xml syntax goes, you're going to have to debug that yourself. I use a "successive test" methodology that I describe in the user's thead as well.

btw, your xml error is on this line:

<parm name="Name" datatype="string" value="<Modified>"/>

should say this:

<parm name="Name" datatype="string" value="<Modified>"/>

I found this by employing a technique I describe in the user's thread: double click on your XML file to open with Internet Explorer. It will point out XML errors to the exact line.
[Windows Mobile Development and Hacking General] OMJ:
thx sleuth....I fixed the xml....actually I had more errors, lol. so now manually running sdautorun works, but still trying to figure out the autorun issue. just reading the post from mr.carter, he indicated he edited the config.txt just as I did, and cook the sdautorun. not sure what i'm doing different. I'm going to try v1 instead of 2....but I do not see this key:

HKLM\Security\Policies\Polices by setting the value 0000101C to a 1.

I don't see a 0000101C, I got a A, B, D etc, but no C, lol.

btw....thx for all your work on this!
[Windows Mobile Development and Hacking General] Sleuth255:
damn! it should be 0000101a :eek:

I can't believe that typo's been on page 1 this long :eek: (its fixed now)

@RanDomIze: please note this & make sure you are setting 0000101a to a 1 to relax security.
[Windows Mobile Development and Hacking General] Noonski:
Well i thought There was something with SDautorun or my ROM.

But after testing with 2.0 and getting the same result i realized why the Autorun was so slow.

Most my cabs install to SD and all where sett TO normal install, overwriting existing files. This slowed down the process.

Making the flags Not to overwrite existing files sped up SDAutorun.

I though maybe will come in handy for some getting slow SDAutorun with Overwrite flags in the cabs.

And shame on you sleuth for those extra 500k ;)

2.0 doing it's job but haven't made bogus wrong lines to test with yet.
[Windows Mobile Development and Hacking General] Sleuth255:
500 bytes bigger == BloatWare for sure :eek:

...maybe I should just go work at m$...
[Windows Mobile Development and Hacking General] Sleuth255:
Version 2.0 is now live. I've updated the first post.
[Windows Mobile Development and Hacking General] l3v5y:
Damn! Now I need to update some ROMs...

Thanks!

Just out of interest, is it signed?
[Windows Mobile Development and Hacking General] Sleuth255:
No. There were a number of devices that couldn't recognize the cert on the signed beta version (in fact, I didn't hear of any that could) so I didn't include it.
[Windows Mobile Development and Hacking General] l3v5y:
Okay... I think I'll just use the signed copy for the moment (all my ROMs are WWE anyway).

Thinking about potential applications for this, is there anyway to run SDautoRun or similar normally (not just after a hard reset) so that one can install a suite of applications rather than one at a time. It's possible to use CeRun.exe to execute a cab installer, but that seems quite crude to me, and needs a PC to run it.
[Windows Mobile Development and Hacking General] Noonski:
Yeah you can reset the registry

HKLM\Com\SDautorunflag=0

(looking up the corect key)

Nope that is the correct key.

After you rest this you can run SDautorun again without reset.

I'm not sure which version i used signed or not.
[Windows Mobile Development and Hacking General] ark666:
Hi Sleuth255

First of all, congratulations for your work, but i have a problem with sdautorun v2.0, i´ve been building and testing two wm 6.1 roms for my artemis, one wwe and other ptg, my wwe build works just fine with sdautorun, but my ptg version has an issue with storage card, the problem is that in english storage card is no issue but in ptg storage card is "cartão de memória", and sdautorun doesn´t recognize the "ã" and the "ó".

Can you help with this??

Sdconfig is the way it´s saved on my storage card and Sd1config is the way it shows on my artemis with sdautorun.

Cheers

:)
[Windows Mobile Development and Hacking General] Sleuth255:
Interesting issue.... I'll take a look....

edit:

Ok, I just tested it and couldn't reproduce your issue. :(

I have some questions for you:

In your ptg version, what is contained in the "Folder" registry value under HKLM\System\StorageManager\Profiles\SDMemory?

When you run UC you must be getting "file not found" errors. Is the storage card part of the filename in those error dialog boxes "Cartão de Memória"?

Where specificially on your device did you obtain the SD1Config.txt example?
[Windows Mobile Development and Hacking General] ark666:
Thank you for answering my post.

1- the name is Cartão de Memória;

2- the error i get is "file not found" followed by the filename than it resets itself, and the Storage card part appears on screen diferent than the line i wrote in sdconfig, (ex: CAB: \Cartão de Memória\Cabs\rltoday.CAB, while running sdautorun appears the file not found error with this wrong path: CAB: \CartÆo de Mem¢ria\Cabs\rltoday.CAB);

3- the sd1config was a file that i saved in msdos mode, and by chance it saved the file like that. with the same errors that appears on my ppc.

Maybe it´s the fact that we cannot save sdconfig in unicode, that sdautorun doesn´t recognize the "ã" and the "ó"??

Cheers.
[Windows Mobile Development and Hacking General] Sleuth255:
It's got something to do with that I'm betting because the file on my machine saves correctly.

When you tap SDConfig.txt on your device, does Pocket Word show it incorrectly as well?
[Windows Mobile Development and Hacking General] ark666:
No. it shoes Cartão de Memória.
[Windows Mobile Development and Hacking General] Sleuth255:
so tapping SDConfig.txt on your device's storage card brings up Word which shows it as Cartão de Memória yet UC bombs. Interestingly, your two files show different codes for the two letters in question. On mine, using the SDConfig.txt file you supplied, UC identified the missing files using \Cartão de Memória\

Looks like a default codepage issue perhaps. Not sure exactly :confused:
[Windows Mobile Development and Hacking General] ark666:
Thanks, i´ll try that, and keep u informed.

Cheers.
[Windows Mobile Development and Hacking General] Noonski:
Check the BOOT.RGU value to the Autorun file.

It ussually points to extended rom.

But if you make a rom without Ext rom.

And only make RGU in either OEM or SYS folders it doesn't overwrite the Boot.rgu registry.

Again a repeat, and this is only a small thread:mad:

Can Someone reset my posts amount back to 100? ;)
[Windows Mobile Development and Hacking General] Sleuth255:
Just making a quick point here: UC = User Customization. We are getting posters in the user's thread who are having difficulties with their SDConfig.txt files because chefs are incorporating SDAutoRun into their own customization process. This doesn't help ROM flashing Junkies who are trying out your ROM ;)

You guys are the cooks and have access to the regular config.txt customization process. Your best bet is to use this for your stuff then follow the page one guide and only execute UC at the final EXEC: statement.

If you are using UC to solve a customization issue let's hear it! I should be able to adapt UC for Chef's customization needs too while still retaining full user compatibility.
[Windows Mobile Development and Hacking General] l3v5y:
Could you create a version of SDAutoRun that combines two config files, one created by the chef and the other that is actually a User Customisation, and if one is not found it just loads the other and re executes autorun.exe?
[Windows Mobile Development and Hacking General] l3v5y:
Is there any way to disable some of the startup things that happen after a hard reset? I ask this because I've been thinking about ways to make the upgrade process slicker: User connects device, runs an exe which dumps certain settings, builds xmls with those settings, edits the SDConfig the user has set up, copies the edited file and xmls across to the device and then flashes the ROM. When the device starts up, it simply uses the xmls instead of going through the normal setup.

This would allow a faster startup and require less user interaction.

I can do most of this, I just haven't figured out how to edit the SDConfig, or to remove the windows customization that happens.
[Windows Mobile Development and Hacking General] tiermann:
Nice work on this

I wrote TierAutoinstall a while back too.

Gives a list of cabs so you can pick and choose on first boot.

I didn't see you had a project going until recently. The PPCGeeks/PPCKitchen.org team included your OEM as an option.

Good to see other options out there.
[Windows Mobile Development and Hacking General] Sleuth255:
Are you trying to find a way to include cabs on SD so your initial startup changes by device type (ie tilt/tytn II)? I'm trying to understand what is it that SDAutoRun gives you that the regular customization process doesn't. Try to give me what it is that you are trying to solve instead of a solution that you think will accomplish it. That way I can see the bigger picture easier.
[Windows Mobile Development and Hacking General] Sleuth255:
Nice app btw. I was wondering where it originated.