Print

[MARCHISIO80]

QUOTE(Swizzy @ Mar 8 2012, 01:36 PM)

.. and the italians didn't create the patch themselves etheir, all they did was grab patches from xeBuild and put it in the build.py script...

Sorry, but it does not seem right.
Compare the patch we've added the patch to the original build.py (GliGli and Tiros)




Congratulations to Nitramb as it should be




we are only the first who completed and issued the new build.py
certainly not the first to have completed

[guerriero di pace]

someone is elegant for coding .... someone else is elegant in real life

[Swizzy]

QUOTE(MARCHISIO80 @ Mar 8 2012, 02:15 PM)

Sorry, but it does not seem right.
Compare the patch we've added the patch to the original build.py (GliGli and Tiros)
Congratulations to Nitramb as it should be
we are only the first who issued the new build.py
certainly not the first to have completed

I know there is a difference in the patches, but what i meant is that when 14717 was released with xeBuild patches it also uses the same patchset for this... to fix dualbooting

QUOTE(guerriero di pace @ Mar 8 2012, 01:46 PM)

1) tx website haven't posted italian patch, why later they posted nitram patch? because looks better coded but works at same time?
2)everyone can understand that:
-or the hack is the same so nitram copied the italian hack, rewritten like at school in good copy
-or works different, so he gaved M$ more info for future patching and TX helped publishing it?

I think  everyone can think on his head and get an idea

Why would they post a script/patch that says "F*CK YOU TX!"? that's frikking idiotic...

yeah, it has been rewritten, just like most other apps, they have the same function, different ways of coding, the patch may be the same, but the way it's applied can be different that means that it can work better with the method used by nitram for example, but it doesn't mean nitram give more information to MS on how the patch works as the patch itself is the same

[guerriero di pace]

QUOTE(Swizzy @ Mar 8 2012, 02:53 PM)

yeah, it has been rewritten, just like most other apps, they have the same function, different ways of coding, the patch may be the same, but the way it's applied can be different that means that it can work better with the method used by nitram for example, but it doesn't mean nitram give more information to MS on how the patch works as the patch itself is the same

ok I hope next time they release OPEN and rewritable, and not COPY others work and became not rewritable, without waiting others push them to be open.
If they use only them original work NO ONE have to remark. But isn't....
You are talking around the problem,like old italian politics man XD
say all for say nothing

@Swizzy I aprreciate you are here discussing,others stay in castle ...banning and deleting

[vola]

QUOTE(Swizzy @ Mar 8 2012, 02:53 PM)

I know there is a difference in the patches, but what i meant is that when 14717 was released with xeBuild patches it also uses the same patchset for this... to fix dualbooting

Yes we know that  patch was in xebuild, maybe this patch it's better and can work also in the future (who knows), but we choose to patch just the boot sequence just to do something different with the same result.

QUOTE(Swizzy @ Mar 8 2012, 02:53 PM)

yeah, it has been rewritten, just like most other apps, they have the same function, different ways of coding, the patch may be the same, but the way it's applied can be different that means that it can work better with the method used by nitram for example, but it doesn't mean nitram give more information to MS on how the patch works as the patch itself is the same

The nitram script may be coded in a better way, more reusable code... and more parameter to pass at the script... but the patching method is the same and produces the same results.
There's is not a better patch than another, if the console boot it has done the job, you get your cpu key, stop.

I want to remember everyone that the patching trick used WAS ALREADY IN THE SCRIPT SINCE THE FIRST RELEASE OF RGH, we only use this to patch all the CB instead of only 3 patches.
If M$ want to patch they can do it in every moment, hiding the system in a a .exe will no stop them to look inside an ecc file...

But maybe TX has a new hack, for new CBs with a new chip to sell.... and then we have broken their plans...

[pudink]

Hey guys,can someone please tell me if there is a reference number to buy the 50 ohm cable.I mean like 345GH/u cable.

Can somebody tell me the number of the 50 ohm cable so that I will ask my retailer here

[ruciz]

QUOTE(pudink @ Mar 9 2012, 12:47 AM)

Hey guys,can someone please tell me if there is a reference number to buy the 50 ohm cable.I mean like 345GH/u cable.

Can somebody tell me the number of the 50 ohm cable so that I will ask my retailer here

double-shielded coaxial 50-ohm RF cabling with low-loss/impedance.
pick one. pick a few. hope for good results.

no idea why its to be double-shielded if your not even going to use the shield (xenon install). Then again I don't know why we should use a 50 ohm RF cable on a low-voltage DC signal...

From the sounds of this thread people are losing touch with the issue at hand here. progressing. It don't matter who released it - they did when they didn't have to
We have seen before that TX hides very simple method (pogo mo thoin, DG4S MXIC, etc) to push their commercial shit. We also know the 360 stuff so far was all figured out publicly by someone else, to have it spiffed up and sold by TX. IMO this fusion kernel should have released with their NAND-X like 4 years ago. more money designing replacement PCB and X360USB tho

[OggyUK]

TX hid Pog Mo Thoin?

Really?

TX Released it publically for free THEN released their commercial product.....

The x360usb was intended to be the first usb2sata device for flashing all 360 drives including MTK Based drives.

It would have been, too, but Maximus also designed one at the same time (seriously a freak coincidence) - Maximus released his first but it's still only ~70% as advertised.

That still, they took one of the most popular I/O devices and ported it to the 360. Hardly a waste of effort was it? Anyone can now mod using a laptop (and I do, daily)

The replacement PCB was a means to an end, it worked, it was all anyone had, would you rather have nothing?

TBH, Geremia produced a fantastic but lethal hack. The measurements are great but not 100% for all drives, kill it, what can you use as a backup? That very same PCB.

I'm hardly Xecuters flavour of the month for the past 12 months but if I see someone talking shit I have to correct it.