yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] matthewpapa:
I think depending on whether or not you cook the PTT software or the Cyberion software into the ROM determines this. I could be wrong though.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] sarvesvara.dasa:
yes, I had skipped in the first run. Now - I got it ok. Thanks
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Alemaker:
HTC Streaming Player PKG 2_20_808714_00

Alex,

Ripped this from the new Rogers ROM and made a package for ya.

A couple of things though, cuz I'm a noob chef.

1) The version is 2_20_808714_00

2) I can't seem to get it to be in the Multimedia section of your kitchen-shows up in apps, but I did manage to get it to install in the proper directory on the phone-the multimedia folder.

Musta missed something, but you prolly can fix it up quick.

If you want, take a look at it, fix it to fit in the multimedia section of your kitchen, :eek: feel free to add it to your kitchen.

Alemaker
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] gthing:
Okay I managed to get my first ROM cooked. After fixing my directory structure I still had some errors (like one of the packages was duplicated) but I managed to work through it!

Now I have a few questions.

1. Some of the stuff I selected in the kitchen didn't end up in the rom I made. For example, I don't see HTC home, and x-button didn't make it in. How can I track down why those didn't work?

2. How do I make more advanced registry edits? An easy example would be turning on OBEX. Something more advanced would be to define custom color settings for batti (which gets installed with the rom).

3. How do I customize the theme. Not only the splash screen but the wallpaper, etc. ??

4. How can I change the way the applications I select are organized on the rom? I want to put some of them in the main apps directory, but they all end up in subfolders.

I think that's it for now. Thanks!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] tripledes:
Is there any fix to this problem? I have been trying to get the kitchen working and I end up with this same issue...

I have tried to run rgucomp.exe -b under temp folder to see if it was a kitchen related problem but I get the same issue...

What are the requisites I should have installed to get everything working?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] tripledes:
There are two files to manage registry settings, they are default.hv and user.hv...both have to be extracted to .rgu files, use rgucomp to get them and use an editor with unicode support to modify them. (notepad, ultraedit...)

Here you may want to use customization features included in windows mobile...IIRC there was a command called cusTSK or something alike...

initflashfiles.dat is what you're looking for... :)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] _Alex_:
This could be an issue with your .NET Framework version / update, but I'm not sure because I have not encountered it. I have 1.0 SP1, 2.0 SP1 and 3.0 SP1 installed with all the latest Microsoft hotfixes for XP.

Alternatively, you could ask in the buildOS parent thread.

When working, it should look like:

[SIZE=1]Completed successfully
Microsoft (R) RGUComp Version 1.0.000
Registry file processor and hive builder.
Copyright (C) 2004 Microsoft Corporation All Rights Reserved.
built: Nov 19 2004 15:17:13
importing registry file ".\boot.rgu"...
importing registry file ".\Registry\1dc3da02-499f-4547-9fd2-78cddfda9c62.rgu"...
package "MSXIPKernelLTK" does not contain .rgu file "d92a4f0a-378a-4482-8fd3-bd127a05e4de.rgu"
importing registry file ".\Registry\8cb4ac12-6bc5-4bda-ab45-539988c36a95.rgu"...
importing registry file ".\Registry\6b4ed31c-5ced-41b2-b917-2c006f046a5e.rgu"...
...
[SIZE=1]importing registry file ".\Registry\f020c116-6598-4f77-a71f-93ca483028d8.rgu"...
(RGUComp) done!
Rom's Dump Created successfull!!!

[/SIZE][/SIZE]
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] _Alex_:
Depends on which OEM Packages you've used. I believe some of the v4 packages had problems. v5 should work.

Also, make sure that you don't have multiple .NBH files in the same directory when flashing, as KaiserCustomRUU will only choose the first file in alphabetical order, which may not be the file you want to flash to your phone.

Create or modify an existing OEM package. Check out the OEM tutorial for more information.

Turning on OBEX would just be a .RGU file containing the registry information + option.xml in a separate folder.

Changing default batti colors would be editing the existing .RGU file and adding the appropriate registry entries to control color.

There are a couple of ways to do this, but I'll reference the easiest. In the v5 OEM packages, I have a OEM package called 'Startup - Alex'. Change the image files in this package to your own and that will change the images used in various areas.

You can change the themes by editing the config.txt file in either Tier AutoInstall, Theme-HTC or Theme-ATT.

OEM_Lang_0409\initflashfiles.dat controls the locations of all the files that are included in the base ROM. initflashfiles.txt in each OEM package folder is what controls the locations of the files for that particular package.

