User Customization is a config.txt file that's located on an SD card which can install cab & xml files located there too! Think about it: this gives anyone who loads your rom the ability to automatically install their preferred apps/settings as part of customization. Here's how to make your next ROM UC capable:
Cook the attached SDAutoRun.exe into \windows
if AutoRun.exe isn't already in \windows then place a copy there too. Note: some devices don't have a compatible AutoRun.exe. If you have issues, try the attached version.
Replace the "RST: Reset" line in config.txt with "EXEC:\windows\SDAutoRun.exe"
That's it! SDAutoRun will do the final reset unless it encounters a file called SDConfig.txt in the root directory of the storage card. If it sees this file, it will restart autorun and install cabs/configure settings from SDConfig.txt which can point to files that are also located on the SD card.
What's important is this: If every chef uses this system then ROM junkies will be able to freely move between ROMs. If you decide to include this in your next cooked ROM, then make sure you indicate that it's UC capable. I'd really like to make this a standard because it will greatly ease the time consuming task of re-installing apps/settings.
UC v2.0 is now Live!
Changelog
Works with non-WWE ROMs & Internal Storage Roms. SDAutoRun uses the registry to determine the default name for the Storage Card now. For newer devices, this key might be missing altogether so just cook it in. The "Folder" value points to the actual location that contains sdconfig.txt. Here's the key:
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\SDMemory]
"Folder"="Storage Card"
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.
SDAutorun v2.0 is fully compatible with all SDConfig.txt files created to date. Additionally, there now shouldn't be a config file users can throw at it that it won't re-format to the following template:
Commands will be 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
Assumptions
SDAutoRun is not signed so security must be relaxed in HKLM\Security\Policies\Polices by setting the value 0000101a to a 1.
SDConfig.txt cannot be Unicode.
Here's a link to the User's side of ROM customization:
ROM Flashing Junkies: User Customization is here!
If you build a UC capable ROM, be sure to link to the above thread. Also shoot me a PM and I'll add your ROM to the UC capable list.
The key here is that UC is an automated, unattended configuration. Setting it up is done out of the Hard Reset window and once its on your SD card, it works any time you hard reset. Automated is good because it allows mass customization from a business standpoint too. Any business using a UC capable ROM can set up a single "ROM customization" SD card then give it to their IT staff for the daily provisioning of company software/branding on new devices. Your UC capable ROMs have business appeal now!
We are also working on tools that will simplify the XML/SDConfig.txt file creation process. Several good ones have already surfaced in the Users thread.
Useful Stuff
OEM Package for Kaiser
I think this is/will be a great standard! Well done Sleuth for initiating this.
Genius idea.
Good news: doedoe is looking at building a provisioning tool! Now we have two developers working on this. We can sure use more help though. See the user thread for more info!
Good But What S About Cab Wich Prompt For Choosing Languages Or Some Parameters To Be Installed ?
UC
Very nice.
For flashing junkies it's necassary yes, after each flash all your favorit apps auto installed is awsom, nice one Sleuth
a request
can someone make it for all devices/ for example wizard? that will be awesome
Hehe many many thanks.
I tried to get this working with the standard AutoRun from SD but i couln't get it working.
Screw Extended Rom completly.
Great Work.
Making A bookmark.
character said:
can someone make it for all devices/ for example wizard? that will be awesome
Click to expand...
Click to collapse
ROM chefs should be able to use UC on any ROM. Post a link on your favorite ROM Chef's thread if you want to see UC.
SETOUF said:
Good But What S About Cab Wich Prompt For Choosing Languages Or Some Parameters To Be Installed ?
Click to expand...
Click to collapse
Those will need to be researched by the community. Post findings in the user thread (see page 1 for the link)
Awesome application.. so simple I'm amazed it took this long for someone to think of it!
I've cooked it into my ROM.. but I haven't released it so it cant really count as a UC compliant ROM..
It's definitely useful though and I'd love to see others using it. Thanks Sleuth
Already Found in Kin0kin ROMS
Great idea; however Kin0kin released a couple of roms some time ago that do this plus his final WM6 rom is also capable of auto install of applications off a storage card in this way.
WB
And why not change the reg
HKLM\Comm
\Extended_ROM\autorun.exe
and
\Extended_ROM\config.txt
into
\Storage Card\autorun.exe
and
\Storage Card\config.txt
Most ELF roms don't use Ext rom Auto installs any ways.
I still think this is a good cause because he's trying to get more people into doing this.
Instead of one or a few cooks integrating this.
Sleuth255 said:
sorry. AutoRun, by HTC design, cannot install apps to your storage card.
Click to expand...
Click to collapse
Well it shouldn't be hard to patch cab files hardcoded to a path on SD Card. (once i have found all my software back) But not something for a regular user nope.
Sorry to hear that Limitation still exists, seeing your actually using the Original Autorun.
I was allready removing this from my Roms.
Noonski said:
And why not change the reg
HKLM\Comm
\Extended_ROM\autorun.exe
and
\Extended_ROM\config.txt
into
\Storage Card\autorun.exe
and
\Storage Card\config.txt
Click to expand...
Click to collapse
that's pretty much what SDAutoRun does. It reconfigures the reg settings as you indicate and re-runs autorun. First however, it changes SDconfig.txt referenced cabs to RO since on a kaiser at least, the reg settings to prevent post installation CAB removal are ignored by AutoRun. Also, if no SDConfig.txt exists or there is no SD card installed, then it generates a quick one line config.txt containg the RST: command then re-runs autorun. On a Kaiser at least, the RST: command also re-activates the radio first. Without it, the device comes up with the radio disabled. I figured this scheme would maintain compatibility across all devices.
The standard is the important thing though as you indicate. You don't need to incorporate SDAutoRun in the manner I suggest. Whatever scheme works best for you is fine as long as it meets the following specifications:
user config occurs after all other autorun config
if SDConfig.txt is found on the storage card, set up the registry and re-run autorun
if SDConfig.txt is missing or there is no storage card installed then perform the final RST:
don't remove CABS from the storage card after installation.
I just thought my little 31K pgm was the easiset way to accomplish this. On deck is a way to do this even if the user renames the storage card...
Well looks like you can ad me to the list after monday.
I'm going to strip The new 6. rom to the bone and make some custom cabs hardcoded to SD card installation for the stripped Apps that can work from SD.
Cool... shoot me the link to your support thread when you do & I'll put it up on pg 1 of the UC user thread.
Regedit setting
Sleuth255 said:
HKLM\Security\Policies\Polices by setting the value 0000101C to a 1.
Click to expand...
Click to collapse
Can someone tell me what's "a 1"?
??[HKEY_LOCAL_MACHINE\Security\Policies\Policies]
"0000101C"=dword:a 1??
or
??[HKEY_LOCAL_MACHINE\Security\Policies\Policies]
"0000101C"=dword:a1??
Cheers
Strange that it's contain hardcoded paths ...! The name of my Storage card is Speicherkarte and so it's useless for me!
Probably a dumb question but where would I put this file in the base kit I have. I have a base kit for wm6.1 on titan. Ide love to cook up a rom but I dont know where this file goes.
smarvest said:
Can someone tell me what's "a 1"?
??[HKEY_LOCAL_MACHINE\Security\Policies\Policies]
"0000101C"=dword:a 1??
or
??[HKEY_LOCAL_MACHINE\Security\Policies\Policies]
"0000101C"=dword:a1??
Cheers
Click to expand...
Click to collapse
set the value "000101c" to a 1 ie:
[HKEY_LOCAL_MACHINE\Security\Policies\Policies]
"0000101C"=dword:1
Related
Howdy.
Does anyone know of an autorun.exe which is coded to look in "extendedROM"? (As opposed to "extended_ROM").
I'm aware of PocketPC Installer and that it probably can create a custom autoexec.exe for me, but I'm looking for a free solution if there's already one hacked up out there.
Thanks
--SUmmiter
I thought that it got that value from the registry:
[HKEY_LOCAL_MACHINE\Comm]
"AutoRun"="\\Extended_ROM\\AUTORUN.EXE"
"AutorunCFG"="\\Extended_ROM\\CONFIG.TXT"
"AutoRunType"=dword:0
"TurnRadioFlag"=dword:0
Yes but you have to add this into rom before building if you want it to look for autorun there after flashing
Right. My possibly incorrect assumption was that autorun.exe is hardcoded to look inside "Extended_Rom" for it's config, ignoring what is in the registry. I'll mod my OS rom and try changing AutorunCFG and see what happens.
joemanb said:
I thought that it got that value from the registry:
[HKEY_LOCAL_MACHINE\Comm]
"AutoRun"="\\Extended_ROM\\AUTORUN.EXE"
"AutorunCFG"="\\Extended_ROM\\CONFIG.TXT"
"AutoRunType"=dword:0
"TurnRadioFlag"=dword:0
Click to expand...
Click to collapse
Autorun.exe and config.txt can be anywhere as long as the registry points to them.
(if the registry points to Extended_Rom, then of course the files need to be included in the Extended_Rom.)
My autorun.exe is in windows, and config.txt is in the extended rom, but I've tried it other ways and it's worked.
alot of cooked roms use this feature to do a final modification like loading a theme from the windows directory.
BTW config.txt contains the paths to the files you wish to process, so it doesn't matter where autorun.exe, or config.txt are.
In other words, you could put autorun.exe, and config.txt in windows or anywhere else as long as the registry points to them, and it will process the files on the paths contained in config.txt
Little question, has autoexec any link in startup, or not?
(I make in intiflash registry entry es mentioned before, I have hope corect congig.txt but after HR ... nothing, co customization . Interesting is, that I can launch autoexec in ext rom manualy and it runs ok. I rebuld quite naked WM 6.1 rom)
Thx for help...
ABOUT
The purpose of this CAB is to reach a sort of UC way but with a very easy & friendly approach
HISTORY
I come from Diamond world, so because this CAB can be adapted for other platform/devices why not preparing a separate sUC.cab to use for enabling ALL the stuff (ramdisk, pimbackup,ram recovery,etc...) included in Dia Duit rom series?
what have I to do with this cab?? simply it will apply these features:
Latest stable MortScript is inscluded & ready to go, so no more needs to install as separate cab
Choose between 3 speed profiles: 1. fast (takes more ram & battery), 2. balanced (not heavy tweaked but not funny) & 3. untouched (default WM6 settings)
GPS profile: TomTom, iGO, Navigator or default WM6
Everyday auto recover RAM feature (at 4.30AM) + automatic sms/contacts/calls backup/fav manila people (trough pre-configured pimbackup app, PimBackup included)
Ramdisk (2Mb) feature (optional)
A new way for a fully automated CAB/REG/EXE/CPY installation/copy after every hard-reset/rom upgrade
UPX executable, compress (fully automated) exe files from fresh installed cabs, this saves space & gives faster app load times
Easy & fast tweaking method without 3rd part software: tweak registry scripts (with comments)
Tips enabled by default to preserve a bit more battery life (for ex 3 secs of led blinking instead 5, increased battery life counter,etc) + increased speaker sound volume + many example for setting automatic alarms, rings, etc...
Moved MAIL + Attachments folders from main memory (My Device) to external one (Storage Card)
3 / 4 rows configuration
This should work on every WM based rom, also because I added the auto recognition of "Storage" name... so should work without troubles also on NON WWE roms (except for CABi installation)
DOWNLOAD sUC.cab HERE
DOWNLOAD sUC_source.zip HERE
BEFORE INSTALL (mandatory)
create in your "Storage" (the BIG one) a folder called "Backup and Restore", then inside it a folder CAB (inside this another folder called CABi), then at the same level of CAB folder create a folder called CPY, then REG, then EXE
so practically your basic structure should be like:
Code:
Storage Card (or whatever name)
=> Backup and Restore (folder)
=> CAB (folder, put here all the cabs you want install on main memory)
=> CABi (folder inside CAB folder, specific for "must go into Storage", see notes)
=> REG (if present all reg files here will be joined to default WM registry)
=> CPY (if present all files here will be copied under their correspondent folders)
=> EXE (if present all .exe & .mscr files will be launched)
all files in the CAB folder will be installed (automatically) into "device", the ones in the CABi folder will be installed into "Internal Storage" (or whatever you have, always automatically), from REG folder all *.reg/*.rgu files will be loaded on the fly, from CPY all files will be copied (with overwrite) into correspondent folders (for ex useful for copying personal dlls, wav/wma/mp3 files or background, etc...), for finish from EXE folder will be launched your executables (personally never needed, but who knows?) & if present all *.mscr scripts... pay attention to exe files that needs user interaction
INSIDE THE CAB (a deeper explanation)
when your sUC cab is installed it simply creates a registry entry under [HKLM\init\]"Launch69"="2ndboot.exe", this permits the script 2ndboot.mscr (launched by 2ndboot.exe) to be loaded upon system reboot (just one time)
this script, if the structure mentioned above isn't found, it will create automatically all the folder & default reg files needed under your storage card, the name isn't important because it should guess itself its correct name, so don't care if your storage is called something like "MyBigStorageCard"
then it will ask you some questions... such as if you use ActiveSync, which GPS performance adopt, etc... all this info, which at 1st you'll pay high attention, will be stored under your storage card in a file called config.txt ...why?? simple... because next time you will flash or hard-reset your phone you wont have to push a button the script will found that previous stored config file & it will take all the info needed for final rom configuration to skip all annoying questions after every upgrade/HR
note: there is also an hidden option that should be used only by experts, to enable this option simply add by hand to your config.txt file the line: FastInstall=1
this will skip all countdown menu & messages... personally I use this option because flashing a lot this saves much time more
next it will look in the CAB folder for installing your CABs into "device" or main memory
next in the CABi folder for installing CABs into your storage card (you need to do this just 1st time, I'll explain later...)
next it will look at a file called upxlist.txt (must filled before), where simply you will specify all the *.exe file you want to compress after every cab installation... for example your upxlist.txt could look like:
Code:
\Program Files\Navigator\TomTom Navigator.exe
\Program Files\9.5 Beta\Opera9.exe
\Internal Storage\Program Files\Binaryfish\All Mobile Mines\All Mobile Mines.exe
note: every line for every EXE file, pay attention that you can compress just EXE files coming from extra CABs, because EXE files present in the rom are read-only
next it will copy a set of basic reg files with many tips/tricks/examples inside, useful for making many customizations
note: of course if you have previously prepared the folder structure & you have copied your REGs files under the REG folder they will be processed together the files above
next it will look in the CPY folder and will replicate the found folder structure (with files too), for example create inside it a folder \windows with some file inside & it will copy all found files under \windows on your device, or create \program files\myapp & it will create that folder structure in your device, of course it works also for Internal Storage even if it has no sense, anyway just a note it doesn't create empty folder, to create an empty folder just use a single .mscr script (something like: MkDir("\mydir") ) & copy it in your EXE folder
next it will look in the EXE folder & will launch all the exe files inside it, if found it will launch also all *.mscr scripts
next if found (you'll understand better upon an HR), it will ask you to restore your backed-up start menu, so you don't have to re-arrange your icons again
next if found, it will ask you to restore your last PIM backup & will reboot
notes:
right now CABi procedure works only on WWE roms (due to translations work to be finished), anyway there is a trick to skip CABi installation, or better make by hand just once (read few lines below)
installing cabs into Storage Card sometimes will fail, this simply because some cabs need confirmation/accept license & so on, so don't expect will work 100%, also many cabs require to be installed into main memory so NOT into Storage Card, for ex I use to install into Storage Card simple cabs such as games
sometimes pim backup restore can fail, try to restore by hand after installation; backup are divided into week days (monday, sunday, etc... "Last" is the last saved backup)
if you put sUC.cab in your CAB folder wont re-processed of course, useful if using sUC together with UC/UC2 installation method (see at bottom)
if you still use the 1st sUC release way your personal scripts still work like before, simply move them under EXE folder, or transport as reg entries directly into your personal reg file & copy it under REG folder, you can find on the same folder some examples (to clean all your old stuff simply empty the REG folder, modded REG files wont be touched on future upgrades)
you don't need to re-install every time your CABi, just install them once, then on next upgrade answer No or simply edit your config.txt & change the correspondent value; after CABi installation on a clean boot go with your explorer under "\windows\start menu" folder & re-organize your start menu structure (cut/past links, create/delete folders, etc...), remember to don't delete "Settings" folder even if empty, then go under sUC menu & backup your StartMenu, on next upgrade sUC will detect start menu backup & it will reinstall automatically... because the content of your storage card isn't erased after a rom upgrade/hard-reset your installed CABs will stay there untouched, so backed-up start menu has inside correct links
is possible to move TomTom, iGO, Navigon, etc... definitively into your storage card, so you don't need to install them every time: copy entire nav software folders from \program files to \internal storage\program folders, re-create icon shortcuts (copy/past as shortcut in your start menu), for iGO you have to edit sys.txt (under iGO folder) & change the path of base installation
in the same way is possible to skip for example FingerKeyboard installation from related cab, simply take a look at this short guide
INSTALLATION
note: to migrate in every new sUC version simply move your reg mods in your Personal.reg file, erase all the rest of reg files because they will be re-generated with the new ones, remember that on upgrades reg files wont be touched so pay attention on what you mod
if the rom is UC compliant simply create a called SDConfig.txt file in the root folder of your Storage Card, for example your SDConfig.txt could look like (pay attention to upper-lower case & no empty lines):
Code:
LOCK:Enabled
CAB :\Internal Storage\Backup and Restore\CAB\sUC.cab
LOCK:Disabled
RST: Reset
in this way at reboot will start standard sUC procedure (remember MortScript is included & also that sUC cab wont be re-processed even if present in CAB folder), instead if the rom isn't UC compliant simply install sUC as any normal cab, then it will ask to restart (or restart manually) & automated procedure will begin on reboot[/b]
bye,
davide
OK, that's all very nice, but WTF is it?
Wouldn't hurt to have an "about" section in the post for ppl who see this thing the first time in their life.
GENIAL !!!!!!
aiiro said:
OK, that's all very nice, but WTF is it?
Wouldn't hurt to have an "about" section in the post for ppl who see this thing the first time in their life.
Click to expand...
Click to collapse
yep... you right sorry, I'll correct soon...
suiller
OMG~ You finally made it available!!! I'm going to test it with my HD and will report back once everything is organised
I didn't mean to sound rude, sorry... Anyway, thanks for the addition, but still - what is UC? User Configuration? Could You post some screenshots too to make it more comprehensible for dumbusers like me?
jackkkkk said:
suiller
OMG~ You finally made it available!!! I'm going to test it with my HD and will report back once everything is organised
Click to expand...
Click to collapse
oh FRIEND! I found you
yep, I'm looking here around to see if my mad projects can be useful
the cab isn't still perfect but should work, of course I haven't a different device from diamond so all you will be a sort of beta tester
I've removed all specific diamond stuff, so it should work
Of course this is just a starting point, I'm dedicating much time to develop this small piece of "software", thx also to many other friends
You know as it works, so you should feel a bit like at home
aiiro said:
I didn't mean to sound rude, sorry... Anyway, thanks for the addition, but still - what is UC? User Configuration? Could You post some screenshots too to make it more comprehensible for dumbusers like me?
Click to expand...
Click to collapse
yep you are right... UserConfiguration, the only difference is that you don't need to write any config file, at least not as "normal" user, it's enough to copy under correct folders the CAB plus other stuff you want installed/loaded after every flash/hard-reset
I'll porvide soon a video-guide, so it will be for sure more clear
OK, OK, nuff with making fun of me Or were You seriuous with video guide?
Cos I just had a brilliant idea - I'll install the damn thing and look for myself
I think I should have done that in the first place. But still, I believe screenshots would save some time understanding what's it really about.
Yeah Screwed Up Click for life
no no I'm serious friend... but I'll suggest to wait a couple of days because I'm working on a new version where is possible to cut-off all the specific HTC/manila stuff & above all I'm re-commenting all the registry entries that interact with OS
no no I'm serious friend... but I'll suggest to wait a couple of days because I'm working on a new version where is possible to cut-off all the specific HTC/manila stuff & above all I'm re-commenting all the registry entries that interact with OS
Hi,
really don't want to be rude or offence, but ... isn't this something like SASHIMI????
If so ... where are sUC's pros?
kind regards
fwt
almost... but it's very very simple... I'm testing an heavy modified version able to run on almost every WM6.x base device
OK the CAB is ready for testing purposes... please re-read 1st post because I'm making a better, I hope easier, description of features... thx
bye,
davide
Mate, this piece of software is plain GENIUS!
So much easier than the UC thing, with all the boring scripting. This way you just place in folders, and you are (mostly) done! Amazing stuff!
I have some questions/requests for you though...
Is there a way to repeat the procedure (restore at 1/2 start up), at a later time? This could be useful, for example, if some files get corrupted, or you just want to revert back to default cabs/settings, etc. So I guess what is needed is a way to manually activate the procedure.
Second thing is regarding mail settings. Is there a way to back this up? My hotmail settings get destroyed after every HR.
Cheers.
Forgot to mention, a manual activation of this procedure would also help if (for example) you want to make multiple program installations. This way you could just use the folder CAB, without wasting time on every single program you are installing/testing...
Cheers
krale said:
Forgot to mention, a manual activation of this procedure would also help if (for example) you want to make multiple program installations. This way you could just use the folder CAB, without wasting time on every single program you are installing/testing...
Cheers
Click to expand...
Click to collapse
hmm... it could be a good idea... even if some phases can't be reverted, or better it's very complicated to "go back"... such as for ramdisk
anyway many phases are yet accessible as indipendant scripts just take a look under "\Backup and Restore\scripts" folder, of course other script could be extrapolated but I'll do probably on next version... let's say this is a testing purpose version because I have to "think" that this app must work on many (almost all I hope) wm6.x based devices
As one of the end (l)users who first saw this in Suiller's Dia Duit rom series, I can attest to this resolving one of the major grievances of Windows Mobile rom-upgrades. With some "smart" planning ahead, getting everything back can now be mostly scripted by simply placing the install file in the correct directory. Same with restoring data from your pimbackup, or adding registry settings. Once again we have a case where the xda-developers have surpassed the "offficial" roms in user friendliness.
I have since moved on to WM6.5 (still on my Diamond), but I sorely miss sUC from my later roms.
//Svein
updated sUC, corrected some small issues
I corrected some default/samples reg files, so I suggest to erase all default *.reg files under REG folder to update correctly
move your personalization to something like "MyRegPers.reg"
please reports here bugs/issues/suggestions or whatever... thx
Ok, i was bored about rewriting sdconfig.txt everytime i changed the romlanguage, so i decided to make something that will avoid this, and will avoid to write the sdconfig.txt too
What are the main goals of my project?
Install everything you want without careing about romlanguage
automatize every process
How it works?
Simple. Put your cabs/exes/provxml/xml to import/run in your storage card folder "FB_Install"
Ok. You said that I can install exes, but if i need to add arguments to the execution of the file?
Simple again. Create a file (as an example, if your exe is "myexe.exe") naming myexe.arguments. in it write your arguments. You can use the arguments only on exes.
Well, and if i want to skip some files?
Just create (as an example, if your file is "mycab.cab") a mycab.skip file. This works with all types listed here (cabs, xml,provxml,exes)
Well, i need to hide the customization while I install a cab. How to do that?
Again simple. If your cab is mycab.cab, create a file with name mycab.hide
And if i want to don't reset at end?
Create a file with name "NoResetAtEnd"
Ok, i have that folder but right now i don't want to install anything. how to do that?
Create a file with name "SkipCustomization"
Ok. That's nice. But how i can add my own config codes as i done on UCv2?
Create a file "AddToConfig.txt" and add there your config codes. this will be appended after the other config codes generated by the program.
I want to create some shortcuts. How to do that?
Create a Shortcuts.txt containing the shortcuts to create. You have some IDs:
%SD%
%PROGRAMS_STARTMENU%
%PROGRAM_FILES%
%STARTUP%
%MYDOCUMENTS%
This will allow you to create an universal shortcuts.txt without careing about language.
Each line contains a shortcute to create. Example line:
%PROGRAMS_STARTMENU%\Test.lnk:%SD%\myprogram.exe
this will create a "Test.lnk" in \windows\start menu\programs folder pointing to \Storage card\myprogram.exe (that for wwe).
I want to copy some files in the windows folder. How?
Create a folder in FB_Install called "CopyInWindowsFolder". all files there will be copied to the windows folder. You can do that for Programs,Favorites,Fonts,Startup,Program files folders creating folders:
CopyInWindowsFolder
CopyInProgramsFolder
CopyInProgramFilesFolder
CopyInFavoritesFolder
CopyInFontsFolder
CopyInStartupFolder
I want to install some cabs to storage card instead of internal storage. how?
Just create (as an example, if your file is "mycab.cab") a mycab.ToSD file.
I will include that feature on my future ROMs, but if someone is interested i can release it here.
EDIT: yes i know that noonski done something similar but i was searching about something integrated
Nice idea. Good luck.
One thing though. There might be a clutter of files created but users which can get confusing? How about just parsing one file with all directions?
rjmjr69 said:
Nice idea. Good luck.
One thing though. There might be a clutter of files created but users which can get confusing? How about just parsing one file with all directions?
Click to expand...
Click to collapse
thanks. added other features on first post.
Maybe I missed it but is there anyway to automate .cabs to be installed on storage card?
MrDSL said:
Maybe I missed it but is there anyway to automate .cabs to be installed on storage card?
Click to expand...
Click to collapse
i'm working on that too
michyprima said:
i'm working on that too
Click to expand...
Click to collapse
If you can get that to work then it would be awesome..So far theres no automated option that works to install on storage card..
MrDSL said:
If you can get that to work then it would be awesome..So far theres no automated option that works to install on storage card..
Click to expand...
Click to collapse
Well, i can say i now i got it to work. Requires a bit of work but it works. Well, visual studio is EXTREMELY powerful
Looks really good, I really like to try this UC
This is also a nice tool
finally got it to work right.
Now it can install CABs to storage card without problems
I want that in my ROMs too. Can you share it here?
solved problems on installing cabs too. The installation dll will NOT be executed so you won't need to care about user interaction while installing
Definatly interested in checking this out since it can install to storage card.
hope u make it available..
MrDSL said:
Definatly interested in checking this out since it can install to storage card.
hope u make it available..
Click to expand...
Click to collapse
well that's something for cooks not for users (it needs to be cooked in to work) so if i release it you can't use it at least when someone use it in his rom...
To me it looks like MrDSL is a cook. The ROM linked in his signature is made by him.
Are there any news? Will you release it here soon?
A powerfull alternative;
Will it get released? I'm eager to test it Virtually in an Embedded WM6 environment;
Windows (Embedded) CE/WM6 PowerToy: DiskPrep;
http://forum.xda-developers.com/showthread.php?t=655377
I'm glad though that User Customizer DevPrep (CPY2 Storage Card possible) saved my day(s) until now!
Soon most readers from this thread too IMNSHO,
Senax
Hi,
I'm currently working on a few tools, and want to know what features would be liked by cooks/users or anyone really.
The first tool is an exe generator for hot fixes. Simply put, you plug some files into it, and it generates an exe that can be run on the target device which will do all the hot fixes.
The advantages it gives:
No more cabs!
Can use a custom icon for the exe if desired
Things like messing around with setup.dll files doesn't need to happen, and an application can be launched after install if wanted
Files can be deleted
File properties can be changed
Can use XMLs
Can edit registry
Can install files
Since it's written in native C++, it should run without a hitch on WM5+ devices, whether or not they have .Net whatever...
The second tool is an AutoRun/UC/whatever like system that simply searches through a folder, finds all cabs/xmls/provxmls and then installs them. This means there's no reliance on autorun for parsing config files, or any other requirements. Again, it's written in native C++ so is better
Any suggestions/ideas would be welcome!
Oh, and once I've got slightly further, both these will be released as open source. Probably.
l3v5y said:
Hi,
I'm currently working on a few tools, and want to know what features would be liked by cooks/users or anyone really.
The first tool is an exe generator for hot fixes. Simply put, you plug some files into it, and it generates an exe that can be run on the target device which will do all the hot fixes.
The advantages it gives:
No more cabs!
Can use a custom icon for the exe if desired
Things like messing around with setup.dll files doesn't need to happen, and an application can be launched after install if wanted
Files can be deleted
File properties can be changed
Can use XMLs
Can edit registry
Can install files
Since it's written in native C++, it should run without a hitch on WM5+ devices, whether or not they have .Net whatever...
The second tool is an AutoRun/UC/whatever like system that simply searches through a folder, finds all cabs/xmls/provxmls and then installs them. This means there's no reliance on autorun for parsing config files, or any other requirements. Again, it's written in native C++ so is better
Any suggestions/ideas would be welcome!
Oh, and once I've got slightly further, both these will be released as open source. Probably.
Click to expand...
Click to collapse
Wow, this sounds very very promising. Can't wait!
dwizzy130
yeah some user friendly and easy to understand specialy editing the rom or making add/remove programs EASILY is the best specialy to noobs like me when cooking ROMS all in one tool with advance AI for error checking
Sounds very attractive. go on my friend.....
Sounds good mate
I'm looking for a tool to easily make a setup.dll. Like setup.dll maker/generator/wizard.
Seems the only tools I can ever found is from e-pocketsetup, but that company was sold to another company and the product was never available since then.
I know cooks hate a cabs with a setup.dll. But seems without setup.dll a cab installer can not execute some little complicated actions. And it is impossible to make a setup.dll without grasp a computer language like c++.
Edit: Found another one: setupdllcreator , but it's not strong enough and not freeware.
Edit: If these can be realized, a setup.dll maker is much less needed:
No more cabs!
Can use a custom icon for the exe if desired
Things like messing around with setup.dll files doesn't need to happen, and an application can be launched after install if wanted
Files can be deleted
File properties can be changed
Can use XMLs
Can edit registry
Can install files
Click to expand...
Click to collapse
But we need above mentioned fubctionalities to be DYNAMIC, like:
Can detect availability of certain reg entries or installed apps, base on the result to decide which variants of install files to be installed, or whether some supporting apps like netcf or mortscript to be installed. Or can detect device id, resolutions, drivers to decide what to do.
Otherwise it still can not completely replace setup.dll.
But if dynamic actions can be executed, wow that's a dream of developers & hackers and even common users can benefit from that, a real revolution !
woww can wait for realese
l3v5y said:
Any suggestions/ideas would be welcome!
Click to expand...
Click to collapse
So I'm posting my requests again, the idea is this: It will be much helpful if I can know what is happening/changed in the registry after I did anything to my WM devices. So maybe you can develop a tool to monitor & log the real-time changes of registry. Or at least we can have a registry-comparision tool on ppc.
Another thing is it seems we don't have a file structure viewer on ppc, not the stuff like total commander etc., want to export the file structure to a file like .txt or .jpg.
Update: Now my idea is clearer for this, what I suggest would be a System Snopshot program to realize this:
Can make a system snapshot to record the registry content, file structure, ram usage etc.
The snapshot can be initialized in the similiar way of CapSure screen capture program, i.e., a hardwre button, a fixed time, a screen tap, a program launch, etc., defined by user.
Can choose a full system snapshot or only on selected part of registr, file system etc.
Can generate a file containing the recorded system condition.
Can compare any two system snapshot result and generate a comparision chart/change log.
So I've posted my requests as per your request, whether or not you'll do it is not my business lol.
Update: Found SK Tracker, cost EUR9.95, so forget this one. Why I did not know it in the past?!
Final Customization
What is it?
It's another chef application for having a final step on customizing their ROM. Final Customization runs after AutoRun, SDAutoRun, UC has finished and made a soft reset to the phone.
Basic Flow
First Boot
--> Screen Calibration(skipped in other ROMs)
------> Customize
----------> Soft-Reset
--------------> Final Customization 1st run and will popup application choices
--------------> and the installation begins. Then after the isntallations, it will
--------------> ask if the user want's to soft-reset or not.
--------------> if YES, the phone will soft-reset. If NO, Final Customization exists and
--------------> show the final message.
Why need such another Customization?
Final Customization gives users a chance to decide what application they want to install from the ROM and "from" the ROM means a CAB or REG that is cooked in the chef's cooked ROM.
But why they have to decide which application they need to install?
Simply because not all users like the application we included in our ROM. Me my self is a Chef, and I know some users don't like my application, so I'd like to give them a chance to decide if they want to install that application.
Another benefit for the chefs is you can control the Manila/Sense.
- You can Stop the Manila/Sense then install the cooked cab or reg and Start the Manila/Sense.
- You can Restart the sense after you installed the cooked cab.
So what does it support?
Final Customization can install CAB and REG(requires dotFred Task Manager) and you can execute any files as long as your ROM supports it like running a Mort Script if you have Mort Script included in your ROM, or you can execute EXE files, Play an audio, video, etc!
How does it execute these files?
Final Customization can understand some commands such as:
reset
soft-reset the device. Final Customization knows if it's not yet done installing the user selected apps.
has_manila
Some of your CABs or REG entries might require Manila/Sense to load first. So I made a way to monitor the Manila/Sense if its already loaded and running.
stop_manila
This of course is associated with has_manila command. You can stop the Manila/Sense then install the CAB or execute a REG then start the Manila/Sense after the installation.
start_manila
After you the CAB or REG installed. You can start the Manila.
restart_manila
You might want to execute some REG that doesn't really requires the Manila/Sense to stop and start before and after the installation. You can just execute the REG and restart_manila.
Click to expand...
Click to collapse
SAMPLE COMMANDS
Code:
S3VideoDrivers.cab!|Install 3D Drivers;
reset!|Soft-Reset and Apply Video Drivers;
WiMoSpeed_614mhz.lnk|Overclock CPU to 614.4Mhz;
paint.cab|MSPaint Like Application;
gremotesetup.cab;
reset|Soft-Reset but optional;
has_manila;
stop_manila;
DefaultSenseWallpaper.CAB|Default Sense Wallpaper;
InstallSenseQuickLinks.reg;
start_manila;
these commands (not case sensitive) are saved in a file called cablist.txt. As you can see, they all had semi-colon at the end that acts as a separator between the commands. You can also add TAB or Spaces to make your code cleaner..
Other thing you'll notice is the PIPE character which separates the command and the friendly name that will show in Installation Choices window.
and the "!" after the file, which means, the file is important and cannot be unselected from the choice lists.
format:
command|Friendly Name
or
command!|Friendly Name
The .CAB, .REG, and .LNK you saw there are files.
Click to expand...
Click to collapse
Okay, so how do I really use it?
I will provide the EXT package which contains the initial files needed from Final Customization then you can add whatever you want to include such as CAB or .REG or probably .PROVXML but make sure your ROM supports .PROVXML file types.
cablist.txt file is also included then you can just update it.
another file is included named FinalizeSetup.app.config which contains the parameter used by WCELOAD.exe and your final message after the installation is done. Be careful on WCELOAD parameters! Here are some WCELOAD parameter informations.
Code:
<appSettings>
<add key="wceload_param" value="/delete 1 /noui /silent "{0}""/>
<add key="final_word" value="Installation is done. Have fun!"/>
</appSettings>
AHA! Finally the preview. I just made a sample video for you guys to watch. Sorry but I have to keep silent (again)
A possible issues of Final Customization.
It cannot respond to custom actions when installing a CAB. In regular CAB installation, some installation popups a window aobut agreement and stuff and you have to accept the agreement. So Final Customization cannot handle that.
If you think you can handle that via WCELOAD parameter. Please let me know.
Final Customization can also execute control panel applets such as running Regional Settings but the problem I saw was when executing 2 applets, Final Customization did not wait for the 1st one to finish but instead, it executes the next applet.
Sending a bug report
Final Customization has a logging feature for bug hunting references. It is located in \GambitLogs folder. Please send all the contents to me
and finally, the download file!!
zz_FinalCustomization.7z
RELEASE INFO
Version 1.2.1 - October 02, 2011
- GUI fixed again.
-- fixed the left position of that lists
-- DOWNLOAD HERE
Version 1.1 - September 26, 2011
- GUI fixed. DOWNLOAD HERE
September 24, 2011
- initial release
Doing a test with your setup without cooking it
Basic Registry Information
HKEY_LOCAL_MACHINE\Software\GambitCreativeSoftware\FinalizeSetup.DoFinalSetup
FinalizeSetup.exe will terminate immediately if ran for the 1st time because it will try to read a key in the registry to check if it's ready for final setup.
if FinalizeSetup.DoFinalSetup has a value of 1, then FinalizeSetup will show. So if you're running it for the 1st time, run it again to show up the Final Customization window.
HKEY_LOCAL_MACHINE\Software\GambitCreativeSoftware\FinalizeSetup.cablist
FinalizeSetup.exe stores all the cablists.txt script in the registry. So, if you have some updates in your cablist.txt, make sure to delete that key first
HKEY_LOCAL_MACHINE\Software\GambitCreativeSoftware\FinalizeSetup.IsDone
if FinalizeSetup.IsDone has a value of 1, then FinalizeSetup.exe will terminate because the final setup was done.
HKEY_LOCAL_MACHINE\Software\GambitCreativeSoftware\FinalizeSetup.Status
values:
FinalizeSetup.Status = 2, means the phone soft-reset
FinalizeSetup.Status = 1, FinalizeSetup.exe is installing.
Running FinalizeSetup.exe
1. Copy all the necessary files somewhere in your SD or Main Storage and put them in one folder.
<folder>
-- FinalizeSetup.exe
-- Gambit.Runtime.dll
-- Gambit.IO.dll
-- Gambit.Configuration.dll
-- FinalizeSetup.app.config
-- cablist.txt
- and other required files (.lnk, .exe, .cab, etc)
2. Running FinalizeSetup.exe
Check the registry key HKEY_LOCAL_MACHINE\Software\GambitCreativeSoftware and delete these 3 NVP.
FinalizeSetup.IsDone
FinalizeSetup.cablist
FinalizeSetup.Status
Hi Nullstring
Congratulations for a brilliant idea, let's hope all cooks will adopt it
Thanks for sharing this, as a Chef I know how useful this actually is
Sadly, not sure if that many WM chefs are still around.
But nonetheless thanks for sharing this !
madnish30 said:
Thanks for sharing this, as a Chef I know how useful this actually is
Sadly, not sure if that many WM chefs are still around.
But nonetheless thanks for sharing this !
Click to expand...
Click to collapse
hopefully this is not really late I just started making my own ROM for WM
download now!!
GUI Patch update.
Check download file Post #2
any feedbacks?
Thanks for this Nullstring, working well and it definitely allows users to customize more to their liking.
New Relase
Version 1.2.1 - October 02, 2011
- GUI fixed again.
-- fixed the left position of that lists
added new tutorial in Post #3
hello, sorry if I have not yet updated this thread about the development progress of this app. The app is already using JSON as it's configuration and data and there is already an desktop application that can be use to build your setup configuration.
anybody want it?