Xbox ISO format (Do not use!)

[Redline99]

There have been some mentionings of how the video partition is layed out in the ISO's. There is some confusion on whether Xbox Backup Creator can make the iso's correctly. It currently does not create the video correctly. Only the WxRipper style images are correct, none of the Xtreme style ISO's are correct...(this includes a large majority of existing "scene" releases)

The SplitVid has been in XBC for some time now and it was supposed to be one of the major new features a couple releases ago, but for reasons I can't go into the feature was pulled. Also when doing a Stealth Check, and it returns "Video is questionable" it means that "CD001" was found at sector 16 but it was unable to parse the file system. This can be for several reasons, the file system is not there to be parsed, the file system is corrupt or the file system is split up in the new SplitVid format. The wording was changed at the last minute so it was never very clear as to what it meant.

I'll probably do a new release when there are some advancements on the firmware front. At that time I'll do some house keeping and other bug fixes.
Edit2: On my list is to double check the Stealth Check procedure to make sure it's not buggy

I do not believe that the ISO format is the cause of the bannings based on information coming to light but, seeing how MS has stepped it up some I wouldn't create any in the old format. Remember like everything else, if you play outside of Microsoft's rules you are subject to the consequences. It is up to you to make your decisions on how you want to play.

I've heard of some troubling behavior directed towards members of the scene after the "ban hammer" came down. Shame on those people.

Here is how to get the correct iso format in Xbox Backup Creator.
Save the following to a text file and rename it SplitVid.reg, save it then double click it and import it into the registry.
This will enable a new setting on the options tab, under the read group options and it will display a new button on the Image tools tab. 

Please note that I'm kinda just throwing this out there and really I should do due diligence to make sure it all works properly since it never was a released feature. (This is my disclaimer in case it is buggy)

Edit: I would only do this with the latest release (Xbox Backup Creator v2.5 Build:0230) because I don't remember the state it was in on any previous release

Code:

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\VB and VBA Program Settings\Xbox Backup Creator\AppSettings]
"EnableSplitVid"="1"
"BuildSplitVidISO"="1"

Details:
Note: This is just an example, the values have to be calculated from the PFI and from the SS to correctly determine the offsets.

Basically what the problem is, is that the video data that was supposed to be located on layer 1 (the second layer) is being truncated because it is outside of the valid PSN range dictated by the PFI.  To correct this the video (VL1) data is actually supposed to be split off from the rest of the video data (VL0) and placed AFTER the game data. This moves it to a PSN location that is visible when the dvd is in a locked state.  Currently that data will show as just 00 data, thus looks missing or truncated.

Now don't everyone go out at once and buy new DVD+R DL dvd's, you'll cause a global shortage and drive up the price!
(That was supposed to funny... anyways good luck)

Code:

    Example proper iso build order, Xbox360
    000A90 Video  L0
   
    01F090 Filler L0       'Actual
        - OR -
    01F08D Filler L0
    000003 PFI, DMI, SS    'Xtreme
   
    1B3880 Game   L0
    1B3880 Game   L1
    01F090 Filler L1
    00032F Video  L1
    ------
    3A5FDF Total (7,834,892,288 Bytes)
   
                         |   FILLER   |
    |-------------|------|------------|-------------------------------|----------| L1
                  VL1E   VL1S         GL1E                            GL1S
   
                         | FILLER |   |
    |--------|-----------|--------|PDS|-------------------------------|----------| L0
             VL0S        VL0E         GL0S                            GLOE
        PSN  |0x30000
   
    VL0S = Video Layer0 Start
    VL0E = Video Layer0 End
    VL1S = Video Layer1 Start
    VL1E = Video Layer1 End
    GL0S = Game Layer0 Start
    GL0E = Game Layer0 End
    GL1S = Game Layer1 Start
    GL1E = Game Layer1 End
    PDS  = PFI, DMI, SS

[Schtrom]