Seems like you're ready to move onto the OEM package tutorial! Enjoy!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] decimusmaximus7:
Hey Alex, can you add the htc action screen and the unlimited use mobitv to your kitchen? I've tried creating oem packages from the cabs but they error when building the rom.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Alemaker:
For the mobitv pkg-go to Alex's v4 pkgs. It's in there.:)

Alemaker
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] decimusmaximus7:
I can't seem to find the v4 packages anymore??
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Alemaker:
scroll down to the v4 pkgs-post #2 on this thread :eek: Link is right in there.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] gthing:
There are a couple packages I've found in the version 5 package collection that cause some problems.

As far as I can remember chess, htc keyboard, and one other one I had to change the config.xml to be UTF-16 encoded instead of UTF-8. Otherwise I got errors about invalid characters in the config file.

Also, quickmenu seems to install no matter what I select, so I had to remove it from the packages folder.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] gthing:
Where do I find those files? I can't seem to see them anywhere.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] lowreeds:
check in SYS\Metadata
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] lowreeds:
I am stumped by rgucomp.

What settings, in ultraedit, should I use to save default.txt to unicode?

I'm always getting

InitRegistry FAILED in file ".\boot.rgu" within a few lines of line 1.

Suggestions please.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] _Alex_:
This occurs sometimes when you change a package via BuildOS to 'enable by default'.

There are some packages that do this. The recommended method is to move it out of the packages directory. I actually move all packages out of the directory unless I explicitly want to install them.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] lowreeds:
Alex, if you have the time, can you tell me how you edit the registry hive directly?

In some amount of detail.

I want to be able to remove entries when I remove packages from a rom and can't get a handle on rgucomp.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] JoeWilcox:
I was asking this in another thread. Do you know why they install even if unselected? I assume that BuildOS creates a master manifest somewhere. Do you happen to know where. Maybe it's a tool bug. I've been thinking about writing my own tool for this to add support for things like storing your packages in a common directory, etc.

Also, I've gone through your OEM packages tutorial but the format for initflashfiles.dat seemed to be confusing to me still. Can you think of any additional threads/tutorials on the subject.

I've created a couple of packages that I'll probably release over the next couple of days (Calendar+, my own custom fix for brightness dimming when locked, etc). But I'm not quite there yet.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] _Alex_:
I've included some VB scripts that can help you convert to the proper formats for editing and reconstruction. Enjoy.

edit2: FWIW, I don't think editing SYS\Metadata\default.hv or user.hv does anything, as BuildOS reconstructs this from scratch and puts it into the \temp\dump folder. Please inform me if I'm wrong :D
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] _Alex_:
DSM files are used for the file manifest. BuildDSM in the tools folder can be used to create new DSM files with actual file manifests instead of 0 length files which BuildOS creates. This should fix the bugs we've seen in some of the packages being installed even when unchecked.

Seems like the formatting for that section got fubared when I reformatted it with TOC pages. I'm fixing it now.

edit: If you're looking for an explanation of the @CESYSGEN conditionals, see Microsoft's explanation.

Looking forward to it. Enjoy!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] JoeWilcox:
I'm at work so I can't try this right now but when you say "creates a copy" does it copy the file and leave the original in the windows directory or does it move the file?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] _Alex_:
It does mean copy, not move. One of the limitations of deployment via OEM packages & initflashfiles.txt is that you will have duplicate files if you decide to have files *NOT* in the windows folder.

I've tried to make my own provxml files for use within the ROM with little to no success. You can read about that in a very early thread started by me.

Hope this helps.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] lowreeds:
Thanks for the files.

Where can I edit the hv files that will work?

The temp folder?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] _Alex_:
Short answer: You don't need to edit hive files. Edit the RGU files within the OEM and SYS folders. Use the show editor function within buildOS for RGU editing.

Long Answer:

Hmmm, this is the first time I've looked hard under the hood of this kitchen, as it was originally created by jcespi2005 & JugglerJKR and it worked so good that I decided not to tinker with the commands, I just made it alot simpler by building the DOS UI around it.

Well, based upon what I've just discovered, ROM\XIP\boot.rgu is taken and all other .RGU files are merged into it during the BuildOS process (step 8).

During the os-new.nb creation process, but the registry settings found in boot.rgu are present in the cooked ROM (created in step 10) and default.hv seems to go unused. For instance, if you use the 1.62 ROM base, try to find HKEY_CLASSES_ROOT\rtsp key in any of the ROMs created from it. You won't, because it's not present in boot.rgu unless you cook in realplayer's OEM package, but it is found in default.hv as one of the first keys.

