Database Users

question about packages and initflashfile.txt

Hi everybody,
I'm on the way to learn ROM-cooking. On that long trip I reached another hurdle. I've successfully created packages and put them into the OEM folder of the kitchen. So far so good, ROM has been created successfully. But after I've flashed the ROM to the device I found out that the files are exists twice. For example I've created a package from iContact_0.8.cab. Here is a part of the initflashfile.txt:
...
root:-Directory("Programme")
Directory("\Programme"):-Directory("iContact")
Directory("\Programme\iContact"):-File("default.png","\Windows\default.png")
Directory("\Programme\iContact"):-File("default.skn","\Windows\default.skn")
Directory("\Programme\iContact"):-File("english.lng","\Windows\iCenglish.lng")
Directory("\Programme\iContact"):-File("german.lng","\Windows\iCgerman.lng")
Directory("\Programme\iContact"):-File("iContact.exe","\Windows\iContact.exe")
Directory("\Programme\iContact"):-File("iphone.png","\Windows\iphone.png")
Directory("\Programme\iContact"):-File("iphone.skn","\Windows\iphone.skn")
Directory("\Programme\iContact"):-File("Settings.exe","\Windows\Settings.exe")
...
After flashing the ROM to the device I have file english.lng in folder \Programme\iContact and I also have file iCenglish.lng in folder \Windows, I have file iContact.exe in \Programme\iContact and I also have iContact.exe in \Windows. I thought an entry like Directory("\Programme\iContact"):-File("iContact.exe","\Windows\iContact.exe") means move file from \Windows to \Programme\iContact.
I found out that I have the same problem with a lot of other packages I've created with package-creator 2.7.
What am I doing wrong?
Tom

initflashfile.txt can not move a file it just creates a copy or a shortcut to the file.
If you want to move a file you must use a xml file.

NikMel said:
initflashfile.txt can not move a file it just creates a copy or a shortcut to the file.
If you want to move a file you must use a xml file.
Click to expand...
Click to collapse
@NikMel thank you for that hint. Is that part of provxml files or option.xml? Can you provide an example, please? And sorry that I'm so clueless.
Tom

Ok, I think it is the mxi_<package>_*.provxml what should be created to do this, is that right? Assuming that it is I've created such a file for my package and tried to use it instead of flashfiles.txt. But it seems that the file will not be executed while the ROM has been flashed to the device. Who or what is responsible to execute all the *provxml on the device? Are all *provxml files executed automatically? I found hints that mxip_ and mxipcold_ means that the files are executed during reflashing respect. cold-restarting the device while mxipupdate_ means executing each time the package has been updated.
I have to learn so much ....
Thanks for any help.
Tom

