Xbox Backup Creator v2.7

[Redline99]

Xbox Backup Creator v2.7 Build:0265

Its not a normal full release and doesn't contain an installer.

=================================================================================
Added - Added support for Kreon's SH-D163B firmware
Added - Added support for Kreon's SH-D162D firmware
Added - Verify Disc button on the Drive Tools Tab
Added - Added option to do a Verify Disc after a Burn
   (Note: Used ImgBurns build in Verify when selected)

Xbox_Backup_Creator_v2.7.0.265.zip

Also on xbins.

[sadalius]

Small bug, doesn't affect performance at all, but if you go to image tools and hover on the Video Section button, the tool tip says "Disk Manufacturing Information" instead of "Video Section".

Thanks again Redline99!

[CrUnc}{eR]

Are there any new changes in the works that will make back-ups appear to be more original 1/1?

[nick.king]

Sorry to sound like a complete newbie but as it happens when it comes to making my 'own' backups I am.

Maybe someone can help me and maybe they can't but I'd like the opportunity to ask anyway.

I have a backup that worked on xtreme 5.3 of which I 'thought' I'd stealth patched back in January, obviously with the release of ixtreme 1.2 it no longer boots although xdvdmulleter beta 8 said it was ok.  The problem I get is when it's inserted into the 360 I get the 'please insert this disc into an xbox 360'.  I'm assuming the videoiso is incorrect or I've patched it incorrectly.

I have the pfi, dmi and ss.bin files, my question is do I have to rip again from the original or can I use my existing backup and fix it somehow?  If so how do I go about this, can some explain how I'd go about this or point me in the direction of a tutorial?

Many thanks.

[XFear]

More people have trouble with iXtreme 1.2, just wait. Your backup is fine

[nick.king]

More people have trouble with iXtreme 1.2, just wait. Your backup is fine

It doesn't boot because it's not properly done, ixtreme 1.2 is fine with properly stealthed backups

[nick.king]

ith XBC 2.5 build 0230, when I run the stealth check it says image new splitvid format!

No dont burn it.. the iXtreme and SplitVid of that version are not compatible.  The new build I have will be iXtreme compatible version of SplitVid.  So for now if you want to make iso's for iXtreme, turn off the splitvid option.

Thanks for the reply, I just read through a link you posted earlier in this thread and found that I should turn the option off.

I'll make that image again.

Nick.

[Protonus]

I'm having the aforementioned problem of a gray'd out start button - I can't begin the backup process. I'm using a SH-D163A (SATA, connected to an onboard VIA 8237 SATA controller, to the first/primary SATA port (there are two)) flashed with Kreon .80.

Well, I fixed my own problem - kinda.  This should probobly be a sticky or something some where as I found a few posts on XBS the other day confirming this issue with others. 

Or maybe a note in the software itself?  Or in the requirements?
Bottom line:

The VIA 8237 SATA chipset is NOT compatible with the SH-D163A drive for the purpose of backing up games via Schtom or XBC

I actually got this to work, once, by screwing around for DAYS with the ATA and SATA drivers on my friends computer, trying different revisions and BIOS's... It worked and then never worked again after a reboot.

His PC Died, and I started using another friends computer for this. After having the same )!#%(!*#5 problems again on his computer, I saw that this computer too, had a VIA 8237 chipset.  I tried many drivers and BIOS's etc and never got it working.

So I popped a SIL 3112r chipset PCI SATA controller I had in his computer, flashed it with the latest BASE (not RAID) BIOS, and the latest BASE drivers and... it worked on the first try! And I've backed up several of my games with great success now.

So, if you have a VIA 8237 chipset and the SH-D163A drive, you should try a different controller. Trust me, your PC and the hair you don't pull out will thank you :-D

[Redline99]

Before IXtreme came out the firmware didn't really treat the video data correctly.  It was cutting half of it out when read by the xbox... The data was there just not in the correct position, that was happening since the very first xtreme firmware and the batch files to build the iso's.  When IXtreme came out c4eva fixed the firmware to support the incorrect iso's. So that means anything before IXtreme doesn't read the video data correctly. What splitvid does is copy the video data that it wasn't reading to a position where it will read it correctly.

So now the current splitvid has the data in the correct position for both the old firmware and the new firmwares.

But... it is not a big deal right now because as far as I know the xbox doesn't error out on half of the video data missing. And if you use IXtreme then its been fixed in the firmware anyways. Either way splitvid doesnt hurt anything it adds more compatibility. XDVDMulleter may not treat the original iso layout as an issue, because its only a possible issue on old firmwares.

Its just an extra precaution that if you use a non IXtreme firmware to play games then you should use splitvid, but you don't have to for any real reason and thats why its an option.

