El primer aviso (el largo) está relacionado con el KREON BUG (inofensivo a partir del Ixtreme 1.4)
Current versions of Kreon's ripping firmware use preset values for the angle responses to Challenge Types 24 and 25 (Response Types 7 and 5) which isn't a problem because currently all Xbox 360 games use the same target angles. Kreon applies a small jitter to the preset angles, and sometimes it will give an angle of 359 degrees for CCRT target angle 1 (deviation of -2). When stored in the SS in LSB format this angle is also known as 6701, and back when the now useless KreonChecker was introduced these angles were thought to be timing values, and a value of 6701 was thought to be radically different from values like 0000 and 0100 observed when ripping the same disc with a Samsung drive. Although original firmwares may use timing to calculate the angle measurement, the difference between 6701 and 0000 is actually only 1 degree and definitely not a huge difference as originally thought. All was not in vain however, since this discussion brought about the realization that iXtreme would improperly jitter 6701 to 6801 (359 to 360), which is completely invalid and not an angle that original firmware will ever return. The proper behavior is to rollover from 359 to 0, which was implemented in iXtreme v1.4 and is a very important security update if you use or plan to use Xbox Live, even if you only play backups ripped with a Samsung drive because it can also return an angle of 359, and for some discs it's actually the most likely measurement. And yes, this means that you can stop using KreonChecker! abgx360 has an option (not enabled by default) under the AutoFix tab that will adjust 359 degree angles to 0 so that older versions of iXtreme will not exhibit this bug, but the best solution is to simply update your firmware to the newest iXtreme release for your drive, and there will be no need to reburn any of your backups.
Aún así, ABGX360 tiene una opción para corregir el KREON BUG Pestaña AUTOFIX->Adjust angle 359 (NO TIENE QUE VER que ese juego use WAVE3. Ese aviso puede darlo tb con WAVE2.)
El aviso de abajo es porque en su base de datos no tienen un SS como el que lleva tu backup (para un mismo juego hay muchos SS posibles válidos). NO quiere decir ni mucho menos que tu backup no sea stealth, ya que si te fijas, ha pasado el stealth test más arriba. Lo que ocurre es que no es posible hacer una comprobación CRC de los sectores de seguridad de tu backup, por si hay algún bit corrupto, pero normalmente es improbable que pase eso. Si quieres que SIEMPRE se baje los SS verificados de su base de datos activa en AUTOFIX>THRESHOLD LEVEL 3
Salu2