Hi everybody,
ok, it's the mxi_<package>_*.provxml what should doing the stuff. But it seems that it is not executed after flashing the ROM to the device.
I searched a lot of threads in the forum (for example this one: http://forum.xda-developers.com/showthread.php?t=398025&page=2). It seems that many other guys have the same problem but I couldn't find a solution.
In the meantime I'm totally confused about UC, Autorun, Autoshortcut etc. etc.. It would be very nice if someone could get me going on. What should be done to get this damned *provxml working??
Tom

Ok,
during further tests I found out that the mxip_<package>_*.provxml is being executed if it only contains Registry entries and/or MakeDir FileOperations. If I add a simple copy how it is done in for example this file: mxip_HtcApps_HTC_Ringtone.provxml the mxip-File is not been executed for whatever reason.
Is there somebody who knows what the reason for this behavior is? In the MS documentation I read something about access rights which could be restricted by OEM manufacturers. Could it be that the problem is caused by missing rights? And if yes, how change it?
Tom

Hi,
mxip_*provxml files are executed during flashing. Ok, that's a fact and it is working for me now. I found out that I only can use <characteristic type="Copy"> within the provxml. Once I used <characteristic type="Move"> the provxml will not be executed due to an error.
In fact all files from OEM packages goes into \windows and if someone uses a mxip_*provxml to implement those package for example in \Programme the files are duplicated. It seems not to be possible to remove the source files from \windows.
I did a test with rapiconfig.exe /p mxip_iContact08_100.provxml. If the provxml contains <characteristic type="Move"> I got an error message Config failed (0x80070005): Zugriff verweigert. After changing the provxml and replacing all "Move" with "Copy" the command works as expected.
Then I tried to delete a source file from the windows folder with TotalCommander running on the device. But it is not possible to delete the file.
Is there a way to delete the source files from the windows folder? Is it possible to put the source files from packages in an other folder than \windows?
Thanks for any advice.
Tom

Hi there,
Just want to tell you that i'm following this thread with great interest, as I also want to learn about cooking rom's, when I have some spare time.
So, please keep posting your updates on this matter.
@ all rom kookers and devellopers~
please share what you know, isn't that the spirit of Xda forum? It's the only way to get further, the more people thinking means more and faster advances been made.
Cheers

tomduke99 said:
Is there a way to delete the source files from the windows folder?
Click to expand...
Click to collapse
This is not possible becaue the files are part of the ROM I think. This has to be done before the ROM is created. But I'm not sure whether this is possible I don't think so, this would require the kitchen to do all the stuff with the mxip*provxml.
tomduke99 said:
Is it possible to put the source files from packages in an other folder than \windows?
Click to expand...
Click to collapse
All files from the kitchen stored in \windows. Does the kitchen knows something about the structure of the filesystem? Shouldn't this be provided by the package tool resp. by BuildOS? Or am I being completely off track?
Thanks for any advice.
Tom[/QUOTE]

I think the best workaround for this problem is to use the automated WM customization.
Cook your ROM with only the stuff you want to leave in the Windows folder. Check all initflashfiles.dat and *.provxml files, and remove them from the ROM! Leave only one initflashfiles.dat file, that will create the permanent folders (PermDir directive) and copy the checkautorun.lnk to the startup folder. This shortcut, in theory, is the only duplicate you will have in your whole ROM.
Then build a CAB file to install all files you need outside the windows folder.
Build an ExtROM with this cab file, a config.txt file and the autorun.exe file (see tutorials around the forums on creating an extrom).
Build your nbh file with os.nb and extrom.nb, and flash!
If all goes well, you will see the rom booting, then starting customization, then resetting, and when the phone comes back, you will have a nice, clean, duplicate-free ROM.
I didn´t try any of it, it´s just a theory.
Hope it helps.
Eduardo

Try the following:
<characteristic type="FileOperation">
<characteristic type="yourfile.foo">
<characteristic type="Move">
<parm name="Source" value="\Windows\yourfile.foo" translation="install"/>
<parm name="RemoveAttributes" value="R" />
<parm name="RemoveAttributes" value="S" />
</characteristic>
</characteristic>
</characteristic>

How to clean up or remove folder via xml ?

I need delete all files in some folder or delete it folder and create empty again.
Hot to do it via xml or cab ?

What's the folder, what's in it, and why is i there in the first place. Instead of slapping a band-aid on the problem (and increasing your boot-time), you should prevent the folder from forming to begin with. You probably need to edit a provxml. or maybe initflashfiles.dat.

Farmer Ted said:
What's the folder, what's in it, and why is i there in the first place. Instead of slapping a band-aid on the problem (and increasing your boot-time), you should prevent the folder from forming to begin with. You probably need to edit a provxml. or maybe initflashfiles.dat.
Click to expand...
Click to collapse
I want to clean up %CE11% from default shortcuts.
So I want make cab which can for any ROM replace all default shortcuts with mine.
So I have edit provxml for every ROM or make one cab for all ROMs.

Ethermind said:
I want to clean up %CE11% from default shortcuts.
So I want make cab which can for any ROM replace all default shortcuts with mine.
So I have edit provxml for every ROM or make one cab for all ROMs.
Click to expand...
Click to collapse
may be this one will help u
<characteristic type="FileOperation">
<characteristic type="%CE14%\Solitaire.lnk" translation="install">
<characteristic type="Delete">
<parm name="ForceDelete"/>
</characteristic>
</characteristic>
in my kitchen it delete the solitaire game so u can change with what ever u want i think

To delete single file is very easy. I interested in a la *.lnk deletion : )

Edit initflashfile.dat as farmer said. If you dont want to do that, then use startup scripts.

You should also post all of the links that you want removed. Some may require special tricks to keep them from appearing, and you'll get helped quicker. You can always delete the shortcuts in the Sys folder (what I do), then you don't have to worry about them at all, and they aren't wasting slots in your rom.

It is all good for one ROM.
But if I use today one rom, next week other ROM, next week another etc.
Don't you think it more easy to use one universal cleaning CAB instead of cleaning every ROM?

Ethermind said:
It is all good for one ROM.
But if I use today one rom, next week other ROM, next week another etc.
Don't you think it more easy to use one universal cleaning CAB instead of cleaning every ROM?
Click to expand...
Click to collapse
searching for and deleting some *.lnk's every time a SYS come out isn't that much work is it ? easier then what you're after in any case.

Ethermind said:
It is all good for one ROM.
But if I use today one rom, next week other ROM, next week another etc.
Don't you think it more easy to use one universal cleaning CAB instead of cleaning every ROM?
Click to expand...
Click to collapse
What you need to do is collect all the provxml's that you edit and put them in an EXT. They'll over-write the ones in the new SYS, and won't have the unnecessary file operations. Also, you can just use the same initflashfiles.dat over and over again (edit as needed for new packages). The provxml's are mostly in the obvious packages in the Common directory, and that's where most shortcuts are.