I only wanna say that S360X does not support the SplitVid stuff out of the box and it can't be enabled like in XBC. Therefor it would be good to use only XBC for SplitVid image creation atm. I don't know if the wrong disc building is the reason for a ban, but it is in fact a possibility how MS could detect a backup disc.

[FOOLVER]

Tested! all seems ok! Thanks

[Redline99]

The thing with WxRipper is that is doesn't use the PFI from xbox dvd, in essence it uses the one from whichever dvd you use to swap with (which should be bigger)...well by doing this you bypass the need to recreate the data from both xbox dvd layers and it copies as is, spaced out as is it physically lays.  I can't really say much else on it since I have never personally done that procedure.

[e5frog]

Which means (even if read 100% correctly) the PFI might not be entirely correct...

[sdeens 2006]

Redline99 
 
 
now some immediate feedback:

I made the change to windows registry and now XBC v2.5 is showing these new "splitvid" features...but there are some annomolies in how is it "rebuilding" the new image.

1.  Why does is still state that "VIDEO IS QUESTIONABLE" after we patch to the new Splitvid format?

2.    Why is it NOT patching the splitvid image directly when you intially now do a READ using the 'patched' version of XBC v2.5..the key word here is "initially"

If you READ an XBOX360 image using XBC v2.5 with the option for "splitvid" selected the file size is: (7,572,881,408 bytes), but if you take that same image that was previosly ripped using XBC v2.5 (before or even AFTER the windows registry update) it becomes (7,834,893 bytes)....about 255 MB larger.

Same goes if you read the XBOX360 image using XBCv2.5 (after the windows registry update was applied) using IMAGE TOOLS  command...."Convert to Splitvid"

so in the end it gets patched correctly but NOT in the proper order AND not FROM THE INTIAL read COMMAND...its a two step process...and it does not alert you to its importance.

 
you need to incorporate that into the DIRECT reading function since most people will forget to also run subsequently the "convert to splitvid" command under the image tools section...I can see this comming so be aware...the ONLY notification they will receive is if when they run the stealth check and it states the following:

"Image is in OLD format" or "Image new splitvid format"...

the assumption intially will be that the READ command performs this function, but it in fact does NOT...

so to get our images to be perfect with respect to SPLITVID is a two step process:

a.  READ using the modified XBC v2.5
b.  execute the "convert to splitvid" command under Image Tools

also as a side note an original XBOX1 game when patched in this proper manner is slightly smaller  (7,825,162,240 bytes) than an XBOX360 game re-ripped an patched with the new iamge format (7,834,892,288 bytes)

3.  what exactly is causing this differential between the two games?

Call of Duty 2 (XBOX360 version) and COD: Finest Hour (XBOX1 game) were the test platforms for this new patching technique.
   
 

[Redline99]

1.  Why does is still state that "VIDEO IS QUESTIONABLE" after we patch to the new Splitvid format?

Because it was wasn't completely finished as a release feature.

2.    Why is it NOT patching the splitvid image directly when you intially now do a READ using the 'patched' version of XBC v2.5..the key word here is "initially"

Not sure, it works for me fine. I tested it tonight.
Read Burnout Revenge (Original ISO Format) = 7.05 GB (7,572,881,408 bytes)
Read Burnout Revenge (SplitVid ISO Format) = 7.29 GB (7,834,892,288 bytes)**
Converted Burnout Revenge (Original ISO Format to SplitVid) = 7.29 GB (7,834,892,288 bytes)

So it looks to be working for me, put the Log Level on Debug, do a complete backup using SPlitVid and PM me the log.
**The SplitVid format ISO size can differ slightly depending on the Video partition size

so to get our images to be perfect with respect to SPLITVID is a two step process:

Not for me, so send me your log.

also as a side note an original XBOX1 game when patched in this proper manner is slightly smaller  (7,825,162,240 bytes) than an XBOX360 game re-ripped an patched with the new image format (7,834,892,288 bytes)

