QUOTE(dufc1983 @ Jan 30 2010, 09:55 PM)

i've noticed the dlc that i haven't run through yaris swap ie stuff like forza and left 4 dead dlc we have to use dlc patcher but this app im guessing is using yaris as a base hense it will still report the dlc locked so unlocking it within the app might cause problems im to scared to even try it when i know the dlc is working :-) just thought i'd put that idea forward to you otherwise ace work as always
No, xm360 no longer uses the basic "yaris swap". It has knowledge of the entire block of licenses.
If your DLC is showing up as "locked" in xm360, it just means that if you choose to "unlock", xm360 *will* be changing something. That something might not actually have any effect, but it is very unlikely to break anything. ( as it turns out, there is a slight bug in how it determines if it is "unlocked" or not, but unlocking it if it was wrong won't do any harm...explanation follows, I've already fixed it for the next release)
Once and for all, the algorithm for determining if your content is "unlocked" is as follows:
All 16 license slots must have either all zeros or all FFs in the first 8 bytes.
All 16 license slots that have all FFs must not have 4 zeros after them.
That is the correct algorithm. The bug in 0.6b does this:
All 16 license slots must have either all zeros or all FFs in the first 8 bytes.
All 16 license slots that have all FFs must have the value 0x00000001 after them.
The reason this isn't harmful is that the *UNLOCK* code does the following:
All 16 license slots must have either all zeros or all FFs in the first 8 bytes.
All 16 license slots that have all FFs must NOT have 4 zeros after them. If they do, the value 0x00000001 is written. Otherwise, the existing value is left there.
So, if you have some DLC that has:
FF FF FF FF FF FF FF FF 00 00 01 01
xm360 0.6b will say that it is locked (which is the bug). If you unlock it, it won't do anything.
Anyway, the short story is that it is safe to "unlock" with xm360, as the algorithm is sound.