yashsingh1/xdaforums huggingface dataset:
[Windows Mobile] _Madmatt:
I really like this kitchen! However, I wasn't able to build a ROM with it... Afther this screen:

I get this:

Afther that, I only can cancel the operation.... :(

Someone who knows what the problem is? :)
[Windows Mobile] HD2Owner:
make sure you have enough space left when you build a rom (around 1gb should be sufficient).
[Windows Mobile] _Madmatt:
Also thought that it could be that. But I'm still having 10GB left, so that should be more then enhough? Or not? :eek:

EDIT: It works now! Don't know what exactly did the thing change it's mind :) Another little question. In the NBH settings form, the Radio, RadioCust, PrimarySplash, CONF, UnknownSplash1 and UnknownSplash2 are all unchecked. Does this mean that my Radio is not included in the ROM and I won't be able to make calls? :o
[Windows Mobile] HD2Owner:
no. this means that only os part is being flashed when you flash your custom rom.

radio/splash/spl etc. stay untouched (from previously flashed stock rom).
[Windows Mobile] _Madmatt:
Am I the only one with questions using this kitchen? Anyway, next :p

I yesterday built my first ROM using this one, but when I try to start phone I get a error report (which I can send or not send to MS). Is this a problem with the Radio or is this a missing package? Or something else? :eek:

So, I cannot start my phone and can't get any messages or phone calls....

Because I'm on stock ROM now, I want to fix this ASAP.
[Windows Mobile] Skrobel:
I think you should write which program caused this error. I often had errors from services.exe ("The program services.exe made an exception. blablablala") during startup. But it was only on close-to-stock ROM with 21877 build. When I changed to 21913 it stopped. Soe I guess the cause can be in many different places. I would look among SYS packages first. But can also be any of the programs (but only the ones that start together with the system).

Please write something more (phone model, build no, and what is the basis for your ROM - dump or building from scratch). Is you took a stock ROM dump as the basis I guess you have to modify one thing after another flashing each time and then you will know exactly what caused this error...
[Windows Mobile] _Madmatt:
Okay, I'm sorry that I had not given that info.

The device is a HTC HD Mini, with build 23103. My basis was a dump from a stock ROM (RUU_NLD_1.36.404.1_blablabla.exe). I get the problem when I hit my Talk-button ;) Or when I try to start my phone in CommManager.

But I can't get it, with osKitchen I have not had this problem, and for now I'm only disabling some packages...
[Windows Mobile] Skrobel:
Strange... And when you compile a stock ROM without removing any packages from the dump, do you have the same error?
[Windows Mobile] _Madmatt:
I'll try that tonight! Thanks for the hint, hope it works. But then, what package (that isn't included) should be re-added? I can't imagine it's CoPilot...
[Windows Mobile] HD2Owner:
take a look at the packages.sof/cif tips in post 2.

this problems can be caused by build order of packages.
[Windows Mobile] ZaxXx:
This kitchen looks really good and much easier to use than any other. Unfortunately, I've got a problem with it. I'd like to customize one ROM which I like (only add some more stuff I use and remove what I don't use), so I made a dump from nbh, but when I try to open the dump folder in os builder mode, I get an error: "SYS: Metadata package not found". What do I have to do to be able to customize a complete ROM? BTW it's Blackstone Cloudy 0.4 WM 6.1 + Sense 2.5.

Thanks in advance.
[Windows Mobile] Skrobel:
I'm afraid only stockROMs are fully dumpable. So I guess you have to add XIP/SYS packages manually from downloaded build.
[Windows Mobile] ZaxXx:
Never mind... I have no experiences with building a ROM so I better start with a stock ROM first :) Thanks
[Windows Mobile] HD2Owner:
this kitchen is showing you the problem. that's one of many benefits. ;)

import metadata package from the same build you want to cook in.

then edit/reorder packages.sof/cif with built in editors.

if you don't have cooking experience, you better start off with a stock rom.

this kitchen doesn't make you a experienced chef. you have to learn with it and gain experience.

the best practice for me was to build hybrid roms for the x1i with packets from hd2 (was not released yet at the given time).

i saw so many errors myself and flashed my devices hundreds of times.

i like to share my experiences with everyone. feel free to ask if you have any questions.

but remember:

if you have problems, they are caused by your work in the kitchen and not the kitchen itself.

don't blame the kitchen for errors first. my rom is working very well (many others are successfully using it too).

btw:

when i ported my evk/prb based kitchen to osbuilder structure, osbuilder was showing me dozens of problems that i had to fix (evk showed no problems at all).

it's always better to know the problems and to fix them. i don't really like the fact that they where simply ignored by prb-based kitchens.
[Windows Mobile] Skrobel:
You're damn right!

In case of Rhodium the 2.07 European stock ROM was the worst that I ever had on my device. But it was enough to dump it with OSBuilder and rebuild without any changes and the ROM was better already (by means of memory management)!

Then I started to play with XIP optimization (I read whole thread of manual XIP porting but I'm not really a computer guy so I couldn't understand everything) and I was surprised with the XIP porting tool. No more memory region calculation when you want to remove a file/package from XIP! It's just enough to uncheck it from the XIP tab in Settings, and click "Port XIP" and the tool will assemble the XIP for you!

My good friend Jackos says you should always have control on the memory allocation. But before I can learn everything about it, I can use a good OSBuilder.

The Registry tool is awesome. When it detects error, it indicates in which file the error is, and what kind of error and even the line number. So if anybody of you have problems with registry compili (building .hv files), please go to Additional Tools -> registy preview! This tool will show you what is the problem.

Additionally for every value it also shows which files in which packages changed this value. So if you ever cook your reg tweak which doesn't seem to work after you flash a ROM, go to Registry preview, navigate to the tweaked value, and you will see which package overwrites your changes!

BTW. I think the kitchen installer have errors. I wanted to install the kitchen on my laptop and I already had .NET Framework 4 installed, but the installer hasn't detected it and required to install .NET v3.5, so I had to install .NET v3.5, install the OSBuilder, and then install .NET v4. Could you guys confirm or deny?
[Windows Mobile] _Madmatt:
Another question ;) How can I change the place where files are being copied to? Because now my Start Menu is a mess and I want to get some .lnk files into folders that are created in initflash.

In osKitchen I have a app.dat file for each package that I can modify very easy, but I can't seem to find them here... :(
[Windows Mobile] ultrashot:
_Madmatt, initflashfiles.txt in OEM package = app.dat in EXT package. Is that what you wanted to know? Or I misunderstood your question?
[Windows Mobile] _Madmatt:
I think you misunderstood. I can find the initflashfiles.dat file, but in OsKitchen, there are app.dat files foreach EXT package you have. So, let's say Office for example. In the Office's app.dat I can see every file that will be copied to let Office work. For example, it will copy the .lnk file to \Windows\Start Menu\Office\.

That's fine automatically, but ActiveSync for example, is just in \Windows\Start Menu and I want it to be in \Windows\Start Menu\Extras. In osKitchen it was just a matter of editing one single line... Now I can't find that line :o
[Windows Mobile] Skrobel:
Besides of the "central" initflashfiles.dat file from Base_Lang package there are individual initflashfiles.txt in every OEM package which is an equivalent of the app.dat from EXT.

EDIT: in attachment I present a sample package of HD2 Proximity Sensor Screen Off... I think it's self-explanatory.
[Windows Mobile] AndrewSh:
HD2Owner, dude - you - killjoy!!! Don't touch my friend Ghost :)
[Windows Mobile] Stephen:
Hey give me a chance. In about two hours I have figured out by my self and reading posts, how to setup and import a rom. Stripped out all the stuff I dont want, mixed two base roms together and port accross all my ext packages from oskitchen to osbuilder.

I thought I was doing quite well. I am going to go and cry in a corner now at my stupidity :)
[Windows Mobile] Farmer Ted:
Yeah, it turned out to be syntax. The " symbols around CacheVMSize were curly instead of straight, and the hive-builder didn't like it. I'm not sure how I got the wrong quote signs in there, lol.
[Windows Mobile] HD2Owner:
@ghostx: i'm sorry for offending you before.. just read and try more before asking..

@all: a nice teaser preview pic
[Windows Mobile] AndrewSh:
You goddamn barber's cat :) Time to kill you..... :)
[Windows Mobile] sh4d0w86:
any word when the next release will be made publicly available?
[Windows Mobile] -=Barin=-:
Stay tuned. We are working on it...
[Windows Mobile] tobbbie:
[Workaround available] Merge Packages - different System behavior

Hi all - I am puzzled to notice that the option "merge packages" creates a build that shows a weird behavior. I have excluded all other options and narrowed it down to this one only - here is what I notice:

Without: GPSID configuration program from Microsoft (a .netCF application), see here allows to select HW ports and stores them in the registry.

