Develop Bugs

Beta: WM5 ROM editing tool

I've made a set of tools that can assist in cooking your own WM5 ROMs. These tools were tested only on BlueAngel devices. They should also work on Himalaya. Universal and Wizard support is also present, but it is untested, so the tools may crash or turn your device into brick. But it is possible to extract files from universal/wizard ROMs and use them on other devices.
I've attached 2 archives - make_hv.rar, a tool from Platform Builder that can be used to recreate .HV files (they contain default and boot registry), and imgfs_tools.rar - these tools should be used to edit WM5 IMGFS partition.
With these tools and http://forum.xda-developers.com/viewtopic.php?t=33321 (it can edit WM5 boot XIP partition) it is possible to replace/add/delete any file in WM5 ROM.
Usage:
Code:
prepare_imgfs.exe
Splits nk.nba into imgfs_raw_data.bin and imgfs_removed_data.bin.
imgfs_raw_data.bin - contains raw IMGFS data
imgfs_removed_data.bin - contains extra data (something like FAT table).
Usage:
prepare_imgfs.exe nk.nba [-nosplit] [-mpx200] [-acer]
Use "-nosplit" for HTC Wizard and Universal ROMs that don't contain extra
blocks of data. In this case imgfs_removed_data.bin would be empty.
make_imgfs.exe
Reverse of prepare_imgfs. Combines imgfs_raw_data.bin and imgfs_removed_data.bin
into nk.nba file. Use -nosplit if it was specified for prepare_imgfs.exe.
Usage:
make_imgfs.exe nk.nba [-nosplit]
The nk.nba file would be used as a template, its contents would be overwritten.
viewimgfs.exe
Dumps the contents of imgfs_raw_data.bin to "dump" subdirectory. Files are
dumped as is, modules as directories. File time and attributes are preserved.
If RecMod.exe is present in the current directory, all modules are
reconstructed as working DLLs/EXEs and placed in the corresponding subdirectory.
Tool creates dump_MemoryMap.txt with address ranges occupied by modules.
Usage:
viewimgfs.exe imgfs_raw_data.bin
RecMod.exe
Reconstructs a module dumped as directory to a working state. Rebuilds
relocations information, and tries to guess section names.
Usage:
RecMod.exe [path to module directory]
BuildImgfs.exe
Reverse of viewimgfs. Reconstructs imgfs_raw_data.bin and imgfs_removed_data.bin
from files in "dump" directory. Overwrites contents of imgfs_raw_data.bin/imgfs_removed_data.bin
files. Does not check for errors or end of free space. Approximate free space
left is displayed when program is finished. In case of error contents of bin
files is undefined.
Usage:
BuildImgfs.exe
It would overwrite imgfs_raw_data.bin/imgfs_removed_data.bin in current directory.
DelFile.exe
Deletes one file or module from imgfs_raw_data.bin. Wildcards are not supported.
Usage:
DelFile.exe filename.ext
Uses imgfs_raw_data.bin from current directory. Does not check for errors.
AddFile.exe
Adds one file to imgfs_raw_data.bin. Would reuse space freed by DelFile.
Usage:
AddFile.exe filename.ext
Uses imgfs_raw_data.bin from current directory. Does not check for errors.
The typical process should be:
prepare_imgfs.exe nk.nba
viewimgfs.exe imgfs_raw_data.bin
...modify "dump" directory as you need...
BuildImgfs.exe
make_imgfs.exe nk.nba
or
prepare_imgfs.exe nk.nba
DelFile.exe filename.ext
AddFile.exe filename.ext
...you may add/delete as many files as you need...
make_imgfs.exe nk.nba
Of cause you'll need a tool to convert NBF<->NBA files. SD-card images can be also used instead of NK.NBA file, but this was not tested!
Troubleshooting.
In case of invalid ROM the tools would crash without saying anything. In this case they may destroy the contents of input files.
Use these tools at your own risk! They may make your device completely unusable! Always make an SD-card backup of your ROM and Extrom!
The worst case I had during tests was complete destroying of DOC partition on my device. I had to flash WM2003 OS, repartition DOC from there and this fixed the device. Of cause this method cannot be used on Wizard or Universal.
I've published these tools so that someone could integrate BA patches into a ROM or play with cooking own ROMs.
edited 12.12.2005. AddFile/BuildImgfs should work on Universal/Wizard ROMS (i.e. roms with empty imgfs_removed_data.bin file).
edited 15.01.2005. Fixed a major bug found by TofClock. Short name of files with filename length 24 chars or longer (like "instmsgrresources.96.dll") was incorrectly generated and in some cases they were inaccessible by OS.
edited 05.02.2005. Added several checks so that viewimgfs.exe does not crash on incorrectly patched ROMs (MPX200). Don't use buildimgfs.exe on such ROMs.
edited 30.03.2006. Added RecMod tool that reconstructs modules dumped as directories to a working DLL. So reusing modules from other ROMs is now much easier. Added updated prepare_imgfs.exe with support of ACER N300 ROM (thanks to Tuatara).
edited 12.07.2006. Added source code of prepare_imgfs/make_imgfs tools, so anyone can add the support of new devices.
edited 25.10.2006. Published the source code on my site. The code is ugly and is not commented at all. Don't ask me how to compile or use it!
I've stopped working on this project. There would be no updates.
Complete source code is available on my site.

mamaich,
can this be done on Alpine device??? Alpine that known as faster Himalaya also should be running WM5.....
thanks

Looks nice
Some questions:
1. AddFile:
Can I add single file like
Code:
AddFile something.exe
or have I use 'modules as directories' [like directories dumped with ViewImgfs]
2. AddFile:
Is it possible to add files into directories not in \Windows? For example: "\Program Files\Something\something.exe"
3. Is it possible to modify the kernel? Can I extract and replace \Windows\fatfsd.dll?
Thanks in advance.

mamaich, would for example replacing the internet explorer exe be enough to get it to render gifs correctly? Or are extra dll needed? Also is it necessary to use the other tool you linked to as it appears your tool can add and delete files itself? thanks
Edit: Forgot to add, thanks for your hard work.

mamaiiiiichhhhh I was waiting those tools gr8 work mate, can you upload the modified rom that you already customized for testing it?

baniaczek said:
1. AddFile:
Can I add single file like
Code:
AddFile something.exe
Click to expand...
Click to collapse
You can use both methods, but subdirs can be used only if you are really know what you are doing (i.e. you know all addresses of each section and 100% sure that they don't overlap some other modules and you've edited .VM and .ROM files). In most cases you should add EXE/DLL files as normal files.
Is it possible to add files into directories not in \Windows? For example: "\Program Files\Something\something.exe"
Click to expand...
Click to collapse
All files are placed into \windows dir and then moved by coldinit to subdirs according to instructions in initflashfiles.dat. Of cause you can modify that file as you like.
3. Is it possible to modify the kernel? Can I extract and replace \Windows\fatfsd.dll?
Click to expand...
Click to collapse
Boot part can be edited with http://forum.xda-developers.com/viewtopic.php?t=33321
ramram
There is no ROM I can release for public testing. I would not integrate my patches into the ROM, I'm working on adopting Wizard's ROM for our devices. But everything is on too early stage, I have to combine registry settings, ROM files, find and patch drivers for ROMs to work, etc. And Wizard's ROM is larger than ours, some files should be removed.

efjay said:
mamaich, would for example replacing the internet explorer exe be enough to get it to render gifs correctly? ...
Click to expand...
Click to collapse
I don't have any problems with IE.

Ic
mamaich,
I'll wait you then until you finish the wizard rom adoptation, I'll be glad trying it on the BA if you don't mind, consider my device for development purpose and beta testing if needed.
Concernig the IE, I have the same problems as Efjay mentioned earlier.
Thank you

@mamaich
Thank you for the answer. And thank you for your hard work [sinze Siemens SL45i].

mamaich said:
efjay said:
mamaich, would for example replacing the internet explorer exe be enough to get it to render gifs correctly? ...
Click to expand...
Click to collapse
I don't have any problems with IE.
Click to expand...
Click to collapse
mamaich, the problem is with viewing gif files. On this site using PIE i cannot see the quote button and other buttons below a post. Even manually opening a gif file on the BA opens PIE with a blank page.

go mamaich!!!
;o)))
buzz

buzz_lightyear said:
go mamaich!!!
;o)))
buzz
Click to expand...
Click to collapse
And GooO BuzZ

how about buzz if you can with your know how get a bare minimum rom version of universal not having alot of crap like the various silly tsk files and other pictures and videos that serve as demos on the rom and not do anyting else..im sure alot of us use our own file explorers (resco,tc) so that can be removed aswell.. what do you think...??/

can you use nk.nbf? how can i convert nk.nbf into nk.nba????

zohaer21 said:
can you use nk.nbf? how can i convert nk.nbf into nk.nba????
Click to expand...
Click to collapse
you can use this tool xda3nbftool.exe download from ftp for BA or Xda2nbftool.exe for Himalaya.
@Maimach
All the module files are Directory ??? How can I use these for my purpose ? But it Great work Maimach , go on!!!!!!

