Database Users

[SOLVED] How to cook in a set of folders with duplicate files

Ok heres my dilema:
I wan't to cook in loads of manila files, but theres a few different versions of each one, and they aren't going into windows.
its better I explain it, heres an example:
Root Folder
\Folder 1
¬FileX
\Folder 2
¬FileX
\Folder 3
¬FileX
How can I do this? is I cant put the same file (FileX) in the files folder of a package as it has the same file name... The only way I can think of is to have a seperate package for each invidual file, and considering theres over 40 files, its going to take a long time!
Are there anymore efficient ways to do this? Thanks
SOLVED: AIRXTREME HAS MADE A UTILITY FOR CHEFS TO FIX THIS VERY PROBLEM:
[GET IT HERE]
THANKS AIRXTREME!!!

[★] said:
Ok heres my dilema:
I wan't to cook in loads of manila files, but theres a few different versions of each one, and they aren't going into windows.
its better I explain it, heres an example:
Root Folder
\Folder 1
¬FileX
\Folder 2
¬FileX
\Folder 3
¬FileX
How can I do this? is I cant put the same file (FileX) in the files folder of a package as it has the same file name... The only way I can think of is to have a seperate package for each invidual file, and considering theres over 40 files, its going to take a long time!
Are there anymore efficient ways to do this? Thanks
Click to expand...
Click to collapse
If all these files go into "\Windows", there will be only one in the end ... not 40. Meaning the last "FileX" your kitchen finds will have overwritten all the others ...

