Quote:
Originally Posted by decibel
It is the Operator_config.txt file.. But, be careful because this is in two folders. It is in <OEM\Herman\COMMON\PACKAGE_Raphael_CARRIER> and in <EXT\Herman\COMMON\Apps\Mortscript-4.3b2>.
If you include Mortscript in your build, you have to change it in the Mortscript dir. If you do not, change it in PACKAGE_Raphael_CARRIER. I have two because Mortscript has to be executed on first boot to register. The one in Mortscript overwrites the one in oem IF its included.
|
Heh I assumed the one in the Mortscript directory was simply a mistake and deleted it. The proper way to have multiple configs would be to have something like mortscript_config.txt in the mortscript directory, and put an entry in the correct operator_config.txt file that says CFG: \windows\mortscript_config.txt. Although I believe in that scenario the mortscript_config.txt file MUST exist somewhere otherwise the script will fail, I can't remember exactly. Or maybe just put the mortscript_config.txt at the end of the operator_config file (but before sdautorun) and it will work whether the mortsscript_config is there or not, you'll have to test to be sure. There must be a proper or at least more reliable way to install mortscript...
I guess if I knew I was going to include mortscript I'd just add it to the operator_config script. Because either way having two copies of the config file with the same name is just asking for trouble, especially since Ervius kitchen by default will overwrite files without notification. Just my $.02
