yashsingh1/xdaforums huggingface dataset:
[Windows Mobile] AndrewSh:
Relax - it's quite OK if you checked to delete DSM. Continue building rom.

Sure it is! But **** - I'm still having my good time celebrating St. Patrick (2 days pissed :) )...

Gimme a couple of days - I will translate it - I know that I'm in charge of translating - but for now it's a problem for me :) I am drinking wine and listening to the music :)
[Windows Mobile] HD2Owner:
changelog of V1.2.107 LE updated
[Windows Mobile] Nixeus:
thanks a lot :)
[Windows Mobile] Nixeus:
How can we get the full version?

Thanks a lot,

regards,
[Windows Mobile] AndrewSh:
You should either be a member of Russian mafia :) (kidding) or write PM to Barin... But your plural "we" sounds not good... Full version is an individual stuff with owner name at startup. No "we" is allowed!
[Windows Mobile] Nixeus:
SO, how can i get this full kitchen :D ?

* Will be it possible to having explanations ( screenschots) in order to make a fast rom with the XIP options :

Do not move Ramsart...

Remove GAP

Compile HV...

What are the best settings please ?

Thanks a lot again for this great kitchen tool :)
[Windows Mobile] Farmer Ted:
You want the uncheck the 'don't move ramstart' in order to build a new xip. Otherwise, the size size will probably be wrong, and you'll either run out of space or waste space.
[Windows Mobile] Nixeus:
Thanks a lot, but what about the other settings for XIP ?

Compile boot.hv

Squeeze nk RW sections in RAM

Strip reloc. sections

Remove dll gap in slot0

Use direct adress for nk.exe

Thanks a lot because i would like to optimize at the maximum my rom for my HTC LEO :)
[Windows Mobile] AndrewSh:
Question:

Answer:

What exactly is not clear to you in my words? Abbreviation PM means personal message. The rest should be quite understandable.

Screenshot from my kitchen for Leo - attached
[Windows Mobile] Farmer Ted:
You need to compile the boot.hv if you tweak your boot.rgu; if you just use the stock one, then you can leave it, i guess. I would check to compile it.

I would try the 'squeeze nk' sections; it saves a nano-fart of RAM if it works, I believe.

Strip .reloc if you want a protected rom; personally, I cook unprotected ones, as I just cook for myself. It's a good way to backup your kitchen. In theory, it may speed things up a tiny bit if you strip the reloc sections, but I've never noticed anything. We're definitely talking nano-farts here. It will save a small amount of storage space.

Check 'remove dll gap'; again, you'll probably save a nano-fart of RAM or virtual memory. Compare dump maps or xip maps with and without the option checked to see the whopping difference.

Only Barin knows what 'use direct address search' means. AndrewSh tried to explain it to me once, and he clearly didn't know what the hell it did, either (lol). Maybe he knows now. I believe it may have something to do with cert checking when dll's or exe's are loaded, at least that is what I got from AndrewSh's explanation. I don't have that option selected (never tried it, though).

Edit: my settings are pretty much the same as AndrewSh's, except for the .reloc option and I compile the boot.hv from the ROM\oemxip\boot.rgu.
[Windows Mobile] AndrewSh:
I use edited boot.rgu (not original) - so it's the same thing :)
[Windows Mobile] HD2Owner:
just to show you the performance of osbuilder:

before i was cooking on a smaller machine (e8600 3.33ghz, 4gb ram, slow hdd).

the rom cooking progress took around 1min 13s.

now i switched my kitchen to my gaming rig (ci7 920 oc 3.4ghz, 6gb ram, 10'000rpm velociraptor hdd)

the rom cooking progress takes around 22s now!!!

attached screenshot to confirm. rom cooking never was that fast.... :D
[Windows Mobile] ai6908:
Yea I agree that OSB cooks real fast!:)
[Windows Mobile] prabhat:
I am New to OS Builder - First Time Attempting for WinMo 6.1 Standard Build