You can't end up with all these files, without doing a little bit of legwork.
When you cook a ROM, all the files end up in \Windows, and are then moved around as required.
So, you could either cook all the files in with different names (so they don't overwrite) and then move them using a provxml or initflashfiles.dat, or you could cab up all the files, and run the cab after first boot.

The easiest way is to use a cab or to put everything in a zip file and use an 'inzipall' mortscript to unzip the folders wherever you want during customization.

Diegis0n said:
If all these files go into "\Windows", there will be only one in the end ... not 40. Meaning the last "FileX" your kitchen finds will have overwritten all the others ...
Click to expand...
Click to collapse
Yeah thats what I thought , althought I didnt know they went into windows first, thanks.
l3v5y said:
You can't end up with all these files, without doing a little bit of legwork.
When you cook a ROM, all the files end up in \Windows, and are then moved around as required.
So, you could either cook all the files in with different names (so they don't overwrite) and then move them using a provxml or initflashfiles.dat, or you could cab up all the files, and run the cab after first boot.
Click to expand...
Click to collapse
Hmm the cab sounds like a good aproach, although still I wouldn't be able to have more than one manila file with the same name in the cab.
Farmer Ted said:
The easiest way is to use a cab or to put everything in a zip file and use an 'inzipall' mortscript to unzip the folders wherever you want during customization.
Click to expand...
Click to collapse
hmm thats a good idea, could you point me to that script please

[★] said:
Yeah thats what I thought , althought I didnt know they went into windows first, thanks.
Hmm the cab sounds like a good aproach, although still I wouldn't be able to have more than one manila file with the same name in the cab.
Click to expand...
Click to collapse
Cab files do allow you to specify the paths, so they do allow you to have files with the same name. WinCE CAB Manager is a good choice to create cabs. You can then use RunCC / Autorun/ XDA_UC to install it during the first boot.

[★] said:
hmm thats a good idea, could you point me to that script please
Click to expand...
Click to collapse
Just take a look at this package; it has a zip file, a mortscript, and the add2config that you need. Here's a mortscript package that you can use.

You could also rename the files for example "1_FileX", "2_FileX" and have initflashfiles.dat rename it to the filename you want it to be, like so:
Directory("\Folder_1"):-File("FileX","\Windows\1_FileX")
Directory("\Folder_2"):-File("FileX","\Windows\2_FileX")
Click to expand...
Click to collapse
But that would really clog up your ROM, so the mortscript way is better.

ock said:
Cab files do allow you to specify the paths, so they do allow you to have files with the same name. WinCE CAB Manager is a good choice to create cabs. You can then use RunCC / Autorun/ XDA_UC to install it during the first boot.
Click to expand...
Click to collapse
Yes but putting the files in will overwrite eachother, as they have to have the same file name
Farmer Ted said:
Just take a look at this package; it has a zip file, a mortscript, and the add2config that you need. Here's a mortscript package that you can use.
Click to expand...
Click to collapse
Thanks I dont understand what the mortscript for is (the one from 4shared) but Im using the add2config package, I think I get it I will let you know when its finished cooking. Although I am having a problem where none of my add2config packages are working so it might be useless
seeM_ZA said:
You could also rename the files for example "1_FileX", "2_FileX" and have initflashfiles.dat rename it to the filename you want it to be, like so:
But that would really clog up your ROM, so the mortscript way is better.
Click to expand...
Click to collapse
Yeah but the files have to keep the same name

You need mortscript support cooked into your rom one way or another if you're going to use zip files; that's what the 4shared package is for.

l3v5y said:
So, you could either cook all the files in with different names (so they don't overwrite) and then move them using a provxml or initflashfiles.dat
Click to expand...
Click to collapse
+1 for this...

ai6908 said:
+1 for this...
Click to expand...
Click to collapse
That's ok if you're talking a couple of files, but if you're talking a few dozen (or more), then putting together all the initflashes scripts will get tedious.

Farmer Ted said:
That's ok if you're talking a couple of files, but if you're talking a few dozen (or more), then putting together all the initflashes scripts will get tedious.
Click to expand...
Click to collapse
Did you get my message?
and yeah, it seems your mortscript may be easier If I can get add2config to work lol

SOLVED: AIRXTREME HAS MADE A UTILITY FOR CHEFS TO FIX THIS VERY PROBLEM:
[GET IT HERE]
THANKS AIRXTREME!!!

[Q] about cooking gameloft games to hd2

Default Trouble Cooking
I am trying to add Gameloft games that I have bought to my os kitchen. I am having trouble getting NBA 2010, Midnight bowling 2, and Avalanche Snowboarding to launch. I have all of the file in the correct places and they all show in in the rom after it has finished cooking but they dont launch either from the start menu or the programs files folder. I am hoping that if some could help me figure this out, and in the process help others who could have the same problem.
i used CABTOEXT And Package to ext the edited the appdata with xml maker. then i tried with out editing the appdata and nothing. i will be willing to compansate for the fix

I think it's better to make EXT's from scratch instead of using a cab-2-package creator. There may be registry keys added by a setup.dll that you miss, or that are added after launching the app or a soft reset. Here's how I do it (you need sk tracker):
Do a scan with sk tracker.
Install the cab.
Scan again.
Launch the program, enter any codes or settings.
Scan again.
Now, do comparisons of the scans, and find all the new files and registry keys. Export the reg keys to an app.reg file. You can generally ignore the HKLM\Software\Apps and appinstall keys-these are just keys that allow the device to uninstall the cab. Occasionally, the install directory key is needed, but usually not. Definitely leave out the files in \windows\appmgr, that's just un-install info.
Next, don't bother with getting the program loaded into its own folder in \program files. That's usually a waste, because most apps work straight out of \windows. Exe's search for resources first in their own folder and then in \windows most of the time, so if you put the .exe and everything else in windows, you're good to go. If there are sub-folders, then the sub-folders need to be loaded into \windows\ as a sub-folder (I personally use zip files/mortscripts to do it, but a cab will work as will initflashfiles.dat). You have to be careful about settings files, particularly .ini's. They do not like being read-only, and this may be why your game doesn't launch. So, if you have an .ini file, or a settings.txt file, or a game.dat file (or similar), you need to load it into \windows or wherever so it's not read-only. Personally, if I have sub-folders going into windows, I'll create a zip file that sends the .ini, .dat or .txt file into \windows as an archive file, but you can also use initflashfiles.dat to create a copy wherever you want that isn't read-only.
If you change the install directory from program files to windows, then you may need to look into the .reg keys and change some paths. Also, you'll need to change any shortcut paths to \windows\game.exe. Putting things directly in windows saves memory, and you can also convert files to modules to take advantage of the increase VM slots with native 6.5 kernels. It all comes down to experimentation, though.

Thanks for the info, but all of the reg entrys were either in the hklm\security\appsinstall or the hklm\software\apps, andi i entered them and still nothing. I have never worked with mortscript, I did look for a tutorial but couldn't understand all of what they were saying is there a video tutorial, or another soultion?

Did you check to see if any settings-type files are read-only? That will kill a game for sure, and they usually save user data in files (not the registry).

I appericeate your willingness to help a noob, and thank you. how do I check to see if they are read only, how do I make shure that they are what they need to be during the cooking process?
all of the files for one of the games are as follows
Avalanche Snowboarding.exe
data.bar------------------this one Program Files\Gameloft\Game name
GetRealDPI.exe------------------this one Program Files\Gameloft\Game name
icon_45x45.png------------------this one Program Files\Gameloft\Game name
icon_60x60.png------------------this one Program Files\Gameloft\Game name
icon_90x90.png------------------this one Program Files\Gameloft\Game name
Installer.dll------------------this one Program Files\Gameloft\Game name
STPA001.DLL---------------------------this one is in windows\ appmgr
60DE.tmp---------------------------this one is in windows\ appmgr
Avalanche Snowboarding.lnk------------------this one Windows\start menu\ programs\Games
the structure of each game is very simalier, except for midnight bowling 2 which has no icon.png in the gameloft file after install.
Which one look s like the suspect for tha data file\needs not to be read only?

do the games work when you install them as a cab? after you cook your rom and you say they wont launch, have you tried installing them as cabs and see if that fixes it? if so you know its a problem with your pkg and not something else in your rom. basically what farmer ted is saying is that you can make your own package by installing the cab and then exporting all the installed files/reg and putting them in your kitchen with app.dat to put them in the right places i think this is your best bet.

Data.bar is probably the game store; just check the file properties with total commander. If it's read-only, then uncheck it.
Get rid of the two appmgr files; those are just uninstall junk, and you don't need to cook them in. You only need one of the 3 icons in all likelihood. They're start menu icons, right? Just use the one that is in the startinfo/icon reg key, and leave out the other two. I kind of doubt you need installer.dll or the getrealdpi.exe as well. It seems like those just run the install. Speaking of which, this is probably where you're screwing up. Did you just dump this stuff from the .cab with a package creator? It seems like you have files for a partially installed app. Probably, the cab installs the 'getrealdpi.exe', and that process runs and figures out your device resolution, then the installer.dll decides what files to install or maybe sets reg keys for the proper resolution. I'm not sure that you have everything you need in your package. I suspect this is the source of your problem, more so than having a settings file marked as 'read-only.'
Edit: cough, cough, I know a little more about the game now (not saying how). Data.bar is a resource file (a big one). You need it, obviously. The settings files are .sav files (2 of them, as far as I can see). They're created after you launch the game. The only two files you really need are the avalanche snowboarding.exe and the data.bar file. Do this: stick them in an EXT, and don't use an app.reg file. Just send them to \windows. Send the shortcut to the games folder, but you'll need one with the proper path. You can make the shortcut by putting the following in a .txt file and changing the extension to .lnk.
Code:
1#"\Windows\Avalanche Snowboarding.exe"
Name it whatever you want.
Long story short: put the two files in a package. Screw the icon.png, they're a huge frickin waste, imo. Then use an app.reg to send the shortcut (also in the package) to the games folder. If you want to back up user data, save the .sav files and copy them into \windows after flashing. It should work.

Farmer Ted said:
Data.bar is probably the game store; just check the file properties with total commander. If it's read-only, then uncheck it.
Get rid of the two appmgr files; those are just uninstall junk, and you don't need to cook them in. You only need one of the 3 icons in all likelihood. They're start menu icons, right? Just use the one that is in the startinfo/icon reg key, and leave out the other two. I kind of doubt you need installer.dll or the getrealdpi.exe as well. It seems like those just run the install. Speaking of which, this is probably where you're screwing up. Did you just dump this stuff from the .cab with a package creator? It seems like you have files for a partially installed app. Probably, the cab installs the 'getrealdpi.exe', and that process runs and figures out your device resolution, then the installer.dll decides what files to install or maybe sets reg keys for the proper resolution. I'm not sure that you have everything you need in your package. I suspect this is the source of your problem, more so than having a settings file marked as 'read-only.'
Edit: cough, cough, I know a little more about the game now (not saying how). Data.bar is a resource file (a big one). You need it, obviously. The settings files are .sav files (2 of them, as far as I can see). They're created after you launch the game. The only two files you really need are the avalanche snowboarding.exe and the data.bar file. Do this: stick them in an EXT, and don't use an app.reg file. Just send them to \windows. Send the shortcut to the games folder, but you'll need one with the proper path. You can make the shortcut by putting the following in a .txt file and changing the extension to .lnk.
Code:
1#"\Windows\Avalanche Snowboarding.exe"
Name it whatever you want.
Long story short: put the two files in a package. Screw the icon.png, they're a huge frickin waste, imo. Then use an app.reg to send the shortcut (also in the package) to the games folder. If you want to back up user data, save the .sav files and copy them into \windows after flashing. It should work.
Click to expand...
Click to collapse
I am Trying now.

twopumpchump said:
do the games work when you install them as a cab? after you cook your rom and you say they wont launch, have you tried installing them as cabs and see if that fixes it? if so you know its a problem with your pkg and not something else in your rom. basically what farmer ted is saying is that you can make your own package by installing the cab and then exporting all the installed files/reg and putting them in your kitchen with app.dat to put them in the right places i think this is your best bet.
Click to expand...
Click to collapse
yes the cabs work after i cook, the problem seems to be in the package.

JMM2009 said:
I am Trying now.
Click to expand...
Click to collapse
No Dice, any other suggestions?

Have you tried just clicking on the .exe instead of the shortcut? This should be working.
Edit: ok, I was getting tricked. This game only works when the .bar file is in \program files\Gameloft\Avalanche Snowboarding. Make sure you have the folders named correctly-when I changed it to game loft, the game wouldn't launch. The .exe can be in \windows. I guess the search path for the .bar file is hard-coded to the one folder.

I put them in the Program Files\Gameloft\Game Name and I got one working, Brain Challenge 3. But of the four games I am trying to install I have only been able to get one working at best during any time I have been cooking, could it be possible that the app.dat file that I have for the file path is overwriting the data.bar. This is what I have in each app.dat file
Directory("\Program Files\"):-Directory("Gameloft")
Directory("\Program Files\Gameloft\"):-Directory("Avalanche Snowboarding")
Directory("\Program Files\Gameloft\Avalanche Snowboarding"):-File("Avalanche Snowboarding.exe","\Windows\Avalanche Snowboarding.exe")
Directory("\Program Files\Gameloft\Avalanche Snowboarding"):-File("data.bar","\Windows\data.bar")
Directory("\Windows\Start Menu\Programs\Games"):-File("Avalanche Snowboarding.lnk","\Windows\Avalanche Snowboarding.lnk")
could the fact that I am creating a new gameloft folder with each game be screwing me up?

D'oh, that's definitely it! You need to work around that. Name them data1.bar, data2.bar..., then have the app.dat files rename them to data.bar when it copies them. Lol, glad it's figured out.
Edit: here's a dummy package that I would try out if I were you. It has mortscript included and all the necessary reg keys. What you need to do is to add your .exe's to the \Files folder, then add the data.bar files to the game folders inside the zip file. Basically, create a zip file with this structure: \Program Files\Gameloft\individual game folders\ and put the data.bar files in each corresponding game folder. Make sure the names are correct on the folders. Zip it up, and make sure the paths are correct, just like the way I have it, although I don't know the game names.
Then, look in the UnzipGameloft.mscr file with a text editor. Edit the .exe names in each of the 'createshortcut' commands to the name of the exe (exactly). You can call the .lnks whatever you want. The mortscript will create the shortcuts, so don't bother with putting shortcuts in the folder. Also, the package has a script to back up user data for all of the games. This is only going to work if the .sav files are created in \windows, and not in the stupid program folders (you can write a script to back up the games in that case, but it's more of a pain). During customization, the zip file is unzipped, the shortcuts are created, and the user data is restored.

what do you use to make your pkgs???
OMG i would like to get rid of the windows files with the one in program files...
Does this MSCR pkg can do that you know this is a case of double files in windows and in progranfiles
Edited

Farmer Ted said:
D'oh, that's definitely it! You need to work around that. Name them data1.bar, data2.bar..., then have the app.dat files rename them to data.bar when it copies them. Lol, glad it's figured out.
Edit: here's a dummy package that I would try out if I were you. It has mortscript included and all the necessary reg keys. What you need to do is to add your .exe's to the \Files folder, then add the data.bar files to the game folders inside the zip file. Basically, create a zip file with this structure: \Program Files\Gameloft\individual game folders\ and put the data.bar files in each corresponding game folder. Make sure the names are correct on the folders. Zip it up, and make sure the paths are correct, just like the way I have it, although I don't know the game names.
Then, look in the UnzipGameloft.mscr file with a text editor. Edit the .exe names in each of the 'createshortcut' commands to the name of the exe (exactly). You can call the .lnks whatever you want. The mortscript will create the shortcuts, so don't bother with putting shortcuts in the folder. Also, the package has a script to back up user data for all of the games. This is only going to work if the .sav files are created in \windows, and not in the stupid program folders (you can write a script to back up the games in that case, but it's more of a pain). During customization, the zip file is unzipped, the shortcuts are created, and the user data is restored.
Click to expand...
Click to collapse
Ok Renaming didn't do the trick, so I am trying the mortscript method, have the exe in the first gameloft.zip then I have put the data.bar file in the folders that contain there name, I edited the unzipgameloft file with the creat shortcutlinks. now my question is this the gameloft zip withen the bundled files you sent, does this need to be renamed or can I drop it in my kitchen?
as of right now I am using OS kitchen, I tried cooking them in, which didn't work. then I tried pausing then adding the file, but I thought i remembered reading somewhrer that you need to pause before it reads the dump file however I dont have that ability I can onlt pause before the platform builder runs do I need to use a different kitchen, or should cooking them in or add them before the platform builder work?

Now this is funny
I tried to cook the games in with renaming data1 data2 ect... then I cooked, when the rom loaded I went to program files\gameloft folder and renamed each data.bar back to what it was, and they WORK thats good, now all i need to figure out is how to get each of those files to be renamed during the cooking processes or during the start up customazation. am I correct in thinking this, is it possiable?

JMM2009 said:
I tried to cook the games in with renaming data1 data2 ect... then I cooked, when the rom loaded I went to program files\gameloft folder and renamed each data.bar back to what it was, and they WORK thats good, now all i need to figure out is how to get each of those files to be renamed during the cooking processes or during the start up customazation. am I correct in thinking this, is it possiable?
Click to expand...
Click to collapse
You can edit app.dat and change the destination file name to do that.
Directory("DESTINATIONFOLDER"):-File("DESTINATIONFILENAME","\Windows\SOURCEFILENAME")

airxtreme said:
You can edit app.dat and change the destination file name to do that.
Directory("DESTINATIONFOLDER"):-File("DESTINATIONFILENAME","\Windows\SOURCEFILENAME")
Click to expand...
Click to collapse
It didn't rename it, it did however allow windows to overwrite the other data.bar files so it looks like it will have to be done during the customization

JMM2009 said:
It didn't rename it, it did however allow windows to overwrite the other data.bar files so it looks like it will have to be done during the customization
Click to expand...
Click to collapse
I suggest you to leave the cab as it is and add it in the config.txt file for Autorun (with an add2config.txt file): using cab2ext when the application has to stay in program files can make the first boot a little quicker but it's going to waste more imgfs space because the files are not compressed (also with CABs you can uninstall the game in case you need). If you still want to cook it in as an expanded package you just have to use the kitchen package converter, rename all the package files adding an identifier in front of it like "gamename_" different for each game and edit the initflashfile changing the source file name with the one with the prefix. That should do it.

airxtreme said:
I suggest you to leave the cab as it is and add it in the config.txt file for Autorun (with an add2config.txt file): using cab2ext when the application has to stay in program files can make the first boot a little quicker but it's going to waste more imgfs space because the files are not compressed (also with CABs you can uninstall the game in case you need). If you still want to cook it in as an expanded package you just have to use the kitchen package converter, rename all the package files adding an identifier in front of it like "gamename_" different for each game and edit the initflashfile changing the source file name with the one with the prefix. That should do it.
Click to expand...
Click to collapse
What kitchen package convertor do you reccomned?

[Resolved] Tcpmp issue

Guys, Can't seem to get TCPMP to work in my Custom ROM. I know there are some Regs that are not being applied when cooking as the ROMs accept only Cab installed TCPMP to play. Can someone please share their working TCPMP or tell me how to tweak it to work when cooked. I know NRGZ has one working in his ROM and others out there so, plz share before we start thinking of other xtreme ways....LOL!

Try the one in post 1.
http://forum.xda-developers.com/showthread.php?t=670465
One issue with tcpmp is that is uses a dll named common.dll. The package I use puts tcpmp in windows-the dll goes there, too. Make sure it isn't over-written by a dll of the same name from another package. OMarket also uses a common.dll, so if you cook both into windows, only one will work.

Farmer Ted said:
Try the one in post 1.
http://forum.xda-developers.com/showthread.php?t=670465
One issue with tcpmp is that is uses a dll named common.dll. The package I use puts tcpmp in windows-the dll goes there, too. Make sure it isn't over-written by a dll of the same name from another package. OMarket also uses a common.dll, so if you cokk both into windows, only one will work.
Click to expand...
Click to collapse
Thanks Man, Appreciate. Downloading now will report after cooking at home tonite

Farmer Ted said:
Try the one in post 1.
http://forum.xda-developers.com/showthread.php?t=670465
One issue with tcpmp is that is uses a dll named common.dll. The package I use puts tcpmp in windows-the dll goes there, too. Make sure it isn't over-written by a dll of the same name from another package. OMarket also uses a common.dll, so if you cokk both into windows, only one will work.
Click to expand...
Click to collapse
Tough going mate. Its crushing my platformrebuilder...

Look at your build-log, and make sure you don't already have any of the modules in the package (common.dll, WMADMOD.DLL, WMSDMOD.DLL, WMVDMOD.DLL). I have a feeling you're already cooking in a common.dll, and that's why the package you were using before wouldn't work; over-writing it with another module could cause prb to crash.
Edit: Also, make sure there aren't any registry parsing errors. I've gotten them for the DLL Path key before, although EVK normally just ignores the problem. I might have dumped those keys with total commander, and it doesn't get the path right (either too many or not enough '\'s). You can just delete those keys, if they're causing issues.
You really don't even need the reg file; tcpmp just loads a default set of keys if HKLM\TCPMP is empty. The only key you really want is the one for the skin file (\windows\skin.xml).
You can also try out the Uzard package posted a little later in the thread. It has a combo of Uzard browser/TCPMP. If you don't want the browser, just dump it. The tcpmp reg keys should be fine in that one.

Farmer Ted said:
Look at your build-log, and make sure you don't already have any of the modules in the package (common.dll, WMADMOD.DLL, WMSDMOD.DLL, WMVDMOD.DLL). I have a feeling you're already cooking in a common.dll, and that's why the package you were using before wouldn't work; over-writing it with another module could cause prb to crash.
Edit: Also, make sure there aren't any registry parsing errors. I've gotten them for the DLL Path key before, although EVK normally just ignores the problem. I might have dumped those keys with total commander, and it doesn't get the path right (either too many or not enough '\'s). You can just delete those keys, if they're causing issues.
You really don't even need the reg file; tcpmp just loads a default set of keys if HKLM\TCPMP is empty. The only key you really want is the one for the skin file (\windows\skin.xml).
You can also try out the Uzard package posted a little later in the thread. It has a combo of Uzard browser/TCPMP. If you don't want the browser, just dump it. The tcpmp reg keys should be fine in that one.
Click to expand...
Click to collapse
Thanks, will try again after I get it to go past first boot screen. The Packages have messed up my Kitchen, I am trying to reset it again.

Farmer Ted said:
Look at your build-log, and make sure you don't already have any of the modules in the package (common.dll, WMADMOD.DLL, WMSDMOD.DLL, WMVDMOD.DLL). I have a feeling you're already cooking in a common.dll, and that's why the package you were using before wouldn't work; over-writing it with another module could cause prb to crash.
Edit: Also, make sure there aren't any registry parsing errors. I've gotten them for the DLL Path key before, although EVK normally just ignores the problem. I might have dumped those keys with total commander, and it doesn't get the path right (either too many or not enough '\'s). You can just delete those keys, if they're causing issues.
You really don't even need the reg file; tcpmp just loads a default set of keys if HKLM\TCPMP is empty. The only key you really want is the one for the skin file (\windows\skin.xml).
You can also try out the Uzard package posted a little later in the thread. It has a combo of Uzard browser/TCPMP. If you don't want the browser, just dump it. The tcpmp reg keys should be fine in that one.
Click to expand...
Click to collapse
Thanks, will try again after I get it to go past first boot screen. The Packages have messed up my Kitchen, I am trying to reset it again.
even after removing them Rom won't boot up after customisations. Wierd

Hi,
the attached TCPMP Package works fine for me.
with friendly greet
starbase64

starbase64 said:
Hi,
the attached TCPMP Package works fine for me.
with friendly greet
starbase64
Click to expand...
Click to collapse
Thanks Mate. I am cooking it in right now.
Edit: Just cooked it in and I confirm that its working, even with OMarket's Common.dll in the Rom. Thanks a million starbase64 >>>Issue now closed.

So common.dll was the problem? I knew it, lol.
You could save rom space by cooking tcpmp straight into rom and putting OMarket into \Program Files either with a cab or a zip install. The other way to do it is with an app.dat file, but you need to name common.dll (for OMarket) something like 000-common.dll in rom and have it renamed to common.dll when it is copied to the new location by initflashfiles.dat. That way, you won't have two different files named common.dll in conflict w/ each other during cooking, with one over-writing the other.

Farmer Ted said:
So common.dll was the problem? I knew it, lol.
You could save rom space by cooking tcpmp straight into rom and putting OMarket into \Program Files either with a cab or a zip install. The other way to do it is with an app.dat file, but you need to name common.dll (for OMarket) something like 000-common.dll in rom and have it renamed to common.dll when it is copied to the new location by initflashfiles.dat. That way, you won't have two different files named common.dll in conflict w/ each other during cooking, with one over-writing the other.
Click to expand...
Click to collapse
noted.thanks for all the help man!
peace.

Well, I remember the first time I cooked omarket in, and I was left wondering why the hell tcpmp no longer worked. I wish that developers wouldn't name there modules and files with such bland names. I'm pretty much maxed out on files named settings.txt, settings.cfg, settings.ini, settings.config and settings.xml right now in my windows folder. One more, and I'll be screwed. Oh, wait, I've got a settings.db in there, too, lol.

[Q] Unsigned Folders ?

First of all, sorry for openeing a new thread; but surely i have searched all of chef central din't find anything much or maybe din't understand which one was my solution.
The problem is after boot of my ROM ( regardless of which boot ie 1st 2nd or 10th ) i get 2 pop up errors:
1) "The file 'programs' cannot be opened. Either is not signed with a trusted certificate or one of it's components cannot be found.If the problem persists please try reinstalling or restoring this file."
2) "The file 'Tools' cannot be opened. Either is not signed with a trusted certificate or one of it's components cannot be found.If the problem persists please try reinstalling or restoring this file."
I have a folder called "Tools" in the start menu, and it works fine, and everything inside also works good. But still this error.
I'm pretty sure all the Packages cooked which are meant to go in this folder do go in.
And the programs error is it anything to do with the fact that in the APP.DAT in almost all packages i have used similar naming:
Code:
Directory("\Windows\Start Menu\Programs"):-Directory("System")
Directory("\Windows\Start Menu\Programs\Tools\Tweaks"):-File("Flip_IT.lnk","\Windows\_Flip_IT.lnk")
and also added similar REG in the REGS :
[HKEY_LOCAL_MACHINE\Security\Shell\StartInfo\Start\Tools\Tweaks\Flip_it.lnk]
Click to expand...
Click to collapse
As i was not sure which one will decide the location, so some packages have only .REGs, some have only APP.DATs and some have both ( but all the locations are same that is sure !)
Please help me with this.
Thanks alot.
PS: I have enabled NoCert in EVK, and also cooked in the latest ( 2015 ? ) SDKCerts EXT. And after that no other apps give an unsigned problem.

Just a question, this isnt the full app.dat right?
Code:
Directory("\Windows\Start Menu\Programs"):-Directory("System")
Directory("\Windows\Start Menu\Programs\Tools\Tweaks"):-File("Flip_IT.lnk","\Windows\_Flip_IT.lnk")
If yes, you miss some lines,this app.dat is just copying a link to startmenu but i guess that you need the program in Windows.

i'm afraid that is the full App.DAT
here is another one
Code:
Directory("\Windows\Start Menu\Programs"):-Directory("System")
Directory("\Windows"):-Directory("appdb")
Directory("\Windows\appdb"):-File("_end_mid_2.png","\Windows\_end_mid_2.png")
Directory("\Windows\appdb"):-File("_end_mid_8.png","\Windows\_end_mid_8.png")
Directory("\Windows\appdb"):-File("_folder_2.png","\Windows\_folder_2.png")
Directory("\Windows\appdb"):-File("_folder_8.png","\Windows\_folder_8.png")
Directory("\Windows\appdb"):-File("_folder_8_2.png","\Windows\_folder_8_2.png")
Directory("\Windows\appdb"):-File("_lock_gray.png","\Windows\_lock_gray.png")
Directory("\Windows\appdb"):-File("_lock_green.png","\Windows\_lock_green.png")
Directory("\Windows\appdb"):-File("_lock_red.png","\Windows\_lock_red.png")
Directory("\Windows\appdb"):-File("_logo_2.png","\Windows\_logo_2.png")
Directory("\Windows\appdb"):-File("_single_2.png","\Windows\_single_2.png")
Directory("\Windows\appdb"):-File("_single_8.png","\Windows\_single_8.png")
Directory("\Windows\appdb"):-File("_start_2.png","\Windows\_start_2.png")
Directory("\Windows\appdb"):-File("_start_8.png","\Windows\_start_8.png")
Directory("\Windows\appdb"):-File("_suite_2.png","\Windows\_suite_2.png")
Directory("\Windows\appdb"):-File("_suite_8.png","\Windows\_suite_8.png")
Directory("\Windows\appdb"):-File("_ack_2.png","\Windows\_ack_2.png")
Directory("\Windows\appdb"):-File("_ack_8.png","\Windows\_ack_8.png")
Directory("\Windows\appdb"):-File("_compiling.png","\Windows\_compiling.png")
Directory("\Windows\appdb"):-File("_disable_2.png","\Windows\_disable_2.png")
Directory("\Windows\appdb"):-File("_disable_8.png","\Windows\_disable_8.png")
Directory("\Windows\appdb"):-File("_dt_2.png","\Windows\_dt_2.png")
Directory("\Windows\appdb"):-File("_dt_8.png","\Windows\_dt_8.png")
Directory("\Windows\appdb"):-File("_dukeok_2.png","\Windows\_dukeok_2.png")
Directory("\Windows\appdb"):-File("_dukeok_8.png","\Windows\_dukeok_8.png")
Directory("\Windows\appdb"):-File("_empty.png","\Windows\_empty.png")
Directory("\Windows\appdb"):-File("_end_ams_2.png","\Windows\_end_ams_2.png")
Directory("\Windows\appdb"):-File("_end_ams_8.png","\Windows\_end_ams_8.png")
Directory("\Windows\appdb"):-File("_logo_8.png","\Windows\_logo_8.png")
Directory("\Windows\Start Menu\Programs\\Tools\System"):-File("Java.lnk","\Windows\Java.lnk")
This seems to be correct right ?
Can you please tell me does APP.DAT decide the position or REG ? and what if both exist.
Thanks.
Can an incomplete app.dat cause those errors ?
EDIT: i have identified 3 packages have incomlete app.dat
1) task manager
app.dat says :
Directory("\Windows\Start Menu\Programs\Tools\"):-File("Task Manager.lnk","\Windows\dotFred Task Manager.lnk")
Directory("\Windows\Start Menu\Programs\Tools\Utilities"):-File("Regeditor.lnk","\Windows\dotFred RegEdit.lnk")
Click to expand...
Click to collapse
reg also defines a location.
2) flip it
app.dat says
Directory("\Windows\Start Menu\Programs"):-Directory("System")
Directory("\Windows\Start Menu\Programs\Tools\Tweaks"):-File("Flip_IT.lnk","\Windows\_Flip_IT.lnk")
Click to expand...
Click to collapse
reg defines location and settings.
3) torch
app.dat says
Directory("\Windows\Start Menu\Programs\Tools\Utilities"):-File("hTorch Flashlight.lnk","\Windows\hTorch Flashlight.lnk")
Click to expand...
Click to collapse
reg defines settings only.
4) reg editor
app.dat says:
Directory("\Windows\Start Menu\Programs\Tool\Utilities"):-File("PHM RegEdit.lnk","\Windows\PHM RegEdit.lnk")
Click to expand...
Click to collapse
reg defines sttings and location.
Can anyone of the above cause the issue ?
can some please help me correct them ?
Thanks.
EDIT: can someone please tell me the REG to enable Call Waiting Tone.
I don't hear any tone it when i have a call waiting.