So if you want one file to edit the registry, it seems like if you edit boot.rgu before you go on to step 9, you can put all your registry changes in there. But that's temporary at best, as BuildOS always deletes the temp directory at every run. So your best bet is to find and modify the RGU files directly in the OEM and SYS folders, as I have when releasing my non-beta base ROMs (AT&T 1.60, 1.61 & 1.62, HTC 1.56 and 1.81 are non-beta). The easiest way to do this is to use the 'show editor' function with 'rgu editor' selected in BuildOS and edit the RGU files found in OEM and SYS folders.

Hope this helps!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] gthing:
You must be right, because I don't even have those files.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] lowreeds:
Yes, that helped.

I was thinking that as I removed packages from SYS the registry entries were left behind.

When really they are in the rgu's from each package and don't get written to the registry until build time.

You've inspired me to try again to cook with 1.62.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] doctajay:
Hey Alex or anyone. I've been lurking and reading a whole lot. I've read through every post of this thread and I think I'm confused because I normally don't fool with the registry. But yeah...I have this same Guest Only problem when I hook my phone up to active sync. I know you said that I need to edit the registry, but:

Where exactly is this registry file located?

Do I edit the registry on the actual phone after I flash, or in the folders before I flash?

Can I just use the NotePad software to edit it or do I need to find and download RegEdit4?

Thanks alot in advance for helping me out. This is the last step that is hindering me in the cooking process.

P.S.-I'll be setting up a mirror for all of your files soon Alex.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] _Alex_:
Read the OEM primer, specifically the section describing RGU files. Hope this helps!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] lowreeds:
I am getting an error when I try to run wififofum.

An unexpected error has occurred in WiFiFoFum.exe.
Select Quit and then restart this program, or select Details for more information.

File or assembly name 'System.Data, Version=3.5.0.0, Culture=neutral, PublicKeyToken=969DB8053D3322AC', or one of its dependencies, was not found.

I am guessing this is an issue with the .net framework.

Suggestions?

Base rom _Alex_ 1.62.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] doctajay:
so would I have to find every .rgu file in my OEM, ROM, and SYS folders and add the GuestOnly=0 entry? Because I already serached all the .rgu files and none of them have any type of [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows CE Services] key.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] stainlesspc:
Transformation complete

Alex -

Thanks to you my transformation to the dark side is complete :)

It still will not work on the computer in the office (probably a good thing) but your kitchen works at home :)

Well last night I made 2 roms. the first was a WM 6.1 which I later found out was realy 6.0 so I made a 6.1 but had problems with no sound. I think I had a couple packages that were not compatable with my tilt.

But THANKS the first one I did runs GREAT and is my fastest feeling yet (I may be a bit partial though)

Tonight I will retry the 6.1

I do have a couple questions though.

1. where does the list of packages come from ? do they disapear from the list if you delete them from the "packages" folder ???

2. what did I do different then the rest ? when I Hard reset and go through all the hoops there is NO "3 second" window once it comes up ?

More questions later :)

Thanks again
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] _Alex_:
Do you have .NET CF 3.5 installed?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] _Alex_:
Create a new OEM package with a single RGU file and put that key in there.

BTW, I'm not aware of this problem occurring with any of my base ROMs except for you and that other guy, so you may want to try to hard reset immediately after you flash.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] _Alex_:
Yes. You can also right click on them in buildOS and choose to delete them. They will be moved into a folder called Packages-Deleted.

Did you include tier autoinstall or tier install? Tier Autoinstall prompts you at boot (and nags you until you run it), tier install doesn't.

[/quote]

Hope this helps!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] lowreeds:
I have the NetCF_3 package that was in the original rom.

Do I need to put in NetCF_3.5?

Is there a cab instead of re building/flashing my rom?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] _Alex_:
http://www.microsoft.com/downloads/...37-A62F-4A6E-9727-7791BF4CC2BD&displaylang=en
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Guilf:
Ok - dying here. Can't figure out the registry edits. Started my own thread, but Alex directed me here. I have never asked a question my whole time on the board and I know this may be a dumb one, but I can't figure it out.