I tried to use this tool to add two modules and then flash the finished nbf file but i get an error file is corrupt if i use BaUpgradeUt.exe. If i use MaUpgradeUt_noID.exe it seems to initialise but no rom info is shown on the upgrade screen. Continuing the rom upgrade nothing then happens then a message comes up that the upgrade is finished. Soft reset and back to normal. I followed mamaichs instructions and everything seemed to go ok. Any idea why it didnt work for me?

Yeah, go Mamaich, you rock. After the Wizard ROM on the BA, the next step could be a complete ROMkitchen (á lá Wallaby...).

Stupid question, where can I find the NBF<->NBA converter? (Yes, i did search the forums)

ftp://xda:[email protected]/BlueAngel/Tools/UpgradeTools.rar
and this page for info
http://wiki.xda-developers.com/index.php?pagename=BA_GettingStarted

@efjay
did you use the -sd -sl -so and the -c -u options in xda3nbftool? Thats where i went wrong first time.

[Released Translation TUTORIAL] - HOW to translate ANY ROM

Hi!
After a long time of trying to cook custom roms in greek language I am ready to post a small tutorial on how to translate your Rom to your Language using kitchens with a quick and dirty way .
Attention there is a better way to do so but this is what I Do to make my Greek ROMS
Step 1)
a)Download your language emulator Files from
http://www.microsoft.com/downloads/details.aspx?FamilyID=38c46aa8-1dd7-426f-a913-4f370a65a582&DisplayLang=en#filelist
(b) extract the files in a new folder.
Slumpolo 's suggestion:
-----
to extract files from the emulation rom follow this direction:
- Download Tadzio's imgfs excelent tools in: http://forum.xda-developers.com/showthread.php?t=298327
- Unzip the tools along with the image in any folder.
- Rename the image to A.BIN (to make the next commands easier to type).
- Open a D.O.S. command window and perform these commands:
Code:
> NBSPLIT -emu A.BIN
(it generates two files: A.BIN.EXTRA and A.BIN.PAYLOAD)
> IMGFSFROMNB A.BIN.PAYLOAD IMGFS.BIN
(it generates the file IMGFS.BIN)
> IMGFSTODUMP IMGFS.BINAnd that's all. Files are dumped in /Dump directory
-----
Click to expand...
Click to collapse
(c) Rename ALL the 4xx files to 409 (e.g. 0408.mui -> 0.409.mui) Apply this to all files and folders (an eyasier way to do that is to search from windows for all *408* files and then rename them)
Slumpolo's suggestion
----
For step 1c) during the translation of italian rom for the mui files that resides in directory I edited also a file (simply with Supered) that has a line that pointed to the 0410 files (ea. italian) and changed this to 409.
----
Click to expand...
Click to collapse
Step 2)
Find your BASE ROM.
Step 3)
Download your Kitchen. I prefered Anichillus kitchen due to the fact that supports ROM dumping in an easy way
Step 4)
Dump ROM ( If you use Anichullus Kitchen , follow the manual but Stop BEFORE using Bepe's Package TOOL !
Step 5)
Go to DUMP folder ,(eg C:\core\extract\dump) and paste ALL the language files you have renamed from step 1c . ATTENTION you have to copy and paste ALL files from your language folder AFTER you have renamed them to 409 . REPLACE duplicate files
Step 6)
Continue with kitchen steps . For instance if you were to use Bepe's Package TOOL , go on and build the packages.
Step 7)
Edit Initflashes.dat file . Information on how to do that are in every cooking tutorial. In Intflashes.dat file you will have to translate all the links and directories according to your language files. CAUTION if you make mistakes in translation your WM6 will be crappy and programs may not start
->In order to make a good translation check your original rom, or try the WM6 emulator wth your language files and check the directory names (eg
folder Programs in Greek have to be Προγράμματα)
Step 8)
Save Initflashes.dat in unicode and remove first two bytes with a hex editor
Step 9)
Choose your OEM packages.
For GREEK USERS : If you need a greek software keyboard like the original one I have made an OEM package that allows you to do so
Slumpolo's suggestion
------
For step 9) / 10) about keyboard, you must add with a oem package also:
- dictionary in your language
- settings for your language
- t9 dictionary for your language
- for keyboard layout make this registry mod:
Code:
Registry Editor:
HKCU >> ControlPanel >> Keybd
Create a string "Locale" with "0410" vale. Everything without "Where 0410 is your country value.
------
Click to expand...
Click to collapse
Step 10)
build your rom according to your kitchen manual
I hope this helps
Good luck with your tries

I have used the same method for the italian version but you must translate also some parts of .hv files and .rgu or you must pay more attention during the translation of initflashfiles.dat because not all links and directories can be translated without .hv and .rgu editing.
My suggestion? Edit only initflashfiles.dat
Some add for your excellent tutorial:
----
For step 1b) to extract files from the emulation rom follow this direction:
- Download Tadzio's imgfs excelent tools in: http://forum.xda-developers.com/showthread.php?t=298327
- Unzip the tools along with the image in any folder.
- Rename the image to A.BIN (to make the next commands easier to type).
- Open a D.O.S. command window and perform these commands:
Code:
> NBSPLIT -emu A.BIN
(it generates two files: A.BIN.EXTRA and A.BIN.PAYLOAD)
> IMGFSFROMNB A.BIN.PAYLOAD IMGFS.BIN
(it generates the file IMGFS.BIN)
> IMGFSTODUMP IMGFS.BIN
And that's all. Files are dumped in /Dump directory
----
For step 1c) during the translation of italian rom for the mui files that resides in directory I edited also a file (simply with Supered) that has a line that pointed to the 0410 files (ea. italian) and changed this to 409.
----
For step 9) / 10) about keyboard, you must add with a oem package also:
- dictionary in your language
- settings for your language
- t9 dictionary for your language
- for keyboard layout make this registry mod:
Code:
Registry Editor:
HKCU >> ControlPanel >> Keybd
Create a string "Locale" with "0410" vale. Everything without "
Where 0410 is your country value.
Next days I'll try to release an
Ciao

At last
Very good..now i can direct all people who ask this question here.
Great initiative

Thanks
Slumpolo
Updated

Tna said:
Thanks
slumpolo can you post info about the which parts of hv files you edit?
Click to expand...
Click to collapse
I'll post everything next week. All my files are in office
Ciao

btw. as far as i know only certain wm6 builds can be translated using EMU mui files. i dont remember build no's.

Why is that ? What are the restrictions?

does it work for Universal to ?

thats what i wrote above, as far as i know(consulted with bepe) 17913 build its not supported(latest uni) it must be build ???? i remember there is 4 in build no. cannot fint irc log with that conv. with bepe

Hi and thanks for your tutorial. I try to go a different way and want to port over a hermes mui cab to get german wm6. i have some trouble of getting it done.
- the file explorer draws no softkeybar, so it is not usable. does anyone know what files i need therefore?
- the free space when installing a cab isn't displayed correctly
what have i done?
- i took the cab from asukal and removed hermes specific things
- afterwards i copy the files from the emulator image to get newest versions of the files.
if somebody want to test it - here you go:
http://www.gsm-multifund.de/holg/Making_German_Wizard.cab
i would appreciate every help.
best greetings
holg

answer from midget about builds that can be translated:
Code:
the changes from 17740-5 are not language related so the mui's work for all of them

i tried a newer rom and also got no luck with the file explorer. does anybody know what file is responsible for translating the file explorer?

No i don't... since file explorer is the least used program i didn't really care about it ...
so sorry but i can't help in that ... why don't you leave it as it is ?

i think filesys.exe.0409.mui

I think that he has found the file. The problem is about the softkey .
Try using reshack tool (it can be found in most kitchens) and open the mui file. search for the softkey
But yet I am not sure ...

yeah thanks for the suggestions
i personally like the build in filexplorer, cause it is fast and has softkey control, it's good if you just browse and open a file.
filesys.exe.0407.mui is already inserted in windows directory, so i will test with reshack,but at the moment i am a little busy.

Doubt about Files
Hi people
About the translation... i have one question.
After doing the "IMGFSTODUMP IMGFS.BIN" command, and all files are in the Dump Directory... besides the files with 4xx names, there are also some folders with 4xx names... and inside those folders are some files also with 4xx names.
Do i have to rename the folders and the files inside those folders, or just the files... or just the folders.
And one thing more... for example the folder "bbcbres.dll.0816.mui" inside these folder, one of the files called "imageinfo.txt".. inside this txt there's something written on the first line : " Module name: bbcbres.dll.0816.mui" if i have to change the name of the file inside the folder called "bbcbres.dll.0816.mui".... do i have to change this line also inside the txt ???
Thanks

how about the hardware keyboard? because I am on a German MDA Vario, Wizard of course, since we are using QWERTZ instead of QWERTY?
Will this be fixed automatically as well?
Cheers.