The app.dat decide the position of file and folders.
I found thi " Flip-IT" from a Tom Codon thread and i used Cab Converter for extracting it.
This is the App.dat that i got:
Directory("\Windows\Start Menu\Programs\Tools"):-File("Flip_IT.lnk","\Windows\Flip_IT.lnk")
Click to expand...
Click to collapse
In red are the subfolders that doesnt come with the original.
There are some difference with your but i dunno if this is the problem but worth try.

Umm well i have defined those locations as to fit them lnk in the place i want in the start menu.. isn't that the way ?

Im Quoting you from 1st post:
1) "The file 'programs' cannot be opened. Either is not signed with a trusted certificate or one of it's components cannot be found.If the problem persists please try reinstalling or restoring this file."
2) "The file 'Tools' cannot be opened. Either is not signed with a trusted certificate or one of it's components cannot be found.If the problem persists please try reinstalling or restoring this file."
you got this popup error automatically, no need to open any folder\file?
It seems that you put a wrong shortcut to files called "Tools and programs" in your StratUp folder.
Check some other App.dat

i have checked all APP.DAT in the EXT can't find any which i cook and does not get cokked in the correct location ?
Umm and the two errors are seperate not in one only.
So i guess the conflict is there with 2 seperate folders "Tools" and "programs" respectively.
Ideally it should not conflict with tools, because i do have a tools folder in the start menu.. so everything should go there :/
any other help?