Hello friends,

I working with OS Builder today for doing a WinMo 6.1 Standard ROM Build for T-Mob Shadow and I was able to progress a little with issues.

Below is what I did:

- Dump Tool: Imported the .nbh file (Stock 6.0 rom)

- Dump Tool: After import -> Clicked on Create Packages.

- Changed the Mode = OS Builder

- It opened the Dumped folder

- I dont know what to do next...

- But I clicked on "green go>" button to "Start"

It gave below error during creating dump - initflashfiles.dat

Error: Unhendeled Exception. The given key was not present in the dictionary.

And kitchen closed :(

Can you please help me to do this build using OS Kitchen.

I use osKitchen but never used OS Builder yet so need some initial help.

Thanks.
[Windows Mobile] Nixeus:
Hello my friends,

I'm sorry for this question, bu i have read a lot, but i have difficulties to understand some thing about Slot0 and module.

If i have a device with a WM6.5 kernel, it's better to do a lot of module instead of a lot o file ? --> it's true no ?

But, when i reversmod file in order to converti it to module, i can see my freespace in slot 0 decreasing....and i have read thaht we need to free the SLOT 0 as maximum as possible...So.....how create a lot of module whitout having a lot f freespace in the slot0 ?

I'm think that many people thaht use osbuilder and other kitchen has missunderstood this point, it will be very very good to explain how create module in order to create a good, and fast rom :)

Thanks a lot, and a lot for all people :=)

regards,

Nixeus
[Windows Mobile] tobbbie:
You must take care about your "OS Version". For older devices that have no native 6.5 Kernel (nk.exe) the memory management stays as it is (since WM5 basically). So even if the GUI parts are all "WM 6.5" the kernel stays as it ever was. Nothing to gain from from more memory slots for modules here (see my introduction for cooking -> signature).

OSBuilder should tell you about the Kernel version - and it should be 6.0/6.1 if you cook for the Elf. OSBuilder only tells apart the older and the new WM6.5 slot allocation scheme (which is perfectly ok for that purpose).
[Windows Mobile] Nixeus:
But i cook now for HD2 ;-) So, how deals with modules ?
[Windows Mobile] Nixeus:
I have a big problem since yesterday....

When i reboot my phone, it stuck after the animated.gif...

No problem for the first boot, the phone is OK, but after a reboot, stuck at the animated !

I need to do an hard reset in order to use my phone:(

I don't know what is the problem because i don't have made any changes on my SYS/OEM/XIP :( and i didn't have problem before.

Thanks a lot if anyone have an idea,

regards,

Nixeus
[Windows Mobile] ultrashot:
For native 6.5 kernel the only good way is to make as many modules as possible (though, don't overload your rom with them).

If you don't reversmod, then:

1) OSBuilder will show much more space in slot 0

2) Libraries will be loaded on 64KB boundary and real amount of free virtual memory will be much less than after reversmodding.

Use my DevHealthAnalyzer to get real info about slot 0.
[Windows Mobile] SuperSport:
I've tried to build the kitchen for your device too. I get the same Exception error as you. Maybe this is the same problem that osKitchen was having? I wonder if you can ask people in your device thread that have successfully cooked ROMs what they have done to get it working. Once you know that, maybe you can use either kitchen to get it cooking.
[Windows Mobile] prabhat:
Hi SuperSport, I think you are true.

Actually I asked most of all chefs in the Shadow rom threads, but no reply yet :(.

Any how I will try to short the issues :) It will take some time.

Thanks for all your advise and help.

Thanks.
[Windows Mobile] Spiaatie:
Just move initflashfiles.dat from XIP\LangDB to OEM\OEM_Lang_0409 - that's it.

:)
[Windows Mobile] Farmer Ted:
Don't recmod anything. There will always be some commitment by dll's into slot 0; this is the read/write section, and most modules have this section. If you look in the memory map, the read-write sections of the modules are loaded into the High section. It's normal, don't worry about it. What you don't want to see is modules loading into the Low section of slot 0. It's very unlikely you'll see this, as long as you select the 'split L modules' option in the xip settings.