Be aware that the ISO image sizes are not a hard coded value.. they are calculated based on the PFI and the SS. These differ between xb1 and xb360 and can even differ on the same platform, example Xbox360: PGR3 and Star Trek Legacy will differ in file size.

[sdeens 2006]

oh yes I forgot about the Star Trek: Legacy issues and I can see how that would effect now the overall image sizes;  that was a game as I recall that could NOT be backed up properly until you released v2.5, or was it v2.4...but I see the point.

but for me, its still a two(2) step process to get the image completely ripped into the new SPLITVID format

1.  READ with modified XBCv2.5, with "build splitvidiso": option selected
2.  execute "convert to splitvid" under IMAGE TOOls command aftre its saved to PC in ISO format.

until I do that, my saved ISO images wont be the correct size:  (7,834,892,288 bytes)

I will run some more tests on some other random XBOX360 games to see if this applies to more than just COD: 2 (XBOX360 version)

also,

will XBCv2.5 (modified for SPLITVID) read our backups (already burned to DVD +R DL) in the same exact manner as the originals mastered games?  assuming of course the burn was complete and accurate.


why did I ask?

because, my original COD2 disk (XBOX360) is way too scratched up and it just wont fully read anymore...(this is very common among the heavily used multiplayer games--especially this game); 

so my tests were done exclusively from my saved COD2--360 images I stored on the PC ripped originally BTW with XBCv2.3....and I also tested by reading the backup of this game I burned to a Sony DVD +R DL media, using the "modified" XBCv2.5..with identical results....so ripping and patching the backup or working with my saved images gave me same results...triggering a two(2) step process.

no one(1) step READ for me with modified XBCv2.5 to get it fully patched in the new splitvid format..at least with COD2 (XBOX360 version).

 I will run the debug command option for your log report and post it later...I also use the samsung DVD flashed with Kreonv.81 for these backups and tests always..

[Redline99]

ahh ok.. If you are using a standard dvd to read off a current back then I don't think it will do the converion to splitvid for you. I think it will only create the SplitVid when reading from an original.. that may be where our difference is.  (I would have to double check, but probably is the case)

[sdeens 2006]

my thoughts exactly, I suspected that was the reason too....


here's the results from a fresh READ of a Sony media (DVD+R DL) backup of Ghost Recon: Advanced Warfighter (360 version)

"read":   (7,572,881,408 bytes)
"convert to SpitVid":  (7,834,892,288 bytes)


Does this really make a difference in the end, since many of us don't have the originals anymore and even if we do they are scratched in some cases beyond the abilty to get a clean read?

this would be a huge bummer and negate some of the value of this update...unless of course its not important or you can provide us another update to adjust for it...becasue I gauarantee you this will a huge issue for updating our overall libary's.

The closer we can get to being 1:1 the better....

also here is the clean debug log report..unable to upload it as attachment:

Edit: Logs should be sent via PM's

[mrtvgame]

Just curious and by no means disrespectful, but Redline why couldn't you put the layer break into a previous version or new version?  You mention you can not go into it.  Legal issue?

[e5frog]

Maybe it needs some expertize knowledge or it's to complicated to explain...   Let him work on it instead of explaining it in details to us mere mortals.   



I just ripped my "Full Auto" with the SplitVid option checked, just burned it, but I can't test it right now though as the XBOX 360 ODD isn't flashed.   ;-)  Perhaps Commodore4Eva has a new release this weekend, I might test it offline at least.


I didn't use the "convert" option in between, I understood it as it was only supposed to be used to convert an already ripped .iso into a SplitVid version - did I get it wrong?

The size of my ripped Full Auto is 7,834,892,288 bytes, also tested my new Canon Pixma iP6700 - it printed a pretty nice picture on the Inkjet Printable Verbatim DVD+R DL 2,4x.   ;-)

[Redline99]

I didn't use the "convert" option in between, I understood it as it was only supposed to be used to convert an already ripped .iso into a SplitVid version - did I get it wrong?