Try to cook a rom without one of the latest apps that you have add and if the problem gone then you have find the issue,after that post here the responsable so we can look at it.
madnish30 said:
i have checked all APP.DAT in the EXT can't find any which i cook and does not get cokked in the correct location ?
Umm and the two errors are seperate not in one only.
So i guess the conflict is there with 2 seperate folders "Tools" and "programs" respectively.
Ideally it should not conflict with tools, because i do have a tools folder in the start menu.. so everything should go there :/
any other help?
Click to expand...
Click to collapse

af974 said:
Try to cook a rom without one of the latest apps that you have add and if the problem gone then you have find the issue,after that post here the responsable so we can look at it.
Click to expand...
Click to collapse
I'll try and cook without the 5 EXT i identified with wrong app.dats ?
I have had this problem since long, but i din't bother much, so i really don't know whats the issue..
it has been there basically since i tweaked the start menu locations.
now i have to get rid of it cuz any ROM user won't like to just press ok and continue with the ROM.
I'll try.

My suggestion is to try one by one but ofcourse this way you need to flash 5 times your phone.
Did you ,maybe,tweaked your Initflashfile.dat?
madnish30 said:
I'll try and cook without the 5 EXT i identified with wrong app.dats ?
I have had this problem since long, but i din't bother much, so i really don't know whats the issue..
it has been there basically since i tweaked the start menu locations.
now i have to get rid of it cuz any ROM user won't like to just press ok and continue with the ROM.
I'll try.
Click to expand...
Click to collapse

