yashsingh1/xdaforums huggingface dataset:
[Windows Mobile] CRACING:
Hello Barin,

I have some trouble with the installer. Its random and I just ignored to report here.

1. I will install the OSBuilder (or reinstall to update existing software).

2. Move the installer (.msi) to other dir.

3. Run the OSbuilder.

4. And it will ask for the installer (.msi). :confused:

Looks like the installation isn't fully completed. It only happens once when the software is installed or reinstalled/updated.

This remembers me M$ 0ffice 2000 installation. :p

I think its not the issue, its the way how msi works but the msi file should be copied to C:\Windows\Installer\ while installing and the program should read msi from there to complete installation, rather then ..... :rolleyes:

Thanks...

Best Regards
[Windows Mobile] CRACING:
Hello anybody here? :p

I have a new issue in my ROM. It seems with OSBuilder itself. Problem is, pinch to zoom works but cannot pan around. It sticks to where I have zoomed to and I cannot move the page. I'm talking about TouchGL whitelisted apps.

If I flash official ROM it works but if I recook an official ROM using OSB, it doesn't work as well. :confused:

Can anybody help me please?

Thanks...

Best Regards
[Windows Mobile] HD2Owner:
if you mean pinch to zoom and shift page with both fingers on screen ->

it's only possible in wp7 internet explorer. this was never possible on wm.

are you sure you did not alter kitchen? i'm asking because it could also be a side-effect of using tmous hspl2.08 in combination with eu 3.14 driverbase.

another thing you could check:

extract hives (default.hv & user.hv) from dump with hvedit and compare them with the ones from re-cooked rom (with good comparison utility).
[Windows Mobile] tobbbie:
Look a little down the thread when it comes to registry hives. I found the strange effect that the "merge packages" has created impact on the device while the hive content is indeed identical.
[Windows Mobile] HD2Owner:
yeah, another thing to try.. uncheck merge packages option. thanks tobbbie. ;)
[Windows Mobile] CRACING:
Thanks for the reply.

I mean, take file explorer for example. pinch to zoom works there but when zoomed, I cannot move the page around. i.e holding and moving the box shown below. I will also show you screen shot later.

It works when I flash official ROM and also any ROM cooked in oskitchen. When I recook untouched official ROM in osbuilder, it fails. :confused:

I have compared the reg like you said and did find lil difference but they couldn't help to solve the issue either.

btw; I'm with tmous hspl and base.

Thanks...

Best Regards
[Windows Mobile] HD2Owner:
it's also dependent on osbuilder settings if it's really untouched after re-cooking.. ;)

did you try with unchecked merge packages option?
[Windows Mobile] CRACING:
Yeah that one worked which I wasn't expecting its related to my issue. Thanks!

Anyways, now I cannot let my ROM go with all the DSMs which will be an open source. :p

I think a dsm is needed for the panning to work. any idea how to solve the issue without including all the dsm's?

edit: No luck so far. Only thing is, when I enable merge packages panning fails to work and when disabled, it works.

I have compared both the ROMs (merged and unmerged) and difference were only those DSMs and the same DSM entries over registry (RegistryUpdate). Also tried to copy those extra DSMs (about 400+) to windows dir on the device but no luck or its stupid thing :p)

so what else is getting different (in merged and unmerged) which is causing panning issue. :confused:

Thanks again...

Best Regards
[Windows Mobile] tobbbie:
Well, I think that the "right" things are done in OSB, it just seems that the strategy to merge the packages could be re-thought.

I think that OSB is doing the same that the preview of registry does: It imports all rgu to a new "virtual" registry and then exports the result to a new "merged" rgu (omitting all duplications) which is then finally imported to the relevant hives in the build process.

The result this gives are identical in content, but it seems that some applications' acccess to such hives is not only done by querying a data value directly, but also like "give all below a subkey". The resulting sequence in the query result which the application gets may be different in the original case and the one resulting after the "merge". An application should care about this (by sorting the results or searching the data in the query result) but it seems that some do not, like the one I was talking about in my post (GPSID.exe).

You have now evidence that also another application or device behaviour is impacted by the "merge packages" so the strategy could be different.

A simple alternate (yet primitive) method to merge the packages is to simply concatenate the *.rgu files to a single one in the sequence that they have to be processed and then insert that single one to the hives. This primitive merged *.rgu will be much larger as if the pre-processed one is used but it will retain the original sequence of actions to the hives.

