JT
10-09-2006, 11:26 PM
Here is a C/P I took from RomCode. It's just word for word what it says in the V4.21 information. Turns out they pretty much say it all, including how to easily update the keys in the .ini file. Some good info in here if your a RomCode user.
================================================== ==========================
RomCode4.21.zip - RomCode Premium Loader Version 4.21 (Loader / ROM 102 / 103 Version)
Important *** We are no longer supporting 4.06f so you need to clean your card in 4.06f and use 4.21 with your Unlocker that is flashed with NewdRS. NOTE: Microsoft .NET 2.0 is required to run this version and you can download it from here: Microsoft .NET Framework Version 2.0 ***
NOTE: When switching to the new version, you will havet to go to "CAM Setup", enter your username and password, click "Add User" then click on "Refresh CAM List" to download your cams for use with this version.
NOTE: Currently there is a key rolling issue in RomCode due to the new packets.
As you all know, the key change packets are being morphed by an EMM B1 before they are set correctly. They changed the morphing on the very next keychange. The coder could post an update that will roll this one, but if they change it again, as is suspected, then it will not roll on the next keychange. For instance, Bev has already sent a new key today and it was different from the first 2 morphing updates.
As it stands right now, there is no "Safe" autoroll that will continue to work through future morphs.. There is a patch available to put on top of CoDeSpAcE blocker, but it just looks at the first few bytes as a verifcation and lets the EMM run.. This is very risky. Eventually, that type of fix will get looped. BE WARY of public files that say they have an autoroll fix. If it rolls after the next update, then rest assured, it's a RISKY FIX.
The coder will not provide an update that will risk getting cards looped, so for the moment, there is no autoroll. If we can come up with something that's safe, then we'll do that.
To make it eaiser to update keys, the next version will include a keygrabber in the app. Until that update is ready, you'll have to put the keys into to settings.ini file manually.
So at the bottom of the Settings.ini file:
[Keys]
KEY0=0CFA3973915FF554E9561C428B7ACAB2
KEY1=66B9F65370ED2A5B31D559D29F1C5263
AUX0=
AUX1=
================================================== ==========================
RomCode4.21.zip - RomCode Premium Loader Version 4.21 (Loader / ROM 102 / 103 Version)
Important *** We are no longer supporting 4.06f so you need to clean your card in 4.06f and use 4.21 with your Unlocker that is flashed with NewdRS. NOTE: Microsoft .NET 2.0 is required to run this version and you can download it from here: Microsoft .NET Framework Version 2.0 ***
NOTE: When switching to the new version, you will havet to go to "CAM Setup", enter your username and password, click "Add User" then click on "Refresh CAM List" to download your cams for use with this version.
NOTE: Currently there is a key rolling issue in RomCode due to the new packets.
As you all know, the key change packets are being morphed by an EMM B1 before they are set correctly. They changed the morphing on the very next keychange. The coder could post an update that will roll this one, but if they change it again, as is suspected, then it will not roll on the next keychange. For instance, Bev has already sent a new key today and it was different from the first 2 morphing updates.
As it stands right now, there is no "Safe" autoroll that will continue to work through future morphs.. There is a patch available to put on top of CoDeSpAcE blocker, but it just looks at the first few bytes as a verifcation and lets the EMM run.. This is very risky. Eventually, that type of fix will get looped. BE WARY of public files that say they have an autoroll fix. If it rolls after the next update, then rest assured, it's a RISKY FIX.
The coder will not provide an update that will risk getting cards looped, so for the moment, there is no autoroll. If we can come up with something that's safe, then we'll do that.
To make it eaiser to update keys, the next version will include a keygrabber in the app. Until that update is ready, you'll have to put the keys into to settings.ini file manually.
So at the bottom of the Settings.ini file:
[Keys]
KEY0=0CFA3973915FF554E9561C428B7ACAB2
KEY1=66B9F65370ED2A5B31D559D29F1C5263
AUX0=
AUX1=