Related
Maybe this is a question especially to the developers, but I'm sure there are some other guys, that can advise me or give some hints.
I'm going to create my own rom with the mkrom-tool and I want to add some special programs. I also want to integrate my tomtom software to the rom. Therefore Ii don't have to reactivate every time, when Ii install the xda.
Now my question: Is this possible? Is there enough space to add this program?
What will i have to do?
Thanks...
Stefan
1) Create a snapshot file using 'ssnap' in your SE ROM
2) Install TomTom to the \Windows directory by moving the .cab to the device and double-clicking it. The CabInst program in the SE ROM will offer the option of installing to an alternative location.
3) Set everything up the way you want it. (i.e.: Twiddle all the settings, and install POIwarner and recent camera database also.)
4) create another snapshot.
5) Copy the two snapshot files to the PC, and compare them using a compare tool. (UltraEdit comes with one).
6) Filter the differences for things you do not need, such as 'last used' items in the file explorer and such...
7) Set up 'mkrom', adding the 3.17.03 ROM image, and test that it works by creating a ROM using the config that's in there.
8) Select what you want to lose, because 1.2 is full. Add the files the snapshot difference tells you are new into the 'files1' or 'files2' subdir, making sure the total file sizes for each doesn't grow.
9) Add the changed and new registery keys to default.reg
10) Run 'mkrom'
11) Presto.
I never found TomTom in ROM to be really useful, because it's big meaning you lose almost everything else, if it even fits. And for it to be useful, you always need the maps on SD-card anyway. Why not create an SD-card backup of the entire setup of your machine the way you like it on an old 16 or 32 MB SD-card? Then you can just put that onto your SE ROM device right after cold-boot, and you're in business.
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
This is only OS + ExtROM, does not include radio nor splashes nor SPL.
This is basically the same OS+ExtROM as found on Sprint's latest official ROM 3.56, MINUS all that Sprint bloatware (OnDemand, AudibleAir, Sprint Music, etc.) occupying both OS and ExtROM space. I also removed Sprint Navigation and Sprint TV from the ROM and ExtROM (respectively) because I want more control on how Sprint programs are installed (into the device vs into SD card); I have the separate CAB installers for Sprint Navigation (TeleNav) and Sprint TV so I can install them the way I want. I also removed the ringtones from the ROM because I don't like Windows Mobile's approach to copying ringtones from ROM (\Windows) to internal memory (\Windows\Rings) which effectively results in unnecessary file duplication within device memory, but I have stored the removed ringtones into an SD card so I can later add them either to \Windows\Rings (with no wasted copies in ROM) or to \Storage Card\Windows\Rings.
The amount of memory I gained this way was used to (1) update the core fonts (Courier New, Tahoma) to the latest versions found on Windows Vista (the versions found on the original ROM date way back to 1999, even in WM6.1! plus WM only includes regular-face Courier New, I had to add bold/italic/bold-italic versions), (2) add smartphone fonts Nina and Segoe Condensed, (3) add the Windows Vista version of Japanese font TTC MS Gothic/MS PGothic/MS UI Gothic (the AC3 compressed version is still outdated, version goes back to 1999 ), (4) replace the USA wince.nls with the Japanese wince.nls (which includes all charsets found on USA wince.nls + adds Shift-JIS, JIS, and EUC-JP), (5) add the WM6 Japanese IME files, (6) update the SymbolPad's config file to allow inputting almost all the Pan-Euro characters found in Vista's Tahoma and all math symbols included in MS Gothic, (7) add PQzII with some customized bitmaps so you can map CTRL, ALT, and IME to any buttons you want, (8) add PHM RegEdit, Notepad and a few other PPC PowerToys (I also added MADE because it is more powerful than Notepad), (9) add KT_Capt (print screen!), and (10) add FontOnStorage (yes, a very old program that dates back to WinCE 3.0, but still works on WM6.1 as long as the fonts in your SD card don't conflict with those already in internal memory). I preserved Adobe Reader LE, the Camera app, and IA Zip.
I modified the registry entries to (1) enable ClearType and menu animations (but disabled HTC's EnlargeMenu because it doesn't play nice with menu animation), (2) set internet cache/cookies/history to load onto SD card, (3) display both date and time (and AM/PM) in title bar, (4) enable font linking so Tahoma can work together with MS UI Gothic to display full Latin/Greek/Cyrillic/Japanese, (5) enable and configure the Japanese IMEs, and (6) set the new black Vista-like HTC theme as the default rather than WM6.1's solid-green default theme or Sprint's annoyingly-bright orange theme (although both themes are still included if you want to use them).
I used NBHExtract on the original stock ROM to extract the NB files, then NBSplit/ImgfsFromNB/ImgfsToDump to dump the OS, then PKGTool to convert dump to packages, then the usual ROM-kitchen procedures (remove unwanted files, add wanted files/packages with some help from CAB Extractor and InitFlashFiles Generator, modify RGU entries, regenerate DSM files with BuildDSM, modify packages.sof with XVI32, and dump XIP with RomMaster), then BuildOS to "bring packages to a boil" into new dump, then ImgfsFromDump/ImgfsToNB/NBMerge to "simmer" new OS.nb, then HTC Extended ROM Editor to remove the Sprint bloatware from ExtROM.nb, then finally NBHGen to "bake" both OS.nb and ExtROM.nb into the new ROM.
As I said above, the radio and splash image NBs are not included in this 82.2-MB ROM; adding the radio and splashes, the ROM grows to 94.1 MB, which is still 2.5 MB smaller than the stock ROM (even after adding that big, uncompressed Japanese font MS Gothic which is about 8 MB, but that's because the font itself is smaller than the whole combination of OnDemand/AudibleAir/SprintMusic/TeleNav/ringtones).
I thank pof/TheBlasphemer, mamaich/Tadzio, bepe, AnDim, and bot for all the executables they made that made my ROM cooking possible.
For those Sprint Mogul owners who don't want outdated fonts, annoying bloatware, or duplicated-in-device ringtones, my ROM can be downloaded via RapidShare:
http://rapidshare.com/files/144942116/Sprint_Mogul_3.56_OS_ExtROM_only_by_Unicode787Plus.exe.html
congrats! I just cooked my first couple roms a few nights ago, and one for my girlfriends titan too. its fun and addictive!
Sprint Navigation (TeleNav) and Sprint TV installer CABs
For those who download and flash my Sprint Mogul ROM and still want TeleNav and Sprint TV in their Moguls, they're attached to this message. Just copy them to an SD card and install them, easy! (You can install them either into internal memory or into SD, makes no difference!)
Will later post the ringtones I removed from my ROM.
Sprint Mogul ringtones
Ringtones removed from my ROM are attached to this message. For some reason I had to split them into two different ZIP files because xda-developers constantly refused my single 2.18-MB ZIP (even after using Legacy ZIP 2.0 compression method)
MMS
There is no way to add MMS (PIC/VIDEO)? I'm not using the 8525, i have a new MOGUL (SPRINT)
Sorry, I don't use MMS at all (and VERY VERY RARELY use SMS), so I don't know how to add MMS support to Mogul. For that you'll have to ask either mamaich or bepe in either this forum or ppcgeeks.
If I flash your cooked rom.. and I dont like it ... can I flash back the original rom.
mrfordwrench
What is up with the battery icon on the upper right. It looks like it is broken. Is it supposed to be that way. Otherwise everything works great.
What exactly is the PQzII for?
Mrfordwrench
mrfordwrench said:
If I flash your cooked rom.. and I dont like it ... can I flash back the original rom.
mrfordwrench
Click to expand...
Click to collapse
Yes you can flash back the original ROM - by redownloading it from the HTC website. Same procedure if you try any other custom ROM - like mamaich's or NoChem's kitchens...
Battery icon
mrfordwrench said:
What is up with the battery icon on the upper right. It looks like it is broken. Is it supposed to be that way. Otherwise everything works great.
What exactly is the PQzII for?
Mrfordwrench
Click to expand...
Click to collapse
Read my private message - that explains the purpose of PQzII.
As for the battery icon, I don't know. If you disable date/clock display on the title bar (either by doing so from Settings or by messing up with the Registry), then you'll see a useless battery icon instead of the clock. HTC's own custom battery indicator (shows only on Today screen) is a bit more accurate, but not as accurate as Palm Treo's own custom title-bar battery icon. If I could somehow copy Palm's battery-icon code (cannot do so directly from the phone - it seems to be copy-protected, and I don't have access to a Treo WinMo kitchen) and transplant it into my next Mogul ROM, then I would be happy.
Hi Dear,
I was looking for the same thing you done. I just wanted to remove some of the programs (like office mobile, pdf, audible air, sprint navigation etc) and not to added anything else to that original rom. The process you described over here is quite short and not elaborative. I tried and reached upto the step of generating "imgfs.bin" but thereafter i was hanged and i could not do any more i.e. dumping, packaging and the reverse process. Can you do me a favour and give some detailed steps or if possible can you give me the link providing details on this as well as all the required softwares (I done all these steps on command propmpt, is there any better way like grapical interfece)
Very eagrly waiting for your reply.
Regards
Tarun Kabra
Cooking ROM
tarun_kabra said:
Hi Dear,
I was looking for the same thing you done. I just wanted to remove some of the programs (like office mobile, pdf, audible air, sprint navigation etc) and not to added anything else to that original rom. The process you described over here is quite short and not elaborative. I tried and reached upto the step of generating "imgfs.bin" but thereafter i was hanged and i could not do any more i.e. dumping, packaging and the reverse process. Can you do me a favour and give some detailed steps or if possible can you give me the link providing details on this as well as all the required softwares (I done all these steps on command propmpt, is there any better way like grapical interfece)
Very eagrly waiting for your reply.
Regards
Tarun Kabra
Click to expand...
Click to collapse
Once you have generated imgfs.bin, you must dump it with a tool named ImgfsToDump.exe. It will create a folder containing the whole dumped image. Then you must use another tool, PKGTool.exe, to unpackage the dump folder into its constituent package subfolders (called packages). Now it's just a matter of removing unneeded files (be careful here, you don't want to remove files that are needed by WinMo itself) and updating outdated fonts (Courier New and Tahoma) with newer versions (you will first need to find on which pacakges they are located, then copy the new versions onto those same package folders) and, optionally, adding new fonts, input methods, or other programs onto the Custom subfolder. You will also need to edit some RGU registry entries (each package may have one) in order to activate some features or input methods. Then you will need to run another tool, BuildDSM.exe, to reprocess the edited packages. Then it's time to build a new dump from the new and edited packages: you will need to download BuildOS for this. BuildOS has a tool called BuildOS.exe, but running such a tool is tricky since you can't just double-click on it (it will crash), you must run it from some batch file located just outside the folder containing the tool; BuildOS.exe will convert the packages back into a new dump. Then it's just the matter of reconverting the dump into a new Imgfs.bin (with ImgfsFromDump.exe), inserting Imgfs.bin into a new NB file (the ROM itself) with ImgfsToNb.exe, then repackaging the NB file into the final NBH ROM with NBMerge.exe.
This is roughly all I can remember. You can optionally seek help from other fellow users, since I learned my technique from one or several of them: mamaich, no2chem, maybe Asukal...
Hey Guys,
I am trying to add rlToday.cab to my Glofiish M700 Rom,
but after flashing, when the phone is installing the extRom files, it stops after installing the rlToday.cab file.
When I install the software the normal way, it gives a notification that the rlToday-plugin is added to my todayscreen and than you have to push OK.
So I think that I have to push that button, before the extRom installation continues. So, is there any way to unable that notification.
Thanks in advance
This thread has a program that allows CABs that require user intervention to be installed using Autorun. I use it for rlToday, AEButton plus, and Mortbuttons. All three require user intervention during install, and SDconfigGen works great!
Thanks for your reaction. I read about this, but this is actualy not the way I want it, because now you need the ROM, a SD-card + the cab files on it. I could probably edit the .mscr file and put the rlToday cab in my ROM in the Windows folder, but that way you'll have unnessesairy files in your Rom, or yes, maybe I could do it this way, but isn't there any other way??
You know, I am just trying to make the perfect Rom for myself, so it would be realy great if I got it working.
By the way, does anybody know how to add your contact list to your ROM??
SDConfigGen can show you how to setup user intervention, look at the files it generates, use it as an example and edit a few files so that everything works from the Extended_Rom. It's really easy. here is the mortscript I created for rlToday:
Code:
windowTitle = "Setup"
WaitFor(windowTitle, 60)
SendCR(windowTitle)
Just rename sdconfig.txt to config.txt, edit the paths to the files, move a few files to your Extended_Rom image, and you're good to go.
this is the best way to solve your problem.
other solutions:
1. leave LOCK turned off in config.txt and do your own user intervention. (not sure this works)
2. rebuild rlToday.CAB so there is no user intervention.
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