Calling all kitchen makers - Windows Mobile

This is an idea for airextreme, ondraster... etc and all the current kitchen makers. I'm in the process of trying to setup a 1 Gb RAMDrive for platformrebuilder to use to dump the gazillion files used in ROM cooking, to try to cut down on the hard drive fragmenting and gain quite a bit of speed too in the process. Looks like I might have to use symbolic links, since I doubt PRB supports \TEMP to a different drive. If the other tools (like imgstofs, libnb.. etc) could also use this method, I think we'd have some pretty fast kitchens!
So... any thoughts on this ?

Well I just tried it with the "Romex Software" RAMdrive (free software) and it friggin flies! I've already got an SSD and that's where my kitchen resides, but now that it sits on a ramdrive, it's at least 10-20 times quicker.

Sounds interesting. How long did it take to go from pressing the build button to generating the nbh? OSBuilder by Barin (not platform rebuilder based, but still copies files once) makes a ROM in about 2 minutes from start to finish (623 modules and 7103 files).

mwalt2 said:
Sounds interesting. How long did it take to go from pressing the build button to generating the nbh? OSBuilder by Barin (not platform rebuilder based, but still copies files once) makes a ROM in about 2 minutes from start to finish (623 modules and 7103 files).
Click to expand...
Click to collapse
I made a FULL Cookie 6.5.X Leo ROM in about 40 seconds. This is on a Core2Duo Dell laptop running at 2.7Ghz...
Just made a Titanium ROM in about 28 seconds... There's definitely some improvement here. For a guy like me that makes a metric ton of ROMs, this can certainly be helpful, but it doesn't mean all kitchens can't benefit from this

I know of possibility of using RAMdisk, I used to have full kitchen set up on my ramdisk and have cooked ROM (XPR) with TF3D in about 30 secs from clicking on "build_rom.bat" file.
I think airxtreme is (partially) working on (partial) removation of whole prb, so he might include support for ramdisk and file caching. Let him speak! lol

OndraSter said:
I know of possibility of using RAMdisk, I used to have full kitchen set up on my ramdisk and have cooked ROM (XPR) with TF3D in about 30 secs from clicking on "build_rom.bat" file.
I think airxtreme is (partially) working on (partial) removation of whole prb, so he might include support for ramdisk and file caching. Let him speak! lol
Click to expand...
Click to collapse
I realize now that this might not be for the everyday chef that makes one or two ROMs. However, if you brilliant programmers can find an easy, seamless way to swap everything to RAM, I think the kitchens will get much quicker. I know mine has and every seconds counts for me, when you make hundreds of ROMs. Hehe Now if I could get rid of the biggest bottleneck, compressing the nbh with 7zip, I'd be in heaven. But for that.. I need more processing power unfortunately.

NRGZ28 said:
I realize now that this might not be for the everyday chef that makes one or two ROMs. However, if you brilliant programmers can find an easy, seamless way to swap everything to RAM, I think the kitchens will get much quicker. I know mine has and every seconds counts for me, when you make hundreds of ROMs. Hehe Now if I could get rid of the biggest bottleneck, compressing the nbh with 7zip, I'd be in heaven. But for that.. I need more processing power unfortunately.
Click to expand...
Click to collapse
Even as an amateur cook-in-training, having faster cooking time means being able to test small changes quickly. Instead of making multiple changes, testing and then finding out which change didn't work out.
For the time being I'm definitely going to try using a ram drive. Well, that's as soon as I finish sorting out my packages which seems to need a couple of days

NRGZ28 said:
This is an idea for airextreme, ondraster... etc and all the current kitchen makers. I'm in the process of trying to setup a 1 Gb RAMDrive for platformrebuilder to use to dump the gazillion files used in ROM cooking, to try to cut down on the hard drive fragmenting and gain quite a bit of speed too in the process. Looks like I might have to use symbolic links, since I doubt PRB supports \TEMP to a different drive. If the other tools (like imgstofs, libnb.. etc) could also use this method, I think we'd have some pretty fast kitchens!
So... any thoughts on this ?
Click to expand...
Click to collapse
It's already in there:
{
"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"
}

airxtreme said:
It's already in there:
Click to expand...
Click to collapse
Okay... well then it seems you thought of it. How about PRB's temp\dump folder... does that go to your RAMDRIVE mode as well ?

NRGZ28 said:
Okay... well then it seems you thought of it. How about PRB's temp\dump folder... does that go to your RAMDRIVE mode as well ?
Click to expand...
Click to collapse
Everything is done in the temp folder even the platformrebuilder stuff

mwalt2 said:
Sounds interesting. How long did it take to go from pressing the build button to generating the nbh? OSBuilder by Barin (not platform rebuilder based, but still copies files once) makes a ROM in about 2 minutes from start to finish (623 modules and 7103 files).
Click to expand...
Click to collapse
Well, i redirected Temp folder to RamDisk and i like results very much
Code:
-------------------- TIMING ------------------------
Porting/Rebuilding XIP 00:00:01
Correcting template 00:00:00
Preprocessing 00:00:01
Registry 00:00:09
Metadata 00:00:00
Copying files 00:00:08
Postprocessing 00:00:00
Relocating/Writing modules 00:00:03
Merging/Writing dsm 00:00:02
Building IMGFS partition file 00:00:15
Building ROM file 00:00:12
Net time 00:00:56
Total time 00:01:02
----------------------------------------------------
PACKAGES 418
MODULES 621
FILES 8328
----------------------------------------------------
And also i'll try to reduce registry processing time....

-=Barin=- said:
Well, i redirected Temp folder to RamDisk and i like results very much
Code:
-------------------- TIMING ------------------------
Porting/Rebuilding XIP 00:00:01
Correcting template 00:00:00
Preprocessing 00:00:01
Registry 00:00:09
Metadata 00:00:00
Copying files 00:00:08
Postprocessing 00:00:00
Relocating/Writing modules 00:00:03
Merging/Writing dsm 00:00:02
Building IMGFS partition file 00:00:15
Building ROM file 00:00:12
Net time 00:00:56
Total time 00:01:02
----------------------------------------------------
PACKAGES 418
MODULES 621
FILES 8328
----------------------------------------------------
And also i'll try to reduce registry processing time....
Click to expand...
Click to collapse
Yep. A noticeable improvement for me as well. I use the VSuite Ramdisk application myself. I tried a few and that one seems to be the fastest. I recommend a 1500 MB disk. I had 1000 before and ran into issues with "out of disk space" errors. Of course, the current ROM building tools dont actually TELL YOU they're running out of space, they just crash or give you weird errors. LOL

NRGZ28 said:
Yep. A noticeable improvement for me as well. I use the VSuite Ramdisk application myself. I tried a few and that one seems to be the fastest. I recommend a 1500 MB disk. I had 1000 before and ran into issues with "out of disk space" errors. Of course, the current ROM building tools dont actually TELL YOU they're running out of space, they just crash or give you weird errors. LOL
Click to expand...
Click to collapse
I use SuperSpeed RamDisk Plus on Win7 x64. For me it's enough 1024Mb because only Temp kitchen folder is redirected to ram disk - i tried to rebuild HD2 stock rom with all packages selected

-=Barin=- said:
I use SuperSpeed RamDisk Plus on Win7 x64. For me it's enough 1024Mb because only Temp kitchen folder is redirected to ram disk - i tried to rebuild stock rom with all packages selected
Click to expand...
Click to collapse
Yeah for me, I ran into problems building larger ROMs such as a ROM for the HD2. With 1000, I had to delete the new imgfs.bin right after it gets merged into the .payload, otherwise when nbmerge runs to create the .nb, it crashes. But now with 1,500 it's better. Now I just have to watch out for PRB not to crash, due to low RAM.

-=Barin=- said:
I use SuperSpeed RamDisk Plus on Win7 x64. For me it's enough 1024Mb because only Temp kitchen folder is redirected to ram disk - i tried to rebuild HD2 stock rom with all packages selected
Click to expand...
Click to collapse
NRGZ28 said:
Yeah for me, I ran into problems building larger ROMs such as a ROM for the HD2. With 1000, I had to delete the new imgfs.bin right after it gets merged into the .payload, otherwise when nbmerge runs to create the .nb, it crashes. But now with 1,500 it's better. Now I just have to watch out for PRB not to crash, due to low RAM.
Click to expand...
Click to collapse
I tried using Vsuite Ramdisk Professional with OSKitchen v1.32 beta 4 but the IMGFSFromDump tools crashed. If I don't select to use ramdisk, I can build without any problem. What settings do you use in Vsuite? I'm using 1536MB without selecting any of the other checkboxes. Tried using Scsi Disk and Direct IO Disk and both had errors.

