Is this possible in ROM Kitchen?
 

Let just say I wanted to add PocketBreeze to the ROM, and the cab file contains files that are located in Program Files and as well as Windows directories, now can I somehow write the files to Program Files?

As far as I understand, anything in OEM will be dump to \Windows directory right?

Also, are regular sub folders allowed in the main OEM\Your_Package folder?

Thanks.

You can copy stuff from \Windows to \Program Files\whatever as part of your Rom Kitcen OEM package (there are plenty of examples of this out there), but you'll end up with 2 copies in the final rom. Funky, but works. Only issue there is total rom space used, if its a massive app.

You may be able to tweak your registry entries instead, so any registry references to \Program Files\Foo\bar.exe point to \Windows\bar.exe instead - that's worth a shot to try first.

Subfolders in your OEM package would be ignored, as far as I can tell.

Edit: I'm replying to the OP, not schettj (who beat me to it)

No. That's what initflashfiles.txt is for. The structure of that file allows you to create directories and copy files to them.

Keep in mind I said copy, not move. All files remain in \Windows, even if they are copied to another directory (say \Program Files or \My Documents). What I've been told (yet will have a hard time believing until I prove it to myself) is that these are actual duplicates of the files, meaning they will take up twice as much space in your rom. What I'm still hoping is actually the case is that the rom uses symbolic linking to "copy" the files to their new location (similar to a shortcut but more seamless). That would make much more sense to me... the file appears to be in \Program Files but is actually still in \Windows... The file system thinks it's in both places but it's really not.

However, I may very well be wrong. If I am, and these are actual copies, then what a horrible design and shame on MS/HTC/whoever designed it. But that will mean we should try to only put apps in rom that are ok with running from within \Windows. Otherwise when things get moved around they will end up taking up twice as much space in the rom as they should.

Ugh, the \Windows folder is like a rats nest already. I hate having to go in there because it takes so long to display the directory listing.

OK, so can you post some example for me and maybe others to see how you can achieve create directories, and copy files using initflashfiles.txt?

I know how to do registry and all using initflashfiles.txt but not to create folder and copy.

Thanks.

NVM think I found it...tell me if I'm wrong though

to create do:

Directory("My Documents"):-Directory("Personal")
Directory("My Documents"):-Directory("Business")
Directory("My Documents"):-Directory("My Music")


to Copy file do:

Directory("\My Documents\Templates"):-File("To Do.dot","\Windows\todo.dot")

Edit: Also if I copy to Program Files, does it count against me as far as Main memory usage goes?

All the answers you seek can be found by looking at the initflashfiles.dat (in the LOC folder) and the other ones in the OEM subfolders. But here's an example from initflashfiles.dat:

Directory("\My Documents\Templates"):-File("To Do.dot","\Windows\todo.dot")

So that copies the file \Windows\todo.dot to \My Documents\Templates and in the process renames the copy to "To Do.dot".

If you look on your device, sure enough you will see a file called todo.dot in your \Windows folder and To Do.dot in your \My Documents\Templates folder.

Yeah you've got it. And no, it doesn't matter what directory you copy to, it all is going towards the size of the ROM... your main memory should not be affected at all.

Sweet if that's the case...man I'm cooking ROMs yo!! :)

I'll mess around tonite and see how far do I get.

Thanks luv2chill.

Sorry, but you are totally wrong. Files copied by initflashfikes.txt are not copied into rom. The copy is placed in memory, taking up space.

Have you proven that, Bushrod? Like you have made an OEM package with an initflashfiles.txt file that copies a file to another directory, and once flashed your program memory is decreased by the size of that file?

If so that is a revolting development. Sadly, none of this info is documented anywhere so everything I "know" is from bits and pieces I have read and intuited. I had planned an experiment with an OEM package with an extensive initflashfiles.txt file but hadn't gotten around to it yet.

If that is true then it becomes even more important to leave everything you incorporate in the \Windows folder and just adjust registry entries (and hope the program was written well enough to accomodate a different location).