With (merge packages): The same program refuses to store any of the selectable HW ports with an error "The selected HW port is invalid".

As the "merge packages" should not change any system behavior due to same sequence handling for putting together the registry and building up packages content I wonder how can I further track this down.

Just to repeat: OSB is 1.3.163 - same build setup for everything, only difference is that one time "merge packages" is selected, the other time not. The MergeDsmLog.txt does not show anything special and the merge of RGU is invisible in the logs anyway.

First I thought: could this be another consequence of deleting something defined in the boot.hv that I reported on October 9.? I could easily work around the previous problem - need to find a way for that one as well.

So I compared the created hives in \temp (boot.hv and in \dump also user.hv + default.hv) from either builds and looked for a difference there, but the only one was (as expected) only in HKLM\System\ObjectStore\RegistryUpdate\ - nothing else.

Any hints what else to check?!

Edit: workaround available here: http://xdaforums.com/showpost.php?p=19044141&postcount=610
[Windows Mobile] pdaimatejam:
Barin and HD2Owner

date

new version?

any word when the next release will be made publicly available?

Thanks
[Windows Mobile] ultrashot:
Guys, please stop asking about new version. It will be published as soon as its done.
[Windows Mobile] HD2Owner:
yes.. please stop asking for it. it's not done yet.

barin and ultrashot did a lot of work and i did a lot of testing. and still do...

i still worked with manual tools to reinsert imgfs and xip lately for example...

next goal is to rebuild nb and nbh with osb before barin wants to publish it.

don't you agree that this stuff has to be really proper before release? ;)

just wait and stay tuned....
[Windows Mobile] Nixeus:
Hello,

I'm sorry for this question, but i need to clarify two options in OsBuilder.

First, this screen : "Cleanup Resources/modules Files"

What is the goal ? What it's the good thing to do ?

And secondly : Find module with vBase in slot 0.....

My question is the same, What is the goal ? What it's the good thing to do ?

I'm sorry if it'sa noob question,but it's important for me.

Thanks a lot for your help :)

best regards,

Nixeus
[Windows Mobile] ultrashot:
Some resource files contain little chunks of useless code. This tool eliminates them (That's implementation of Rpack). It is very useful for slot 0 virtual memory.

basically, there is no serious use of this function. Sometimes it may be useful for investigating bad SYS dumps (which are very rare nowadays)
[Windows Mobile] -=Barin=-:
@All:

OSBuilder V1.3.187 is ready, so i've started a

new topic

, because i want to separate WP7/WM ROM assembling discussions.

The future discussion about WP7 ROM assembling by means of OsBuilder will take place over there

@HD2Owner:

Add the link to the first post, please...
[Windows Mobile] Nixeus:
Thanks a lot for the Answer, and, for the first screen, what is the differences between red ligne and blakc line ?

Need I to clean all the lines ? Or only the red ?

To Barin : Thanks a lot for the new build :) Waiting for the link and the Changelog :)
[Windows Mobile] -=Barin=-:
are you kidding? :)

Link is in the previous post - red letters
[Windows Mobile] Nixeus:
OooO but this new build has no news for WM6.5?
[Windows Mobile] AndrewSh:
Are you kidding? The main news concerning WM6.5.x is that OsBuilder still supports it. And will support... What else do you expect?
[Windows Mobile] Nixeus:
Yes, it support, but i want to tell that, we don't have anymore no news feature in order to optimize our WM6.5 rom.
[Windows Mobile] HD2Owner:
accept the facts and get over it..

what do you expect from a dead os and with everything needed/wanted already in osb.......?

besides wp7 cooking support (please show some respect to barin for all the work he did!!)..

to me it sounds like...: "ONLY wp7 cooking support?? nothing else??"

stop acting so ridiculous on barins great wp7 osb release day and leave us alone with your disrespectful comments..

some guys just can't be happy..... :eek:
[Windows Mobile] AndrewSh:
If you know how much time did it get from Barin to implement both OS support in the kitchen!!!!

I would tell that we all (asusmobile team) bought WP7 devices just to develop WP7.... Sounds like a joke for you? Or maybe you've seen Donate button in our profiles?

We all still have Leo devices in hands. And believe me - I still cook for Leo and find ways to develop WM6.5.x.... Concerning OsBuilder - all done for 6.5.x - the rest is up to you.... 6.5.3 is very flexible OS - you have no limits in development.
[Windows Mobile] tobbbie:
If you think that things can be improved in OSB, then tell what it could be? I find it hard already to understand all the advanced options and to judge what may be useful and what may not in my cases.