airxtreme said:
It's already in there:
Click to expand...
Click to collapse
zard said:
I tried using Vsuite Ramdisk Professional with OSKitchen v1.32 beta 4 but the IMGFSFromDump tools crashed. If I don't select to use ramdisk, I can build without any problem. What settings do you use in Vsuite? I'm using 1536MB without selecting any of the other checkboxes. Tried using Scsi Disk and Direct IO Disk and both had errors.
Click to expand...
Click to collapse
I tried again with RamDisk Plus with OSKitchen v1.32 beta 4 and got the same error. See the error message and settings I used for OSKitchen. Note that with beta 4, it highlights problematic packages and I had corrected them before building a rom. Without using ramdisk feature, I could build my rom. I've also tried disabling everything in EXT but the same error happens.

zard said:
I tried again with RamDisk Plus with OSKitchen v1.32 beta 4 and got the same error. See the error message and settings I used for OSKitchen. Note that with beta 4, it highlights problematic packages and I had corrected them before building a rom. Without using ramdisk feature, I could build my rom. I've also tried disabling everything in EXT but the same error happens.
Click to expand...
Click to collapse
Maybe the problem is that you chose Q: instead of Q:\?

airxtreme said:
Maybe the problem is that you chose Q: instead of Q:\?
Click to expand...
Click to collapse
I'm using your "Browse" button to select drive Q, and it is showing as "Q:" after selecting. Taking your suggestion, I changed it to "Q:\" and clicked on "OK" button. When I clicked on Settings again to see if the new change had been saved, unfortunately, it was not. It showed as "Q:" again.

-=Barin=- said:
I use SuperSpeed RamDisk Plus on Win7 x64. For me it's enough 1024Mb because only Temp kitchen folder is redirected to ram disk - i tried to rebuild HD2 stock rom with all packages selected
Click to expand...
Click to collapse
If you want to save some space I can give you a imgfsfromdump version that deletes files/modules after adding them. I was also thinking about adding an input file list cache (to avoid having to copy the file in the dump folder and using the source file directly) and a compression cache since most files never change and the compression is done only on data and not on the stream as whole.

zard said:
I'm using your "Browse" button to select drive Q, and it is showing as "Q:" after selecting. Taking your suggestion, I changed it to "Q:\" and clicked on "OK" button. When I clicked on Settings again to see if the new change had been saved, unfortunately, it was not. It showed as "Q:" again.
Click to expand...
Click to collapse
No idea but it should work, the kitchen can work without issues on different drive letters. I'll see if it 's a drive path issue: a \ should be added in the path while from your error messages it looks like it wasn't.

Related

[Idea/App][Alpha Source code Released]TouchFlo3D Theme Installer, maker, backup...