Farmer Ted said:
What you need to do is collect all the provxml's that you edit and put them in an EXT.
Click to expand...
Click to collapse
Good idea. I will use it for now.
But still interested in xml scripting : )

[FYI] If a .provxml seems to not work in your coked ROM, Try this

The attached .provxml will not execute. It's supposed to associate icons with folders in the start menu, but it's just not working. It is totally unmodified from the Rhodium S2 ROM. The directories are there as the initflashfiles.dat file is unmodified and the folders are in the start menu. Anyone care to help?

Your file is fine so I guess that you have the same issue I had .
I guess you don't have that provxml added to any of dsm files . Just use this tool and add it to any of dsm files.
http://forum.xda-developers.com/showthread.php?t=523139
You can also use xml parser to check if file is good, for example Serna Editor.
Click to expand...
Click to collapse
Maybe I'm wrong, so if you already have this provxml added to any of dsm files, we'll look for more reasons. One more question, do you try to cook this into ROM or execute from Advanced Configuration Tool?

It's cooked in. The package is directly from the Rhodium S2 ROM, so I don't quite understand why it's not executing. I'm thinking about putting it in another OEM folder and seeing if that will help. Heck I'm lost, and about to turn it in for the night.

As I wrote, try adding it manually to dsm file in that OEM folder, this should help you, if this won't help, then I'm out of ideas.
Anyway, you can just add content of that provxml to another provxml, it's dirty way but probably the easiest one.

This happens because the messenger.lnk have not been created when this provxml is executed and it fails.
So just rename the provxml to mxipupdate_zprojectdefault_a_000.provxml
Notice the "z" ahead of the project.
This trick will put the provxml after the mxipupdate_windowsliveim_1.provxml, so the messenger.lnk will have been created and the provxml will run just fine.

But he said that provxml isn't excuted at all, I'm out of ideas . Anyway, it's worth to give your idea a try.

jwzg said:
The attached .provxml will not execute. It's supposed to associate icons with folders in the start menu, but it's just not working. It is totally unmodified from the Rhodium S2 ROM. The directories are there as the initflashfiles.dat file is unmodified and the folders are in the start menu. Anyone care to help?
Click to expand...
Click to collapse
the provxml isn´t executed on my rhodium as well. but renaming to mxipupdate_zzzzprojectdefault_a_000.provxml
does work for me.
as the posters above me wrote:
the problem seems to be the messenger package which includes another *provxml file which should be prozessed BEFORE mxipupdate_projectdefault_a_000.provxml but it isn´t! also *.provxml aren´t prozessed if there´s a failure inside. when you remove a program and you don´t clear the line in the *.provxml the file would not me prozessed.
this problem is related to platformrebuilder breaking something, you can pm airxtreme for info, it seems that he solved this problem in his wonderful kitchen
steph

Provxml can be launched but they stops at the line it find a problem so it seems that it doesnt works.
Platform rebuilder can reads DSM in EVK? or just in OsK? or none?

Renaming the .provxml solved the issue. Man, the start menu looks good now! Thanks!

Great, I wouldn't think about renaming on my own . Anyway, it seems that those provxml files are processed in alphabetical order, right?

everything is alphabetical order processed in platform rebuilder based kitchens ¬¬
Mod edit: Solved

Dude!!! The sameprob here with Leo ROM... same file... going to try your tip!

kurniawan77 said:
Dude!!! The sameprob here with Leo ROM... same file... going to try your tip!
Click to expand...
Click to collapse
@kurniawan77 - Did it work for you?
Same prob here, using osKitchen Zero for HTC LEO. Already tried renaming by adding zzz in name and also tried adding the provxml in dsm. Any other suggestions? This is drving me nuts, please help.
p/s: also tried opening the provxml in internet explorer/XML notepad 2007 - no errors. Made sure there are no "<?xml version="1.0" encoding="utf-8" ?>" in the headers.

Try to replace platformrebuilder.exe with another version, that did the trick for me.
Before you ask, sorry but I'm using a private edition of platformbuilder so I can't share.
I'm using platformrebuilder.exe v.2.1.0.0
tidus18 said:
@kurniawan77 - Did it work for you?
Same prob here, using osKitchen Zero for HTC LEO. Already tried renaming by adding zzz in name and also tried adding the provxml in dsm. Any other suggestions? This is drving me nuts, please help.
p/s: also tried opening the provxml in internet explorer/XML notepad 2007 - no errors. Made sure there are no "<?xml version="1.0" encoding="utf-8" ?>" in the headers.
Click to expand...
Click to collapse

