Fry Cook Questions for the Real Chefs - Touch Pro, Fuze ROM Development

Greetings,
It seems like the talented experts in this forum are making it easier for everyone to build Custom ROMS. As such, I think many of us are trying this for the first time with the excellent Kitchens that show up on the forum. I thought this might be a good thread to ask noob questions so we do not clutter up the ROM specific treads with our general, how-to noob questions. Most of the ROM threads are cluttered enough.
We should always try the search function, but sometimes the answers are not as apparent or as clear as we would like. So here is a venue to ask for help from the pro's.
Doug M.

---

Start Menu Organization
So here is my first question for the pros. How do I clean up the start menu in a ROM? Using the 21501 B4 kitchen from DaG and the Erviuskitchen tool, I can easily click the items I want, but many ROMs have all of the apps neatly organized in the start menu. How do I do that?
Thanks for any advice.
Doug M.

---

It seems like the talented experts in this forum are making it easier for everyone to build Custom ROMS. As such, I think many of us are trying this for the first time with the excellent Kitchens that show up on the forum. I thought this might be a good thread to ask noob questions so we do not clutter up the ROM specific treads with our general, how-to noob questions. Most of the ROM threads are cluttered enough.
Click to expand...
Click to collapse
Great idea, here's to hoping it catches on. Eventually, you may want to change the title of the thread to something [FAQ] Commonly Asked Questions, [Q&A] ROM Cooking Techniques, etc. Could be a great candidate for the Useful Links thread (i.e. sticky).
On to your question ...
So here is my first question for the pros. How do I clean up the start menu in a ROM? Using the 21501 B4 kitchen from DaG and the Erviuskitchen tool, I can easily click the items I want, but many ROMs have all of the apps neatly organized in the start menu. How do I do that?
Click to expand...
Click to collapse
There are several methods that can be used to get shortcuts over to the Start Menu. One method is to copy .LNK files from the .\Windows folder to the .\Windows\Start Menu using a file called INITFLASHFILES.TXT.
Another method uses a .PROVXML file to perform copy operations, once again, .LNK files are copied from the .\Windows folder to the .\Windows\Start Menu.
Some chefs may choose to leave the processing actions in each package, others prefer to consolidate shortcut processing to a "master" package.
HTH,

---

hilaireg said:
Great idea, here's to hoping it catches on. Eventually, you may want to change the title of the thread to something [FAQ] Commonly Asked Questions, [Q&A] ROM Cooking Techniques, etc. Could be a great candidate for the Useful Links thread (i.e. sticky).
On to your question ...
There are several methods that can be used to get shortcuts over to the Start Menu. One method is to copy .LNK files from the .\Windows folder to the .\Windows\Start Menu using a file called INITFLASHFILES.TXT.
Another method uses a .PROVXML file to perform copy operations, once again, .LNK files are copied from the .\Windows folder to the .\Windows\Start Menu.
Some chefs may choose to leave the processing actions in each package, others prefer to consolidate shortcut processing to a "master" package.
HTH,
Click to expand...
Click to collapse
This doesnt really answer his question hehe. He is asking how to move files that already in the startmenu.
As fare as i know there are 3 methods that you can use(i know there are more but these are the ones i know of).
1. Via program that will move them...like NueLinks
2. Via proxml, tho proxml's are very complicated and one mistake will kill the whole proxml.
3. & Easies way imo is with the use of MortScript, which is what i do.
Just use a mort oem or install mortscript via autorun then exec the mortscript to move the files. here is an example of hte mort command.
Code:
If ( FileExists( "\Windows\Start Menu\Programs\Office Mobile\Start_Icon_Office.lnk" ) )
Move( "\Windows\Start Menu\Programs\Office Mobile\Start_Icon_Office.lnk","\Windows\Start Menu\Programs\Programs\Office","TRUE" )
EndIf
first you have the If which checks to see if the file exists, if it does then it Moves it to a set dir. If the file is not there it just moves on to next function in mort file.

---

jug6ernaut said:
This doesnt really answer his question hehe. He is asking how to move files that already in the startmenu.
Click to expand...
Click to collapse
You are correct, hence the:
On to your question ...
Click to expand...
Click to collapse
... had hoped a seasoned chef would jump in.
Cheers,

---

You also have to remember that some if not most of the files are write protected, so if you use a mortscript(I also just started using these too) you have to set the file property so it is not read only. This might only apply to links you want to delete, but I have a script that covers most of the common links in the programs folder. I have a cab install my links that have custom icons, so if it does not overwrite the original you will have 2. I like my programs all in folders and organized, so I delete all of the links inside of start menu\programs\ an just use my cab with custom icons to install links. I've attatched my script for Da_G's 21042 kitchen(I actually only use the SYS\XIP) that you can use as a base. It also does some cleanup of extra files, but you can delete that part if you dont need it. I started out by cooking the ROM, flashing, then I go through and write the script to cover all the links I need changed or deleted. Then I test the script before cookin it into a ROM, this way you know what is going to happen I have a different way of writing mine tha Juggernaut, but still effective.
Just have it run near the end of your configuration as:
Code:
EXEC:\windows\cleanup.mscr
Also, a good way to do it which is probably what a pro would say is to get to the root of the shortcuts in the initflashfiles.dat file. It stores where shortcuts go and a lot more. I am actually going to give this one a try next time, as I just now remembered seeing those entries in there...duh. But it does not define where all shortcuts go, as there are plenty of provxml's and initflash.txt files. Lets see what the seasoned cooks have to say though, as I am just a young padawan myself