PauloBarreiros said:
Hi people
About the translation... i have one question.
After doing the "IMGFSTODUMP IMGFS.BIN" command, and all files are in the Dump Directory... besides the files with 4xx names, there are also some folders with 4xx names... and inside those folders are some files also with 4xx names.
Do i have to rename the folders and the files inside those folders, or just the files... or just the folders.
And one thing more... for example the folder "bbcbres.dll.0816.mui" inside these folder, one of the files called "imageinfo.txt".. inside this txt there's something written on the first line : " Module name: bbcbres.dll.0816.mui" if i have to change the name of the file inside the folder called "bbcbres.dll.0816.mui".... do i have to change this line also inside the txt ???
Thanks
Click to expand...
Click to collapse
You have to change all the *0816*. There is no need to change the folders al long as you rename the *.816* files that are included in those folders. There is no need to change the imageinfo since your are not going to replace the original one.
After renaming All the files (including the language files inside the folders) then you shoud copy only THESE files to your dumped ROM .

4irm said:
how about the hardware keyboard? because I am on a German MDA Vario, Wizard of course, since we are using QWERTZ instead of QWERTY?
Will this be fixed automatically as well?
Cheers.
Click to expand...
Click to collapse
no ... look for hades language pack to fix that, too

[KITCHEN-WWE-NL-DE] O.R.D.E. v2.04.00.01[118.51|61.26][VACATION]

Open.Rom.Diamond.Edition​
​
The First ever MultiLanguage Support NOOB Kitchen.
Now It Cooks you either a German, English or A Dutch Rom without the need of knowing what goes on underneath the cooking hood.
Just Start Cooking Select your Language then Disable or enable the applications you want in the rom and Flash.
For the more experienced Cooks, Package Updates or extra packages are always welcome to be submitted. Place the name into the Package like "PACKAGE_DSIXDA_Mortscript_Screen_Rotate_Simple_0000". You can PM me about it or post directly into the thread.
The Kitchen is Hybrid and i have given no attention to the Build Numbers that you SEE in device information. I only Update Incrementally and only what is needed as long as it's stable i don't care about version numbers Shown, trust me i know what i'm talking about, stop the paranoia.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
​
Make It Like You Want To And Help Making It Better​
Version 1.97.162.6 WWE+DE+NL BETA|132.66|14.15|118.51||115.03|53.77|61.26|​
The last stage of Development before it leaves Beta has now been reached. The Selectable Options will all be put into the correct groups. A few more options will be added, Bugs will be found and the mort installation script will be optimized.​
IPMORTANT Cooking Instructions​
Contents & Options​
Blauwe Tand Me Up Scotty.​
OLD SKOOL XDA Respect, to Brothers "The Great" Faria and the "Kitchen Classic" Anichillus​
This Project could not have been Possible without, Bepe, Bram_smulders, cmonex, dark simpson, panosha, Anichillus, itsme, jcespi2005, joubertvasc, jugglerlkr, mamaich, Mort, OliPro, pfcsabre, pof, sushilange, Paul at Modace for Apptodate, Nadavi, Snailslug, tadzio, theblasphemer, AlphaZero, SwTos, MRHawaii, Mondilv, Tom Codon, Tuspidin for sharing the Blackstone ROM, udk and Many More.
Direct Contributors, Noonski, Ameet, DSIXDA, NFSFAN, mccune, aruppenthal, bbobeckyj (for teaching me the Mort Regread and If else commands, for even more optimized packages), Bl0w, mst46, Kokotas, stief (without him i would not have a Diamond to Cook and work with in the first place), Pkoper, Piranha1, Mossi, comec, (The German Team). TheDizzAR, Aarge (For their Appreciative Donation)
If i have forgotten to add credit to you, i'm sorry for my slip up. Feel free to PM me about it so i can correct it.
Please Report Your **** Ups (Combination's of Selections that don't work together)​
If you like what we're doing and would like to motivate me into making it WWE (Almost Done) and bringing the kitchen over to Touch Pro to, you can show us some love.​
​
Packages are Allowed to be used for Personal Roms only.
And if you manage to use the heavily MortScript Dependable Packages in a Public ROM respect to you for understanding Why it is being used.
Give a Holler, but most importantly help making it better.
Or Do as most do Send a PM and most of the Time the Answer will be Yes.​

O.R.D.E. German
ORDE German version available.
Current version:
22.12.2008 1.97.162.2
Please leave your comments here or in german here.
22.12.2008 v1.97.162.4DE

Temporary Placeholder for ORDE WWE Messages.

Extra Packages
Added into Next Update (1.97.162.7).
PACKAGE_McCune_Quickmark_0000
PACKAGE_McCune_Stopwatch_0000
Upgrade Packages
PACKAGE_McCune_Quickmark_0000 & Install Script
PACKAGE_McCune_Stopwatch_0000 & Install Script
The contents of the INstall scripts need to be added manually to the SPC.mscr in the OEMOPERATORS folder if your upgrading before version 1.97.162.7

PACKAGE_AltTab_0000:
Adds "Alt-Tab" functionality (program switching) under the Start menu.
PACKAGE_Opera_Mini_4_2_0000:
Installs Opera Mini 4.2 on your Diamond and also creates a shortcut on the Start menu. It is recommended that the Esmertec Jbed 20080912 package is selected or else the shortcut may not work (see the next package).
PACKAGE_VGA_Esmertec_Jbed_20080912_5_1_0000:
Thanks to trueg for pointing this version out to me. It is one of the first versions of Jbed that allows you to resize the tiny fonts in Opera Mini, among other things.
PACKAGE_TouchHD_EnglishOnly_Keyboard_0000:
Touch HD Keyboard, English only. Similar to Diamond keyboard but with left/right/up/down soft keys below the keyboard. Files are based on the multi-language CAB by sblop at this link; I simply took out the appropriate files and registry keys, reducing the size significantly.
.

Screenshots
Some Screenshots:
More To Come​

Instructions
Instructions
1. Be Sure you have Developers HardSPL Flashed to your Phone before you start Cooking.
In the Folder "Tools\SPL's" you will find three versions of these.
2. The Kitchen is not set up to use a specific Radio nor do i Advice any as Radio performance can differ from Operator To Operator
A Collection of Radio's can be found in the folder "Tools\Radio's"
3. The Kitchen does not include the OS.NB anymore because it was getting to big. Fortunatly Modilv has the LEGO Kitchen Thread Kitchen Thread Where He Provides two OS.NB versions in his Rapidshare Folder.
Download either the 8MB Pagepool version or the 12MB Pagepool version and then drop the OS.NB into the "\Rom\" folder.
4. The Kitchen has three Language Options to choose from when it Begins.
1 for English (not working yet) 2 for German & 3 For Dutch (Not Working Yet).
5. After Choosing your language Disable or Enable extra options in the BUILDOS screen and then Press Play. If you get errors during this process please post them in this thread. After BUILDOS is finished Close the Build OS window and it will continue do to it's job until the Flash to you phone Screen comes up, so Flash it.
6. Flashing Roms to your phone is always risky, no matter how much precautions i have taken, everything that goes wrong is also your responsibility. If your not that familiar with the process the advice is to not tick OF more then the already preselected options.
If you want the kitchen to keep using your preferred packages you have to edit the Corresponding language file in the Options folder.
If your making an English Rom edit the EN.xml file in notepad.
Look up the option you want preselected in BuildOS (The Kitchen) and change the value from False to True (or the other way around).
Don't forget to also to put True into the correspondant Language Option.
0407 for German 0409 for English 0413 for Dutch.
For German edit the DE.xml and for Dutch NL.xml

Content and Default Options
[X]= Default set to ON
[0]= Default set to OFF
If no other MUI Locale Code Present, the Package does not need it.
[X] PACKAGE_francarl_FingerMenu_0000_1_10 [AppToDateSupport]
[X] PACKAGE_joubertvasc_RemoteTracker_0000_0_3_2-0 [AppToDateSupport]
[X] PACKAGE_sushilange_Diamond_TF3D_Config_0000_0_6_7 [AppToDateSupport] [0407] [0409] [0413]

Downloads
​O.R.D.E. NL Kitchen (No ROM download but a Full and Easy Do it Yourself Kitchen)​ SYS: 52.19965 & 5.20954
XIP: 52.20954
OEM: 1.93.404.5, 1.96, 1.97 & 2.00
|Storage|Total|In Use|Free||Program Memory|Total|In Use|Free|
Version 1.0
Version 1.93.404.2 |115.30|17.63|97.66||111.02|56.98|54.04|
Version 1.95.404.7|127.04|19.81|108.47||111.02|55.33|55.69|
Version 1.95.405.1|114.80|24.44|90.36||111.02|49.80|61.22|
Version 1.95.405.3|120.80|20.38|100.04||111.02|48.12|62.90|
Version 1.96.405.5 |122.54|19.20|103.34||111.02|47.07|63.32|
Version 1.97.161.9 |129.16|18.18|110.35||115.03|48.56|66.47|493
Version 1.97.162.5 DE+NL |134.41|12.07|122.34||115.03|56.87|58.16|
Version 1.97.162.6 WWE+DE+NL BETA|132.66|14.15|118.51||115.03|53.77|61.26|
Version 1.97.162.7 WWE+DE+NL|132.66|14.15|118.51||115.03|53.77|61.26|
(Measured after a second boot and killing Active Sync)
Then above numbers are by using the default Ultra Clean preconfigured settings. (not as Clean as it should be yet)
If you change these, the numbers will also change.
This is so easy it can't go wrong (if you Meet the requirements below and don't mess with the settings)
XP SP2 or Vista with MS .NET Framework required to use it.
Also Developers HardSPL is recommended
(Also required is Microsoft Visual C++ 2008 Redistributable Package added to Package)
Any Changes To Kitchen Are at Own Risk!​
Updated Packages (All in the Next Kitchen upload)
(ORDE Packages have no Unneeded Files like Package.Provxml, Initflashfiles.txt, Help, .LNK or other files that are not needed to make the app working. Because Mort Takes Care of most of that)