tidus18 said:
@kurniawan77 - Did it work for you?
Same prob here, using osKitchen Zero for HTC LEO. Already tried renaming by adding zzz in name and also tried adding the provxml in dsm. Any other suggestions? This is drving me nuts, please help.
p/s: also tried opening the provxml in internet explorer/XML notepad 2007 - no errors. Made sure there are no "<?xml version="1.0" encoding="utf-8" ?>" in the headers.
Click to expand...
Click to collapse
You still have problems even with oskitchen 1.31beta3? Some people reported the new DSM-based provxml order to be working fine.

Evil Provxmls....
airxtreme said:
You still have problems even with oskitchen 1.31beta3? Some people reported the new DSM-based provxml order to be working fine.
Click to expand...
Click to collapse
Hi Airxtreme - Thanks for developing the kitchen! Its really great. But i just recently moved to osK Zero from ervius. Previously in ervius i didnt even bother to add provxmls in any dsm. I dont quite understand DSM management fully, but i did add the provxmls in DSM of my ext package (ext package contains my custom icons for start menu and the provxml to add reg entries).
When i get back home, i will try to rebuild the ROM with older version of kitchen and report back. Currently im using v1.31Beta3.
p/s: i had trouble with theme provxmls as well, finally i had to put all the theme files in Operatorpkg, and put the xml entries in HTC's provxmls (the one named HTC_100) for it to work.

Laurentius26 said:
Try to replace platformrebuilder.exe with another version, that did the trick for me.
Before you ask, sorry but I'm using a private edition of platformbuilder so I can't share.
I'm using platformrebuilder.exe v.2.1.0.0
Click to expand...
Click to collapse
2.1.0.0? Then what's the version that is publically available? And can you say something about the new functions, etc.? Thanks!

tidus18 said:
Hi Airxtreme - Thanks for developing the kitchen! Its really great. But i just recently moved to osK Zero from ervius. Previously in ervius i didnt even bother to add provxmls in any dsm. I dont quite understand DSM management fully, but i did add the provxmls in DSM of my ext package (ext package contains my custom icons for start menu and the provxml to add reg entries).
When i get back home, i will try to rebuild the ROM with older version of kitchen and report back. Currently im using v1.31Beta3.
p/s: i had trouble with theme provxmls as well, finally i had to put all the theme files in Operatorpkg, and put the xml entries in HTC's provxmls (the one named HTC_100) for it to work.
Click to expand...
Click to collapse
Those having problem with provxmls where it is used to overwrite other provxmls in sys (ie: for theme settings), please try this http://forum.xda-developers.com/showpost.php?p=7038082&postcount=2477
This version of your kitchen solved all my probs. THANKS!!!!!!!!!!!!

I only tried to help make the provxml load
Bepe created the kitchen tool and knows everything about it.
Edit; a bit late but the version I use is 2.1.0.0 indeed.
cnzqy1 said:
2.1.0.0? Then what's the version that is publically available? And can you say something about the new functions, etc.? Thanks!
Click to expand...
Click to collapse

tidus18 said:
Those having problem with provxmls where it is used to overwrite other provxmls in sys (ie: for theme settings), please try this http://forum.xda-developers.com/showpost.php?p=7038082&postcount=2477
This version of your kitchen solved all my probs. THANKS!!!!!!!!!!!!
Click to expand...
Click to collapse
glad it worked out for u... been away for days... working on bugfixes... and more. v1.31b3 from worked out even better... sorry for late response

[SOLVED] Start Menu icon that just won't go away

So I added MP3 Trimmer to my kitchen, but moved the location of the start icon to a Tools folder. The problem: an MP3 Trimmer icon remains in the initial start page. There is no associated .lnk file in the Start Menu\Programs folder, and the registry HKLM\Security\Shell\Startinfo\Start has the reference to the link in the correct spot.
I have tried placing the link by moving it from the default location with a MortScript, and by changing the app.dat. Same results.
I have done this same move with many other packages, this is the only one causing any problems.
No other references to MP3 Trimmer.lnk exist in the registry or kitchen. Why is it displayed in the start menu when no .lnk is present, and where is that information coming from? Thanks!

Did you check your Initflashfile.dat ?

Also the language folder may contain a app.dat or .provxml file which creates the shortcut

I didn't bothered about two folders that was empty in "\windows\start menu\programs\" until I read this post. I found one of them in Initflashfile.dat, "Outlook" and had deleted the line away. I'm still unable to find the other folder "Start Menu". It's not in Initflashfile.dat, nor any of the xml or proxml files in the "OEM Packages" folder. :-(

Check for some App.dat in EXT folder or a provxml in Project A.
Both OsKitchen and EVK has a search string inside,use it to find your dead folder.
zard said:
I didn't bothered about two folders that was empty in "\windows\start menu\programs\" until I read this post. I found one of them in Initflashfile.dat, "Outlook" and had deleted the line away. I'm still unable to find the other folder "Start Menu". It's not in Initflashfile.dat, nor any of the xml or proxml files in the "OEM Packages" folder. :-(
Click to expand...
Click to collapse