---

I've done it using a combo of setting things I want in the start menu in the initflashes in their packages and removing the stock stuff out of initflashes.dat (found in one of the oems, oem_lang_0409, I think). I don't believe it's absolutely necessary, but if you edit the initflashes.dat, afterwards you should open it up with a hex editor and remove the first two bytes (check before and after, and you'll see that there are two extra new bytes at the beginning after the edit). Anyway, this file has stuff like the phone, messaging and contact links in it that always appear in start menus.

---

Farmer Ted said:
I've done it using a combo of setting things I want in the start menu in the initflashes in their packages and removing the stock stuff out of initflashes.dat (found in one of the oems, oem_lang_0409, I think). I don't believe it's absolutely necessary, but if you edit the initflashes.dat, afterwards you should open it up with a hex editor and remove the first two bytes (check before and after, and you'll see that there are two extra new bytes at the beginning after the edit). Anyway, this file has stuff like the phone, messaging and contact links in it that always appear in start menus.
Click to expand...
Click to collapse
If you edit the initflashes.dat in the ervius visual kitchen (the one from Da_G's 6.5 kitchen), do you still have to edit out the first two bytes with a hex editor?

---

I don't think you actually need to do it; I just read about it in the blackstone cooking thread. Apparently, with some of the older devices you had to do it, but you may be able to let it slide with the newer ones. I downloaded a hex editor and wanted an excuse to use it, so I personally deleted the two bytes when I edited the .dat file. I'm using At0m's kitchen; can't speak for Da_G's. FWIW, it's a real simple thing to do (heck, get the hex editor package and you can do it on your phone).
Oh, and jmckeejr's cleanup script is very nice. Glad he explained about the first part (setfilattribs....). You need to do that if you want to delete most links or .txt files, as a lot of them are read-only. (I'm also a noob, lol, but figured I might as well contribute where I can. Hopefully the pros will answer the tough ones.)

---