Cooked about ten + of my own very successful ROMs. Have created ten or twelve custom packages for software I own (Memmaid and Opera Mobile, etc.) and can make the registry edits to include my keys and such. No issues and everything works perfectly (THANKS Alex, great tools). However, I still have to make a lot of tweaks after flashing and I've been trying to cook them all in. They include most of the Kaisertweaks, remapping the softkeys, operator settings, media file saves to Storage Card, etc. Have read for double digit hours on the different methods people have used. Perhaps I'm trying something that is too far reaching (at least for my level), but I've had absolutely no issues with anything else and can hand enter the tweaks with no issues. Finally, did a registry compare clean flash and post all my tweaks. Thus, I have a .reg (or .rgu or whatever I want) with just my desired changed settings. I have checked this file repeatedly for errors. Have tried everything from just importing the new file into a file to creating a package with just the .rgu file and an options.xml file (errors out while compiling the registry) in it to using Settings Savior to trying to create my own provxml file to trying to create my own cab for implementation post hard reset. I have even installed SDKcerts.cab to assure it wasn't a certifications issue. Can I not implement all the changes at once? I assure you that I've searched and read everything I can find more than once. Can anyone direct me to an idiot-proof method, because apparently that's what I am :). (If you can't tell, this has slightly frustrated me). Thanks in advance for your help.

Attached my .rgu file if that helps.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] cushcalc:
Memmaid OEM package, and others . . . ?

Would you post the OEM packages you have created?

Memmaid would be appreciated by many, I would guess . . .

Have you done SKTools by any chance?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] _Alex_:
You're lacking REGEDIT4 on the top of the file. In the future, please include the last couple of lines from BuildOS, because I could have had an answer that much quicker :)

Hope this helps!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Guilf:
No problem doing that at all. I have to edit to take out my reg keys. Will get them up later tonight. Have not done SKTools.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Guilf:
I knew there was a reason my pride wouldn't let me ask. I'm an a$$hole :). Had it there initially, but ran it through so many registry editors trying to figure things out - I must have dumped it somewhere.

Alex, you're a hero. Truly - I appreciate all you've done here...particularly recently with cleaning up all the boards and the wiki and such PLUS your amazing work on the Kitchen. I know there are a lot of contributors around here, but you've been a particular help to me lately. Will also get a donation out to you. It's way overdue.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] _Alex_:
LOL. No need to be self-effacing, glad to be of help. I'm looking forward to that donation!

PS, sent a PM...
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] doctajay:
Well no matter what I tried, that Guest Only thing wouldn't go away, so i guess I was destined not to be a chef... :). Anyways, I uploaded all of your kitchen Alex onto my website so that folks can dowload the whole package. Even though cooking didn't work out for me, I plan on working on some screencasts for the fellow noobs to delve into cooking also. I'll let you view them first to make sure I didn't say anything wrong. Anyways, here's the mirror for your files:

MIRROR FOR ALEX'S COOKING KIT: http://xdadev.doctajay.com/?page_id=5
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] gthing:
Okay, I'm making some major progress here! Thanks for all the help so far.

Three questions:

1. [Fixed!]

2. No matter what I do, I cannot get OBEX enable to stick. I have an OEM package that sets the appropriate registry key, and I verify in default.hv after building my ROM that it is in there. But when I compile the ROM to an .hgu and flash it, it is reset to not enabled. What am I missing?

3. When I try to install Windows Live Search Mobile I get an error "File or assembly name 'Microsoft.WindowsMobileStatus,Version=..." which I think has something to do with NetCF. I have tried both 2.0 and 3.5 contained in the cooking kit and gotten the same error. This is on a rom based on the new AT&T 1.62 Rom. Any ideas?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] stainlesspc:
Question from noobe chef

1. how do you go about RE-cooking a ROM. Say I have one I just want to tweak, can I just tweak it and not have to start all over and cook it from scratch.

2. I am using Alex's kitchen and tutorial, I cookec a 6.1 ROM using the ROM from Alex's 6.1 ultra clean, added the packages (nothing to crazy, fairly clean but functional for me) and flashed. When it booted my phone kept buzzing ? when I finally got it to quit through a series of resets it had NO sound. I flashed back to My 6.0 Rom and no problems.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] gthing:
I think this has to do with the radio version you used. Not all radios are compatible with WM 6.1 and if you don't have the right one you will get no audio.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] lowreeds:
how did you get batti to work?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] _Alex_:
For OBEX, you may want to check if a provxml is removing your registry entry. I believe provxml files are run after you flash the ROM, which is why it wipes out any .RGU entry in an OEM package.

Is this an OEM package you've created yourself? The cab installs just fine if you include .NET CF 3.5 and SQL CE 3.0... I haven't tried it w/o SQL...

BTW, I've never released a MS Live Search OEM package or put it in a ROM because it updates too frequently. You may want to consider that when choosing OEM packages to put into your ROM.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] _Alex_:
It's missing a link in \windows\startup and registry keys for width. Glad gthing fixed it for himself, although I'd be much more appreciative if he would release his OEM package fixes :)

Here is a fixed version from me...