af974 said:
Check for some App.dat in EXT folder or a provxml in Project A.
Both OsKitchen and EVK has a search string inside,use it to find your dead folder.
Click to expand...
Click to collapse
I'm using OSKitchen. It's not in provxml in Project A. I tried using search in OSKitchen to search "Start Menu" and "Start*.*" but can't find it. :-(

Ok, i dunno why you didnt find nothing ...anyway, cook the attached file in your rom, i have set it for deleting any Start Menu.lnk in Start Menu\Programs.
Basically you can use it for deleting any dead links.
If it doesnt work try to leave ".lnk" after Start Menu.
It is a mortscript , i have include also Mortscript package in case you dont have it.
zard said:
I'm using OSKitchen. It's not in provxml in Project A. I tried using search in OSKitchen to search "Start Menu" and "Start*.*" but can't find it. :-(
Click to expand...
Click to collapse

zard said:
I'm using OSKitchen. It's not in provxml in Project A. I tried using search in OSKitchen to search "Start Menu" and "Start*.*" but can't find it. :-(
Click to expand...
Click to collapse
You probably can't find it because of hexadecimal or html entities values in which the shortcut name is probably encoded into, try looking for the encoded values instead.

Check to make sure autoshortcut isn't doing it (it could be in a reg file). Autoshortcut sucks, but I don't know if it's still used.

airxtreme said:
You probably can't find it because of hexadecimal or html entities values in which the shortcut name is probably encoded into, try looking for the encoded values instead.
Click to expand...
Click to collapse
I did try hexadecimal and html but still couldn't find it. I'm using v1.31. Maybe it is the format of the search that I'm not doing right.

af974 said:
Ok, i dunno why you didnt find nothing ...anyway, cook the attached file in your rom, i have set it for deleting any Start Menu.lnk in Start Menu\Programs.
Basically you can use it for deleting any dead links.
If it doesnt work try to leave ".lnk" after Start Menu.
It is a mortscript , i have include also Mortscript package in case you dont have it.
Click to expand...
Click to collapse
Thanks for this but unfortunately, my kitchen is screwed up when I tried out your packages. My kitchen was alright before that. Even unchecking the two packages didn't help.
Don't worry, I'm not blaming you for the problem in my kitchen. Will have to find out what went wrong before I can test your packages again and hopefully, it can solve the problem since I can't find the culprit within my packages.

Farmer Ted said:
Check to make sure autoshortcut isn't doing it (it could be in a reg file). Autoshortcut sucks, but I don't know if it's still used.
Click to expand...
Click to collapse
Still very new to cooking so don't know what you meant by "Autoshortcut". :-(

HTC puts a file called autoshortcut.exe in one of the oem folders. It runs during customization, and creates shortcuts for htc apps. There are reg keys in the apps that get the shortcuts.

oooo__OoO__oooo said:
So I added MP3 Trimmer to my kitchen, but moved the location of the start icon to a Tools folder. The problem: an MP3 Trimmer icon remains in the initial start page. There is no associated .lnk file in the Start Menu\Programs folder, and the registry HKLM\Security\Shell\Startinfo\Start has the reference to the link in the correct spot.
I have tried placing the link by moving it from the default location with a MortScript, and by changing the app.dat. Same results.
I have done this same move with many other packages, this is the only one causing any problems.
No other references to MP3 Trimmer.lnk exist in the registry or kitchen. Why is it displayed in the start menu when no .lnk is present, and where is that information coming from? Thanks!
Click to expand...
Click to collapse
It is 100 % a app.dat or initflashfiles.dat issue. Or a reg in the 0409 folder.
Also when looking in you initflashfiles be careful to look for entries that point to Windows\Start Menu
instead of Windows\Start Menu\Programs

bobsbbq said:
It is 100 % a app.dat or initflashfiles.dat issue. Or a reg in the 0409 folder.
Also when looking in you initflashfiles be careful to look for entries that point to Windows\Start Menu
instead of Windows\Start Menu\Programs
Click to expand...
Click to collapse
What I'm talking about is behavior on the phone itself. Let's assume my kitchen searches have been wrong and it really is an app.dat issue. I have a shortcut that exists in the start menu with no associated link file or reg entry -- so there's nothing to delete to get rid of the shortcut on the actual phone!
Kitchen searches result in only the expected "MP3 Trimmer.lnk" locations and "MP3Trimmer.exe" text.
As far as I can tell, ManilaShortcut.exe only makes shortcuts for HTC People and HTC Calendar (but I have IsShortcutEnable = 0 to keep those from popping up). MP3 Trimmer isn't in the original ROM from which the Manila is based, so it's possible there's something going on there.
It's not a huge issue so I haven't been spending a lot of time trying to find or fix it, but I'm virtually out of bugs to fix. What's bothering me more is something seemingly simple that I don't understand.

