Quote:
Originally Posted by psyki
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 
|
Any file an autorun file calls has to be there. So if I called CFG: \windows\mortscript_config.txt it would have to exist. So it would still require overwriting (in other words I would have to have that file blanked out in the carrier package and included in the carrier_config.txt then in mortscript have the file overwrite the one from carrier with the EXEC call then, it would have to go ahead and send itself back... blah.. too touchy. My way is best. Go with it.
dB