Need to run the Image Tools SplitVid Convert if you read the iso from an already burned copy using the "Current Partition" option.

[e5frog]

I would probably not try to make a SplitVid version from anything but the original, I might however copy a backup that was made with the SplitVid option - I guess using a program like CloneCD or Nero straight off? If I wanted to have an additional backup that would perhaps be the quickest way instead of starting the procedure all over (if I didn't save the iso I made the first time that is).

Is there any way to verify that a SplitVid backup is equal to the original disc? Would it be possible (and feasable) to have the original disk in the Kreon 0.81 flashed SH-D162C drive, read the whole disc and compare it to the backup (skipping the stealth parts) placed in another DVD-drive - like the DVD-writer? Checking one layer at a time?

Would be neat just putting original and DL DVD+ in one drive each, press a button (after setting options) and wait for an iso to be saved, backup burnt and a verification that checks original and copy corresponds.


BTW - I didn't burn the iso I mentioned earlier from XBC, I ran ImgBurn instead, wasn't sure that part of XBC was OK.

[Redline99]

I would probably not try to make a SplitVid version from anything but the original

This is the best option and you should have your original in a safe place not getting scratched anyways.

Is there any way to verify that a SplitVid backup is equal to the original disc?

At one point in time I was going to add a verify procedure, but I lost interest in that to be honest. Maybe in the future I'll have some kind of verify after burn, or verify like you described.

I didn't burn the iso I mentioned earlier from XBC, I ran ImgBurn instead, wasn't sure that part of XBC was OK.

For some people it works others is doesn't, that why I also included an option to use Nero or ImgBurn from my app. You can still use any burning app you want as long as you can set the layerbreak.

[sdeens 2006]

So the key and most important issue here is that this SPLITVID must only be done via a complete READ using the original game disks with the "modified" XBCv2.5..and not on burned backups or even the saved .iso-images on our PC's.


thats a big problem potentially.


Edit: Surely we don't want what you are suggesting.

They are going to be paying much close attention to these backups since that seems to be the area where the most permutations exists for detectable flaw generation.

Staying one step ahead is the ONLY way one might escape the next round of ban activity...I would NOT be surprised if they step up the frequency of these kernel updates..if that happens which I expect then cat and mouse game gets much worse.

BTW,

please keep up the good work, its greatly appreciated......

[sdeens 2006]

I use to have a problem burning these DVD +R DL using any previous versions of XBC on my Sony-DVD-RW "DRU810A", but NOT anymore after v2.5 was released;

If I select the option for "NERO engine"..its burns the disk perfectly, but the other option: "XBC engine" will generate a trouble code error shortly after launch and crap out and subtly corrupting the blank DVD +R DL....so I can burn ONLY using the NERO engine option in v2.5.

The other option:  "IMGBurn"  remains shaded and not available as a selectable option..only NERO option works.

Is there a reason why IMGBurn is not an available option under XBC v2.5 ..?

also, ImgBurn v2.3.2 is fully installed on PC and still burns perfectly as a standalone application, but I can't select it as an option in "modifed" XBCv2.5, which would be the more ideal solution....

[Redline99]

sdeens 2006:

There is a button next to ImgBurn on the write tab, use that button to tell Xbox Backup Creator where the executable is.

[sdeens 2006]

great that worked...

I thought that tab to the right was still unshaded...at least to a casual glance it looks that way.

thanks a bunch it now works.

I suspect this would have NOT been a problem if I let the IMGBURN installer appplication install itself to its native default directory like i did with Nero v6.6..I moved it around on my PC.

BTW,

new splash screen upon a restart of XBCv2.5 shows its now detected:

Nero v6.6.0.19
ImgBurn 2.3.2.0 is available
   ImgBurn - The Ultimate Image Burner! by LIGHTNING UK!"

[XFear]

Ok, it's not very clear for me.

Just to verify:

It isn't possible to use the Covert to SplitVid option for a ISO on your pc, right?