Recmodding modules to files is worse for slot 0 than leaving them as modules. Don't do it.

Does it get loaded in xip sometimes? That's weird. If that isn't the issue, then I'd recommend making sure that it's in unicode (not ANSI) and that it has a blank line at the end.
[Windows Mobile] prabhat:
Hey mate, thanks for the tip. YES that worked. I moved the file and kitchen can now Compile/build without any issues :).

Thanks a lot for input.

So after the build I can see \Temp\RUU_signed.nbh file is generated.

Now I want to port 6.1 STANDARD SYS and XIP into this Build. So SYS was good but when porting XIP I get below error:

Extracting XIP packages...Ok

Extracting XIP packages from DONOR\xip.bin...

Donor not found D:\ROMKitchen\Source ROM\Shadow OS Kitchen\Dump\Donor\xip.bin

Here is what I Did:

So I used the Dump Tool - Create Packages to generate the DUMP of 6.1 OS.

And Copied the "SYS" and "XIP" folder from the above dump into my kitchen \Donor\SYS and \Donor\XIP folder.

1) Now I clicked on the Setting Icon and "Port SYS" -> Selected above \Donor\SYS folder and it shown the merge dialog and all good.

2) Now I clicked Setting Icon and "Port XIP" and get the above error :(.

When I did a folder/file search for xip.bin, I could not find that as well :(

Also the XIP (ROM\xip.bin) [just below the Template of settings icon] is also disabled :(

Any input here?
[Windows Mobile] mwalt2:
I think you just need to change the setting so XIP is ported from packages and not xip.bin.

See the screenshot posted earlier:

http://xdaforums.com/attachment.php?attachmentid=548180&d=1300736434

Also, under Build Dump and ROM in Settings, choose Ported/Rebuilt XIP for While assembling use XIP (you probably already have it like that, but I'd just make sure).
[Windows Mobile] Nixeus:
Thanks a lot about your answers about modules and slot0.

Any idea please for my quotted problem?

Thanks a lot :)
[Windows Mobile] prabhat:
Hi mate, Thanks for your input. Yes that solved the issue and Now I am able to port XIP and build the ROM as well.

So I did the 2 changes suggested by you:

1) Selected XIP from Package

2) Selected Ported/Rebuilt XIP.

One more small question:

If I click on first icon on toolbar and click on "Advanced Settings" I can see the ROM Version and Page Pool Size settings. But where is the "ROM Date" like I have in osKitchen ?

Thanks.
[Windows Mobile] + Que PPC:
Hey guys im new in Osbuilder i already set the basic packages OEM ROM & XIP everything is ok but this is weird HTC TyTN or Hermes already has a 6.5 kernel but the kitchen sas it is 6.1... even tho, 6.1 wasnt developed for hermes it is a hidden secret from Da_G in that ancient times, patched to work as 6.5 thekitchen says this

Detecting kernel type... WM6.1

Rebasing modules (WM6.1 kernel)...Ok - Slot 0: 3072 Kb free (00060000-00360000)

Merging DSM...Ok

any idea bout this cause i want to recmod my modules into slot 60 and 61

thansk for the amazing kitchen

Edit: My bad.... i already found the answer in post 84 page 9 by pituzzzooo or wahtever thanks to madmatt or something like that lets now migrate all my EX to OEM :s heavy task :s

just a question.... how can i enable the Page pool option in rom build process, it shows the field unabled
[Windows Mobile] Farmer Ted:
If you drop your packages into os kitchen and do a quick build, it will generate dsm's for you (assuming you don't have them). You're on your own for the rest of the conversion, lol.

PP is in the config menu, in one of the options. Good luck w/ this, once you're set up, you'll love it.
[Windows Mobile] ultrashot:
Little tool I've made when was converting ext packages to oem a while ago - ext2oem. Make a backup of all your packages, also use this tool in separated folder.