Changelog
>>=IN <<=OUT
​
Build from Original Dutch HTC Build and numbering goes up from there.
>> (Version 1.97.162.8) Updated Stop Watch with newer version from McCune's Post.
>> (Version 2.04.00.01) Switched to 2.03 OEM/SYS/Restarted Cleanup.
>> (Version 2.04.00.01) Patched and updated PACKAGE_ORDE_ConnectionSetup_0000_1_5_35852_1 Icon removed CPL Item (using MyCPL to get Conn Setup in Control Panel) and Made Modules.
>> (Version 2.04.00.01) Patched PACKAGE_Snailslug_TouchResponse_0000_v03_2 Icon and Updated Package Made Module for the DLL and it now supports AppToDate in Rom to.
>> (Version 2.04.00.01) Updated Taskmanager to PACKAGE_ORDE_TaskManager_0000_2_1_35603_1 Made Modules, removed CPL item and replaces WM taskmanager in Control Panel, Reduced Graphics to 8 Bits.
>> (Version 2.04.00.01) Reduced PACKAGE_pfcsabre_SocialNetworksEngine_0000_1_0_1819_3528 by 0.5 MB by optimizing Graphics to VGA and 8 bits where possible (Graphics without Transparancy), Made Modules.
>> (Version 2.04.00.01) Updated RemoteTracker to PACKAGE_joubertvasc_RemoteTracker_0000_0_3_4-1
>> (Version 2.04.00.01) Added
PACKAGE_KDKobes_FootPrints_0000_1_11_33557_0, Plus the 4 options for different Navigational Soft ware, TomTom, NaviTel, PapaGo & Copilot.
>> (Version 2.04.00.01) Updated Album to PACKAGE_ORDE_Album_HTC_0000_2_5_1820_4127
>> (Version 2.04.00.01) removed CPL item from PACKAGE_Schaps_Network_Plugin_0000_1_0_30468_1
>> (Version 2.04.00.01) Updated Butler to PACKAGE_Siggie1970_Butler_0000__1_2, It's now made into a mort install Package

Q & A
Q: I tried the 'connectionSetupAuto' package and it did nothing - is this package meant to be
used in conjunction with the 'connectionSetup' package? Connection Setup on its own
works fine.
A: PACKAGE_OREE_ConnectionSetup_0000_1_5_34564_2_Auto & PACKAGE_OREE_ConnectionSetup_0000_1_5_34564_2 Need to be installed together to get the Auto part working (sort of)
PACKAGE_OREE_ConnectionSetup_0000_1_5_34564_2
Causes connection setup to run only once after reboot (60 seconds)
PACKAGE_OREE_ConnectionSetup_0000_1_5_34564_2_Auto
Sets it as an Autostart Item that is being run by The Taskmanager and runs whenever you switch the SIM card.
If once is enough, only use the PACKAGE_OREE_ConnectionSetup_0000_1_5_34564_2
(or you can start it manually)
If you switch a lot of Sim Cards and don't mind the extra memory being used at start up leave in the Auto version

Request
Who can help me create a MortScript that reads specific Registry values.
SOLVED thanks to bbobeckyj
Something like these
Code:
[HKEY_LOCAL_MACHINE\Software\MortInstaller\LNK\Reader.lnk]
"SourcePath"="\Windows\AdobeReaderLE.exe"
"TargetPath"="\Windows\Startmenu\Office Mobile\"
[HKEY_LOCAL_MACHINE\Software\MortInstaller\LNK\Calculator.lnk]
"SourcePath"="\Windows\MobileCalculator.exe"
"TargetPath"="\Windows\Startmenu\Office Mobile\"
It then Creates and Executes the Parts below.
Code:
CreateShortcut("\Windows\Startmenu\Office Mobile\Adobe Reader.lnk","\Windows\AdobeReaderLE.exe")
CreateShortcut("\Windows\Startmenu\Office Mobile\Calculator.lnk","\Windows\MobileCalculator.exe")
It's an AutoShortcut/ProvXML/Removeatribute.exe/initflashfiles.dat/Excessive .LNK files in Windows, replacement.
At the moment i put all commands into one start up script, but that makes separate and COMPLETE OEM packages impossible. As disabling one Package in the Kitchen, still leaves the Command in the start up mortscript to create the shortcut.
This is not just for my own convenience, but for building a kitchen that can be used by every NOOB, that contains optimized and clean Packages.
This way i can put the creation of .lnk files into that package it's RGU file.
If it could also unzip and Change attributes through this script using registry values it would even be better.
I know there's someone out there that can cook this one up.
Thanks for the attention at least.
Update:
Script has been adjusted.
It now reacts to if a file is present in Rom and then reacts to that taking into account the MUI localization.
Code:
if (FileExists( "\Windows\RotateScreen.mscr" ))
WriteFile( SystemPath("StartMenu") \ "Rotate Screen.lnk", "99#""\Windows\RotateScreen.mscr""?shellres.192.dll.0413.mui,-8259")
Else
EndIf

