Quote:
Originally Posted by Juggalo_X
[B][COLOR=#ff9933]gguruusa,[COLOR=LightBlue]does initflashes.txt not mandate where a file is placed, and if one does not exist or the file is only referenced in DSM it is placed in /windows?
that seems ot be the way my kitchen operates.
|
No. That's not how it operates.
Quote:
Originally Posted by aceracer24
It does but only after the fact. The initflashfile.txt only "copies" the program from windows and places it into what ever folder you decide. If there is no file listed in the initflash.txt, it is then placed only in the windows folder. Based on another thread that was being dicussed, the provxml is the best way to "move" and then delete the existing copy..however, I was also told that that process happens after the build process and thus making the file a "rom" file and not possible to delete.
|
Correct.
When the ROM builds, directories don't exist. Not even /windows. There is no mechanism to create them and there is no mechanism to read them even they existed. There is only a collection of files.
At cold boot, all the files in the ROM are "defined" to be in /windows, and initflashfiles is processed. This can create directories and copy files from /windows (which are the only files that exist at this point) to anywhere else you want. Delete is not implemented because why would you need it? (you can't delete ROM files) Then the os is started.
Early in the OS boot process, provs are run. Unlike initflashfiles, provs can do more actions than create dirs and copy files (mainly because the OS is now minimally alive). You still can't delete ROM files (ROM, rememeber?)
Then all the "run once" processes run
Eventually, everything finishes and the user gets to interact.