Scenyx Entertainment Community > Xbox360 Forums > Xbox 360 Hacking Forums > Technical DVD-ROM and Modified DVD Firmware Forum
i hope we see a new fw for hitachi soon too.
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.
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.
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.
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.
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.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.