A call to programmers with TouchFlo3D interests
Update... See POST #3
As many of you knows there can be some problems when people are trying to install TF3D themes...
* They are not compatible with the current Manila version in the ROM
* They are not compatible with Landscape (Raphael)
* New people don't know how to install them
* There is no standard to the packaging (.theme, .cab, .zip)
I have an idea that I think will simplify the making, distributing and installing of TF3D themes..
I will try to explain this as good as I can, hope you understand...
The theme maker starts of with a set of files that the use as a Template
It consists of all files needed in TF3D
*_manila
lua.dll
manila.exe
ManilaActivateToday.exe
ManilaDesktop.dll
ManilaToday.dll
mode9.dll
(There can also be added extra files like .png or .bmp files)
The theme maker changes the files needed to make their cool TF3D theme...
could be only the images, or...
they can change mode9, lua, dll or exe files to make functions work as they want..
Then they zip all the files and it is ready for install...
Now here comes the main thing about my idea...
A Install theme application opens the zip file and compares each file to the file in the ROM..
If they are different from eachother it will copy the 'theme' file to the ROM...
This way It will only copy the files needed to change TF3D... It wont take unnecessary space on the ROM!...
If the theme maker has tested the theme before releasing it,
the theme will always work with no problems (or at least I hope so )
And if this gets done and is treated as a standard in theme making/installing there are more functions to include in the app..
* Tab selector /Tab organizer
* Replace Font's
* ... (whatever you guys can imagine)
I'm not very good at programming, that's why I'm posting this...
So, if anyone feels like taking on this project we can get less questions, complaints and angry messages in the threads
And I am willing to help in anyway to make this happen...!
/Nisse
Sounds good to me, since that most problems seem to be due to difference in manila installs from rom to rom, diamond to raphael, even cdma to gsm. I'll help as I can, but unfortunately I'm not a programmer either
Update
Ok.. I started making this myself... See first post
It's almost done... but I still cant figure out the zip function...
Thanx davidwhitney for your code examples... but it's in C#
I'm not really good at this, so I'm having a bit trouble...
But now when I'm almost done, I started to think that maybe It shouldn't be zip'ed...
because It maybe would take to much time??
Anyway... I've Included the source code here for all to test...
I am trying to make the program Idiot proof (n00b proof) hehe
Copy your theme's to a folder of your choice...
Open the program and enter the path of your theme's
Choose a theme from the dropdown
Read theme (Now it starts comparing files)
When It's done, you can see how many files/Mb it will copy.. You can see screenshots(if the there are any)
Advanced users can make additional choices from a checkbox list
Install theme
You can include other 'non-manila' files like png files or other..
It will make a list of the files copied, this way you can choose to remove them on next install, or keep them on next install
--
Option to 'Make your own theme', It will copy all your manila+ files to a folder, for u to use later or distribute..
Option to Restore to ROM default manila files
Here is the source code for anyone to try...
Remember its an Early Alpha...
If u don't know much about VB programming or manila files... DON'T TRY IT...
I will not have time to answer a bunch of n00b questions..(soory I don't want to be rude but....)
Download
TF3DThemeLoader.zip (source code)
Example Theme's
I really would like some feedback on this...!
and sorry about the code... I know it's a mess...
Some new screenshots...
{
"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"
}
Other files
Hi Nisse, could your idea extend to other windows files not just tf3d files? for example shell res dlls or even welcomeheads.
uniqueboy said:
Hi Nisse, could your idea extend to other windows files not just tf3d files? for example shell res dlls or even welcomeheads.
Click to expand...
Click to collapse
Yeah, whatever file u want...
But I don't know about dll files.... It's a bit tricky to copy/delete those...
Maybe not at first release... I have to first make the manila copying
This is going to take a little time... (a few weeks!!??)
But I really think this could be a good thing when it comes to the TF3D manila files
Hey man, nice work, would save a lot uninteresting questions. I know you are superior to me in all ways of the manila and know nothing of writing code. But anything to take the load of your hands. I'm just learning about the mode9 editing (kinda stuck) but in time can probably help there also. I do know a little about the taskbar makeovers, but that's for future time's. So any thing you want to out source let me know, 12
It might be useful if the software made a backup of any files it was overwriting. Often the files I am overwriting when installing a set of custom icons are not the original ones from the rom anyway. That way the backup could be used to simply restore to the previous state if it turns out looking crap, without getting stuck back with the original rom manila files.
paying it forward...
Hi,
Your idea wasn't too difficult to implement.
I've been using ROM updates from xda-dev for years silently so I've been prototyping this out as my way of saying thank you and giving something back.
I've built a proof of concept (that mostly works) for your app. A Data model, unit tests, a packaging format (zip file + xml descriptor to deal with validating files before copying), and some working code that packages and unpacks files on a device.
Requires the compact framework (I've targetted 3.5), and I've written a quick Windows packaging utility.
I don't have too much time on my hands, but anyone with any experience in C# should be able to pick it up.
Uses DotNetZipLib for archive access and MbUnit 2.x for unit testing.
I've got a stub project for the windows mobile implementation, but all the code that makes up the nuts and bolts is written.
Someone'll need to finish this up before it's fit for purpose but the legwork is all done, I just don't have more than an hour or so to work on it!
You'll have to excuse any dubious looking UI code in the windows app, it's really hacked together just to prototype out the idea.
I've pretty much just written this and packaged it up. Take it, use it, throw it away, delete it, open source it, I don't care
Hope this helps.
- David ( david at davidwhitney.co.uk )
Thanx...
I had a look at it.. but I don't know much about C# ... I just manage Visual Basic
But I appreciate it... maybe someone else can use it...
davidwhitney said:
Hi,
Your idea wasn't too difficult to implement.
I've been using ROM updates from xda-dev for years silently so I've been prototyping this out as my way of saying thank you and giving something back.
I've built a proof of concept (that mostly works) for your app. A Data model, unit tests, a packaging format (zip file + xml descriptor to deal with validating files before copying), and some working code that packages and unpacks files on a device.
Requires the compact framework (I've targetted 3.5), and I've written a quick Windows packaging utility.
I don't have too much time on my hands, but anyone with any experience in C# should be able to pick it up.
Uses DotNetZipLib for archive access and MbUnit 2.x for unit testing.
I've got a stub project for the windows mobile implementation, but all the code that makes up the nuts and bolts is written.
Someone'll need to finish this up before it's fit for purpose but the legwork is all done, I just don't have more than an hour or so to work on it!
You'll have to excuse any dubious looking UI code in the windows app, it's really hacked together just to prototype out the idea.
I've pretty much just written this and packaged it up. Take it, use it, throw it away, delete it, open source it, I don't care
Hope this helps.
- David ( david at davidwhitney.co.uk )
Click to expand...
Click to collapse
Ok, so here's a version with a working Windows Mobile client and a slightly altered zip component (as in, one that works on the compact framework ).
So you've got some tests, a windows packaging utility and a windows mobile unpacker that I've tested in the virtual machine and seems to work fine.
"Complete", if rough. Compiled exe's are in the respective bin/debug folders.
Enjoy!
Update
I've made a beta app.... see post #3
BUMP...
Anyone who wants to try this app??
See post 3
Sounds like an awesome great application.. well my question is that does this only "read and copy" over .theme files or does it do this with all files that want's to replace the manila file i.e cab files and so forth?..
well i have a Raphael ... you might have heard about xboxmods HD manila... it doesn't support landscape mode fully functionally yet.. well we managed to get landscape mode up but there are some bugs.. well my question is that will this application manage to make landscape mode stick on and detect that the phone is a Raphael and detect that there should be a landscape mod and manage to apply it when switching to landscape mode?..
gah.. i guess your answer would be, "why don't you test and tell us"... well unless you know anything i can't do it at the moment.. but will test it maybe tomorrow or at the day after tomorrow... well i just wanted to know if this application do this with all files that want's to replace the manila file i.e cab files and so forth?
Hei Norge!
Well... this app does whatever the Theme maker wants it to do...(almost)
It compare files from the theme folder(not .theme files yet) with the files on your phone... and only copy the files needed...
and you can add other files... like .png .dll (haven't tested that yet) and so on... but no .cab files....
I know about the Landscape problem with xboxmod's HD...
but this app won't solve the problem... maybe make it easier to install it?? when it's solved...
I haven't looked in to it, but (and correct me if I'm wrong) the problem with landscape with HD is the .exe and .dll files?? (manila.exe, mode9.dll ... ..)
Arju007 said:
Sounds like an awesome great application.. well my question is that does this only "read and copy" over .theme files or does it do this with all files that want's to replace the manila file i.e cab files and so forth?..
well i have a Raphael ... you might have heard about xboxmods HD manila... it doesn't support landscape mode fully functionally yet.. well we managed to get landscape mode up but there are some bugs.. well my question is that will this application manage to make landscape mode stick on and detect that the phone is a Raphael and detect that there should be a landscape mod and manage to apply it when switching to landscape mode?..
gah.. i guess your answer would be, "why don't you test and tell us"... well unless you know anything i can't do it at the moment.. but will test it maybe tomorrow or at the day after tomorrow... well i just wanted to know if this application do this with all files that want's to replace the manila file i.e cab files and so forth?
Click to expand...
Click to collapse
NisseDILLIGAF said:
BUMP...
Anyone who wants to try this app??
See post 3
Click to expand...
Click to collapse
haha, sure I'd like to see what this baby can do, but i'ts valentines day man. QT man, can't spens my time browsing around having fun right now. I'll let you know, 12
NisseDILLIGAF said:
Update
Ok.. I started making this myself... See first post
It's almost done... but I still cant figure out the zip function...
Thanx davidwhitney for your code examples... but it's in C#
I'm not really good at this, so I'm having a bit trouble...
But now when I'm almost done, I started to think that maybe It shouldn't be zip'ed...
because It maybe would take to much time??
Anyway... I've Included the source code here for all to test...
I am trying to make the program Idiot proof (n00b proof) hehe
Copy your theme's to a folder of your choice...
Open the program and enter the path of your theme's
Choose a theme from the dropdown
Read theme (Now it starts comparing files)
When It's done, you can see how many files/Mb it will copy.. You can see screenshots(if the there are any)
Advanced users can make additional choices from a checkbox list
Install theme
You can include other 'non-manila' files like png files or other..
It will make a list of the files copied, this way you can choose to remove them on next install, or keep them on next install
--
Option to 'Make your own theme', It will copy all your manila+ files to a folder, for u to use later or distribute..
Option to Restore to ROM default manila files
Here is the source code for anyone to try...
Remember its an Early Alpha...
If u don't know much about VB programming or manila files... DON'T TRY IT...
I will not have time to answer a bunch of n00b questions..(soory I don't want to be rude but....)
I really would like some feedback on this...!
and sorry about the code... I know it's a mess...
Click to expand...
Click to collapse
So I am somewhat familiar with VB. This is a great concept and I will definitely look into the source code and see if I can make some improvements.
If I remember correctly a .theme file is just a zip with a renamed extension, correct? That shouldn't be too hard to accomplish. Are you planning on making an automatic backup before the overwrite? How are the screenshots suppose to be formatted, i.e. which extension, size and so on.
I tried out the program but I couldn't get the browse button to work. That is about as far as I made it.
Currently installing Visual Studio and Windows mobile sdk. I forgot how long VS takes to install.
Hi, I'm glad you've got somewhere with this.
I don't really have too much time to check up on the threads here, however if you're still struggling for zip support, in my example code take a look at the file ArchiveManager.cs (it's actually misnamed, it should be Archive.cs really as it represents a single compressed archive).
There's code in there you should be able to adapt to VB pretty easily (I think there's a method called ExtractPackage or something, it opens a zip archive using the DotNetZip 3rd party component, parses the file for an XML definition file and then extracts the contents).
It really is no more than:
using (ZipFile zip = ZipFile.Read(_filename))
{
zip.Extract("archivedFileName.ext", "destination" true);
}
I forget what the method call is offhand but you can enumerate through the contents of the zip file by doing a foreach through zip.Entries (or something similar).
You can almost convert that to VB by removing the curly braces
(I hate reading vb or I'd actually try compile it myself ).
NisseDILLIGAF said:
Hei Norge!
Well... this app does whatever the Theme maker wants it to do...(almost)
It compare files from the theme folder(not .theme files yet) with the files on your phone... and only copy the files needed...
and you can add other files... like .png .dll (haven't tested that yet) and so on... but no .cab files....
I know about the Landscape problem with xboxmod's HD...
but this app won't solve the problem... maybe make it easier to install it?? when it's solved...
I haven't looked in to it, but (and correct me if I'm wrong) the problem with landscape with HD is the .exe and .dll files?? (manila.exe, mode9.dll ... ..)
Click to expand...
Click to collapse
Hei Sverige!
well yeah there are som probs with the HD manila to fully functional with a landscape mode.. well either the functions of HD manila must be ported to the stock tf3d or the bugs in landscape mode of HD manila be fixed.. i managed to make a video where i managed to stick the landscape mode on HD but there are some bugs like when i press on a function key on screen as calander or other stuff and the exit, then tf3d landscape will go into portrait but by closing and opening the slider on HTC Touch Pro then it will go back to a good looking landscape.. well i hope the HD manila added with landscape mode will get fixed.. the HD manila runs really really fast and very much faster when cfc compressed.. like 4 times faster than stock tf3d manila... i also think it lays in the exe files and mode9.. the mode9 in touch pro probably contains some strings to the landscape mode which probably should be ported to the mode9 of HD.. well i do not know what i'm talking about 100% since i'm not a pro developer and do not have any inside knowledge about manila or mode9... i'm a dreamer
A manila tab organizer could be very interesting
Hi NisseDILLIGAF,
Load a theme is nice but maybe a tab organizer could be great, activate or desactivate tabs and change the order. Similar to HD or TD2 application, very, very simple.
Thanks a lot,

Installing & Using Ervius Visual Kitchen V1.8.1 For OPAL

Hi Everybody, I have a good news, Ervius Visual Kitchen V 1.8.1 is working well on OPAL, and with it you can make your own Up to date ROM and Multi Languange ROM.
First and Last, I am only presenting the Kitchen, Not the ROM, so if you have any nonworking app, please don't ask me, discuss it here with others Opal Owner because I DON'T HAVE OPAL. But if you ask me about the kitchen, i will answer it.
Thanks to:
- imblfmstr for tested the kitchen
- Ervius & Bepe for the great tools and kitchen
- Olipro
- tadzio
Download Link 21844 KITCHEN:
http://www.4shared.com/file/129247993/76a618f3/ERVIUS_KITCHEN_FOR_OPAL_By_BesFen.html
CONTENT OF 21844 KITCHEN
This is the kitchen root preview in Windows Explorer:
{
"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"
}
1. EXT Folder
The External packages (EXT) folder is divided into Device Specific folders and a Shared folder:
*Device Specific folders are typically used for files (packages) that should only be applied to a specific type of the device.
Each Device Specific folder is further divided into Operating System Build Version Specific folders and a Common folder.
*Operating System Build Version Specific folders are typically used for files (packages) that should only be applied to a specific build (version) of Operating System. The Common folder is typically used for files (packages) that can be installed on any Operating System build version.
2. OEM Folder
The OEM folder can contain multiple Device Specific folders.
*Each Device Specific folder is further divided into Locale Specific folders and a Common folder.
*The Common folder is typically used for files (packages) that can be installed in any locale – not specific to a language.
*Locale Specific folders are typically used for files (packages) that should only be applied to a specific locale.
3. ROM Folder
The ROM folder is divided into Device Specific folders and a Shared folder.
*The Shared folder is typically used for kernel system files that are compatible amongst devices. (MSXIPKERNEL folder)
*Device Specific folders are typically used for kernel system files that should only be applied to a specific type of the device. (OEMXIPKERNEL folder)
-The Shared folder is further divided into Operating System Build Version Specific folders. Operating System Build Version Specific folders are typically used for kernel system files that should only be applied to a specific build (version) of Operating System.
-Each Device Specific folder is further divided into Operating System Build Version Specific folders.
4. SYS Folder
The system (SYS) folder is divided into Operating System Build Version Specific folders.
*The Build Version Specific folders will often contain files (packages) specific to the device DPI (Dot Per Inch) and Horizontal/Vertical display size.
*Each Operating System Build Version Specific folder is further divided into a ROM DPI, ROM Resolution, and Shared folder – providing a significant amount of flexibility during ROM compilation.
*The ROM DPI, ROM Resolution, and Shared folders are further divided into Locale Specific folders and a Common folder.
*The Common folder is typically used for system files (packages) that can be installed in any locale – not specific to a language.
*Locale Specific folders are typically used for system files (packages) that should only be applied to a specific locale – for example, 0409 (English).
Updating visual kitchen with new build
SOURCE OF HOT BUILD
If you want to Build a new ROM with The new Build, go to here to get the Source.
http://forum.xda-developers.com/showthread.php?t=544445
UPDATING VISUAL KITCHEN WITH NEW BUILD
We assume to update my 21844 visual kitchen for OPAL with newer Build (example 23037).
A. EXT
1. In the EXT\Opal create a new empty folder with the name of the build (example 23037).
2. copy the folder “Opal_External_Packages” inside EXT\Opal\21844 to EXT\Opal\23037.
Now your extended packages is ready
B. OEM
No need to modify this Folder
C. ROM
1. In the ROM\Opal Folder, create a new folder with the name of the build (example 23037). Copy the OEMXipKernel folder from ROM\Opal\21844 into this folder as shown below:
2. in the ROM\Shared Folder, create a new folder with the name of the build (example 23037). Copy the MSXipKernel folder from New Build into this folder as shown above.
D. SYS
In the SYS Folder, create a new folder with the name of the build (example 23037). Copy the SYS from the new Build into this folder as shown below:
DUMP XIP.BIN TO GET MSXIPKernel
TO make a new build ROM, we need MSXIPKernel, and sometime people only provide xip.bin of the new build. If it happens we need to dump it to get MSXIPKernel, download that file, and dump it with XIPPort.exe, here is the tools.:
http://www.4shared.com/file/125449740/a1b9e454/XIPPort.html
Now, put the attached file and the xip.bin in the same folder, then run XIPPort.exe, click “dump xip.bin” and wait until folder “OUT” appear, then click “make pkgs”, close the XIPPort.exe.
Go to folder “out” and you will find “Files and Modules” folder, inside each folder, you will find folder MSXIPKernel. Move the module inside OUT\MODULES\MSXIPKernel to OUT\FILES\MSXIPKernel, now you have the MSXIPKernel. And don’t forget to delete any *.txt file inside MSXIPKernel.
USING VISUAL KITCHEN
After add new build, run the kitchen, and you will get pic as below:
1. Choose your device, Opal
2. Choose your XIP Build
3. Choose your SYS Build
4. Choose your EXT Build
The default compression is XPR, you can make LZX compression by select the LZX.
You can change the PP, click "Other" Buton, you will see pic below:
Enter the number of PP as you want, the default for Opal is 12Mb, More PP make the ROM more stable and multitasking, you can make experience for the number of PP.
You can weather the package in the EXT, OEM, or SYS to include in the ROM or no by double click the name of packages.
OK that is all, you ready to click the "Create ROM" Button.
HAPPY COOKING Time to SLEEP....
Useful tools
USEFUL TOOLS
EXT PACKAGES CREATOR'S TOOL
http://forum.xda-developers.com/showpost.php?p=4489567&postcount=17
http://forum.xda-developers.com/showpost.php?p=4714566&postcount=69 Thanks XirXes
Here is some method posted by XirXes to minimize memory leak by make SLOT 0 memory free from Modules, Thanks XirXes.
Original posted by XirXes
XirXes said:
Hey BesFen, I think we need a post about memory mapping in this thread. One of the biggest things I've found that makes a rom invariably suck is poor memory mapping. It can even lead to not booting. I use this list of modules that can be converted to files from EDTP. It helped me fix my mapping issue without breaking anything. I use RightClickRecmod from this post for converting. Right click recmod needs C++ Runtimes and .NET Framework in order to work. If for any reason that doesn't work for someone they can do it from inside the kitchen itself (I've never tried it that way) or they can use a .bat script I found here.
RightClickRecmod
•C++ Runtimes
•.NET Framework
The modules that can convert to file:
Code:
AdobeFlash = ALL
AdobeFlashCodecs = ALL
BaseApps = Beam.exe, caldl.dll, calendar.exe, doclist.dll, fexplore.exe, hotvoice.exe, note_prj.dll, notes.exe, pimg.exe, shptutil.dll, VoiceBar.dll, VoiceCtl.dll and voicedll.dll
BlueTooth = bthpbap.dll ONLY!!!!
BROWSING = browser.dll, iexplore.exe and wmlview.dll
BROWSINGCORE = jscript.dll, mlang.dll and msscript.dll only.
Browsingie = ALL
BTDUN = NONE
Bth_A2DP = Avrcp_MPplugin.dll only.
Bth_HID = All except for bthidsvc.dll
GPSid = gpsid.dll
InternetSharing = ALL
MediaOS = ALL
NetCF = ALL
OS = dw.exe, dwui.dll, enrollnot.exe, machineenroller.dll, machineenrollerlaunch.exe, networkpolicycsp.dll, omadmclient.exe, quartz.dll, tcpstk.dll, tmarshaller.exe, umarshaller.exe
Phone = simsec.dll, tkitapp.exe
PhoneRedist = siclnt.exe
Redist = configmanager.dll, configmanager2.dll, obexapi.dll, obexinbx.dll, remnet.exe, syscsps.dll, welcome.exe
RemoteDesktopMobile = ALL
Shell = autotimeupdate.exe, CertInstaller.exe, fbrowser.dll, find.dll, msnsspc.dll, mstli.exe, peghelp.exe, richink.dll, rnaapp.exe, shfind.exe, sndplay.exe, taskmgr.exe, tskschcsp.dll, tskschedule.exe and tskscheduleu.exe
SkyBox = All but MyPhoneService.dll
WindowsLive = ALL but any DLL with Resource in the name.
WindowsLiveIM = ALL, unless you leave it running.
WMWidgets = unkown since I don't run any, but I imagine if you leave widgets running there should be a few.
Click to expand...
Click to collapse
Here some source of SYS, ready to use in VK Kitchen.
http://forum.xda-developers.com/showthread.php?t=587655 =====> Already Recmod/convert to file
http://forum.xda-developers.com/showthread.php?t=551470 =====> some build of SYS already Recmod/convert to file
Great BesFen, really good work! Can any mod make this post a sticky? Thanks!
I will be trying this kitchen soon...
I have successfully cooked a booting 23041 rom with this kitchen and once its working right I'll make a thread for it. Thanks BesFen, you're the man.
XirXes said:
I have successfully cooked a booting 23041 rom with this kitchen and once its working right I'll make a thread for it. Thanks BesFen, you're the man.
Click to expand...
Click to collapse
Nice to hear that the kitchen work well, Now time for you and others to build ROM and share it in Forum.
GO A HEAD, MAKE A ROM....
how to solve the following error?
ERROR: Not enough space in Slot 0!
Click to expand...
Click to collapse
**Sorry for not related to your kitchen**
lkachun9129 said:
how to solve the following error?
**Sorry for not related to your kitchen**
Click to expand...
Click to collapse
You can convert some modules to files.
If you can, try to make 0 module in slot 0 by convert some module, it will very good in releasing memory management and avoid "not enough memory" happened in your device.
Something wrong
Hey guys thanks for all your work on making this kitchen.But i think something is wrong somewhere.I build a rom 23037 and it booted and came up to the home screen,it has good speed but no backgroung,the home settings does not work,comm manager don't work and some other settings. What could be wrong?
Oh and i noticed that on boot the ONBL is 1.27.0000 and the OS is 1.26.0.0.
100% working
Guys i figured out what was wrong.The EXT folder don't have all the files for the Opal to work correctly.You can download the files from here : http://rs415.rapidshare.com/files/148930538/Opal_Stock_ROM_OEM_Folder.rar
I replaced all the files in the EXT and OEM folder with the ones i downloaded, build the rom and everything works great.By the way the SYS and XIP has to be 96dpi for it to work on the opal.
theglen35 said:
Guys i figured out what was wrong.The EXT folder don't have all the files for the Opal to work correctly.You can download the files from here : http://rs415.rapidshare.com/files/148930538/Opal_Stock_ROM_OEM_Folder.rar
I replaced all the files in the EXT and OEM folder with the ones i downloaded, build the rom and everything works great.By the way the SYS and XIP has to be 96dpi for it to work on the opal.
Click to expand...
Click to collapse
That's GOOD, This is we call THREAD for OPAL DEVELOPMENT, I hope everybody can share every knowledge in COOKING here.
Take a look others thread, they blow very quick, come on, i want to see other guys active here.
Transfer knowledge, Discuss, and Release a ROM.... Make OPAL FORUM HOT
how do i use this?
i just want to remove some apps from the rom like TouchFLO, Opera, Voice Commander etc... the ones i don't use to free up some memory.
is it like Bart PE Builder?
if i ʞɔnɟ up the cooking, will it brick my Viva when i flash it?
TheRem said:
how do i use this?
i just want to remove some apps from the rom like TouchFLO, Opera, Voice Commander etc... the ones i don't use to free up some memory.
is it like Bart PE Builder?
if i ʞɔnɟ up the cooking, will it brick my Viva when i flash it?
Click to expand...
Click to collapse
You can double click the app name from the kitchen list, or you can remove the folder name of app from EXT Folder.
The PDA may not boot (Brick) if:
1. the different version of XIP and SYS to far.
2. you don't put complete xip's files
But you can fix it by flash with others ROM, just go to Bootloader or Tricolor (I don't know which Button must press in Opal), connect your PDA to PC, and Flash again, very simple.
thanks BesFen!
i gotta try this.
ROM create is running, but very slowly. Looks like a fresh ROM. Btw, when I dump a cooked rom, it stop with error, may be protected ROM! Anybody know how to overcome that?
Including Other Apps
Does anyone know how to add Apps (.cabs) to the list on the Kitchen so its included into the ROM like other apps not included.
Diagrax said:
Does anyone know how to add Apps (.cabs) to the list on the Kitchen so its included into the ROM like other apps not included.
Click to expand...
Click to collapse
Here the tools:
http://www.4shared.com/file/131050367/e9febb08/Package_Creator.html
Put the tools and cab file in the same folder:
1. run package-creator-v2.7.exe, Click "Open Cab File", navigate to the cab file.
2. run OLD2NEW.bat
nguoc said:
ROM create is running, but very slowly. Looks like a fresh ROM. Btw, when I dump a cooked rom, it stop with error, may be protected ROM! Anybody know how to overcome that?
Click to expand...
Click to collapse
Protected ROM can not be dumped, better you dump a stock (Official) ROM.
The ROM should run fast in opal, not slow, pls inspect the xip and sys, maybe you miss some module/file, or put the module not in right place.
BesFen said:
Here the tools:
http://www.4shared.com/file/131050367/e9febb08/Package_Creator.html
Put the tools and cab file in the same folder:
1. run package-creator-v2.7.exe, Click "Open Cab File", navigate to the cab file.
2. run OLD2NEW.bat
Click to expand...
Click to collapse
Thanx but where should i place them
BesFen said:
Protected ROM can not be dumped, better you dump a stock (Official) ROM.
The ROM should run fast in opal, not slow, pls inspect the xip and sys, maybe you miss some module/file, or put the module not in right place.
Click to expand...
Click to collapse
Thank you,
I follow all the instruction in http://forum.xda-developers.com/showthread.php?t=554858, dump the orginal rom 6.1, built a rom, then I want to dump the created rom, but cannot!
The instruction does not mention anything about xip, cause the kitchen create it during building process. So just the sys. I download the sys in
http://forum.xda-developers.com/showthread.php?t=544445;
ported it in the kitchen, change the dpi to 96, res to 240x320, then create. But some time the ROM can boot, some time it cannot. Btw, if it boot, I found lots of errors, and don't know how to resolve it.
Does anybody have a stock 6.5 ROM or every thing dump from it?

[SOLVED] Include .cabs in ROM?

I'm trying to include a newer Google Maps and a few other applications and converted the .cab installers to EXT in osKitchen. They get included in the list in EXT Packages and I select all of them but still I cant find them when I have flashed my ROM to my device.
Am I supposed to do something more?
Double check that they are in the windows folder. All you should have to do is check the package.
djr83 said:
I'm trying to include a newer Google Maps and a few other applications and converted the .cab installers to EXT in osKitchen. They get included in the list in EXT Packages and I select all of them but still I cant find them when I have flashed my ROM to my device.
Am I supposed to do something more?
Click to expand...
Click to collapse
If your ROM is not in english you have to edit the app.dat to use the correct start menu folder.
look into or show us your buildlog...
airxtreme said:
If your ROM is not in english you have to edit the app.dat to use the correct start menu folder.
Click to expand...
Click to collapse
Thanks! Havent tried the new rom yet but the paths in app.dat was wrong.
But I do have to change the path to the programs folder too, I guess?
When I check the path in file explorer it says \Program and in app.dat it says \Program Files.
If you use cab 2 oem and oem 2 ext the app.dat is automatic created with the correct path.
So if you use a WWE package it will be 'Program files' and for the shortcut 'start menu'. If you use another language (Dutch for example) 'program files' has another name 'programma bestanden' and 'start menu' becomes 'startmenu' in Dutch.
So you need to correct that path according to the language you use.
You can use initflashfiles.dat as an example for every language you use.
djr83 said:
Thanks! Havent tried the new rom yet but the paths in app.dat was wrong.
But I do have to change the path to the programs folder too, I guess?
When I check the path in file explorer it says \Program and in app.dat it says \Program Files.
Click to expand...
Click to collapse
Laurentius26 said:
If you use cab 2 oem and oem 2 ext the app.dat is automatic created with the correct path.
So if you use a WWE package it will be 'Program files' and for the shortcut 'start menu'. If you use another language (Dutch for example) 'program files' has another name 'programma bestanden' and 'start menu' becomes 'startmenu' in Dutch.
So you need to correct that path according to the language you use.
You can use initflashfiles.dat as an example for every language you use.
Click to expand...
Click to collapse
I'm using osKitchen Zero 1.31 beta1 and cab 2 oem doesnt seem to exist anymore. I think it was in my old kitchen, osKitchen 1.25 but I dont use that anymore.
One of my cabs is actually a today screen plugin. How do I choose what plugins which should be selected from start?
Hmm the program files gets into the correct folder and a link is created in the start menu, but the link doesnt start the program. I guess it's still pointing to the wrong path.
How do I fix this?
djr83 said:
I'm using osKitchen Zero 1.31 beta1 and cab 2 oem doesnt seem to exist anymore. I think it was in my old kitchen, osKitchen 1.25 but I dont use that anymore.
One of my cabs is actually a today screen plugin. How do I choose what plugins which should be selected from start?
Click to expand...
Click to collapse
Everything is in the universal package converter now
djr83 said:
Hmm the program files gets into the correct folder and a link is created in the start menu, but the link doesnt start the program. I guess it's still pointing to the wrong path.
How do I fix this?
Click to expand...
Click to collapse
Just edit the shortcut; total commander works well.
Farmer Ted said:
Just edit the shortcut; total commander works well.
Click to expand...
Click to collapse
Cant I change that in the ROM? I dont want to have to change a lot after flashing.
I did a quick search for you:
http://forum.xda-developers.com/showthread.php?t=510806&highlight=cab2oem
Today items you enable/disabled like the sample of registry below.
1 is enabled and 0 is disabled.
[HKEY_LOCAL_MACHINE\Software\Microsoft\Today\Items\HTC Sense]
"Enabled"=dword:1
djr83 said:
I'm using osKitchen Zero 1.31 beta1 and cab 2 oem doesnt seem to exist anymore. I think it was in my old kitchen, osKitchen 1.25 but I dont use that anymore.
One of my cabs is actually a today screen plugin. How do I choose what plugins which should be selected from start?
Click to expand...
Click to collapse
{
"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"
}
Laurentius26 said:
Today items you enable/disabled like the sample of registry below.
1 is enabled and 0 is disabled.
[HKEY_LOCAL_MACHINE\Software\Microsoft\Today\Items\HTC Sense]
"Enabled"=dword:1
Click to expand...
Click to collapse
Thanks! But the plugin doesnt even show up in plugin list when I pre-install it in the ROM. The plugin is TodayAgenda. Do I need to do something more when adding today screen plugins?
djr83 said:
Cant I change that in the ROM? I dont want to have to change a lot after flashing.
Click to expand...
Click to collapse
Just edit the shortcut and then swap the new one into your package for the bad one. Although this whole topic is confusing. Are you trying to install cabs during customization, or are you trying to make actual packages from cabs? If it's the former, then you'll need to edit the .cab file to fix the shortcuts (if they are the problem).
Farmer Ted said:
Just edit the shortcut and then swap the new one into your package for the bad one. Although this whole topic is confusing. Are you trying to install cabs during customization, or are you trying to make actual packages from cabs? If it's the former, then you'll need to edit the .cab file to fix the shortcuts (if they are the problem).
Click to expand...
Click to collapse
I want to be able to select which programs I want to include in the ROM. How it gets included doesnt matter (I think?).
What's the difference between installing them during customization and making packages?
I found the bad shortcuts now, thanks, so I guess that problem is solved now. But please tell me the difference between customization installing and packages. I want to do it the correct way
There are different ways to include apps into a rom. Installing a cab during customization isn't a whole lot different then just installing a cab normally. There's nothing really special about it, except that the cab file is stored in rom. This could be a good thing or a bad thing, depending on how you look at it. You don't get any of the benefits of cooking an app into rom when you use cab files.
Creating a package means extracting the files (and reg keys, if there are any) from the cab file and then cooking them directly into the rom. In many cases, you can re-locate the application directly into the \windows folder (from \program files), and this saves space and shortens the time for first boot. You may also be able to convert some of the files to modules, which can increase performance (mainly, the apps boot up faster), but it doesn't always work. Modules can also save a bit of ram by loading code into the page pool. As an example, you can create a package with TCPMP (core player) that loads all of the files directly into the rom. This is much better than having the files in their own folder in \program files\tcpmp, because you don't end up having duplicate files in \windows (if you use an app.dat to copy the files into the program file directory) or one big cab file sitting in \windows. It saves on storage. Also, some of the .dll's and the .exe can be made into modules.
On the other hand, some apps just don't work if the files aren't placed in the proper directory. I've had a bugger of a time getting the new resco keyboard to work properly. Most of the time, you can just move files and sub-folders from program files straight into \windows, but it doesn't work with resco keyboard. The bloody skin files have to be located in \program files\resco keyboard pro\skins (the same goes for the language and sound files). It's not a big deal, but I could save a bit of space if I could locate some of the files in \windows. I get these files into the program files directory by unzipping a zip file with a mortscript during customization. Zips are easier to edit than cabs, and install faster, so that's what I prefer to use. You also don't have to bother with uninstall info (I always seem to leave that crap in when I pack a cab, even though it's pretty much useless to me).
Customization is the step after the screen alignment. It's basically the time when you pretty up your rom, and put in the final touches so that when the phone is fully booted up, it's just the way you want it.
Your post is just kind of unclear. It sounds like you're just trying to install cabs during customization, but some people are telling you how to extract cabs to make EXT's. I'm not really sure what you're asking.
Farmer Ted said:
There are different ways to include apps into a rom. Installing a cab during customization isn't a whole lot different then just installing a cab normally. There's nothing really special about it, except that the cab file is stored in rom. This could be a good thing or a bad thing, depending on how you look at it. You don't get any of the benefits of cooking an app into rom when you use cab files.
Creating a package means extracting the files (and reg keys, if there are any) from the cab file and then cooking them directly into the rom. In many cases, you can re-locate the application directly into the \windows folder (from \program files), and this saves space and shortens the time for first boot. You may also be able to convert some of the files to modules, which can increase performance (mainly, the apps boot up faster), but it doesn't always work. Modules can also save a bit of ram by loading code into the page pool. As an example, you can create a package with TCPMP (core player) that loads all of the files directly into the rom. This is much better than having the files in their own folder in \program files\tcpmp, because you don't end up having duplicate files in \windows (if you use an app.dat to copy the files into the program file directory) or one big cab file sitting in \windows. It saves on storage. Also, some of the .dll's and the .exe can be made into modules.
On the other hand, some apps just don't work if the files aren't placed in the proper directory. I've had a bugger of a time getting the new resco keyboard to work properly. Most of the time, you can just move files and sub-folders from program files straight into \windows, but it doesn't work with resco keyboard. The bloody skin files have to be located in \program files\resco keyboard pro\skins (the same goes for the language and sound files). It's not a big deal, but I could save a bit of space if I could locate some of the files in \windows. I get these files into the program files directory by unzipping a zip file with a mortscript during customization. Zips are easier to edit than cabs, and install faster, so that's what I prefer to use. You also don't have to bother with uninstall info (I always seem to leave that crap in when I pack a cab, even though it's pretty much useless to me).
Customization is the step after the screen alignment. It's basically the time when you pretty up your rom, and put in the final touches so that when the phone is fully booted up, it's just the way you want it.
Your post is just kind of unclear. It sounds like you're just trying to install cabs during customization, but some people are telling you how to extract cabs to make EXT's. I'm not really sure what you're asking.
Click to expand...
Click to collapse
What I'm doing now is definitly makeing EXT's. But that doesnt mean I'm sure that it is what I want to do. I just want to include some programs in the ROM from the beginning and EXT's seems like a good way to go.
But if I want to install cabs during customization, how do I do that?
You create an EXT:
Sample:
Yourpackage\
Yourpackage\files\your cab
And you add a line to config.txt so it will be autoinstalled during device setup.
A sample of that line:
CAB: \Windows\your_app.cab
djr83 said:
What I'm doing now is definitly makeing EXT's. But that doesnt mean I'm sure that it is what I want to do. I just want to include some programs in the ROM from the beginning and EXT's seems like a good way to go.
But if I want to install cabs during customization, how do I do that?
Click to expand...
Click to collapse
Laurentius26 said:
You create an EXT:
Sample:
Yourpackage\
Yourpackage\files\your cab
And you add a line to config.txt so it will be autoinstalled during device setup.
A sample of that line:
CAB: \Windows\your_app.cab
Click to expand...
Click to collapse
Where should this config.txt be? Yourpackage\config.txt?
And can I add an app.reg to this EXT so I get some settings installed too? Will these settings be applied before or after the cab-install?

◄ ▌ brainmaster´s Kitchen for Acer NeoTouch Version 1.2▐ ►

So, finally I am releasing my Kitchen. It was nice to be with all of you NeoTouch guys, and I am kind of sad that I am leaving the Acer Community as Kitchen Chef.
But there are others that can continue my work.
As I already told I wont have a time to answer all of your questions regarding my Kitchen. I will give you small Tutorial on how to cook and then you are on your own.
But you can find everything you need here on XDA Forum.
TUTORIAL:
​
My Kitchen is customized Kitchen that Stefano_1986_ already released.
The Kitchen is based on OSBuilder. Any questions that you have about how to use the OSBuilder can be answered here and here.
It is a Multi Kitchen - it contains Clean, Titanium GTX and all of the 5 Manila ROM, every ROM in 5 Languages - that means you can make 35 different ROM's with this Kitchen.
Its ziped and takes 500 MB, when extracted 1,03 GB. Sorry, but you need to download the whole package. First of all - use the latest 7zip for extracting, so you don't get any errors.
1. First install the .NET Framework 4 and then install the latest OSBuilder.
2. The Kitchen is configured for Clean and Titanium GTX ROM out of the box, if you want to cook a Manila ROM then first go to the extracted Kitchen folder and move all the files from the "____manila_ROM_move_everything_inside_this_folder_to_EXT_folder" to the EXT folder.
3. Go to the extracted Kitchen folder and double click on OSBuilder.osb to start the Kitchen.
4. Now choose from the configurations menu the "_Default_28244_Manila_Stock" configuration.
{
"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"
}
​
5. Choose the ROM language from the drop-down field: 0409 (English).
6. Now as you can see on the next photo, there are packages that are crossed out. That means that those packages wont be processed in the cooking procedure, only the 0409 and those without any language marks will be processed. This is how you can easily create Multi language ROM's by just switching the language in the drop-down field.
7. The next step is to start the cooking procedure with the green "play" button. You will have your ROM cooked in 3 minutes after you confirm few dialogs. The file is processed as flash.bin file in the "RELEASE" folder in your Kitchen.
8. As next, you need a extrom.bin file to complete your ROM. In the Kitchen folder you will find "___EXTROM_WWE" folder that contains cab files for Clean ROM and all the other ROM's. Copy the files from the "Normal" folder into the "EXTROM" folder in your Kitchen. In OSBuilder click on the "Tools" and then on "Build extrom.bin".
9. Now you have two files in your "RELEASE" folder: "flash.bin" and "extrom.bin". Extract the Flash ROM Basis.zip. There is a folder with the Basis for WWE ROM. Place the two cooked files in that folder and start the flashing procedure.
This was only a short Tutorial for my Kitchen. There is allot to explore. Many packages that I've created. And allot chances to blew the things out.
But, don't worry - if you fail flashing your ROM or you interrupt the flashing procedure, just put your Acer into the Bootloader mode and start again with the flashing procedure.
Here are the download links for my Kitchen:
Part 1. Part 2. Part 3. Part 4. Part 5. Part 6.
Flash ROM Basis
4Shared Mirror : password is as always "brainmaster"
Happy cooking!!! ​
Reserved 1.
Reserved 2.
Reserved 3.
Reserved 4.
The Kitchen is now online!
Finally the kitchen is online.... thx you so much dear Brainmaster, your are the S200 user who gave the most to the community. I spent the 2 last week to learn how to cook with osbuilder, and i know how long it takes to gather tweaks and package for cooking. This wil really help us to make great rom for our acer. Have fun with your HD2 and see you soon...
Can't download two last parts, 5&6, multiupload's page is empty. Is it because of limitation for free users, or smthn else?
dimamyth said:
Can't download two last parts, 5&6, multiupload's page is empty. Is it because of limitation for free users, or smthn else?
Click to expand...
Click to collapse
O.K. I will reupload them in couple of hours.
Brainmaster, thanks in advance. I'm using your beta ROM for last three months, and it's best firmware I even tried for S200. Is it built using this kitchen?
dimamyth said:
Brainmaster, thanks in advance. I'm using your beta ROM for last three months, and it's best firmware I even tried for S200. Is it built using this kitchen?
Click to expand...
Click to collapse
Yes this Kitchen is in fact the latest BETA ROM Kitchen.
Multiupload didn't accepted the last two files, so I had to re-upload all of the files to rapidshare.
If you already downloaded the files 1 - 4, you don't need to re-download them. Just download the 5th and 6th file and rename them so that you can extract the files without any problems (rapidshare is renaming the files automatically).
I will also make a mirror for the Kitchen on 4shared.com.
thanks a lot dude!!
definitely gonna use this kitchen and keep using s200 until acer releases a wp7 device (acer warranty is the best in my country)
The new OSBuilder is out.
AndrewSh said:
OS Builder V1.2.99 (19.02.2011)
1. Fixed package description window size (5 lines, 120 pxl)
2. Built-in HTC Splash Tool added - you can create Primary и Secondary boot Splash WVGA (480x800) in NB or NBH format. You can also extract image from NB splash. See Menu Tools -> Built-In.
3. Built-in HTC NBH Builder Tool added
– allows to create NBH file from NB files. You can import NBH header parameters from settings, registry or NBH file. Files and code sections are added and deleted using the context menu.
Sections, which should be included to NBH must be toggled in checkboxes. You also can save your settings in a separate file. See the menu Tools -> Built-In.
4. For HTC-LEO - in case when the date and time sync failed on first start - date and time of the ROM creation will be added.
5. Several improvements in assembly and merge dsm algorithm
6. Fixed a problem with new versions of Yandex-maps
7.The option RomConfirmOverwrite has been added to the section [OSBuilder] of configuration file. If the parameter = False, then the assembly of the ROM process does not display “Over-write?” dialogue (the file is automatically overwritten). By default, this option is True
8. Built-In Personal data generator tool is added
– see Additional Tools - Personalize. You can pre-enter owner name, Wi-Fi settings, mailboxes, VPN connections and favorites.
You can add, delete and change personal data by using the context menu.
Favorite links found in OEM provxml files are added automatically to the top list. Toggle correspondent checkbox if you want them to be added to Favorites. You can add your custom Favorites in the bottom list via context menu.
Personal data is stores in the root of OEM folder in the file Personal.dat. You can save it in menu File->Save to OEM.
To integrate your personal data to your custom rom you should go to Configuration Menu->Advanced Settings->Write Personal Data (toggle checkbox)
Full version:
9. Added the possibility to save personal data (paragraph 8) in a readable xml (provxml) file.
Keep in mind that not all data can be imported during provxml runtime.
P.S. Sorry for Russian screenshots
Click to expand...
Click to collapse
hello
Thanks again brainmaster for ur kitchen.i am going to make a rom with this kitchen.
hello
i got some erorr while making a rom with this kitchen.it showing erorr with default.hv and user. hv.please give me an advice what to do.
Getting a error by building a ROM with my settings, or have you added some of your packages?
Before building a ROM always use these two options from the additional tools menu: "Registry preview" and "Initflashfiles.dat preview". If there is something wrong with your packages - these options gonna show you which package it is.
If you do this every time before cooking ROM, you are gonna save some time.
brainmaster said:
Getting a error by building a ROM with my settings, or have you added some of your packages?
Before building a ROM always use these two options from the additional tools menu: "Registry preview" and "Initflashfiles.dat preview". If there is something wrong with your packages - these options gonna show you which package it is.
If you do this every time before cooking ROM, you are gonna save some time.
Click to expand...
Click to collapse
i did not added any pakages.got error from your settings.
ok. i will try again with your instruction.thank you for ur support.
hello
i have some problem with cht2.0.i could not modyfy the widget. any solutions?
CHT 2.0 is not part of my kitchen. You have to ask in the CHT 2.0 Thread.

[PC] DevHealthAnalyzer v2.0 and rpack

I've decided to post these tools here.
rpack - not a ResourcePacker, but the tool that can be used to remove useless sections from resource-only libraries making more memory available for applications.
Usage:
Make a backup of your kitchen
Drag&Drop your *.mui files to rpack.exe. Their size will be reduced.
Make sure you didn't kill USEFUL libraries.
Original thread
DevHealthAnalyzer - memory analysis utility. Can be used to determine the most memory-eating libraries. Then you can reversmod them (yes, reversmodded libraries reserve less ram than recmodded ones) or make r/w sections shared.
Screenshot:
{
"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"
}
From my experience - it looks like the most popular ROMs have the worst memory management
Original thread
v2.0 (15.05.11):
changed output file format (although, old files still can be opened)
more info
better UI
Download DevHealthAnalyzer v2.0
Great work ultrashot. The DevHealthAnalyzer looks nice. Is the DevHealth that is run on device the on from this thread?
mwalt2 said:
Great work ultrashot. The DevHealthAnalyzer looks nice. Is the DevHealth that is run on device the on from this thread?
Click to expand...
Click to collapse
Yes, it is totally the same. Thanks for pointing - I forgot to attach it to the first post.
Also, what is the significance of the blue, green, and white cells in the output? Does the exe column just show what the dll is tied to? I know next to nothing about this stuff , but it does look like there are some files loaded in slot0 that I should reversemod.
mwalt2 said:
Also, what is the significance of the blue, green, and white cells in the output? Does the exe column just show what the dll is tied to? I know next to nothing about this stuff , but it does look like there are some files loaded in slot0 that I should reversemod.
Click to expand...
Click to collapse
Blue means NULL - unused or reserved areas.
Green means that this memory block is from DumpMap.txt
White cell - from DevHealth log.
EXE column shows exes that use this library at the moment.
Main purpose of this app is that it lets you find which recmodded libraries waste 64 KBs of you slot 0 while they really need less RAM.
Thank you for sharing Ultrashot.
If I understand right I need to run Devhealth on the device but when I do I get a Netcf error.
I'm running Netcf version 3.5.9085.00
Laurentius26 said:
Thank you for sharing Ultrashot.
If I understand right I need to run Devhealth on the device but when I do I get a Netcf error.
I'm running Netcf version 3.5.9085.00
Click to expand...
Click to collapse
You should run devhealth.exe, not devhealthanalyzer.exe
Oh yeeh I didn't realise there where two exe, that's it, thanks again.
ultrashot said:
You should run devhealth.exe, not devhealthanalyzer.exe
Click to expand...
Click to collapse
Laurentius26 said:
Oh yeeh I didn't realise there where two exe, that's it, thanks again.
Click to expand...
Click to collapse
DevHealth is to dump memory map from the device and DevHealthAnalyzer is to Analyze the dumped data on pc.
Copy the text data from mem_X.txt into DevHealthAnalyzer.
@ultrashot; Thanks for the tool. Its very essential.
BTW; is it possible to analyze other slots also? i.e slot1, slot2, slot3 and etc ?
I know Dumpmem has this feature but its slight buggy or like, when used in newer OS cores since it was developed very long time ago for WM2002. Not sure how well it works on newer OS cores.
I guess DevHealth also provides data about other slots but it would be great to see in GUI tools like DevHealthAnalyzer.
Just a query. I'm not that expert in memory maps either.
Thanks...
Best Regards
CRACING said:
DevHealth is to dump memory map from the device and DevHealthAnalyzer is to Analyze the dumped data on pc.
Copy the text data from mem_X.txt into DevHealthAnalyzer.
@ultrashot; Thanks for the tool. Its very essential.
BTW; is it possible to analyze other slots also? i.e slot1, slot2, slot3 and etc ?
I know Dumpmem has this feature but its slight buggy or like, when used in newer OS cores since it was developed very long time ago for WM2002. Not sure how well it works on newer OS cores.
I guess DevHealth also provides data about other slots but it would be great to see in GUI tools like DevHealthAnalyzer.
Just a query. I'm not that expert in memory maps either.
Thanks...
Best Regards
Click to expand...
Click to collapse
In fact, DHA makes maps of all slots because there is no info about slot 0. Then it merges them.
If you create a map you can take a look at info about other processes, but I don't save it in a *.slotmap file as all other slots aren't so interesting.
ultrashot said:
In fact, DHA makes maps of all slots because there is no info about slot 0. Then it merges them.
If you create a map you can take a look at info about other processes, but I don't save it in a *.slotmap file as all other slots aren't so interesting.
Click to expand...
Click to collapse
Yeah you are right.
Edit: BTW; I have too much null spaces and by seeing the posts in asusmobile.ru, AndrewSh said they are memory holes.
Should we correct it and remove those memory holes?
If so please let me know how? sorry for my noob queries!
Just an hour back, I have reversmode'ed few dlls on HTC packages and saved space in Slot0. About 1.3 MB. MAX Amount 24736 KB.
Thanks...
Best Regards
CRACING, while ultrashot is offline for now - I will try to answer
These NULLS normally happen if the library was a file (not module) while cooking and it's loaded without fixed address to slot 0. Try to reversmode all dlls that have NULL space reserved and cook again. Than - make test and you will see that almost all NULLs are gone...
I wanna warn - do not try to reversmode rsaenh.dll - leave it as is. Otherwise you will get unbootable rom.
Normally I have 27484 kb free for Leo at the moment
BTW, if you browse through asusmobile.ru topics - you are welcome to post there your requests and comments in English - we appreciate that
Yeah, I learned about rsaenh.dll the hard way! Took a while to trace it back to that one, that taught me to take baby steps.
I think if you put rsaenh.dll on the do not split list (or do not relocate list, with the proper addresses already set), it may be ok. Or, comment out the 'loadmodulelow' value in your boot.rgu, and it may work as a module. I'll let you try it, though, lol. (Maybe on a rainy day I'll see if I can get it to work for the hell of it.)
AndrewSh said:
CRACING, while ultrashot is offline for now - I will try to answer
These NULLS normally happen if the library was a file (not module) while cooking and it's loaded without fixed address to slot 0. Try to reversmode all dlls that have NULL space reserved and cook again. Than - make test and you will see that almost all NULLs are gone...
I wanna warn - do not try to reversmode rsaenh.dll - leave it as is. Otherwise you will get unbootable rom.
Normally I have 27484 kb free for Leo at the moment
BTW, if you browse through asusmobile.ru topics - you are welcome to post there your requests and comments in English - we appreciate that
Click to expand...
Click to collapse
Hello,
Thanks for your reply.
I though its NULL reserved space for files but NULL space is also below modules. i.e mdpl, htcdevservice, htcgeosrvc and many modules.
Thats why I have confused.
Is it because the modules aren't reloc correctly or those are reserved for the modules which aren't loaded? I'm using OSKitchen to build ROMs.
However, I have attached my last memory map dump. From 1828000 to 18BF000 are files. i.e conncurrencemgr.dll, ntfconfig.dll, notificationmanager.dll, voammbenc.dll, lap_pw.dll, pimdlg.dll and rsaenh.dll
Please have a look...
Thanks...
Best Regards
CRACING, hi!
You can force some of your dlls not to be loaded to slot 0 to release space. That can be performed by sharing r/w sections of modules and files.
I think ultrashot will explain here in the topic how to make that. I don't want to do that because it's his research and his brilliant idea. Besides - he's a real professional and he will do it much better than me.
Anyway - almost all HTC services can be processed to share r/w sections. And thus they will never be dropped to slot 0 on boot.
As I can see from your map - 80 % of your files and modules with NULL can be shared.
We will wait for topicstarter's post concerning the matter. If he does not - I will try to describe how to do that.....
But this process it quite dangerous - you should backup your kitchen before sharing r/w.
AndrewSh said:
CRACING, hi!
You can force some of your dlls not to be loaded to slot 0 to release space. That can be performed by sharing r/w sections of modules and files.
I think ultrashot will explain here in the topic how to make that. I don't want to do that because it's his research and his brilliant idea. Besides - he's a real professional and he will do it much better than me.
Anyway - almost all HTC services can be processed to share r/w sections. And thus they will never be dropped to slot 0 on boot.
As I can see from your map - 80 % of your files and modules with NULL can be shared.
We will wait for topicstarter's post concerning the matter. If he does not - I will try to describe how to do that.....
But this process it quite dangerous - you should backup your kitchen before sharing r/w.
Click to expand...
Click to collapse
That would be awesome. Looking forward...
Thanks a lot...
Best Regards
Meanwhile – the translation of original ultrashot’s explanation at asusmobile:
How to share r/w section:
1. For the file: using LordPE program set flag Shareable on r/w section (C0000040->D0000040)
2. For the module: edit imageinfo.bin – change 402000C0 for 402000D0
All files and modules should be backuped!!! Every modified file/module should be tested separately.
Additional explanation from Barin
For module and file – it’s necessary to change RW section flags (set up additional flag IMAGE_SCN_MEM_SHARED = 0х10000000)
Example: RW section has flags C0002040
It’s necessary to add flag 0х10000000
0xC0002040 OR 0x10000000 = 0xD0002040
How to modify imageinfo.bin from 402000C0 to 402000D0: Calculate the offset to the appropriate flag o32_rom and then edit with any HEX-editor
Module o32_rom structures start at 0х70 address in imageinfo.bin consistently
The structure of o32_rom:
DWORD o32_vsize
DWORD o32_rva
DWORD o32_psize
DWORD o32_dataptr
DWORD o32_realaddr
DWORD o32_flags
That means - the address of the flags of any section will be equal to 0x70 + (0x18 * <section number>) + 0x14
Sections are numbered from zero.
AndrewSh said:
2. For the module: edit imageinfo.bin – change 402000C0 for 402000D0
All files and modules should be backuped!!! Every modified file/module should be tested separately.
Click to expand...
Click to collapse
How to do this?
I checked in IDA and HexEdit. No such things.
AndrewSh said:
Click to expand...
Click to collapse
And could tell me which is this tool?
May be I saw but couldn't remember.
Sorry for noob queries.
Thanks a lot...
Best Regards
CRACING said:
How to do this? I checked in IDA and HexEdit. No such things.
Click to expand...
Click to collapse
I use WinHex - and normally you should look for 402000C0 Hex Value - modify if exists See attached image.
CRACING said:
And could tell me which is this tool?
Click to expand...
Click to collapse
OsBuilder (BTW - the full version allows to share r/w sections of modules and files "on the fly" without modifying original ones and without hex calculators and other sophisticated ****)

Categories

Resources