oooo__OoO__oooo said:
What I'm talking about is behavior on the phone itself. Let's assume my kitchen searches have been wrong and it really is an app.dat issue. I have a shortcut that exists in the start menu with no associated link file or reg entry -- so there's nothing to delete to get rid of the shortcut on the actual phone!
Kitchen searches result in only the expected "MP3 Trimmer.lnk" locations and "MP3Trimmer.exe" text.
As far as I can tell, ManilaShortcut.exe only makes shortcuts for HTC People and HTC Calendar (but I have IsShortcutEnable = 0 to keep those from popping up). MP3 Trimmer isn't in the original ROM from which the Manila is based, so it's possible there's something going on there.
It's not a huge issue so I haven't been spending a lot of time trying to find or fix it, but I'm virtually out of bugs to fix. What's bothering me more is something seemingly simple that I don't understand.
Click to expand...
Click to collapse
I know how frustrating this is and I have had the same in the past. I know this is not what you want to hear but the fact is there is only a few ways for a shortcut to be created. Mainly initflashfiles.dat to move or rename shortcuts, and app.reg or rgu files to create shortcuts, and by way of provxml file. The chances are 99% one of the above. But there is also the possibility of shortcuts to be created by mortscript as well but if it is your kitchen I would think you would know if you created a mortscript. There is also the Older HTC Auto shortcut found in some reg files.
I know it is sometimes hard to find but you will eventually find it.
By the way where did the package from the MP3 trimmer come from? Was it from a chinese ROM?

af974 said:
Ok, i dunno why you didnt find nothing ...anyway, cook the attached file in your rom, i have set it for deleting any Start Menu.lnk in Start Menu\Programs.
Basically you can use it for deleting any dead links.
If it doesnt work try to leave ".lnk" after Start Menu.
It is a mortscript , i have include also Mortscript package in case you dont have it.
Click to expand...
Click to collapse
bobsbbq said:
It is 100 % a app.dat or initflashfiles.dat issue. Or a reg in the 0409 folder.
Also when looking in you initflashfiles be careful to look for entries that point to Windows\Start Menu
instead of Windows\Start Menu\Programs
Click to expand...
Click to collapse
bobsbbq said:
I know how frustrating this is and I have had the same in the past. I know this is not what you want to hear but the fact is there is only a few ways for a shortcut to be created. Mainly initflashfiles.dat to move or rename shortcuts, and app.reg or rgu files to create shortcuts, and by way of provxml file. The chances are 99% one of the above. But there is also the possibility of shortcuts to be created by mortscript as well but if it is your kitchen I would think you would know if you created a mortscript. There is also the Older HTC Auto shortcut found in some reg files.
I know it is sometimes hard to find but you will eventually find it.
By the way where did the package from the MP3 trimmer come from? Was it from a chinese ROM?
Click to expand...
Click to collapse
Since I was trying to improve on the response of my Contacts in Manila 2018 by mixing and matching 2016 and 2018 tabs, I took the opportunity to continue to search the elusive "Start Menu" folder in my Start Menu.
I was still not able to find it in the initflashfiles, nor dat, app.reg or proxmls. I modified the mortscript that af974 gave me into "Delete("\Windows\Start Menu\Programs\Start Menu.lnk")" and ran it from SD Card. Even after soft reset, the "Start Menu" folder is still there.
What I find strange is that in my \Windows directory, there was no "Start Menu.lnk" - I'm using Resco Explorer and is able to see hidden files. But in \Windows\Start Menu\Programs, I could see "Start Menu" folder. I was able to delete it using Resco Explorer.

bobsbbq said:
I know how frustrating this is and I have had the same in the past. I know this is not what you want to hear but the fact is there is only a few ways for a shortcut to be created. Mainly initflashfiles.dat to move or rename shortcuts, and app.reg or rgu files to create shortcuts, and by way of provxml file. The chances are 99% one of the above. But there is also the possibility of shortcuts to be created by mortscript as well but if it is your kitchen I would think you would know if you created a mortscript. There is also the Older HTC Auto shortcut found in some reg files.
I know it is sometimes hard to find but you will eventually find it.
By the way where did the package from the MP3 trimmer come from? Was it from a chinese ROM?
Click to expand...
Click to collapse
To the best of my ability utilizing search there is no reference to the link or the executable in any initflashfiles.dat/app.dat/.reg/.rgu/.*xml. Even the hex coded .dat entries still refer to a "normal" name.lnk, so my search should uncover those.
I pulled the MP3 Trimmer from the Rhodium 2.07 EXT latest packages, which is from an asian ROM at least judging from the links in the original app.dat.
No autoshortcut.exe exists in the ROM. The MP3 Trimmer and a bunch of other packages create an AutoShortcut key, but there's nothing under that so I'm not sure exactly how it's used (and it would therefore be present even if I deleted it from the trimmer package).
My guess is that it has to be either the start menu initial creation process some Manila initialization process that is creating the initial link. How it gets into a state where it remains in the start menu but no information exists to delete it is the 2nd question -- where is that information??
I've verified if I delete \Windows\Start Menu\Programs, then copy the directory structure back in the link goes away. This could be a solution long term, but I was trying to stick to the automatic creation process as much as possible.
Thanks to those who have responded and provided input so far.