There are things that were important in the past or to debug certain effects in the OS handling - probably not delivering true benefit for the average user. Still they are in OSB - more confusing people than enlightening them sometimes.

It may not be so logical to find all options and tools at various places for different purposes - but hey, OSB has grown over time and it has obligations regarding BW compatilibity, also including the UI. So to not confuse those that have learned to live with what is where it stays as is - I got used to it as well :-)

Mind that the tool just gives you things at hand - you must understand them first and then build your ROM the way you want it. OSB is very powerful for all these tasks (in the kitchen) but it will not make a delicious ROM - this is what the cook has to do.
[Windows Mobile] Jackos:
Relax and let him be. He didn't show any disrespect. Damn, again a bunny fight? :mad:
[Windows Mobile] tobbbie:
OK, so can we keep this thread for anything dealing with WM5 -> WM6.5 and WP7 is in Barin's thread?

Hardly anyone will cook for WM5, but my nk.exe is from that level and I will continue to deal with that until WP7 will meet my desk. I think I am the only one dealing with such old stuff still and I got used to either being ignored or flamed sometime - but no offense taken :-)

If there is anyone out there still cooking for WM5/6 and just for smartphone (so no touchscreen) on OSB - let me know about it.
[Windows Mobile] Nixeus:
Woowww Relax please :)

I have just asked if WM6.5 had new optimization. I respect greatly the work of Barin and you all, I misspoke (I do not speak very good English it must be said). OsBuilder is a very great kitchen and I take great pleasure in using it. I'm a senior member, I'm not one to denigrate someone's work:)

So relax ....:)

Best regards,

Nixeus
[Windows Mobile] feras1989:
have done. Keep it up, good times
[Windows Mobile] HD2Owner:
the tone makes the music.... always consider the context around your post....

just the simple fact that today wp7 supporting osb 7 was released and you ask for more...
[Windows Mobile] AndrewSh:
Peace brothers!

No-one is going to discard WM support. Despite the fact that I cook for Mozart now, I quietly hate WP7 in particular..... and all MS for it in general :)

Hopefully tobbbie does not let this topic die due to his deep digging :)

Other WM guys also will not be left without support.....
[Windows Mobile] tobbbie:
No offense taken here anyway - we are here for collaboration not flaming :-)

My recent problem with different OS behavior regarding COM port settings for GPSID on smartphone (if using "merge packages") has now at least a usable workaround.

I am not sure which of the two observed behaviors is really the right one (so to allow any HW port listed or just those that are listed under HKLM\Drivers\RegisteredDevice Keys BTD_COMx). Anyway the workaround is to simply add the keys so that they are in line with the referenced supported ports for connecting external serial devices at:

[HKEY_LOCAL_MACHINE\Software\Microsoft\Bluetooth\Serial\Ports]
"SupportedPorts"=multi_sz:"COM6","COM7"

I had to add:

[HKEY_LOCAL_MACHINE\Drivers\RegisteredDevice\BTD_COM6]
"Dll"="btd.dll"
"Prefix"="COM"
"Flags"=dword:0
"Index"=dword:6
[HKEY_LOCAL_MACHINE\Drivers\RegisteredDevice\BTD_COM7]
"Dll"="btd.dll"
"Prefix"="COM"
"Flags"=dword:0
"Index"=dword:7

supplemental to the already defined generic part:

[HKEY_LOCAL_MACHINE\Drivers\RegisteredDevice\BTD_COM]
"Dll"="btd.dll"
"Prefix"="COM"
"Flags"=dword:0

Now it works as needed - still different with and without "merge" packages". I traced the registry access with reglogger and tried to debug the .netCF with .netCF powertoys but no real hints from the latter.

Reglogger has revealed that the sequence of accessing the HKLM\Drivers\RegisteredDevice is consistently different in both cases but if an application reacts differently if the sequence of access is different then I judge this as a fault of the application not the OSB.

It puts however light on a level deeper than the pure registry hives's data. The sequence of hive-population in a subkey seems to have sometimes an influence on applications behavior. To track this it could be helpful to have the merged package .rgu saved to a place for investigation.

added:

I also noticed by comparing the active hives content that the sequence of loading drivers in the HKLM\Drivers\Active is consistently different as well. Looking up MSDN it tells that the drivers are loaded using the value of "Order" in their relevant driver entry in HKLM\Drivers\BuiltIn\<drivername>. However are there many drivers that have the same value set in "Order". MSDN tells that sequence of loading is then "undefined". It is however possible that in this case the order of getting the driver data from the HKLM\Drivers\BuiltIn\ may leave a trace in the sequence for the drivers with the same "Order" value. Probably another reason to see potentially different OS behavior in case the "merge packages" option is used.
[Windows Mobile] WojtasXda:
OS Builder V1.3.187 FULL (03.11.2011)

small problem...

Copying XIP packages from DONOR folder...Ok

Package not found GFX_NK
[Windows Mobile] AndrewSh:
wojtas_p5n, look:

"Over there" means http://xdaforums.com/showthread.php?t=1330850

Here is WM thread

Also - define the phone model, source rom damped and build ported.
[Windows Mobile] tobbbie:
Did you check the DSM in the donor folder so it includes all packages to transfer?

Did it work with older versions of OSB?

oops - is that WP7 or WM65?!
[Windows Mobile] Nixeus:
Hello Hello,

I have saw the "Rebase all libraries (modules in EXT, OEM, SYS) to 0x10000000".

Can i doing it for my HD2 ROM ?

What's the goal please :)

Thanks a lot,

Best regards,

Nixeus
[Windows Mobile] -=Barin=-:
There are no any goals. This special option was appeared when we were playing with WP7 modules relocation. We rebased all modules to the same base address and then checked if the relocation works fine while rom building process.

You don't need to use it.
[Windows Mobile] mydear2020:
i was build HD7 rom error popup.

"Unhandled exception

startIndex cannot be larger then length of string

parameter name : startIndex"

any answer?

Regards
[Windows Mobile] tobbbie:
Probably this thread title should reflect that as well - so WM6.x or alike included.
[Windows Mobile] Farmer Ted:
I tried that setting at 4 MB and 16 MB, and ran into some weird issues. If I ran my fuze for a few days without resetting, windows media player would refuse to launch (usually after a day). Also, Microsoft Reader wouldn't launch. And even weirder, in Mobipocket (which I use more than anything else), I would all of a sudden be unable to flip pages using any hardware button pushes. I could still flip them using soft buttons or screen taps, but even if I closed the program and restarted it, I couldn't flip pages. It was actually kind of comical. If I reset the device, I was good to go. I increased the cachevmsize to 40 MB from 16 without changing anything else in the rom, and now after 5 days of regular usage and no resets, everything is still working well. I use small caches (all are set to 0, except replstorecachesize which is 800, I think). I would've thought I could have a small cachevmsize, but hell, I guess I was wrong. Lol.
[Windows Mobile] tobbbie:
For some caches the value "0" lets the OS determine the "right" size afaik - so it is not "small" in that sense as you just don't know how big it is, or?
[Windows Mobile] ultrashot:
I haven't told anyone that it is the best value for all devices. HD2 in fact has a little-big approach for VM - new extended slot which is used in OOM state and by XHammer. So? :)

Also you tell something wrong. Minimum VM size is 256KB, default is 512 KB, maximum is 10MB. If you say "changing from 40 MB from 16" helps, it isn't true.

Don't trust MSDN fully - there is no any cache that actually determines the best value. Best value to their minds is a VERY little FIXED value.

If you want to learn something about driver internals, feel free to ask: disassembler is always ready :)
[Windows Mobile] Farmer Ted:
I thought the default was 32 MB; maybe I'm reading it wrong? This is what I've seen on msdn:
[Windows Mobile] ultrashot:
It isn't true, also you're watching Win Embedded Server page :)
[Windows Mobile] manvantara:
HD2Owner Kitchen "Credential.exe"

Thank you to HD2Owner for its cuisine, I spend all my time to verify its contents

before they can produce a Personal rom.

Just a few points:

1 - What is the file "Credential.exe" found in the directory OEM.

(I find nothing with google).

I noticed that this file is in ROM TMOUS.

2 - I found the following files:

TaskManager.cpl.040C.mui, TaskManagerApp.exe.040C.mui, TaskManagerLite.exe.040C.mui, 0a12ea29_manila, 1c0a2a7a_manila, 3e777095_manila, 5af640d8_manila, 273B6B50_manila, 4759986a_manila, voicerecorder.htm, HTCMenuEnhance.dll.040C.mui, ICR. exe.040C.mui, TaskApp.exe.040C.mui.

which have a link with any package that came with the kitchen

(Found in the directory _EXT_040C) can safely remove?

Thank you.