No i don't play with initiaflash... because i don't know much about it..
I guess i will not cook anyone of them so that if its one of them i will just download fresh CABs for them and convert them into EXTs rather than flashing my phone 5 times..
Thanks alot.

i tried cooking without those apps no luck
Same 2 errors hence those 2 apps are ok..
Attached my Initflashfile.dat if that helps.
Please help.

You really need to look in your startup folder to see what is in there. That's the first thing to do. Then, look in the start menu and see if anything weird is going on. Particularly, look for corrupted files or folders. If there are any files that look like folders, that could be the issue.
You're initflashfiles.dat is effin' huge!! Learn to make a cab, or relocate apps to windows. You must be wasting a ton of storage space.

thanks for the help Ted,
In the startup i see 2 folders
1) programs in which there is tools->system->Arkswitch.
2) tools -> system -> XDA_UC.
rest are the normal i guess.
Then in the startmenu it seems fine.
but one problem there i see in the start menu i see a system folder which is empty AFAIK i did not create and such path why is that there ?
You're initflashfiles.dat is effin' huge!! Learn to make a cab, or relocate apps to windows. You must be wasting a ton of storage space.
Click to expand...
Click to collapse
I'm not good with initflashfiles.dat i don't know much about it.
Can you please link me to a thread where i can learn about it.
Also what do you mean by CABs ? does that mean using UC to install via CABs ?
And how can i reloacte apps to windows ?
can you give a little explaination please.
thanks alot for the help.
The app.dat for Arksswitch is
Directory("\Windows"):-Directory("StartUp")
Directory("\Windows\Start Menu\Programs"):-Directory("Tools")
Directory("\Program Files"):-Directory("ArkSwitch")
Directory("\Program Files\ArkSwitch"):-Directory("Theme")
Directory("\Program Files\ArkSwitch"):-Directory("NLS")
Directory("\Program Files\ArkSwitch\NLS"):-File("1033.xml","\Windows\1033.xml")
Directory("\Program Files\ArkSwitch\NLS"):-File("1036.xml","\Windows\1036.xml")
Directory("\Program Files\ArkSwitch\NLS"):-File("1040.xml","\Windows\1040.xml")
Directory("\Program Files\ArkSwitch\NLS"):-File("1049.xml","\Windows\1049.xml")
Directory("\Program Files\ArkSwitch\Theme"):-File("config.xml","\Windows\config.xml")
Directory("\Program Files\ArkSwitch\Theme"):-File("status-bar.png","\Windows\status-bar.png")
Directory("\Program Files\ArkSwitch\Theme"):-File("x-deselected.png","\Windows\x-deselected.png")
Directory("\Program Files\ArkSwitch\Theme"):-File("x-selected.png","\Windows\x-selected.png")
Directory("\Program Files\ArkSwitch"):-File("Microsoft.WindowsMobile.Gestures.dll","\Windows\Microsoft.WindowsMobile.Gestures.dll")
Directory("\Program Files\ArkSwitch"):-File("ArkSwitch.exe","\Windows\ArkSwitch.exe")
Directory("\Program Files\ArkSwitch"):-File("ArkSwitchNative.dll","\Windows\ArkSwitchNative.dll")
Directory("\Windows\Start Menu\Programs\Tools\System"):-File("ArkSwitch.lnk","\Windows\_ArkSwitch.lnk")
Directory("\Windows\StartUp\Programs\\Tools\System"):-File("ArkSwitch.lnk","\Windows\_ArkSwitch.lnk")
Click to expand...
Click to collapse
and the app.dat for XDA_UC is
Directory("\Windows\StartUp\Tools\System"):-File("XDA_UC.mscr","\Windows\XDA_UC.mscr")
Click to expand...
Click to collapse
Please help me correct the two in order to remove the warning.
Will try and cook without them to see if they cause they problem.