Package Submittal
If there's an app or package that you think would be a good one to include in the kitchen you can always submit it.
Here's what you need to take into account.
1. If the package does not need an RGU, you don't need to include it.
2. The RGU and DSM files need to be hand made.
Make a blank .txt file. Go to http://www.famkruithof.net/uuid/uuidgen get a new UID, Rename the text file and extension with the UID number and .dsm extension.
(Ervius Packages sometimes don't work correctly)
Make a blank text file again and rename it to the new UID name and .rgu extension. Make sure you resave the RGU file as Unicode. (that is only if you need the RGU file.
3. When the package is complete. Drop the Package Folder onto the BuildDSM.exe in the tools folder. (be sure that Initflashfiles and option.xml are temporary removed from package when you do this)
Some more explanations about Mortscript installation.
As we try to Use as few as possible files in the rom and also make accommodate with the three language.
The way to create a link to a program has a little trick to it so it installs into the correct directory for the language.
Beneath is an example:
Code:
if (FileExists( "\Windows\StopWatch.exe" ))
if (FileExists( "\Windows\shellres.dll.0413.mui" ))
MkDir(SystemPath("ProgramsMenu") \ "Applicaties")
CreateShortcut(SystemPath("ProgramsMenu") \ "Applicaties\StopWatchk.lnk","\Windows\StopWatch.exe")
Else
EndIf
Else
EndIf
This way it checks for two conditions before it creates a link
As shellres.dll.0413.mui only exists in a Dutch rom this particular shortcut will only be created in a Dutch rom.
Also when a directory does not exist, MORT will not install a link into it.
So i added the MakeDir command first.
Two other variables of the script are needed so it supports German and English.
Now if the file did not need to go into the sub dir Applicaties
One script would do:
Code:
if (FileExists( "\Windows\StopWatch.exe" ))
CreateShortcut(SystemPath("ProgramsMenu") \ "StopWatchk.lnk","\Windows\StopWatch.exe")
Else
EndIf
And only one version of the script would do.
Or the link creation could be more dynamic:
Code:
if (FileExists( "\Windows\YouTube.exe" ))
if (DirExists(SystemPath("ProgramsMenu") \ "MultiMedia" ))
CreateShortcut(SystemPath("ProgramsMenu") \ "MultiMedia\YouTube.lnk","\Windows\YouTube.exe")
Else
CreateShortcut(SystemPath("ProgramsMenu") \ "YouTube.lnk","\Windows\YouTube.exe")
EndIf
Else
EndIf
So if the Folder "MultiMedia" does not exist the shortcut will be made in the main programs folder.

ToDo
1. Check Manila Options (Checked)
2. Check Remote Desktop
3. Fix and put put back main ringtones.
4. Fix Dutch Missed Calls Issue.
5. Fix FullScreen Player. (Checked)
6. Add more configuration scripts.
8. Put back rtps reg values to streaming media and the file itself.

you kitchen is birrliant how i can make wwe rom?
what i need to change ?

yes2000 said:
you kitchen is birrliant how i can make wwe rom?
what i need to change ?
Click to expand...
Click to collapse
Either use the Full Kitchen
http://forum.xda-developers.com/showpost.php?p=2392286&postcount=3
To extract the OEM/SYS/ROM from an Official Rom.
Then Replace the OEM/SYS/ROM folders in ORDE Kitchen.
Then Compare the differences
The Brilliance of the Kitchen is because of all those other People that have worked on it, i just made it a bit more Noob Proof with some very amateuristic adjustments of the batch files.

Your calculations are correct...

pkoper said:
Your calculations are correct...
Click to expand...
Click to collapse
Well it's better then making a WWE Dutch or German ROM.
All the OS parts can be ported from newer WWE builds instead of Porting Localization to a newer WWE build.

Hey for all the people who make this kitchen ..i thank you.
Geat work but now i have to find a way to cook my own favorite programs in the rom.

UC Autorun + The Power of MortScript PreCooked.
Want to Change or add some stuff Through UC Autorun?
Here's a way for the advanced user to do even more.
Code:
CPY1:\Intern geheugen\Cabs\MyMort.mscr
CPY2:\Temp\MyMort.mscr
EXEC:\Temp\MyMort.mscr
Inside the script you can do anything you can do with Mortscript.
For instance copying over a complete Directory to Phone Storage.
Code:
UnzipAll( "\Intern geheugen\Cabs\ExtraTemplates.zip", "\Mijn Documenten\Templates" )
Code:
CreateShortcut("\Windows\Startmenu\Programma's\TomTom.lnk","\Intern geheugen\Program Files\Navigator\TomTom Navigator.exe")
As long as you don't forget to delete the script.
Code:
Delete( "\Temp\MyMort.mscr" )

[UC]XDA_UC V2.RC1, Automated & Silent User & Cook, Configuration Service[14/05/10]

[UC]XDA_UC V2.RC1, Automated & Silent User & Cook, Configuration Service[14/05/10]
V2.RC1 Update,... New AutoShortcut Commands, new SDConfig.txt Commands, Manual and Storage Card install folders added, Extra parameters for Cooks.
I'll be updating all documentation accordingly later today.​
Another (The?) new way to implement User Customization and Cooking.
This Thread is meant for Rom Cooks.
Users should take a look at the User To User Tips, Tricks ideas and issues thread.
What the XDA UC service does, is silently install (or not so silently if needed by User), .cab, .xdas, .xml, .reg, .mscr, copy over user manila files, install files from SDconfig.txt if wanted and then a few extra's for the freaks like copying folders or creating shortcuts from specific registries. This happens either at first or second boot depending on the existence of either RunCC.exe or Autorun.exe in rom.
It's all Mortcsript so it's very easy to get a grasp of it and change the behaviour and or Chip in adjustments/improvements.
But no knowledge of mortscript is needed to implement
It Uses DotFred's Taskmanager to parse and implement the .reg and .xml files. But it can also be used to disable or enable services or register DLL files.
More Information about the XDA Type Files at:
http://wiki.xda-developers.com/index...ename=XDA_file
My Shout out for this Two Year Long Evolving Collaborating Endeavour go to:
Bengalih (that has a very similar UC variant called Sashimi and helped with some of the early scripts I was trying to do with mort while cooking, I wish I could have collaborated more with him, it would have saved time re-inventing the wheel), RoryB for bouncing back ideas, supplying new scripts and perfecting older ones, serfer222 For making the script compacter, jmckeejr, Ameet & the whole Digital XDA SPC Cooking Crew, bbobeckyj, CLHatch, Scinor, Mort, Sleuth255, McCune, DotFred, MrVanx, danny_and_2, Cmonex, utak3r, Laurentius26, Radimus, and the Whole Original SPC Crew for accepting my obsessions.
For Knowingly helping me get the information, unknowingly helping me get the information or motivated me in keep going on in my Quest resulting in this.
If I Forgot you, Forgive me.
If you feel that certain information that has been used originated by you give me a holler and I will credit you if this is so.
Before you consider buying me a beer. Please consider Donating to XDA to help out with the maintenance of the forum and get cool stars next to your Nickname showing your appreciation. Then there are always the people that without their apps this wouldn't have been possible at all that you can consider showing some love. Mort, DotFred & Sleuth255 All of whom made Apps Seemingly simple But oh so useful for the whole XDA and PocketPC community.
Download and Info in next Post

What this version of the XDA UC service does, is silently install and execute (listed in the order the items get installed)
Run the Users customisations of course.
User side information here...
Run Cook.mscr in Windows folder(For Cooks Only)
More Cook info coming.
Add native support for .mscr, .mortrun, .xda, xdai, xdas & .xdaz files
(Where in "\Storage Card\" is read from HKLM\System\StorageManager\Profiles\SDMemory For MultiLanguage Support)
Requirements
The Rom should have the security relaxed in HKLM\Security\Policies\Polices by setting the value 0000101a to a 1.
So unsigned installations and Mortscript do not give a security error.
If you have a different language then English, don't forget to change the path in the initflashfiles.txt/app.dat file (if your using legacy kitchen )
The rest of the script should dynamcliy get the correct variable for the storage location.
In the end the process it comes down to the device starting after flashing and not needing any reboot while silently installing Cook and User configurations.
On the User end and cook end no SDConfig.txt ort config.txt file is needed.
Attached the OEM Package and a Sample Package for SD.
(Klaxon.Cab, GoogleMaps.xdas, two .reg files, two xml files, my.tsk, and a test mortscript)
The Control factors of the Sample SD Package is that is should install
HKLM\Software\XDA\Test\Reg 1 Parsed=1
HKLM\Software\XDA\Test\Reg 2 Parsed=1
HKLM\Software\XDA\Test\xml1parsed=1
HKLM\Software\XDA\Test\xml2parsed=1
These are the tweaks present in those files.
In addition everything installed will be found under
HKLM\Software\XDA\UC\
And the Morscript in the sample SD Card Package should give a message to confirm it was executed "Mort UC From SD Working"
Cab Files and XDAS files should eventually just be in the startMenu Programs.
G-Alarm is there because it needs User interaction and that will pop up when it needs your attention.
At the end of it all you get a message Installations have finished.
When using SDConfig.txt be sure to add a blank line at the end of it.
Disclaimer:
Please be aware that the XDA_UC script contains a disclaimer, not to post errors with it to the Mortscript forums, and the usual this **** cloud be dangerous to your phones health.
For Standalone version, place XDA_UC folder from "User_Storage Card" on Storage Card.
Then run "\Storage Card\XDA_UC\Install\XDA_UC.exe"

Information about the SDAutorun.exe V2 UC can be found here:
http://forum.xda-developers.com/showthread.php?t=366337
Information about SDConfig.txt & .xml user setup can be found here:
http://forum.xda-developers.com/showthread.php?p=5011285

Changelog:
V 1.0.01
Changed Sleep to start UC to 50 seconds for full device Boot before UC starts.
Changed "XDA UC Service Start" title to "customization" to match the old one.
Changed sleep before completion message to ten second in case the last cab needs user input and the Completion message pops up to early.
Changed Sleep at while for Theme installation to 2 seconds.
V 1.0.02:
Added Copy1 to Copy2 by reading from registry settings
[HKLM\Software\XDA\DirCopy]
"\\Storage Card\\Some Folder"="\\My Documents\\Some Folder"
Added Disabling Manila from Homescreen then Copying files from "\Storage Card\XDA_UC\manila" to Windows, The checking for existence of wallpaper_TF3D.png or wallpaper_TF3D.jpg and adding that to
[HKCU\Software\HTC\Manila]
"HomeBackgroundPath"="\\Windows\\wallpaper_TF3 D.jp g"
Import registry files from "\Storage Card\XDA_UC\manila\manila.reg"
Re-enable Manila on Homescreen and redraw it.
If not present do nothing.
Added RoryB's Complete SDAutorun.exe replacement/SDConfig.txt parser script.
Check for existence of Autorun.exe or RunCC.exe to automatic determine which method/bootcount to use.
There is no longer the need for two separate XDA_UC versions let alone a third.
.reg and .xml files will no be sent to renamed taskmanager "FS_TaskMgr.exe"
Added checking for cab files in "\Storage Card\XDA_UC\SD\", for those that don't have the luxury of changing the install paths in a cab file to hardcode these to Storage Card. So you get full user input to choose on these cabs.
V 1.0.03:
Todo's
Add Support For Diamond Internal Storage Need Someone with a Diamond to Test.
V 1.0.04:
Added Support for PimPackup files *.pib & .cer files.
Moved Disclaimer to the beginning and added an option to reset ad the end.
V 1.1.00:
Added extra Runs for Diamond and Samsung Internal Storage.
V 1.1.1B2:
Applied script improvements to reduce code used and make script a bit faster.
Removed Manila folder copy and replaced it with more general Copy2Root function/folder.
Added recognition of "REG: " command in SDConfig.txt parsing.
Added recognition of "CER: " command in SDConfig.txt parsing.
Testing:
Code:
If( FileExists( "\" & SDF & "\Cabs\pim.vol" ))
Kill("cprog.exe")
EndIf
During SDConfig.txt just before cpy1, cpy2 function.
V 1.1.1B3:
Mayor overhaul by new script from Serfer222
And then I started adding more crap and messing the new clean code up.
XCP1 & XCP2 commands for SDConfig.txt (Folder Copy with SDConfig.txt)
MCAB command for SDConfig.txt (Cabs that you want manual input for during SDConfig.txt)
SCAB command for SDConfig.txt (Cabs that you want installed to SD SemiAutomaticly during SDConfig.txt)
SC1 & SC2 commands for SDConfig.txt (Shortcut creation with SDConfig.txt)
KILL command for SDConfig.txt (Kill a running .exe/process)
EXEC: command for SDConfig.txt (Was already present but i removed the checking if the file is a .exe so anything can be executed and)
Del: Command for SDConfig.txt
.PROVXML now also get parsed in XDA_UC folder
Changed Serfer222's fix to parse mail xml files before PimBackup to "*mail*.*xml" so now if there's a file containing mail anywhere or is a .provxml get's parsed before PimBackUp.
RESET command for SDConfig.txt
WR1: & WR2: commands to write files using SDConfig.txt
Parse File containing "WiFi in it's name" Early like MyHomeWiFi.xml or MyHomeWiFi.provxml
Add a script to run and add XDA_UC to rom's without it.
"Manual" Folder in XDA_UC folder for Full Manual .cab Installs
"Storage Folder in XDA_UC folder for Semi Silent .cab installs to Storage
Early "*wifi*.*xml" parsing from XDA_UC for quick Wifi connecting.
Eauh maybe i forgot some stuff....
Bug Tracker for last Beta.
Wrong code for the WR1: & WR2: commands (Updated Beta Download with Fixed Script)
WR1: command needs a delete or else the next time it is run it will add text to the file instead of write a new one. Working on Fix. Fix Updated in original Download.
Changed XCP1: XCP2: commands into MOV1: & MOV2: to avoid confusion with CPY1: & CPY2: (TNX RoryB good one) Updated in original Beta Download.
Other Updates I'm looking into All Beta:
Changed Manila/Sense Script so it now Checks for manila.reg @ "\Storage Location\XDA_UC\Copy2Root\Windows\manila.reg" and runs the reg from there.
Test everything again
More optimisation of the code suggested by Serfer222
Call for Sashimi & PresetInstaller, so having Making an XDA UC Rom doesn't force users switching their preferred UC Setup.
Add DELT: command
Config.txt for Cooks (May not be included as it is partly redundant)

SDAutorun replacement without SDAutorun.exe
Information will be added about this in the future.
Some more changes to my method I thought I would share.
Run the items in SDConfig.txt without using SDAutorun. I do not have any tsk to run, but it would work the same. I put copy first since some EXECs like xcopy need to be copied before execution.
Code:
###############################
# SDConfig without SDAutoRun
###############################
; Wait 10 seconds to start to be sure SDCard can be accessed
Sleep( 10000 )
If( FileExists( "\Storage Card\SDConfig.txt" ))
xcount = ReadLine( "\Storage Card\SDConfig.txt" )
While( IsEmpty( xcount ) = FALSE )
If( SubStr( xcount, 1, 5 ) eq "CPY1:" )
xcopy1 = SubStr( xcount, 6 )
xcount = ReadLine( "\Storage Card\SDConfig.txt" )
If( SubStr( xcount, 1, 5 ) eq "CPY2:" )
xcopy2 = SubStr( xcount, 6 )
Copy( xcopy1, xcopy2, TRUE )
EndIf
ElseIf( SubStr( xcount, 1, 5 ) eq "CAB: " )
RunWait( "\windows\wceload.exe", "/nodelete /silent " & [COLOR=blue]"""" & [/COLOR]SubStr( xcount, 6 ) [COLOR=blue]& """" [/COLOR])
While( ProcExists ( "wceload.exe" ))
sleep( 3000 )
endwhile
Else[COLOR=red]if[/COLOR]( SubStr( xcount, 1, 5 ) eq "EXEC:" )
If( SubStr( xcount, -[COLOR=red]3[/COLOR] ) [COLOR=red]eq[/COLOR] [COLOR=black]"[/COLOR][COLOR=red]exe[/COLOR][COLOR=black]"[/COLOR] )
Run( SubStr( xcount, 6 ))
EndIf
[COLOR=red] ElseIf( SubStr( xcount, 1, 5 ) eq "XML: " )[/COLOR]
[COLOR=red] RunWait( "\windows\TaskMgr.exe", "/provxml " & SubStr( xcount, 6 ))[/COLOR]
[COLOR=red] While( ProcExists ( "TaskMgr.exe" ))[/COLOR]
[COLOR=red] sleep( 3000 )[/COLOR]
[COLOR=red] endwhile[/COLOR]
[COLOR=red] ElseIf( SubStr( xcount, 1, 5 ) eq "TSK: " )[/COLOR]
[COLOR=red] RunWait( "\windows\cusTSK.exe", SubStr( xcount, 6 ))[/COLOR]
[COLOR=red] While( ProcExists ( "cusTSK.exe" ))[/COLOR]
[COLOR=red] sleep( 3000 )[/COLOR]
[COLOR=red] endwhile[/COLOR]
[COLOR=red]Else[/COLOR]
EndIf
xcount = ReadLine( "\Storage Card\SDConfig.txt" )
EndWhile
EndIf
I have a mortscript I call user_C.mscr for some customizations that I used EXEC to run, but thought this way people could have multiple scripts.
Code:
If( DirExists( "\Storage Card\SDAUTO" ))
ForEach xscriptfile in Files( "\Storage Card\SDAUTO\*.mscr" )
CallScript( xscriptfile )
sleep( 3000 )
EndForEach
EndIf
Lastly, I have this final folder to hold cab files I want to install with user input. It also has a script to cleanup a few things from the cab install.
Code:
If( DirExists( "\Storage Card\SDAUTO\Final Files" ))
ForEach xcabfile in Files( "\Storage Card\SDAUTO\Final Files\*.cab" )
Runwait( "\Windows\wceload.exe", "/nodelete " & [COLOR=blue]"""" & [/COLOR]xcabfile [COLOR=blue]& """"[/COLOR] )
While( ProcExists ( "wceload.exe" ))
sleep( 3000 )
endwhile
EndForEach
ForEach xscriptfile in Files( "\Storage Card\SDAUTO\Final Files\*.mscr" )
CallScript( xscriptfile )
sleep( 3000 )
EndForEach
EndIf
I had to set config.txt to hide the overlay image and not lock the screen to allow seeing the messages and responding to them. Eventually I see this changing to have the first script copied to start up folder by an initflashfile and not even need AutoRun. Currently config.txt starts the mortscript and does nothing else.

Cook.mscr
If your cooking and want your own mortscript to also be run at first boot just name it cook.mscr and put it into Windows folder.
Update: From Version 1.2.0 Cook.mscr will be executed at the same moment as the rest of XDA_UC, so this is depended on if RunCC or Autorun is used.

Suggestion:
install the cabs in a known order, perhaps alphabetically, so that we can name the files in the order to install like so
10_MSVC.CAB
20_PIMBackup.Cab
etc means we can control the install order.

Reason I chose not to use the known "Cabs" folder is not to screw with that configuration.
(XDA_UC is backwards compatible with SDAutorun v2 SDConfig.txt)
Cabs will be automatically be parsed alphabetically that's a default when more cab's are being processed.
At least I think so
It's using MortScripts ForEach File command.
Almost Everything processed will be written to registry under.
HKLM\Software\XDA\UC
And no more hassle with cabs that need user interaction.
You just interact when they come up.
If it's a good idea I could also make it check for a present Welcomehead.png or the Existence of a TF3D folder to copy over personal TF3D files.
Uploaded the OEM and a Sample SD Test Package.

is there a way this could be done without removing the RUNCC?

Yes there is.
There's a few different solutions.
I have added your request to the first Posts.
It runs at second boot and skips a few things that RunCC takes care of like installing cabs present in the windows folder.
This way you can keep everything is with RunCC and the welcome.lnk in initflashfiles.dat
Personally I prefer the First method with no reboots at all but it does require some extra meddling in the Rom.

Hello,
I have some questions...
Noonski said:
(This Method is under Review as it seems the latest RunCC accepts config.txt files from SD)
Click to expand...
Click to collapse
Noonski said:
This didn't work in earlier versions i had my hands on.
Click to expand...
Click to collapse
Which version is this? 1.0.9.0?
RunCC can execute the same commands in config.txt? (EXEC, TSK, XML, CAB...)

I have yet to get a hold of the version l3v5y's using.
Yes RunCC can but it needs configuration. Now for a cook that isn't any problem. But for Simple users all they need to do is drop some cabs and tweaks they have collected throughout the forum into a folder not be annoyed by.

I posted a rom already that has runcc installing from sdcard's config.txt. Not too difficult at all, wonder why more cooks don't figure it out.

Because Earlier releases of RunCC from leaked roms did not except these commands.
I have just extracted a version of it from an official Rom and it's got the same version i was using before 1_0_9_0
So weird that it is now accepting it.
But looking back i did not use the addrun("RunExtra"
I did try the Run customer, and default tho.
(Slaps in his forehead)
But it's still not the same as i'm trying to offer here.

Noonski said:
Because Earlier release of RunCC from leaked roms did not except these commands.
I have just extracted a version of it from an official Rom and it's got the same version i was using before 1_0_9_0
Click to expand...
Click to collapse
Noonski said:
So weird that it is now accepting it.
But looking back i did not use the addrun("RunExtra"
I did try the Run customer, and default tho.
(Slaps in his forehead)
But it's still not the same as i'm trying to offer here.
Click to expand...
Click to collapse
What you're trying to offer here is IMHO a far better solution!
Sorry for not getting you my tweaked package, though you seem to have managed without...
I think having a complete solution, with automated install of all cabs in a folder would be great.

Well i also needed to Scour the new Roms for some updated OEMS and i needed to know for sure that welcomehead.192.png was named that way to add it to the process.
And maybe even a Copy User Preferred Manilla files from SD to device if present. There must be some other good ideas from people that like flashing, but are tired of installing their preferred skins, settings and Apps.
Unfortunately i found that the newer package of Connectionsetup asks for a reset where my previous VGA reskinned package did not.
All the Regs are te same (Except for two new unrelated ones).
I like the old non rebooting version better.
I know that a reboot isn't needed but i can see users unkowingly agree to that reboot. (But that's another subject)
I think i will change the package this weekend So it is only one method.
By default it is set to run at second boot, but it can easily be changed by the cook to run at first boot if that is the setup that one would prefer.
Also i'm still tinkering out the exact form of the XDA files.
But nice to hear i'm not on an island, l3v5y.

Noonski said:
Well i also needed to Scour the new Roms for some updated OEMS and i needed to know for sure that welcomehead.192.png was named that way to add it to the process.
And maybe even a Copy User Preferred Manilla files from SD to device if present. There must be some other good ideas from people that like flashing, but are tired of installing their preferred skins, settings and Apps.
Click to expand...
Click to collapse
Noonski said:
Unfortunately i found that the newer package of Connectionsetup asks for a reset where my previous VGA reskinned package did not.
All the Regs are te same (Except for two new unrelated ones).
I like the old non rebooting version better.
I know that a reboot isn't needed but i can see users unkowingly agree to that reboot. (But that's another subject)
I think i will change the package this weekend So it is only one method.
By default it is set to run at second boot, but it can easily be changed by the cook to run at first boot if that is the setup that one would prefer.
Also i'm still tinkering out the exact form of the XDA files.
But nice to hear i'm not on an island, l3v5y.
Click to expand...
Click to collapse
I think the "EXEC:" command waits for the process to close? If yes, then an application that runs some mortscripts could wait till all the mortscripts are run before continuing, so it can be run at first boot within RunCC. That saves the issue of an extra reboot...
Welcomehead.192.png is the file for VGA/WVGA devices, welcomehead.96.png is for QVGA devices, though it's actually set in the registry, so that could be checked at load time? (I'll find the registry key at some point...)
Something I've just thought of:
If there were a way for ROM cooks to block things that are known not to function or are included already, that would be quite useful. E.G. I include PIMBackup in ROMs, so why would anyone install an extra cab to do the same?

You could add a check for a specific .Cab name.
And if present change the extension.
Repeat and Rinse a few times.
Then at the end rename all .cabxx back to .cab
I think in general, not a lot of people change their cab names.
Unless like that previous post, someone likes to add numbers to them to control the order.
But in this Silent install method i can see that having one app being installed first could be useful as there's small pauses build into the script so the device isn't slow as hell the first minutes it boots.
I think it might get more error prone if it gets executed through RunCC.
With all the processes that get proccesed through the script.
It's using and starting, cusTSK.exe, TaskMgr.exe, wceload.exe and mortscript. But when Mortscript exitst it should be finished.
I would need to test this style to feel confident it doesn't reboot while there's still work in progress.
I Agree that getting it into the No Reboot style might be some extra work for cooks. And maybe i'm seeing this to much from my own perspective where i always remove and convert OEM configurations to straight forward packages.

Noonski said:
You could add a check for a specific .Cab name.
And if present change the extension.
Repeat and Rinse a few times.
Then at the end rename all .cabxx back to .cab
Click to expand...
Click to collapse
Noonski said:
I think in general, not a lot of people change their cab names.
Unless like that previous post, someone likes to add numbers to them to control the order.
But in this Silent install method i can see that having one app being installed first could be useful as there's small pauses build into the script so the device isn't slow as hell the first minutes it boots.
I think it might get more error prone if it gets executed through RunCC.
With all the processes that get proccesed through the script.
It's using and starting, cusTSK.exe, TaskMgr.exe, wceload.exe and mortscript. But when Mortscript exitst it should be finished.
I would need to test this style to feel confident it doesn't reboot while there's still work in progress.
I Agree that getting it into the No Reboot style might be some extra work for cooks. And maybe i'm seeing this to much from my own perspective where i always remove and convert OEM configurations to straight forward packages.
Click to expand...
Click to collapse
I personally hate having cabs installed, so in theory my ROMs should be good to go without the reset.
Based on what you said, it might be best if the number of complications are minimal, and device compatibility as great as possible. RunCC probably would make things more complex and error prone, so yes, I agree not having it as a dependency makes sense.
A mortscript could always recognise *cabname.cab, so even using an order flag at the front should work.
Silent install sounds like it could be great, although some of the cabs need user intervention... Also, having a flag settable somewhere that makes (or stops) a message box with "auto install is complete" would be useful...

At the moment i have G-Alarm in my SD folder for that User intervention.
It just pops up at the moment after it's install i know at first i waited for it, no i grab a beer and tap it when i arive but the script continues with the rest of the files present so it's not waiting on that user interaction.
The possible Pop up message would in theory come up at the moment the last cab is just starting to install but it should be possible to add a check if wceload is still active before it pops up.
Which reminds me i still need to contact some of the people that actually helped out a lot without knowing.
"Installation has Finished, if your in a good mood and were planning to get beer from the fridge choose yes to reset the device, If your not in the mood and need to actually use your phone right now, press no to reset whenever you feel like it"
Do you think that would fit in the screen

[PC-APP] RecModFolder - fast module to file conversion

01/04/2010 update - program can read list of modules from text file.
download link: http://www.4shared.com/file/255038195/c2b5de9b/RecModFolder_04.html
mirror: http://narod.ru/disk/19297102000/RecModFolder_04.zip.html
how to use
1. create text file RecModFolder.txt,
2. write list of modules to this file, for example:
SYS\MediaOS\wmpocx.dll
SYS\OS\dw.exe
SYS\OS\dwui.dll
SYS\OS\DwXfer.dll
3. pass RecModFolder.txt as a parameter:
RecModFolder.exe RecModFolder.txt
that's it.
and, of course, you can convert all modules in folder like this
RecModFolder.exe SYS\AdobeFlash
RecModFolder.exe SYS\AdobeFlashCodecs
there are sample RecModFolder.txt and cmd file that I use with OSBuilder
cmd file is executed from the root of my kitchen, program is in the tools\RecMod subfolder
====================================================
old post:
I developed small tool which helps me to update my kitchen with new OS build.
My device has wm6.1 kernel and I get tired with "too many modules" problem.
I know I can use RecMod to convert modules to files, but it's so slow and inconvenient:
find folder with module,
drop it on recmod.exe,
get new file out of this folder,
delete folder,
move file back,
find, drop, get, delete, move...
find, drop, get, delete, move...
GRRR!!!! =)
My tool will do all these steps for me.
I just select parameters:
1. Folder - folder with modules, for example SYS\21872,
2. Mask (optional) - any mask that is valid in windows is acceptable,
(common masks are *.dll, *.cpl, *.exe, *.mui), no mask means "*".
3. Count (optional) - how many modules to convert, no count means "convert all".
[new in v0.3] If Count is 0, program will only display all modules matching the mask,
and do not change your files.
=======================================
Example 1:
>RecModFolder.exe c:\xda\v1\SYS\21054
means - RecMod all modules in c:\xda\v1\SYS\21054 recursive
=======================================
Example 2:
>RecModFolder.exe c:\xda\v1\SYS\21054 *.exe
means - RecMod all exe modules in c:\xda\v1\SYS\21054 recursive
=======================================
Example 3:
>RecModFolder.exe c:\xda\v1\SYS\21054 *.dll 10
means - RecMod first 10 dll modules in c:\xda\v1\SYS\21054 recursive
=======================================
Algorithm
Code:
read parameters from command line
find all modules in given folder (recursive) using given mask
for each module folder
{
call RecMod
create temporary unique file name (GUID for safety reason)
move new file to parent folder and assign it temporary name
delete module folder (with all files)
rename new file, give it real module name
if (count >= requested count)
{
stop
}
}
=======================================
Installation
make sure you can run RecMod from console, add its folder to PATH or drop RecModFolder.exe to the same folder.
That's it.
=======================================
Tips
You can create shortcut to RecModFolder and drop folders on it from explorer or Total Commander. RecModFolder will convert all modules in that folder to files.
Backup your files. This tool doesn't ask any questions,
it just informs you in case of error and stops immediately.
Save log file and check it for errors.
This is console application - you can use it in bat files.
You can save output of this program to text file - add >fileName.txt to your command line.
example:
RecModFolder.exe c:\xda\v1\SYS\21054 *.dll 10 >log.txt
this command will call RecMod first 10 dll modules in c:\xda\v1\SYS\21054 recursive
and save its output to log.txt.
Do not open folders you want to delete (replace with files) in explorer (or Total Commander, FAR, etc.) while this program works.

very nice, but there is already a similar app which does it from right click menu..
see here -> recmod by OndraSter
you probably have more options on the whole process, but the other tool might be more convenient.. anyways i will try

serfer222, you know that you may be responsible for whole lots of nab made VERY bad rom releases now, lol?
hheh, thanks for that tool anyway.

nosedive said:
very nice, but there is already a similar app which does it from right click menu..
see here -> recmod by OndraSter
you probably have more options on the whole process, but the other tool might be more convenient.. anyways i will try
Click to expand...
Click to collapse
I can explain what is the main difference:
If I choose one module folder, for example
Code:
SYS\21055\SHARED\COMMON\BROWSING\browser.dll\
and select osRecmod "Recmod this folder" it will work.
but if I select parent folder
Code:
SYS\21055\SHARED\COMMON\BROWSING\
osRecmod will just delete this folder and create empty file BROWSING
in the SYS\21055\SHARED\COMMON\
So, you see, it doesn't work for me.
I want to convert all modules inside folder
Code:
SYS\21055\SHARED\COMMON\BROWSING\
in one step. I drag this folder on my tool and all modules are converted to files. That's what I want =)

pupakota said:
serfer222, you know that you may be responsible for whole lots of nab made VERY bad rom releases now, lol?
Click to expand...
Click to collapse
You know, there are a lot of such rom developers already here.
This tool will just save their time and maybe they will find out whole new world outside computer and then will quit rom development... =)

Thank you serfer222 for this application, which complements my kitchen.
By

New version - v0.3.
new option is added - if you set Count to 0 program will just display list of matching modules.
Example: I want to see a list of *.mui module folders that can be converted to files.
Command: >RecModFolder.exe d:\mega2\SYS\21874\ *.mui 0
Output:
Code:
d:\mega2\SYS\21874\SHARED\0409\AdobeFlash_LANG_0409\flashresource.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Autoupdate_Lang_0409\AutoUpdateRes_wpc.exe.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Base_Lang_0409\commctrl.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Base_Lang_0409\commdlg.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Base_Lang_0409\coredll.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Base_Lang_0409\coreres.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Base_Lang_0409\crypt32.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Base_Lang_0409\fatutil.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Base_Lang_0409\filesys.exe.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Base_Lang_0409\gwes.exe.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Base_Lang_0409\ieceext.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Base_Lang_0409\jscript.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Base_Lang_0409\miscres.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Base_Lang_0409\netmui.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Base_Lang_0409\notify.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Base_Lang_0409\OutlookLiveUpdaterResources.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Base_Lang_0409\outres.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Base_Lang_0409\quartz.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Base_Lang_0409\shellres.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Base_Lang_0409\shellresapps.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Base_Lang_0409\syncres.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Base_Lang_0409\tapres.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Base_Lang_0409\tshres.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Base_Lang_0409\unimodem.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Base_Lang_0409\waveapi.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Base_Lang_0409\wsp.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Browsing_Lang_0409\browsres.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Browsing_Lang_0409\mlang.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Browsing_Lang_0409\shdoclc.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Browsing_Lang_0409\shlwapi.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Browsing_Lang_0409\urlmon.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Browsing_Lang_0409\wininet.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\CHome_Lang_0409\cmhomeres.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Entertainment_Lang_0409\bbcbres.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Fwupdate_Lang_0409\MdsRes_wpc.exe.0409.mui
d:\mega2\SYS\21874\SHARED\0409\IPSECVPN_Lang_0409\ipsecvpnres.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\Skybox_Lang_0409\MyPhoneConsole.exe.0409.mui
d:\mega2\SYS\21874\SHARED\0409\WMWidgets_LANG_0409\riahostres.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0409\WMWidgets_LANG_0409\wmwidgetinstallerres.dll.0409.mui
d:\mega2\SYS\21874\SHARED\0419\AdobeFlash_LANG_0419\flashresource.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Autoupdate_Lang_0419\AutoUpdateRes_wpc.exe.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Base_Lang_0419\commctrl.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Base_Lang_0419\commdlg.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Base_Lang_0419\coredll.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Base_Lang_0419\coreres.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Base_Lang_0419\crypt32.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Base_Lang_0419\fatutil.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Base_Lang_0419\filesys.exe.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Base_Lang_0419\gwes.exe.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Base_Lang_0419\ieceext.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Base_Lang_0419\jscript.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Base_Lang_0419\miscres.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Base_Lang_0419\netmui.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Base_Lang_0419\notify.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Base_Lang_0419\OutlookLiveUpdaterResources.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Base_Lang_0419\outres.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Base_Lang_0419\quartz.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Base_Lang_0419\riresdll.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Base_Lang_0419\shellres.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Base_Lang_0419\shellresapps.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Base_Lang_0419\syncres.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Base_Lang_0419\tapres.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Base_Lang_0419\tshres.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Base_Lang_0419\unimodem.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Base_Lang_0419\waveapi.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Base_Lang_0419\wsp.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Browsing_Lang_0419\browsres.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Browsing_Lang_0419\mlang.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Browsing_Lang_0419\msscript.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Browsing_Lang_0419\shdoclc.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Browsing_Lang_0419\shlwapi.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Browsing_Lang_0419\urlmon.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Browsing_Lang_0419\wininet.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\CHome_Lang_0419\cmhomeres.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Entertainment_Lang_0419\bbcbres.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Fwupdate_Lang_0419\MdsRes_wpc.exe.0419.mui
d:\mega2\SYS\21874\SHARED\0419\IPSECVPN_Lang_0419\ipsecvpnres.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\MediaOS_Lang_0419\wmploc.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\RemoteDesktopMobile_Lang_0419\wpctsc.exe.0419.mui
d:\mega2\SYS\21874\SHARED\0419\Skybox_Lang_0419\MyPhoneConsole.exe.0419.mui
d:\mega2\SYS\21874\SHARED\0419\WindowsLive_Lang_0419\WLMContactsResources.dll.0419.MUI
d:\mega2\SYS\21874\SHARED\0419\WindowsLive_Lang_0419\WLMDeckResources.dll.0419.MUI
d:\mega2\SYS\21874\SHARED\0419\WindowsLive_Lang_0419\WLMHSContainerResources.dll.0419.MUI
d:\mega2\SYS\21874\SHARED\0419\WindowsLive_Lang_0419\WLMHSMailResources.dll.0419.MUI
d:\mega2\SYS\21874\SHARED\0419\WindowsLive_Lang_0419\WLMHSMeResources.dll.0419.MUI
d:\mega2\SYS\21874\SHARED\0419\WindowsLive_Lang_0419\WLMHSMessengerResources.dll.0419.MUI
d:\mega2\SYS\21874\SHARED\0419\WindowsLive_Lang_0419\WLMHSSearchBarResources.dll.0419.MUI
d:\mega2\SYS\21874\SHARED\0419\WindowsLive_Lang_0419\WLMHSSplashResources.dll.0419.MUI
d:\mega2\SYS\21874\SHARED\0419\WindowsLive_Lang_0419\WLMHSSyncResources.dll.0419.MUI
d:\mega2\SYS\21874\SHARED\0419\WindowsLive_Lang_0419\WLMMailResources.dll.0419.MUI
d:\mega2\SYS\21874\SHARED\0419\WindowsLive_Lang_0419\WLMMessengerResources.dll.0419.MUI
d:\mega2\SYS\21874\SHARED\0419\WindowsLive_Lang_0419\WLMServiceResources.dll.0419.MUI
d:\mega2\SYS\21874\SHARED\0419\WindowsLive_Lang_0419\WLMSharedResources.dll.0419.MUI
d:\mega2\SYS\21874\SHARED\0419\WindowsLive_Lang_0419\WLMSpacesResources.dll.0419.MUI
d:\mega2\SYS\21874\SHARED\0419\WindowsLive_Lang_0419\WLMSyncResources.dll.0419.MUI
d:\mega2\SYS\21874\SHARED\0419\WMWidgets_LANG_0419\riahostres.dll.0419.mui
d:\mega2\SYS\21874\SHARED\0419\WMWidgets_LANG_0419\wmwidgetinstallerres.dll.0419.mui
97 modules found.
download it from the first post.
have fun =)

keep on
good job man

I have an idea for next update.
Now I'm using 21874 with my wm6.1 kernel and just simple update it to 21876 is a headache. This tool helps me to convert modules fast, but I still must choose what should be converted. I'm lazyyyy. I did it for 21874 and want to REUSE my old work.
Idea is:
1. run application and choose good existing build AS TEMPLATE.
2. select new build folder and drink a cup of coffee.
3. my app will do the job - take old working build as template and prepare new build exactly the same way.
What do you think? Is there a program that already implement this feature or
I need to create it? (lazy question)
=)

When I start doing recmod the recmodefolder.exe shows this message "Do you have RecMod.exe in PATH?" and then stops.
What happens?

program is updated, list-mode added,
first post is updated

hi, friends, it seems an excerllent apps, but how can i download it? when i visit that link, it seems a Russian web, i even don't know one letter!
can you upload it rapishare ?

www.4shared.com link in the first post

useful App ,, Thanks
when selecting or specifying 1 module folder, it doesen't work for me.
It shows "RecMod 0 modules completed"
It works only using multiple (eg: *.mui).
Maybe the first prob. will be replaced by osrecmod, & ur tool for multiple files ,, LoL
------------
ANY idea of converting back file to module?
-Yasser-