Print

[TukTuk]

About the kreon checker. Is this tool still valid?

I'm guessing it checks for high angle values that could in ixtreme result in incorrect values >359? (<0?)

So the jitter max/min random value generated by ixtreme is indeed considered in this tool?

(Can this value also be negative? If so, does ixtreme report incorrect values then too?)

Sorry about all the questions... just want to clarify.

Keep up the good work folks - u know who u are!  (IMG:style_emoticons/default/cool.gif)

[Pwnr_Dood]

I think just screw making backups all together it's to much work and money and is not nearly worth the effort.
When in the end your going to get banned anyway. I'd rather just buy the real games.

[mikearama]

QUOTE(Pwnr_Dood @ Dec 7 2007, 01:45 AM)

I think just screw making backups all together it's to much work and money and is not nearly worth the effort.
When in the end your going to get banned anyway. I'd rather just buy the real games.

Excellent idea... you go ahead and do that.  Microsoft appreciates your business.

For the rest of us who enjoy the effort and challenge, we'll keep doing what we do.  And, based on the numbers, only a few of us will end up banned.  We understand the risk.

[HackMy360]

QUOTE(staple123 @ Dec 6 2007, 02:09 PM)

I quote KREON:

"the 359 angle can be found in SS files extracted on an OEM 360 DVD drive as well. "

Now this is the exactly opposite of what we were told 18 months ago...and it was THAT SPECIFIC  concern about the integrity of the SS file and the way it was randomly generated by one of the early v.80 KREON drives..in fact it was understood that the 360's internal OEM drives were considerd a much better choice for ripping any ISO to make sure that the SS was proper...;we were told that there was no doubt the OEM360 will do a much better ripping job of the game image.  I STILL BELIEVE THAT IS TRUE.

TIME TO BUY A REALLY LONG SATA CABLE TO CONNECT YOUR PC TO YOUR 360 and retire these KREON rips...I don't trust them and neither should anyone.
I am not trying to insult KREON, I very much appreciate his work, but its time to eliminate one of these programs from the ripping equation and simplify this process...from reading your newest comments you still have many unknows in your KREON software..the less unknowns the better.

Its time to buy a really long SATA cable to connect our 360's to our PC's and retire KREON

seeing as the longest sata cables are around 3 ft maybe you can design a 20 ft then give each and every one of us one (IMG:style_emoticons/default/grr.gif)  (IMG:style_emoticons/default/grr.gif)  if you do not want to use the kreon drive don't!! if you can come up with better firmware for the 360 and the samsung drive then make your own and mess up your own s**t stop coming in here bashing other peoples hard work. You make me sick (IMG:style_emoticons/default/grr.gif)  (IMG:style_emoticons/default/grr.gif)

[DeeRez]

Just curious, could an original disc produce this error when handled by the iXtreme firmware? Sorry if this is a silly question.

[Terminality]

i hope we see a new fw for hitachi soon too.

[telo{+}]

Not to be a dick, but SATA cables can not get too long. They start getting common mode noise and shitting the bed.

Whoever suggested a long sata cable is obviously mistaken of reality. Now, if you lowered the speed enough and adjusted the rise/fall wave shaping then its just copper and will work fine. You can look up capacitance, biased termination and differential signals but for the sake of argument sata speeds over cheap copper drop out probably around a meter depending on speed.



Back on topic, I appreciate everything C4e is doing.... but isn't a degree value to be returned going over 359 a very basic mistake ?  I do embedded work all the time, granted its not drive firmware, I would think unless the value was never identified as 'degrees' and rather just a magic value its odd that would have been overlooked.

Now, I could understand if they limited the return to one byte (0-255) and then adjusted the physical rationality to 1 bit is not equal to 1 degree. In that situation I could understand a rollover issue since then 255 (which could be 358, 359, 360, or 0, etc). It would be tough to reverse engineer that situation without having a game that rolled over, which it seems until now has been the case.

But if its over a two byte value (or at least a minimum of 9bits) then I find it either a really simple mistake, or the entire truth behind whats going on isn't being reported.

Doesn't really matter, I'm sure it'll be fixed. But, it makes me think he either kicked his own ass after a mistake like that or its more complicated then just a value rollover.

QUOTE(DeeRez @ Dec 7 2007, 02:33 AM)

Just curious, could an original disc produce this error when handled by the iXtreme firmware? Sorry if this is a silly question.

Thats not a silly question. I would almost doubt that any signal modification is done to originals. If the 'jitter' function is written to be the same function that originals would be just to as well as backups - it could maybe possibly but most likely not and issue.

[Iriez]

Ok, there has been more than enough flaming and arguing.

We dont have all the answers, but I think kreon summed it up quite nicely. Its not neccessarily his firmware that is the issue at stake, but instead the combination of jitter between the two, combined with ixtreme's inability to wrap (no 360 response).

This is what ixtreme 1.4 will do.

Instead of me deleting like 300 posts, im just going to close this thread. It has saturated enough, and I dont believe any more value can be added.