I don't use xda_uc, but delete the sub-folders in startup and the problems go away.
App.dat copies files from windows to other places. In many cases, an app works fine in windows. You just need to fix paths (shortcuts, registry) so they point to windows. It's a complete waste to have two copies of all your files, especially when the ones in rom work perfectly fine. Personally, I don't even use app.dat's, except to create directories and to copy the important customization links into startup.
Edit: ok, so I'm looking at your initflashfiles.dat. One, there's something weird with your Manila twitter lines. Why does it appear twice? That's kind of a waste, and will slow down 1st boot. Also, you've got a dozen mui files in there. Just put in the one you need (0409 or whatever), and delete the rest. You've to two copies of a bunch of files that you don't use. Remove the lines you don't need from the app.dat.
As far as relocating apps, you've got 20 or so that would work fine in windows. For example, clean ram does not have to be in program files. Just leave the exe's in windows, and send 1 lang file to \windows\lang. The app will work fine. Do you really need 20 lang files for cleanram? Dude, that's a total waste.
Here's an easy one to fix: pocket rar. You've got two copies of it now on your device. Just get a shortcut for it to windows, and you're done. You stick rar.exe in a package, along with the shortcut, and send the shortcut to the start menu as normal. Speaking of which, it looks like you've got a syntax error there:
Directory("\Windows\Start Menu\Programs\\Tools\System"):-File("Pocket RAR.lnk","\Windows\_Pocket RAR.lnk")
Click to expand...
Click to collapse
Get rid of the extra \.

