ProvXML Reference for Developers

[mikledw]

Originally Posted by boggsie

So, arranging start menu items via provxml, as you are experiencing, is a very challenging thing to pull off.

When you are executing the cab file, you know exactly ... exactly where every shortcut is located, because you stage the cab file to execute a precise point in the post-flash process. you do this either manually, via SDconfig or sashimi.

The same cannot be said of the provxml execution. It is entirely possible, and likely, that you are trying to move items via provxml, that don't exist yet in their source location. One thing to consider is that other provxml is also executing to do exactly the same thing that you are doing. The creation of Microsoft Office shortcuts are a perfect example as they are copied via provxml. Your provxml is trying to move them, when the Microsoft Office provxml hasn't copied them to thier source location, yet.

So in order to avoid this with provxml, you need to give your provxml oem file a name which helps to ensure that it will execute as the last provxml in your flash process.

However, if you are looking for a less painful approach, I can tell you that after working on this for a long, long time, I have come to learn that doing this particular task is so much easier via mortscript. One of the very nice things about mortscirpt, is that each copy/move can be setup as a elseif statement, whereby if the items doesn't exist, the script just proceeds to the next command. As you are learning, provxml is very unforgiving. If one statement for a copy or move cannot be executed, the script will die.

Best regards,
-boggsie

alright so you mean if i named the provxml file itself or the OEM folder its in starting with the letter z it will be executed last? Also for mortscript how would you get it to run at start up im very new to this as well lol?

[boggsie]

I'd try leaving the OEM alone and then use this as your file name for the provxml:

mxipupdate_zzzOrganizeStartMenu_100.provxml

Best regards,
-boggsie