@Barin, Ultrashot: any chance for this?
[Windows Mobile] c_shekhar:
Dear experts!

Is there a way where i can run a .cmd before XIP operations? Actually I wish to format the RAMDisk before any activity from this kitchen (OSB) starts.

regards,...

c_shekhar
[Windows Mobile] -=Barin=-:
Settings -> Build Dump and ROM ->Run cmd file at the beginning
[Windows Mobile] CRACING:
Any help for my merge packages issue? :o
[Windows Mobile] c_shekhar:
Gettting error "Could not find a part of the path R:\Temp\Dump|initflashfiles.dat"

(I guess Perhaps some files are removed due to formating which are required at time of preparing the initflashfiles.dat)

Need is for running .cmd before even XIP operations start.
[Windows Mobile] -=Barin=-:
Why do you need to format RAMDisk every time? If you redirect temp folder to the ram disk all operations with Temp will be done correctly.

I use

SuperSpeed RamDisk Plus
[Windows Mobile] CRACING:
Hello,

I'm facing another problem now. I thought to make an un-merged ROM to solve panning issue but when I tried to dump the ROM (using OSB), I get "Reading dsm...An entry with the same key already exists." error. I haven't tried to flash the ROM yet.

I know its an dsm issue in one or more of package(s) and I tried few thing but again ended up with the same error.

Changed the GUID of the troubling DSM and RGU and it solved but when I do DSM corrections, I face the trouble again with different DSM.

Any idea why is it happening?

Thanks...

Best Regards
[Windows Mobile] tobbbie:
Cleanup the DSM content (align folder content with DSM content).

There is tool for that in one of the 3 places for tools (don't remember which it was).
[Windows Mobile] CRACING:
Ok guys, I found the reason about the issue "Reading dsm...An entry with the same key already exists." error

I have packages called:

Connection Setup v3.1.20162829.00

Connection Setup v3.1.20162829.00 WVGA

The DSM autocorrection was fixing the DSMs inside the above packages and writing package name as Connection Setup v3 for both the package DSMs. So thats why dumping process was failing because there are two DSMs with same package name.

Same goes for:

Sim Contact Import v3.4.20211925.00

Sim Contact Import v3.4.20211925.00 WVGA

Looks like DSM autocorrection doesn't wanna take full package name to writing into DSM package name or is it because package name contains spaces and dots? I guess its because of dot

Anyways, atleast I was able to solve this isssue. Yet I hoped merged package would have also. :o

Thanks...

Best Regards
[Windows Mobile] -=Barin=-:
@CRACING

Dots and blanks are not accepted in package name

That's why stock packages are named like PACKAGE_NAME_XXX_XXX
[Windows Mobile] manvantara:
I'm lost :(

Is what you can take to OEMXIPKernel TMOUS and use it in HD2.

thank you.
[Windows Mobile] AndrewSh:
Sorry, is it possible to write it in more English? I can not get the sense....

If you mean:

Is it possible to take OEMXIPKernel from TMOUS and use it to build HD2 rom - than - the answer is - yes.

It's not only possible but it's recommended.
[Windows Mobile] manvantara:
Beginner in the kitchen. Base HD2Owner (thank you for our kitchen)

sorry

It's a google translation from French to English.:(

Thank you for responding quickly

Why is it recommended?

For MSXIPKernel is the pure heart of the system. I understand.

But OEMXIPKernel I see OEM. I thought TMOUS is different from HD2?

What then reall OEMXIPKernel?. :confused:
[Windows Mobile] AndrewSh:
manvantara, by using XIP and OEM from TMOUS you will enable hidden memory of HD2.

It's a normal practice.
[Windows Mobile] manvantara:
Ha thanks, I did not think at this point of view.

Let me explain:

1 - RUU_Leo_S_HTC_FRA_3.14.406.2_Radio_15.42.50.11U_2.15.50.14_LEO_S_Ship.exe

HD2 is the official and 576 are activated.

2 - RUU_Leo_1_5_TMOUS_3.14.531.1_Radio_15.42.50.11U_2.15.50.14_LEO_1.5_Ship.exe

that's the TMOUS 576 is default.

In the kitchen (HD2Owner) or try to learn how it was produced and

at the same time understand OsBuilder (my god this is the best food, I am computer engineer and I know a powerful and very well done: good luck. Thank Barin =- -=)

In the directories:

DONOR / 21913: I think it's exactly the XIP 21916.

XIP / ROM: Same TMOUS_3.14.531.1

OEM and SYS: one part comes from the LEO 3.14.406.2

If TMOUS_3.14.531.1 LEO_3.14.406.2 and have 576MB

Why use OEMXIPKernel of TMOUS?

I am lost, if I find no logic to this, I get stuck.
[Windows Mobile] WojtasXda:
Hi Barin!

Thank you for the new version OSBuilder

I have a problem with the "apply updates to packages"

started update of the 7389-7390

i have 7004-7403 and 7403-7720 from this website

OSBuilder crashed on these files :

1. Build Info ( *.rgu , 7389-7390...cab)

2. ShellCore ( *.rgu , 7403-7720...cab)

3. SILVERLIGHT ( *.rgu , 7403-7720...cab)

My Device: Toshiba TG01

My ROM: 7389 (Hybrid 7003/7355/7389/7510)
[Windows Mobile] Nixeus:
Hello,

Thanks a lot to Barin and all the stuff for this new release.

12. Added the ability to build the file NB (D000FF) with sections written in the DIRECT_MAPPING form. This process uses only the template, so the base NB file is not needed. This method improves ROM performance. I want to warn you that updates (cab) in this case will setup slower, but thanks god – we don’t have them every day. The corresponding checkbox can be found in ROM files and Formats settings.

Can we use this feature for wm6.5 rom ?

Any advice for using it ? How using ?

Thanks a lot,

Best regards :) :)