Thanks sir i got it, now i will impliment it.
Sir if you don't use app.dats then how do you chose which package shows up where in the start menu ?

I do pretty much everything with morscripts. I put all files and directories in zip files that are unzipped during customization, and all shortcuts are created by a script. This reduces the rom file count by hundreds (I have about 1800 rom files), and the zip files reduce the storage memory for files that have to be inserted elsewhere. There's also a restore script that resores files that change a lot and that aren't practical to cook in.
Anyway, were I you, I'd work on fixing all of your packages to make the rom more efficiently designed (instead of worrying about upgrading build numbers). I bet you could removed 500 files and clean up a crazy amount of memory (like 50 mb). It can be tricky moving an app to windows. Some apps have .ini files or similar settings files, and the app will crash or not load if the setting file is read-only, so you need to get the file into windows without having it read only (do it with an app.dat that copies or renames it to windows). Some apps have their settings in the same damn file name (like settings.txt), so you can't have them both in the same directory.
To relocate to windows, almost anything in the root program folder (like \program files\cleanram) can be moved straight to windows. Sub-folders generally just need to be moved to \windows. Typically, an exe looks for .dlls first in its own directory and second in \windows, so just about any dll can be moved to windows without issue. It will then usually look for the support files in the same directory that it's located in. The only apps I've had problems with are resco keyboard (the skin files seem to be hard coded to program files), and the latest Power Radio (2.4.0.2, or something like that). I had a bunch of power radio packages that worked fine in windows, but the latest wouldn't, so I just didn't do the upgrade.
It's usually easiest just to test things without cooking. In your case, you've already got everything in windows. Just click on exes and see what works and what doesn't. Some apps will need sub-folders relocated to windows, and it looks like your cab-to-ext package unfortunately renamed the rom files, so some files in the program folder will need to be copied to windows. Just do this for testing purposes, to see what works and what doesn't. I bet your rom is effin huge, and you could make it a lot leaner by cleaning your packages up. The cab-to-ext makers all more or less suck; it's better to do things manually (or with kheb 1.1).
Edit: you've got the tachan black theme in there twice, too. You really, really don't need those files copied elsewhere. I'm guessing there's a reg file with all the file locations (in HKCU\Software\Microsoft\Today). Fix it!!! All you need to do is do a 'replace all' and replace \\My Documents\\Themes\\tacchan23black with \\windows. Then delete that gawdawful app.dat file (both occurrences). That will remove 101 redundant files.