Another way is using the *.provxml like :
Code:
<wap-provisioningdoc>
<characteristic type="Registry">
<characteristic type="HKLM\SOFTWARE\HTC\AutoShortcut">
<parm name="\Windows\Start Menu\Programs\Adobe Reader LE.lnk" value="\Windows\Adobe Reader LE.lnk" datatype="string" translation="install"/>
</characteristic>
</characteristic>
</wap-provisioningdoc>
to sort :
Code:
<characteristic type="Registry">
<characteristic type="HKLM\SOFTWARE\HTC\AutoShortcut">
<parm name="\Windows\Start Menu\Programs\[B]Whatever[/B]\Adobe Reader LE.lnk" value="\Windows\Adobe Reader LE.lnk" datatype="string" translation="install"/>
</characteristic>
</characteristic>
</wap-provisioningdoc>
I hope this helps but I dont use this way (i hope this will clear a bit for hilaireg's post)

---

monx® said:
Another way is using the *.provxml like :
Code:
<wap-provisioningdoc>
<characteristic type="Registry">
<characteristic type="HKLM\SOFTWARE\HTC\AutoShortcut">
<parm name="\Windows\Start Menu\Programs\Adobe Reader LE.lnk" value="\Windows\Adobe Reader LE.lnk" datatype="string" translation="install"/>
</characteristic>
</characteristic>
</wap-provisioningdoc>
to sort :
Code:
<characteristic type="Registry">
<characteristic type="HKLM\SOFTWARE\HTC\AutoShortcut">
<parm name="\Windows\Start Menu\Programs\[B]Whatever[/B]\Adobe Reader LE.lnk" value="\Windows\Adobe Reader LE.lnk" datatype="string" translation="install"/>
</characteristic>
</characteristic>
</wap-provisioningdoc>
I hope this helps but I dont use this way (i hope this will clear a bit for hilaireg's post)
Click to expand...
Click to collapse
what do you use monx? teach us ur ways!

---

jug6ernaut said:
what do you use monx? teach us ur ways!
Click to expand...
Click to collapse
nothing special mate, just the oldest method. initflashfiles.txt in each oem folder. So I only use minimum *.provxml (I also removed autoshortcut.exe )

---

monx® said:
nothing special mate, just the oldest method. initflashfiles.txt in each oem folder. So I only use minimum *.provxml (I also removed autoshortcut.exe )
Click to expand...
Click to collapse
ahh ic (i hate proxml's and will never touch them ). it toke me a while to figure out that autoshortcut.exe was putting .lnks in the startmenu(many headakes in the process hehe).
Glad to see your still around and spreading ur wise wisdom .

---

I prefer to keep the shortcuts with the respective package ... makes it easier to hand-off the package to other folks who might like to use it.
I have obtained packages where INITFLASHFILES.XML contains the operations, others where .PROVXML contains the actions, and then others where they use a hybrid of both. In my custom configuration kitchen package, I almost exclusively use .PROVXML to apply registry settings or changes to attributes on files.
@dwmackay:
So there you have it, a comprehensive answer to a "simple" question. Some excellent (seasoned) masters have shared their experiences and recommendations. I've picked up some great tips and I'll be interested in reading the responses on the next question(s).
What an awesome community!

---

Thanks for the detailed answers. I may have concluded that this is above my pay grade. I'll read through the details more carefully and see what I can figure out.
Thanks again,
Doug M.

---

i'd go for monx way allthough i see no difference in the two pieces of code , it is the best way.
that way you keep the oem-packages clean and won't end up with unnecessary shortcuts.. besides u wont need install mortscript

---

Even if I didn't use the mortscript way, I would cook it in. Mortscript can be a very powerful thing, and its only a little more than 1MB so good to put it in either way. I personally use Sashimi to autoinstall and import Registry and what not, so I cook it in and all of my programs and settings are auto. I can flash a ROM now, and have it set up within 5-10 minutes(after initial customization runs). Sashimi relies on mortscript, so good to have it in there. You can add Sashimi compliance and UC, so why not add them both? I would try a lot more ROMs if they were Sashimi compliant, and I'm sure others feel the same. Just a headsup for cooks. It takes almost no extra effort to add one line to your config_operator.txt, and include a mortscript in your operator Package.
This is a good thread. I have a question, not really a cooking question more of a preference question. What PagePool have you found to be the best for you? I tried a bunch of different settings, and haven't found a huge difference so I usually set mine at 16-18MB which leaves more free RAM than say 24MB. I there any relation between pagepool and battery usage? I found my battery life to be better when pagepool was set a little lower, but wondering how others feel about it. Stands to reason that a lower pagepool would mean a smaller memory footprint therefore better battery. Am I wrong here?

---

jmckeejr said:
Even if I didn't use the mortscript way, I would cook it in. Mortscript can be a very powerful thing, and its only a little more than 1MB so good to put it in either way. I personally use Sashimi to autoinstall and import Registry and what not, so I cook it in and all of my programs and settings are auto. I can flash a ROM now, and have it set up within 5-10 minutes(after initial customization runs). Sashimi relies on mortscript, so good to have it in there. You can add Sashimi compliance and UC, so why not add them both? I would try a lot more ROMs if they were Sashimi compliant, and I'm sure others feel the same. Just a headsup for cooks. It takes almost no extra effort to add one line to your config_operator.txt, and include a mortscript in your operator Package.
This is a good thread. I have a question, not really a cooking question more of a preference question. What PagePool have you found to be the best for you? I tried a bunch of different settings, and haven't found a huge difference so I usually set mine at 16-18MB which leaves more free RAM than say 24MB. I there any relation between pagepool and battery usage? I found my battery life to be better when pagepool was set a little lower, but wondering how others feel about it. Stands to reason that a lower pagepool would mean a smaller memory footprint therefore better battery. Am I wrong here?
Click to expand...
Click to collapse
500kbs if u use an oem , i <3 mortscript.
umm i recently heard 16mb pp is the best from benchmarks.

---

The difference is the "whatever" part. Can't say I'm a seasoned chef but messing with provxmls is really not that hard as long as you don't move or rename them. I've been cleaning up my entire start menu every time da_G released a new kitchen and I made a folder with the files that I have changed before and need to insert to get a clean startmenu:
- initflashfiles.dat
- mxip_HtcApps_translation.provxml (this is for the settings menu)
- mxip_MyPhone_100.provxml
- mxipupdate_office_100.provxml
- mxipupdate_onenote_100.provxml
- mxipupdate_PACKAGE_Raphael_CAMERA_0409.provxml
- mxipupdate_windowslive_1.provxml
- mxipupdate_windowsliveim_1.provxml
, 12

---

Same here,
I have a '01_PACKAGE_CUSTOMIZED' where I have a copy of the OEMOPERATORS .provxml, .DLL's or .EXE's that should take precedence over those in a package, and custom images/sounds.
PackageBuildOS 5.3 processes the contents of this package before the others ('01_') ... not sure if this will still work /w the New Style Kitchen as I haven't tried it yet.
Added benefits include:
- Not messing around as much with other packages
- Not messing around as much with OEM and SYS
- Quick to test a .DLL/.EXE for compatibility during a test ROM cook
It doesn't address configuration entries that appear in multiple .PROVXML's (or .RGU's) but it sure helps me track down the culprit if I see that my changes aren't present.
Cheers,