Looking at a stock rom dump for the raphael, the autoshortcut operations are in a .provxml in the 0409 folders, like this:
Code:
<wap-provisioningdoc>
<characteristic type="Registry">
<characteristic type="HKLM\SOFTWARE\HTC\AutoShortcut">
<parm name="\Windows\Start Menu\Programs\Streaming Media.lnk" value="\Windows\Streaming Media.lnk" datatype="string" translation="install"/>
<parm name="\Windows\Help\Streaming Media.lnk" value="\Windows\Help_Streaming Media.lnk" datatype="string" translation="install"/>
</characteristic>
</characteristic>
</wap-provisioningdoc>
The autoshortcut.exe is in oemdrivers. I really don't even know what the point of it is; I guess it's for book-keeping, to keep track in the registry of all the shortcuts being moved around. It could just be done by a provxml file operation instead of by autoshortcut during customization, but whatever, that's how it's done. Just try deleting the autoshortcut references. Heck, delete or rename the shortcut in the kitchen and send it to the start menu a different way (like by renaming it while copying it with an app.dat file).

Farmer Ted said:
Heck, delete or rename the shortcut in the kitchen and send it to the start menu a different way (like by renaming it while copying it with an app.dat file).
Click to expand...
Click to collapse
OK, I'm going to modify the orignal post as solved, because this simple idea (which of course didn't occur to me) is the ticket. I renamed the .lnk to .link in the kitchen and it's renamed back to .lnk when copied by the app.dat. Presto change-o, no MP3 Trimmer.lnk file in \Windows. Works like a charm.

[SOLVED] Delete files in ProvXML doesn't work

Hi,
I try to delete *_manila files via provXML but that fails with error 0x80070005.
Here you can see what I do foreach file
Code:
<characteristic type="\Windows\00061bfb_manila" translation="install">
<characteristic type="Delete">
<parm name="RemoveAttributes" value="R" />
<parm name="RemoveAttributes" value="S" />
<parm name="ForceDelete"/>
</characteristic>
</characteristic>
<characteristic type="\Windows\000bbc87_manila" translation="install">
<characteristic type="Delete">
<parm name="RemoveAttributes" value="R" />
<parm name="RemoveAttributes" value="S" />
<parm name="ForceDelete"/>
</characteristic>
</characteristic>
Please help!
MadMatt

Are you trying to delete a rom file? It doesn't work. Just remove the file from your kitchen.

Farmer Ted said:
Are you trying to delete a rom file? It doesn't work. Just remove the file from your kitchen.
Click to expand...
Click to collapse
Yes, I want to delete it, but only afther it's copied to \Extendir\Manila Search for extendir and you'll know what I want to do. But indeed, I fear that it are ROM files... Is there another way to get them there in first boot?