Do you remember this from your 1st post?
Directory("\Windows\Start Menu\Programs"):-Directory("System")
Directory("\Windows\Start Menu\Programs\Tools\Tweaks"):-File("Flip_IT.lnk","\Windows\_Flip_IT.lnk")
Click to expand...
Click to collapse
Here is (marked in red) your System folder (empty) in startmenu.
madnish30 said:
Then in the startmenu it seems fine.
but one problem there i see in the start menu i see a system folder which is empty AFAIK i did not create and such path why is that there ?
Click to expand...
Click to collapse

Thanks ted & af974.
i will try to do things you suggested.
But Ted, what does the attachment mscr do ?

I attached and EXT package from Chucky's Rom thanks to birkoffsjunk, i guess you will understand what mscr does looking at it.
madnish30 said:
Thanks ted & af974.
i will try to do things you suggested.
But Ted, what does the attachment mscr do ?
Click to expand...
Click to collapse

[q] xml / pxml

Sorry for being dumb once again.
I know how to create an XML and convert reg files to PROVXML etc but :
I flashed my cooked rom and did snapshot with kheb made all my changes and got a difference .reg file.
I converted that to PROVXML cause i believe its the best way of doing it.
What I dont know is what to do with it and where to put it in order to flash it.
Ive put it under custom settings\files but iot needs to be named something specifically according to 0Kitchen . Also i have an xml file that has my exchange settings in that which i want to cook in as well but dont know how.
I do use XDA uc but id prefer to let it be done with runcc or something?
Please advise whats better and whats the difference between the differentx PROVXML file naming.
Thanx

I would preffer using reg instead Provxml because they take a lot of time for 1st boot....anyway you need to name them mxip_xxxx.provxml if im not wrong.

af974 said:
I would preffer using reg instead Provxml because they take a lot of time for 1st boot....anyway you need to name them mxip_xxxx.provxml if im not wrong.
Click to expand...
Click to collapse
Can i renam the exchange.xml to mxip_exchange.provxml as well. does a xml and provxml contain the same information/layout?

Uhmm...it seems that should work, give a look here http://ip208-100-42-21.static.xda-developers.com/showthread.php?p=6995989.
Grumps said:
Can i renam the exchange.xml to mxip_exchange.provxml as well. does a xml and provxml contain the same information/layout?
Click to expand...
Click to collapse

af974 said:
Uhmm...it seems that should work, give a look here http://ip208-100-42-21.static.xda-developers.com/showthread.php?p=6995989.
Click to expand...
Click to collapse
Leme just try quickly we do flash like 30 times a day in any case hey. Will revdert just now
Thanx for your help

There's various file names, mxip, mxipinit and mxipupdate. In my experience I've never needed to add anything to a .dsm file, as long as the extension is .provxml they execute ok.
What I do though, is put my post-boot provxml's into the very last folder that my kitchen picks up so it's named ZZZ_postboot_provxml or something similar and I also name the file to mxipupdate_zzzPostBoot.provxml but I'm not sure if this helps. I do this because:
If you use total commander and search for *.provxml files in your windows folder you might find that none of them have the original name you gave in your packages, but if you step through the files you find there, you can see the execution order.
Hope this helps a bit.

arealityfarbetween said:
There's various file names, mxip, mxipinit and mxipupdate. In my experience I've never needed to add anything to a .dsm file, as long as the extension is .provxml they execute ok.
What I do though, is put my post-boot provxml's into the very last folder that my kitchen picks up so it's named ZZZ_postboot_provxml or something similar and I also name the file to mxipupdate_zzzPostBoot.provxml but I'm not sure if this helps. I do this because:
If you use total commander and search for *.provxml files in your windows folder you might find that none of them have the original name you gave in your packages, but if you step through the files you find there, you can see the execution order.
Hope this helps a bit.
Click to expand...
Click to collapse
ok so postboot is also one of the names like mxipinit and mxipupdate. Why are there so many different ones and which ones are executed in what order?

Grumps said:
ok so postboot is also one of the names like mxipinit and mxipupdate. Why are there so many different ones and which ones are executed in what order?
Click to expand...
Click to collapse
I think the order is all to do with the way the kitchen picks them up. e.g. I use OSKitchen and it seems SYS, then OEM, then EXT packages are picked up, alphabetically-so my provxml's get the same order, which is why I put them in a package of their own with the ZZZ_postboot name. It just makes it the last one to be picked up of the EXT packages-ensuring everything is in place when the script runs

arealityfarbetween said:
I think the order is all to do with the way the kitchen picks them up. e.g. I use OSKitchen and it seems SYS, then OEM, then EXT packages are picked up, alphabetically-so my provxml's get the same order, which is why I put them in a package of their own with the ZZZ_postboot name. It just makes it the last one to be picked up of the EXT packages-ensuring everything is in place when the script runs
Click to expand...
Click to collapse
Ok lemme try
Im trying to change my timezone from dublin -8 to gmt +2. n start kheb take snapshot make the change get i difference .reg file. convert it to xml and the paste it in files folder of lastflash folder?? ill try and see what happens