Enjoy.

p.s. test app on testpackagesgroup first to understand how it works.
[Windows Mobile] + Que PPC:
Ok lets try ;)

Thanks Farmer ted, yeah seems to be amzingly FAST!!!!!! :eek: dear god! i went to heat some milk at microwave, put some cofee and sugar i return and **** it was finished the cooking in 4 minutes :o hopefully it can handle the PP ok cause i need to set it to 4 not dynamic you know Hermes is a tiny device.

will search for that option, and reading all the thread, i can see that many ppl is lost cause the kitchen has many options checkboxes drop menus and so on :p constant questions about where is this and that are all over the thread ;)
[Windows Mobile] Farmer Ted:
When in doubt, check the box. Ignore the warnings, lol. I think I have them all checked now. The 'direct address search for nk.exe' works fine for me. Just make sure you port the xip properly; if you don't, it will surely mess things up. For a while, I had bastardized builds with 236xx/282xx sys/xip combos. And get the rom.tpl correct, too. It's harder when you don't have a stock 6.5 rom to dump.

Yeah, it cooks in about 2 min for me.
[Windows Mobile] + Que PPC:
so xtrange... i cant make it works, the app made by ultrashot i mean, :p it makes OEM pkgs of the Files folder and the lang of the ext pkg separated :p

i guess it is due to not have a dsm for each ext pkg.

the one posted in underground works ok i guess i will mess a little more with this cause it seems to be faster.

one thing is true... its weird how OEM pkgs cant handle multilang... guessin with the results, i need to separate the f**kn pkgs 0c0a and 0409... god

and this is a real mess :p

Root:-Directory("files")

Directory("\files"):-File("Camera.exe","\windows\Camera.exe")

Directory("\files"):-File("Camera.exe.0409.mui","\windows\Camera.exe.0409.mui")

Directory("\files"):-File("camera.htm","\windows\camera.htm")

Directory("\files"):-File("Camera.lnk","\windows\Camera.lnk")
[Windows Mobile] ultrashot:
Emm, what do you want then? That's much more correct to make a separated folder for every lang! Especially if you deal with multilang roms.
[Windows Mobile] Nixeus:
Hello my friends,

Anyone could make and post a screenshot in the settings ->Build Dump and Rom, in order to having the better settings please ?

Thanks a lot :)

regards,

Nixeus
[Windows Mobile] AndrewSh:
For example.... :)
[Windows Mobile] HD2Owner:
i just wanted to post my screenshot... :D
[Windows Mobile] -=Barin=-:
Don't use this option if you have stock nk, because it's too risky.

This option can help only if You have nk patched by someone and .reloc section doesn't have enough info about absolute addresses in patch commands. In this case You can use direct (agressive) search for nk.
[Windows Mobile] Farmer Ted:
I'm using one that's got the cmonex cert check removal patch. Is that the sort of nk to use it with? Everything is good after 4-5 days, although I can't tell much difference in behavior, to be honest.
[Windows Mobile] + Que PPC:
mmmm interesting

BTW I was playing again with the kitchen, it seems that the kitchen recognize the 6.5 nk but when its relocating it only made it as 6.1 kernel look the pics.

and i have non .hv correctly made due to my OEM new pkgs :p i guess im doing it wrong :p
[Windows Mobile] dany547:
hmm

this will work for a QVGA device ,htc tytn 2? or just for new devices?
[Windows Mobile] Nixeus:
Hello my friends,

I have made a lot of modules on my OEM packages.

I cook for a LEO ( so, native wm6.5 kernel).

OsBuilder tell me thaht i have 8000kb free in sltot0.

My rom have some problems :

* Windows Live Messenger can't connect ( no error message, but loop)

* Opera cannot launching ( no error message)

* When i reboot my phone, sometimes it boot whitout problem, sometimes it stuck at the animated.gif or at the welcomhead.png