Nixeus
[Windows Mobile] HD2Owner:
@nixeus: building nb from template works since long ago for wm...

@WojtasXda: just take sys and msxip from other device. no need to update with cabs.

@manvantara: 576mb ram is not unlocked in non-tmous-roms.
[Windows Mobile] Nixeus:
Thanks a lot for the answer UltraShot,

Why this feature improve rom performance ?

In addition, i don't find where is the checkbox in order to activate this options.

Thanks a lot,

Nixeus
[Windows Mobile] WojtasXda:
Hi HD2Owner :)

if it were that simple ... ROM for the TG01 is very strange; /

so I checked cabs in the kitchen and watched what is causing the problem ...

need to check why some exe / dll / rgu can not update / change

heh .. really strange is this ROM;)

greetings;)
[Windows Mobile] Nixeus:
Hello,

12. Added the ability to build the file NB (D000FF) with sections written in the DIRECT_MAPPING form. This process uses only the template, so the base NB file is not needed. This method improves ROM performance. I want to warn you that updates (cab) in this case will setup slower, but thanks god – we don’t have them every day. The corresponding checkbox can be found in ROM files and Formats settings.

Can you explain me why this improve rom performance ?

Where is this famous checkbox ? I don't find it :(

Thanks a lot,

Best regards :)

Nixeus
[Windows Mobile] -=Barin=-:
It's available in WP7 mode only
[Windows Mobile] tobbbie:
Files and Registry preview

While cooking and porting I got to learn that 2(3) minor quirks still reside in the previews (as of version 1.3.187, did not step up in the middle of the project):

Contrary to the WWE Manual, the initflashfiles preview does not care about provxml.

Files Preview does not care about the changes that provxml files can do to the filesystem either (evolution of the previous?)

Registry Preview does not find un-escaped "\" characters in multisz values. It accepts them instead while the registry compile will complain.

In that context one more thing about the boot.rgu and boot.hv. It is not so obvious, but I think that boot.hv is usually taken unchanged while the boot.rgu is used to insert its content when building the default.hv and user.hv. Consequently any early in the boot-process required definitions come from the boot.hv and not from the place that you see in the registry preview! I know that I can recompile the boot.hv (and so I solved the problem) - but it could help to include the boot.hv itself also in the registry preview - to notice the difference of boot.hv and boot.rgu.

Anyway it is still fun cooking with OSB :-)

Edit 20111223:

Additional note to the .provxml treatment: Only the commands meant for the Registry Service Provider will be merged to the registry preview, not any other that will finally (on the device) have their output also visible in the registry.

