Print

[Sphinx3]

Ok I recently got my kreon SH-D162C (kreon 1.0) drive.

I installed it.

I put in my original guitar hero 3 disc.

I used XBC to rip the image (.iso and .dvd files).

I then used schtrom360 to do a stealth and crc check on the image.
I compared the CRC results to that listed for guitar hero 3 in schtrom360's "stealth.ini" file.

EVERYTHING matched EXCEPT SS, SS RAW, and DMI.

If i am correct are these values that vary between manufacturing companies of the discs?

Now heres the interesting part.

I used XBC to rip the security sector .bin file from the ORIGINAL DISC in the kreon drive.
I then used XBC to rip the security sector .bin file from the IMAGE i just burned w/ the kreon drive.

I compared these two files in a hex editor and found they were different - what the heck!!??


I reripped the image with schtrom360 (instead of xbc) and got the same results.

Also i noticed schtrom360 is a LOT slower ripping the disc - is xbc still recommended?

I am concerned about the inconsistency between the original disc and the image. Should I be worried about this? I can return my kreon drive and instead get an extra ms28 if that would fix the issues.

Please someone help me, thanks!

[destro604]

QUOTE(Sphinx3 @ Dec 17 2007, 11:50 PM)

...I then used schtrom360 to do a stealth and crc check on the image.
I compared the CRC results to that listed for guitar hero 3 in schtrom360's "stealth.ini" file.

EVERYTHING matched EXCEPT SS, SS RAW, and DMI.

If i am correct are these values that vary between manufacturing companies of the discs?

Having a CRC mismatch between what you ripped and what is 'known to be safe' does not necessarily mean that there is anything wrong with your rip.  These values can change between manufacturers and pressings.

QUOTE(Sphinx3 @ Dec 17 2007, 11:50 PM)

I used XBC to rip the security sector .bin file from the ORIGINAL DISC in the kreon drive.
I then used XBC to rip the security sector .bin file from the IMAGE i just burned w/ the kreon drive.

I compared these two files in a hex editor and found they were different - what the heck!!??

This is normal behavior; nothing to get too excited over.

QUOTE(Sphinx3 @ Dec 17 2007, 11:50 PM)

Also i noticed schtrom360 is a LOT slower ripping the disc - is xbc still recommended?

Take a look under options, you'll see you can adjust read speed there.

QUOTE(Sphinx3 @ Dec 17 2007, 11:50 PM)

I am concerned about the inconsistency between the original disc and the image. Should I be worried about this? I can return my kreon drive and instead get an extra ms28 if that would fix the issues.

Firstly, make sure you have iXtreme 1.4.
It is not possible to make a true 1:1 backup of an original disc.  Both the kreon drive and an ms28 will create an acceptable image.  Run the stealth checks and if it passes, you're about as safe as you can get.

[Sphinx3]

Great reply - thanks a lot.

I will be upgrading to 1.4 from 1.3, before i use any kreon backups. I will keep the kreon.

I am just curious though, why would the CRC of the SS of the original game differ from the CRC of the SS of the image burned from the original game (both using the same kreon drive). ?

And secondly - I don't use mulleter often, but what does the 'check game data' (the part that takes forever in mulleter) do exactly? Does it find one CRC value for the entire game data partition? Or is multiple CRCs.
Are tehse compared against an online database or against something on the game itself?  In Schtrom360s CRC check, there is a CRC value for "game.iso" or whatever its called. This does take a good couple minutes to calculate, but why does mulleter take like 40 minutes to do that?

Is schtrom360s check not as thorough as mulleters, or is it sufficient?

I don't use mulleter because it doesn't run on my desktop (i have .net 2.0, i simply get an "sorry for the inconvenience, have to close" error as soon as I start it up.  I am used to schtrom360 however and would like to just use that (and XBC) if the CRC check is sufficient.

Thanks

[destro604]

QUOTE(Sphinx3 @ Dec 18 2007, 01:23 PM)

I am just curious though, why would the CRC of the SS of the original game differ from the CRC of the SS of the image burned from the original game (both using the same kreon drive). ?

Your SS CRC can change each time you rip the SS, from what I understand more so with the kreon drive due to the way it handles timings. However, this is not a bug, it's a feature (IMG:style_emoticons/default/tongue.gif) .  For example I ripped the SS from gears of war 10 times with an SH-D163B (a very limited test) and I got 7 different CRCs.  Don't worry about it.

QUOTE(Sphinx3 @ Dec 18 2007, 01:23 PM)

And secondly - I don't use mulleter often, but what does the 'check game data' (the part that takes forever in mulleter) do exactly? Does it find one CRC value for the entire game data partition?

yes

QUOTE(Sphinx3 @ Dec 18 2007, 01:23 PM)

Are tehse compared against an online database or against something on the game itself?

yes, if you check the correct box.

QUOTE(Sphinx3 @ Dec 18 2007, 01:23 PM)

In Schtrom360s CRC check, there is a CRC value for "game.iso" or whatever its called. This does take a good couple minutes to calculate, but why does mulleter take like 40 minutes to do that?

wow. I've never had mulleter take 40 mins to check game data.  Hop on to #stealth360 and ask there.

QUOTE(Sphinx3 @ Dec 18 2007, 01:23 PM)

Is schtrom360s [CRC] check not as thorough as mulleters, or is it sufficient?

I don't really have an opinion on the CRC check in schtrom360 because I don't use it.  Not because I don't like it, I just don't use it.  It is my opinion that the CRCs (especially the SS CRC) are not that important.  The stealth data - SS, PFI, DMI - could change between manufacturers and revisions.  Whats important is that they are present and valid, which the stealth check will handle nicely.

This post has been edited by destro604: Dec 20 2007, 08:24 AM