That's why it's a rom file. There's no deleting them. If you could delete rom files, you could totally eff up your device rather easily. The way I move batch groups of files is with zip files. You can load dozens or hundreds of files into a zip file (which is a single, compressed rom file) and have them quickly copied to other locations using a mortscript. It's much faster than a cab install, and doesn't load any of the uninstall crap into the file system/registry/databases. There's really no point in copying one file at a time into the \Extendir directory, as you'll be defeating the purpose of using Extendir, so if you want to use extendir, you'll either have to move the files there with a mortscript/unzip or with a cab file, or just copy them from your sd card to the extendir directory. In the latter case, you could probably just put them in the extendir folder on your sd card and not even worry about it.
Here's an example of an unzipping mortscript:
UnZipALL("\Windows\Bing.zip","\Windows\")
Click to expand...
Click to collapse
I have a zip-folder with all the Bing sub-folders in it (\audio and \xaml). The script unzips the files into windows, where the rest of the Bing files and modules are located. In total, 104 files are stored in the zip folder, so I've basically been able to replace 104 rom files that would need to be copied to another directory with 2, which lowers the rom file count by a lot. If you put all your manila files in zip folder, and then unzip it to \extendir\manila, you'll save on the rom file count, which is basically the entire point of using extendir. The unzipping only works if the directory has already been created and also if there are no over-writes required. You could also make the directories by adding these commands to the beginning of the script:
MkDir("\Extendir\")
MkDir("\Extendir\Manila\")
Click to expand...
Click to collapse

Okay, I gave this a try, but extracting using a MortScript doesn't work... Or do I need some packages to be able to run a Mscr file?
This is what I have in my Config_AP.txt file
Code:
CFG: \WINDOWS\config_end.txt
CFG: \WINDOWS\Madmatt.txt
And in my Madmatt.txt (that will contain all customization made by me):
Code:
EXEC: \Windows\ManilaExtendir.mscr
But thats not working with this in my ManilaExtendir.mscr file:
Code:
MkDir("\Extendir\")
MkDir("\Extendir\Manila\")
UnZipALL("\Windows\Manila_CFC.zip","\Extendir\")
And another question (maybe I should ask this in Extendir thread): How can I cook the Extendir.dll in my XIP? Because when I use the BuildXIP_Of_MSXIPkernel tool (provided by Alexx~) that crashes. I guess that happens because it's a dll and not S000, S001 and so on. But how can I convert?
Thanks for the help you already provided to me! Hope you can help me out with this!

You've got mortscript cooked in, right? Assuming that you do, just test out the unzipping script on your device, and make sure it works before you cook and flash. Put the zip file in \windows and run the script. It may help to delete the directories first, too. And if you're doing a lot of morscript stuff during customization, you could just dump autorun and config.txt's altogether. I did it a while ago, and am really glad that I did. First boot is much faster without autorun. I just have a shortcut called custom.lnk that I have copied into the startup folder with initflashfiles.dat. It points to a mortscript (custom.mscr) that has a queue of unzips in it that does all of my customization; at the end, it deletes the custom.lnk from startup so it doesn't run every time I reset the device. I also import an xml; I don't use cabs, so don't have to deal with them. This is what it looks like (off-topic, but what the hell):
Code:
WriteFile("\Windows\Active sync xml.lnk","1#\Windows\dF_TaskMgr.exe /provxml \WINDOWS\zzz-Active Sync.xml")
#runwait("\WINDOWS\UnzipFpseCE.mscr")
runwait("\WINDOWS\Unzipmotweet.mscr")
runwait("\WINDOWS\UnzipRescoAudio.mscr")
runwait("\WINDOWS\UnzipResco.mscr")
runwait("\WINDOWS\UnzipRescoPhoto.mscr")
runwait("\WINDOWS\UnzipRescoRadio.mscr")
runwait("\WINDOWS\UnzipSchema.mscr")
runwait("\WINDOWS\UnzipUCWEB.mscr")
runwait("\WINDOWS\StartMenu.mscr")
runwait("\WINDOWS\UnzipTemplates.mscr")
runwait("\WINDOWS\Unzip1.mscr")
runwait("\WINDOWS\UnzipBing.mscr")
runwait("\WINDOWS\Restore.mscr")
runwait("\WINDOWS\cleanup.mscr")
run("\Windows\Refresh.lnk")
run("\Windows\Active sync xml.lnk")
SetFileAttribs("\Windows\Active sync xml.lnk","system",FALSE)
delete("\Windows\Active sync xml.lnk")
SetFileAttribs("\Windows\StartUp\Custom.lnk","system",FALSE)
SetFileAttribs("\Windows\StartUp\Custom.lnk","readonly",FALSE)
delete("\Windows\StartUp\Custom.lnk")
run("\WINDOWS\AEBPlus.exe")
run("\WINDOWS\RKbdInit.exe")
run("\Windows\skbackup.lnk")
I'm not sure what to tell you about building the XIP; I was using EVK when I played around with extendir, and it rebuilt it w/o problem.

Thanks! And how can I check if I have MortScript installed? What packages do I need to cook in?

If you have to ask, it's not installed, lol. It's not native winmo software. Here's a package; I changed the default icon because I find it annoying. The package is in oem format; you can either convert it to an EXT or probably put it in your OEM directory.

Farmer Ted said:
If you have to ask, it's not installed, lol. It's not native winmo software. Here's a package; I changed the default icon because I find it annoying. The package is in oem format; you can either convert it to an EXT or probably put it in your OEM directory.
Click to expand...
Click to collapse
Thanks! I'll take a look for what I can use MortScript too! I like it! The only thing that doesn't work is Extendir now... But I'll post that in the Extendir thread. This one can be closed. Thanks Farmer Ted.

Ok, I'll close it. The 0-commands.txt file in the package is a quick list of mortscript commands. I put a 0 on it so that it pops up to the top of the\windows folder and is easy to access. You can delete it if you don't want it. There's also a much more thorought manual in pdf form out there, if you search for it.