WindowsLiveMessenger and Opera aren't module , but file !

Abd for my reboot problems...no idea:(

Is there a tweak in osBuilder in order to solve it ?

Before converting a lot of file to module, i didn't have this problem.

Thanks a lot,

regards,

Nixeus
[Windows Mobile] ultrashot:
Nothing more to say. I've told you to keep balance. 26 MBs is okay but your value is too low.
[Windows Mobile] Nixeus:
Thanks UltraShhot :)

So, it's better to make a lot of modules....but not less that 26 000kb for the leo ?

Thanks :)
[Windows Mobile] Farmer Ted:
I suspect you need to split L modules. That's your problem. And don't even bother flashing a rom w/ only 8 M free in slot 0. Having a lot of modules isn't the problem, unless you somehow managed to overload slot 60, which I really, really doubt.
[Windows Mobile] ultrashot:
That's a good balance between performance and stability.

With AndrewSh we achieved >27 MBs on our full-featured Leo-based roms. His device is Leo, mine is X1. That's if we check it using DevHealthAnalyzer. OSB shows just a little bit more space.

but you can't check real amount before flashing, though it is another story.

when I answered Nixeus I considered he followed the settings posted by AndrewSh (http://xdaforums.com/showpost.php?p=13006379&postcount=236)
[Windows Mobile] Nixeus:
I will try this evening with the Split L module options....

I don't remove the ULDR or replace with empty. I leave it.

Is there a wteak with the DSM correction for the L module ? Is it useful in my case ?

Thanks
[Windows Mobile] Farmer Ted:
Post up your dump map; I'm sure you probably have 100 or so Low modules, which is bad. Ideally, you don't want any. Also, check to make sure slot 60 isn't filled. This is really unlikely, though. The other thing to check in the dump map is that there aren't any overlapping modules (you'll see '!!!!'s if there are).

You want the start of the dump map to look something like this:

01A20000 ------------------ START: Slot 0 IMGFS Low
01A20000 ------------------ END: Slot 0 IMGFS Low

01A20000 ------------------ START: Slot 0 IMGFS High
01A20000-01A2D000 L0000D000 NUL
01A2D000-01A2E000 L00001000 ramdiski.dll
01A2E000-01A2F000 L00001000 ramdiskb.dll
01A2F000-01A30000 L00001000 PDC.dll
01A30000-01A31000 L00001000 PDAStatusPlugin.dll
01A31000-01A32000 L00001000 zlibce.dll
01A32000-01A33000 L00001000 fbservice.dll
01A33000-01A3D000 L0000A000 WeatherToGo.dll
01A3D000-01A3E000 L00001000 TcmObex5.dll
01A3E000-01A3F000 L00001000 TcmObex3.dll
01A3F000-01A40000 L00001000 registry.tfx
01A40000-01A41000 L00001000 TodayNotes.dll

There shouldn't be anything in the Low section, or if there is, just a few modules. If you don't split L modules, you'll get around 50 or so just from the Sys section of your build. I think I had a total of maybe 80 without that option selected, and only around 16 MB free in slot 0 (I never flashed those, though, lol).

I guess the other kitchens must automatically split the L modules, because I never had the issue with EVK or OSK (which I just played around with). I wonder if that is the reason that you don't get bootable roms without doing some recmodding with the newer HTC builds with those kitchens.
[Windows Mobile] Farmer Ted:
Huh, I'm not sure what's going on there. When I do the dsm auto-correction, I also do it for all dsm's (in rom and sys), and I do the sync the dsm flags with the module flags (and check the two sub-boxes for L flags).

I'm sure you can split all those modules (especially the mui's). You don't have anything on the 'Slot 0 Modules list' do you? And make sure you have the 'built-in engine to rebase modules list' option in the 'build dump and rom' tab selected. I've got 67 dll's with L flags or the Vbase in slot 0, but splitting them puts them all in the other slots without any issues. Many are the same as yours.
[Windows Mobile] Nixeus:
* I have made a dsm autocorrection with the params you said to me.

* 'Slot 0 Modules list' is empty

* 'built-in engine to rebase modules list' is checked

I have always the same result :(
[Windows Mobile] ultrashot:
Do you have .VM and .ROM folders somewhere? Try to delete them.

Then attach a full dumpmap.txt, *.osb and *.xml config.
[Windows Mobile] Nixeus:
Yes my friend, i Have my .ROM and .VM folder, i will delete the and relaunch my build.

Thanks a lot for your helps :)
[Windows Mobile] Nixeus:
There is no changes if i delete my .ROM and .VM folder.

Here is my full dumpmap.txt and my *.osb file. I don't have a XML file :

http://www.multiupload.com/JN68MDW8EZ

Thanks :)
[Windows Mobile] ultrashot:
try packages.cif-based reloc
[Windows Mobile] -=Barin=-:
Hey Nixeus, it seems that you've reversmodded to much files! How much entries do you have in reversmod list? Why do you convert mui to modules? It's quite enough to remove code sections from them and then keep as files.

