tinkertiler
08-12-2007, 04:12 PM
[08:21] +c4eva: the problem with kreon is all timings are fake/estimated, not from original disk
[08:23] +c4eva: dump ss with samy is the best, kreon can be used to dump game data/dmi/pfi
[08:24] DannyZee: c4eva: but Kreon told us his firmware was OK, and the problem was with the iXtreme?
[08:25] +c4eva: kreon timings are not ok, they are valid to boot, but still could be suspect
[08:25] DannyZee: +c4eva: that means that ALL kreon rips are bad then :/
[08:26] +c4eva: just the ss (timings)
[08:29] +c4eva: 1.4 will fix the 360 value, but will not fix kreon suspect timings
[08:30] +c4eva: evenn though 360 is valid as it still boots, no proof 360 is invalid
[08:34] +c4eva: sdf495:dump ss with sammy is the only true correct values
[08:35] +c4eva: 1.4 gives jitter with fixed wrap, so a timer value of 6801 will become 0000
[08:37] +c4eva: as kreon ss will sometimes have 6701, then a possible jitter of +1 will give 6801
[08:38] +c4eva: blindly changing 6701 to 0000 may still boot, but could be suspect for that particular game
[08:45] +c4eva: sammy 0800 records actual timings from the disk, so is best
[08:53] +c4eva: fact remains a new game may have new timing values and kreon will just put a fake/estimated value in
[08:55] +c4eva: kreon fw would have to replicate exact routines to do timers, this may not be possible with its drive hardware
[08:57] Meks: c4eva: did the timmings use to always be the same, was kreon correct up until a certain release?
[08:58] +c4eva: meks:it was ok up to the bannings, as what would boot is not good enough, values must be from the disk
[09:29] <c4eva> 1.4 will fix the 360 value, but will not fix kreon suspect timings
;[09:30] <c4eva> evenn though 360 is valid as it still boots, no proof 360 is invalid
;[09:34] <c4eva> sdf495:dump ss with sammy is the only true correct values
;[09:35] <c4eva> 1.4 gives jitter with fixed wrap, so a timer value of 6801 will become 0000
;[09:36] <c4eva> as kreon ss will sometimes have 6701, then a possible jitter of +1 will give 6801
;[09:38] <c4eva> blindly changing 6701 to 0000 may still boot, but could be suspect for that particular game
;[09:41] <c4eva> this is why i didnt make 1.4 blindly change timer value to 0000, as that may not be correct for that particular game
;[09:43] <c4eva> 1.4 has been finished for days on all drives
;[09:41] <nylan> So can we use bad kreon rips with 1.4 on live, or not? And if not I still don't see why a 1.4. Anyone please clear this up for my dumb ass.
;[09:43] <M0mD4d> nylan: because the 6801 can occur even on older games where the 6701 is valid
;[09:45] <c4eva> sammy 0800 records actual timings from the disk, so is best
;[09:53] <c4eva> fact remains a new game may have new timing values and kreon will just put a fake/estimated value in
;[09:55] <c4eva> kreon fw would have to replicate exact routines to do timers, this may not be possible with its drive hardware
;[10:02] <c4eva> soulpet:fact would ramain that you are not using actual 360 drive hardware, and timings could not be trusted
[08:23] +c4eva: dump ss with samy is the best, kreon can be used to dump game data/dmi/pfi
[08:24] DannyZee: c4eva: but Kreon told us his firmware was OK, and the problem was with the iXtreme?
[08:25] +c4eva: kreon timings are not ok, they are valid to boot, but still could be suspect
[08:25] DannyZee: +c4eva: that means that ALL kreon rips are bad then :/
[08:26] +c4eva: just the ss (timings)
[08:29] +c4eva: 1.4 will fix the 360 value, but will not fix kreon suspect timings
[08:30] +c4eva: evenn though 360 is valid as it still boots, no proof 360 is invalid
[08:34] +c4eva: sdf495:dump ss with sammy is the only true correct values
[08:35] +c4eva: 1.4 gives jitter with fixed wrap, so a timer value of 6801 will become 0000
[08:37] +c4eva: as kreon ss will sometimes have 6701, then a possible jitter of +1 will give 6801
[08:38] +c4eva: blindly changing 6701 to 0000 may still boot, but could be suspect for that particular game
[08:45] +c4eva: sammy 0800 records actual timings from the disk, so is best
[08:53] +c4eva: fact remains a new game may have new timing values and kreon will just put a fake/estimated value in
[08:55] +c4eva: kreon fw would have to replicate exact routines to do timers, this may not be possible with its drive hardware
[08:57] Meks: c4eva: did the timmings use to always be the same, was kreon correct up until a certain release?
[08:58] +c4eva: meks:it was ok up to the bannings, as what would boot is not good enough, values must be from the disk
[09:29] <c4eva> 1.4 will fix the 360 value, but will not fix kreon suspect timings
;[09:30] <c4eva> evenn though 360 is valid as it still boots, no proof 360 is invalid
;[09:34] <c4eva> sdf495:dump ss with sammy is the only true correct values
;[09:35] <c4eva> 1.4 gives jitter with fixed wrap, so a timer value of 6801 will become 0000
;[09:36] <c4eva> as kreon ss will sometimes have 6701, then a possible jitter of +1 will give 6801
;[09:38] <c4eva> blindly changing 6701 to 0000 may still boot, but could be suspect for that particular game
;[09:41] <c4eva> this is why i didnt make 1.4 blindly change timer value to 0000, as that may not be correct for that particular game
;[09:43] <c4eva> 1.4 has been finished for days on all drives
;[09:41] <nylan> So can we use bad kreon rips with 1.4 on live, or not? And if not I still don't see why a 1.4. Anyone please clear this up for my dumb ass.
;[09:43] <M0mD4d> nylan: because the 6801 can occur even on older games where the 6701 is valid
;[09:45] <c4eva> sammy 0800 records actual timings from the disk, so is best
;[09:53] <c4eva> fact remains a new game may have new timing values and kreon will just put a fake/estimated value in
;[09:55] <c4eva> kreon fw would have to replicate exact routines to do timers, this may not be possible with its drive hardware
;[10:02] <c4eva> soulpet:fact would ramain that you are not using actual 360 drive hardware, and timings could not be trusted