You can upgrade to 2.6 and just turn off the splitvid in the options.

[Lord Sesshomaru]

Thanks for the explanation Redline!

[cygnet]

With the new splitvid in the latest XBC, is it right to get 7.29GB size when normally its 7.05GB? 

[Zivi]

7,29 that's the correct size for SplitVid! 7.651.848 kb

[Redline99]

FYI.

You might want to check for firmware updates for your burners. Updates typically add support for new media. For example, with my burner I could only burn 2.4x with the new Memorex 8x DVD+R DL dvds.. updating to the latest firmware added full 8x support.

[whiteboxx]

sorry.. omg maybe its becouse there is too less cafeine in this coffe.. but where can i download this firmware?

[Redline99]

from you DVD manufacturer's website probably. (btw this is not xbox firmware related)

[phool]

I have maximus garyopa 2.3 stealth rev. 2 Hitachi

I have the Hitachi GDR-3120L 
ROM Version 0059DJ
Manufactured April 2006

I Also Have the Samsung SH-D162C With Kreon 0.81 Firmware
and XBOX Backup Creator 2.6.0260

I am interested in making 1:1 complete backups of my brought 360 games

A few questions for redline99 or anyone else who knows for sure

Should I change or update my firmware in my xbox 360 Hitachi Drive ? what's the best firmware for playing originals and backups with this drive ?

I'm looking for the best stealth firmware with media guard media stealth and firmguard I want my drive to look like the original drive when I play my original purchased games online if I decide to go online (correct me if i'm wrong but I can make perfect copies with my kreon drive so I don't need to use xbox 360 to rip extract images right ? so I should get a firmware for xbox360 drive that focuses on reading originals and backups only and doesn't have extraction capabilities ? right ? or do most or all have extraction ability and it doesn't make it look changed modified from the original unmodded xbox 360 dvd rom drive original rom flash either way with or without ?.)

also when I'm not online I want to have playable perfect 1:1 copies of my brought games in case the original gets messed up

I'm a little bit confused about splitvid option should I enable it when ripping with my samsung kreon drive ?
does it make it more or less like the original game from the data standpoint ?

I'm looking to make perfect stealth 1:1 complete backups of my original that mirror the original perfectly or as close as possible

finally I have clonecd so I can use that to burn the image and .dvd files generated by xbox backup creator and they will remain perfect 1:1 stealth backups with that instead of using imageburn ?
Which aspi layer should I use when ripping games with my Samsung SH-D162C With Kreon 0.81 Firmware PC DVD-ROM drive ? does it matter or is SPTI okay or is nero better or adaptec aspi or frog or alcohol etc...

I think that's it for now sorry just trying to get up to speed I modded my xbox360 drive originally a year ago and hardly ever used my xbox360 so just trying to catch up and have the best possible mod setup and game backup playability all that

Thanks In Advance for any suggestions help given

[kickme]

I've a problem with Backup Creator if I have turned on AHCI-Mode for my SATA-Controller. After start of the tool a message box is displayed with the following description:

Logic Error in cboDrive_Click
              Set moODD = moDrives.Item(cboDrive)

If I check OK, the tool opens, but the two drives which a hanging on the SATA-interface are only displayed with the drive-letter. It is not displayed the name of the drives. There is a Pioneer 212 and a Samsung SH-D163B attached to the SATA-Port. There is no problem if the AHCI-mode is turned off of the SATA-Interface. But I won't do that because there is also a SATA-HDD in the System.

The SATA-Controller is from the internal Intel ICH9R Chipset.
OS is Vista.

Schtrom360Xtract seems to have no problem with AHCI.

Greets

Mario

[pash]

This is not a true 1:1 copy of the image.

This is just a little bit confusing, i thought this text only belongs to sector mapper. But when creating a 360 image the sector mapper checkbox is grayed out, with sector mapper aktivated, but the text not.

Or does the text vanish?

So i think the text only belongs to xbox 1 and can be ignored on creating xbox 360 images.
(Found a lot of people that are confused, hope i got it right..)

[CrUnc}{eR]

-Request: show file name selected when using the write feature. That way I can remember what game I just burned

-?Bug: the write verification never seems to work. Games play just fine but it always says that the write has failed. Ripping with a D162C Kreon 1.0, burning with 111D.

-Request: Add support for CloneCD split image files

-Request: Option to Refuse to burn unless it is a valid image. (in attempting to burn CloneCD split image files XMC would not utilize the .dvd file, so I attempted to use the .000 file, so it only burned the first part of the image- my dumb fault)

[Redline99]

Thanks for the post, I'll look into them.