Adding 'alternative' firmware files into BTCNF
-
- Posts: 4
- Joined: Mon Sep 21, 2009 2:12 am
Adding 'alternative' firmware files into BTCNF
Let's say I have a decrypted/decompressed KD file from a firmware newer than mine. If I copy this KD file into my flash as a renamed file (xxx_550.prx), then added the file into the *editable* BTCNFs, would it like conflict with the other (older version) PRX that's already there?
You'll probably have to remove the old entry or change the name of the new one since the module info would be the same, assuming you want to have both of their exports available to your application. Whether they can coexist or not depends on what they do internally. Most of the kd modules probably can't be replaced. Custom modules will work fine provided their dependencies are loaded before or they are flagged for late binding.