Huh?! Other "Service Providers" are e.g. Security, or Metabase, see here: http://msdn.microsoft.com/en-us/library/bb737336.aspx . So if your .provxml changes security policies you will not see the results in the Registry Preview. Depending on your .rgu settings of the security default such a provxml may not execute at all.
[Windows Mobile] tobbbie:
See previous post - update with proof how .provxml is treated in sequence.

Please update the relevant sections of OSB:

Provxml Files tool

Registry Preview should take the correct sequence when merging the registry Service Provider from provxml to the hives

Merge Packages to one should mimic the true sequence when merging the various provxml to the reduced set
[Windows Mobile] AndrewSh:
tobbbie, I read your posts!!!

I am pretty sick and tired of this ugly MS stuff from hell (called WP7). I hate this OS and I am going to return to my beloved 6.5.3 soon...

So - you are not alone!!!

Happy New Year to you and all the best!!! :)

Regards, Andrew
[Windows Mobile] Skrobel:
Don't worry tobbbie

There is still some life in WM as Andrew wrote. There are so many ugly things about WP7 that I think some users will return here.

I still use Rhodium as my main device. Additionally I just got my Brother's Kaiser and will play with it a bit.

As Jackos is gone to Android, I started to play with his kitchen an see what can be improved.

You are not alone :)

Happy New Year to you all!
[Windows Mobile] tobbbie:
Happy New Year

Thanks guys! I know I am alone with my smartphone(s) - but still good that some care about the WM6.x ! There is so much explored already here and still things creep up which make me wonder why I am the first to find this (like the .provxml execution sequence trace).

I hope Barin and Ultrashot find time to get things fixed that do not deal with WM7 only, despite I know that is where all the interest goes.

Andrew, wish you a fast recovery (back to WM6 :-))!

Happy New Year to all of you!
[Windows Mobile] Farmer Ted:
I've actually been cooking a lot lately, like once a week (was down to once a month or so). But I wouldn't expect much action here anymore. It's too bad winmo is in the dumpster, it is a really great operating system.
[Windows Mobile] ultrashot:
OSBuilder isn't abandoning WM support and never will.

Well, we still have some interesting features to implement for WM6 (like Default Thread Quantum changing, higher slots align changing etc).
[Windows Mobile] HD2Owner:
word buddy.. it's like people think that you can't cook wm roms anymore with osb7.

for me, all that is needed to cook wm is already present in osb.

ultrashot even ported xph compression from wp7 to wm (armv7 instructions).

and like ultrashot said, we are constantly trying to do new things.

like default thread quantum adjustments in osb (we do this manually for now).

i just have to drop another BIG THANKS to barin/ultrashot for everything.
[Windows Mobile] tobbbie:
Hi, I wonder if there is any planned-feature or bug list published someplace? Especially the latter would be interesting to see to avoid double reports and estimate on a potential fixup timeline. There are several (also free) bug tracking tools, sure you know more than I do.

Thanks for the tool as it is, however! It has supplied so much insight to me already and its continued support and devoted developers are a pleasure to deal with.
[Windows Mobile] ultrashot:
no, there is no any feature list and bug tracker.
[Windows Mobile] tobbbie:
Hm, I hope you have an internal one :-)

Would you mind to comment on reported bugs (or what the reporter thinks to be a bug)? Unfortunately I have a history of reported bugs (and just quirks) that I have not seen noticed or fixed. Some are very minor and others are not (like the recent ones, I think).
[Windows Mobile] ultrashot:
Barin can tell you much more than me about "reported bugs" (I've created only some parts of OSB while Barin made everything else). He is busy right now.
[Windows Mobile] tobbbie:
No Problem - I know that bugs have lesser priority than WM7 and since OSBuilder is a spare time project also the overhead of dealing with a public bug list would further cut the time budget. I am happy to contribute where I can.
[Windows Mobile] ultrashot:
bugs always have highest priority, don't hesistate to report them.
[Windows Mobile] Nixeus:
MMM sound's great !!

Waiting for the new wm6 tweak :)

Great thanks to all the team :)
[Windows Mobile] goldsmit409:
well i have 2 questions...

will os builder be able to mango roms....or it is just for wp7 yet???

second the nokia lumia rom is Rm803_xxxx_boot.esco

will i be able to edit it with OS builder please help....
[Windows Mobile] ultrashot:
Isn't Mango wp7 after all? :D

Edit isn't implemented currently. Dumping is possible with a bit of magic - rename file to .payload.
[Windows Mobile] hassan19:
goooooooooooooood work
[Windows Mobile] tobbbie:
Reconstruct Relocation Section?