2 Utrashot, Andrew

Во всём нужны ум да бережь, а то сядешь срать, и член обсеришь :)

Согласны? ;)
[Windows Mobile] Nixeus:
How doing this please ?
[Windows Mobile] ultrashot:
-=Barin=-, indeed :D

settings->build dump and rom->allocate according packages.cif

http://xdaforums.com/attachment.php?attachmentid=571918&d=1303151790

and listen to Barin.
[Windows Mobile] Nixeus:
Thanks a lot, here is running...

Here is my list :

Uploaded with ImageShack.us

Need i to clear some L flags ? For the OEM, the SYS ? Just the OEM ?

Thanks
[Windows Mobile] Farmer Ted:
Wow, man, Barin's right, you actually managed to fill slot 60 and overload modules into slot 0. That's your problem. Here are some modules that I would think about recmodding, because they have big read/write sections. Or, do the shared read/write thing if you know how to do it.

01CDF000-01D21000 L00042000 HTCMIDI.dll------270,366 bytes

01C77000-01C88000 L00011000 contacts.dll-----69,632

01D36000-01D61000 L0002B000 MDPL.dll-------176,128

01D9C000-01DB0000 L00014000 ResLoader.dll---------81,920

01E2B000-01E41000 L00016000 smd.dll----90,112

01F4D000-01F81000 L00034000 bcmsddhd.dll-----212,992

Those are all pretty big commitments. I don't know what the modules do, but if they don't have to be loaded at startup (meaning they aren't used all the time), then it might be better to use some of them as files. If you add those up, they're eating about 0.9 MB of virtual memory. This doesn't solve the bigger problem, which is that you have too many modules. You probably need to clear up 24 MB or more of virtual memory to remove all the L modules from slot 0 and to also clear up some space in slot 60. You need some free space there just to be able to load files (like for Opera) without crapping up slot 0.

To clear up slots 60/61/1, just look for the modules you created that have really big commitments. The mode9.dll is huge; I don't know if you converted it, or if it came that way. If you converted it to a module, you should probaby revert to a file:

7A9A2000-7AC84000 L002E2000 mode9.dll---3,022,848 bytes

It's eating up ~3 MB of memory in slot 60 alone.

7AC84000-7B0F5000 L00471000 phcanImages.dll

7B0F5000-7B578000 L00483000 phcanImages2.dll

Those are monsters, as well. They're eating 9.5 MB of virtual memory. Just look for the modules that have 3 digits before the -000 at the end, and they're the big ones that you need to re-file. Again, it won't help you any if the files load at startup (like, they're a service.dll or a driver). But if they're just a resource for a program you like to use from time-to-time, then leave them as a file.

Oh, and I salute you for making so many damn modules. :p I've tried like a mutha to fill up slot 60, but I think the most memory I ever used there was 24 MB (which is probably a good place to stop, as you need free space for files).