Hi Barin,

...please don't sigh :-) that I come with this topic again.

I had PM-ed below to ultrashot and he recommended to post it here - despite it is rather special, I admit.

After I made Typhoon work with OS Builder (putting 5 modules to the "do not relocate" list) I wanted to do the same with the Hurricane but there are many more (~18) to be treated like this and I did not succeed getting a booting device yet with OSB yet.

I have found that the wmreloc.exe creates a dedicated list of offsets where relocation has taken place, called reloc.txt. I wonder if that list cannot be re-converted to a regular relocation section so that the module can be treated normally again. I have setup a 7z file (http://www.mediafire.com/?a5o619j9ot2zk) containing the backlight.dll from the OEMDriver and the same in the dump folder after relocation with wmreloc.exe (also included).

If you compare the section files in the two directories you will find for each of the deltas a corresponding entry in the wmreloc.txt file in the dump directory.

Are there any tools that can add a relocation section to a module again?

Another thing regarding OS Builder's relocation: Why is it needed to put modules without reloc-section to a dedicated list "do not relocate"? Such modules should automatically be added there or at least treated like this (so do not occupy their address space during relocation of other modules)! If I want modules WITH reloc-section to stay where they are then an entry in the list makes sense. I had put this to my initial queries at asusmobile.ru but it was buried under a lot of other work I guess.

No flames please - I just love these old candybar phones :-)
[Windows Mobile] AndrewSh:
tobbbie, don't be upset if Barin does not reply soon - he's still extremely busy in the office and not so often online now. I will definitely point him on your request when I see him next time in private chat.

Regards, Andrew
[Windows Mobile] tobbbie:
No problem - spare time projects have to wait for spare time, naturally. As I care for old devices, the only time factor is that batteries may die in some years :-)
[Windows Mobile] tobbbie:
Saving/maintaining configurations - option.xml should supersede package info

While creating sets of settings for my smartphones kitchen before distribution, I noticed that changes I make to a package description in one setting will not propagate to other settings - due to the way how information is stored.

It is actually good to have everything stored in just one settings file in the Configurations folder, however this makes updating package information a tedious task when you have many different settings files - sigh...

In old days the package information was stored in the options.xml file, yet linked with its selection status - which made creating settings impossible :-(

So how could the positive of an option.xml (storing the package properties) be combined with the advantage of a single settings file?

To not change the existing strategy too much my proposal is the following:

keep settings where they are

if options.xml exist, then

overwrite the settings file content for everything except the selection status when a setting is loaded

when a package information is changed, then also update the option.xml

Above makes sure that package information is automatically propagated from the option.xmls when loading a configuration, so they should never be out of sync when used. Optionally a tool could be created to sync the various settings with the option.xml files.

A cleaner way would be to separate the selection status and the package description from each other. So shorten the settings files (exclude the package description) and instead store the same in the package folder with a dedicated "description.xml" file. The latter could resemble identical syntax to the option.xml file - just skipping the selection status part.

I know above is cosmetic and more important stuff needs to be done, but maybe the low effort part has a chance some time.
[Windows Mobile] dunkhy:
Folder not found .VM or file .VM\imageinfo.bin is corrupted

hello all, i m very noob here and i m sorry for this -i understand noobs pbms are often annoying ;)-

i've followed the video presenting the soft, to extract ahmedfikry wm6.5 light rom nbh file, however while trying to dump it i get error message saying "Folder not found .VM or file .VM\imageinfo.bin is corrupted". same result with shifu rom's .nbh

i looked in the thread for such error and also in the manual but found nothing in.

those roms are for tytn2 kaiser, which is not directly indicated as compatible phone. Is it therefore not compatible with this builder (if so which one would you advise me to try, knowing i m truely beginner), or if i m doing something wrong, where can i get more detailed infos to not come over every time i m stuck here?

Many thanks
[Windows Mobile] Farmer Ted:
It sounds like you're trying to dump custom roms; unless they're unprotected, you're going to have issues. The easiest way to find out is to look in the \windows folder and see if there are a crapload of .dsm files. If they aren't there, it's protected. The .reloc sections are probably missing from all the modules as well.
[Windows Mobile] dunkhy:
yes it s customs, then i understand why some pple wrote "here is my kitchen". thanks for the info :)