Print

[sosotiit]

Before you use isbuster you must unlock the drive (even with kreon 0.81), so use dvdinfopro and send the custom command FF 08 01 11 01, close dvdinfopro and then extract using Isobuster. When ask for the name enter game.iso (even if it says .tao ) the file generated is then game.iso (no cue file or changing extension required, not sure if it has an impact but that is how it worked for me.). The game.iso file should be 7,307,001,856 bytes if you right click on it in windows (6.8G)

Then use xbox creator (that part was working for me) to extract ss.bin (and PFI , DMI if you want them) and ssmerger (pad with blank, no NME compatible), layerbreak and ssoffset as per xbox360, burn 2.4X on good media.

hope it helps, rgds, soso

[sosotiit]

in dvdinfopro
bottom left make sure you have the sh-d162 selected,
just right of this select in the advance command, the one that says send custom command (a window will open cdb 0 to 11 field. Enter FF 08 01 11 01 in the first five field as per image below(from a tut I refer in previous post), and send it.



It is not permanent in any way, do not worry.
then it is isobuster time.
It is worthed, great game (all but one mission which is a pita)
rgds,soso

[sosotiit]

QUOTE

1) What do I need to do with DVDInfoPro BEFORE I use isobuster
2) What do I extract (SS.bin? what is that ... etc)
3) How do I merge (I see some references to a batch file which I can't locate)

for 1) See post 17 and 19 , you need to unlock the drive yourself with isobuster (something XB creator and schtrom does for you)
for 2) With isobuster : click on dvd, rightclick and choose Extract From-To and enter 0 and 3567872, start extraction. call it game.iso (even if it suggest .tao enter exactly game.iso as name)
With xbox creator go in Drive tools extract to the same folder as game.iso the Security sector (SS.bin), PFI and DMI.
for 3) If you do not know about the batch file in the firmware package I suggest you rather download ssmerger 1.7b.
and select the four files you have just created, put the options as per post 17  and hit the big merge sign (get a coffee it is 15 minutes to process )
Burn with imgbrun @2.4x (or your favorite prog) on good quality media.

rgds, soso

[sdeens]

SOSOTiiT:

[sosotiit]

QUOTE

let's keep this strickly an XBC v2.3 solution and avoid IsoBuster and DVD.infoPro

If you have a different solution you are welcome to present it, but in a proper way. if you are not interested to participate in a constructive way in this thread, I politely invite you not to do so.

From your message, you say that you believe the way to do this and
 I will test tonight for XBC v2..3 complaince so you have not even tested your assumptions!!!
When I presented to Redline99 (author of Xbox creator) the difficulty to extract the whole disc of STL, he confirmed he had seen this behavior before, that he would look into it as he wanted to correct this.

What I presented here is one way (tested and working) to address this backup of STL.
I will stop it at that.
rgds,soso

[sosotiit]

@PSPPSP
If your command in dvdinfopro



is done Ok (besure to do send) then you should see only this in Isobuster
- DVD
- session 1
- track 01

I believe the Dvdinfopro did not work, sorry, try again as they say under the cap .

in ssmerger it is ok to choose the four lines as
game.iso  (if that is what you called it)
SS.bin
pfi.bin
dmi.bin

and



happy to help,

rgds,soso

[sosotiit]

Happy it worked, and the game is good,
merry xmas,
rgds, soso

[sdeens]

just follow the procedures I laid out earlier in this thread and its an easy backup, you don't need to use Isobuster or DVdinfoPro at all..that's old school and redundant...as long as you have an SH-D162B drive flashed with Kreon v.81 connected to your PC....if you use your XBOX360 drive instead to perform the RIP then you have to unclock drive with DVDinfoPro, but after xtreme v4.2a I am not sure you need to do even that anymore.

simplest method:

1.  launch XBC v2.3
2.  select Drive Tools
3.  Unlock Drive--press this twice to get it to recognize the partition size correctly (that's the bug in it--no big deal--its NOT always automatically detected)--ignore the response that says drive is already unlocked--tha';s the KREON firmware doing its job, I suspect.
4.  READ image--select "current partion" NOT "complete backup--I mis-stated that in my first tutorial---ooops type too quickly.
5.  It will be 7,135,744 (or: 7,307,001 if you go into Properties---that;s why I don't use the PROPERTY values)
6.  XBC v2.3--go back to Drive Tools and extract all three (SS, PFI and DMI)--YES definately all 3!
     ---2kb each in size
7.  save to same folder as the .iso that XBC v2.3 created earlier
8.  Launch SS Merger 1.7b--use those settings in thread posted above--#25--select ALL 4 files
9.  ignore the request to do an on-line Xtereme verfication--select NO when prompted.
10. press the MERGE button--this takes about 30-45 minutes to merge the new complete ISO
11.  Burn wih ImgBurn v2.1..same deal as before--I used 4x speed on Verbatim DVD +R DL media

works exactly as it should, this is the DEFACTO STANDARD for ripping and burning these newer 360 games with SH-D162B KREON v.81 drives.


BTW this game has no way to save the game progress during a MISSION...what a tremendous mistake by the game developers...no doubt that will be frustratinbg later in game on more difficult levels..


as I said before you don't need Isobuster ($30 program)  or DVDinfoPro if you have the kreon flashed sammy drive..

p.s.

sometimes knowing a way to do a thing "old school" is good, but NOT this time

[sosotiit]

As per my first message, I have backed up all my game before this one with Xbox Creator and absolutely love that software. In fact the majority of my post are in the Xboxcreator threads.

There are many things I could tell you on your posts , but it would only feed your apparent inclination for confrontation; things like the Kreon FW default is unlock 2 ( as indicated in NFO) and that is why you need to send the FF08011101 in order to have unlock 1 and get an Xtreme style (instead of Wxripper style in unlock 2);     In the end your approach requires to extract all separately and merge so there is little gain why make such a fuss;     If everything must be Xboxcreator or nothing why burning with imgburn (use xboxcreator) ?.

All of that is irrelevant, my point is that if you find another way to do things you can present it in a respectful way without telling everyone they are wrong and that all threads in X-S should follow your authority (that after 12 posts!!!). Many people are using Wxripper and isobuster ( i am not one of them) and I fully respect that. If you do not want to do that, do not participate.

again, what I presented here is one way (tested and working) to address this backup of STL. It has helped many people it seems.


rgds,soso

[sosotiit]

QUOTE(PSPPSP @ Dec 23 2006, 10:56 PM)

THANK YOU Sostiit!!!  You are the man!!  I got it going and works great!!  The only thing was when in isobuster the file that was created this time was a little smaller than you indicated "The game.iso file should be 7,307,001,856 bytes if you right click on it in windows (6.8G)"  It was actually a little bit small than what you stated, but when I sent the command and saw what I indicated in post #23, it came out to the exact size as you stated.  In any case it seems to have worked out!  Thanks for ALL your help.  

Sometimes trying to figure out the "how to part" is just as fun as the Playing part.  Thanks for ALL YOUR HELP!!
   

You may have been in windows explorer in which case it is shown in KB (kiloBytes) which would be 7,135,744 KB. That is the same as 7,307,001,856 Bytes or 6.8 GigaBytes (GB). To see it in Bytes you need in explorer , to right click on the file and choose properties. But if you get 7,135,744 KB it is the same thing.

rgds, soso

[sosotiit]

The author of XBCreator (redline99) says he knows this problem, but he does not have access a STL. He mentionned he might look into it later.

I beleive it is the only title doing this. It seems to have something to do with the unlock of the game partition.
Some people had success by unlocking manually then using Xboxcreator to extract the game.iso.

But you still need to extract separatelly ss, dmi, pfi and then merge so it is not a big gain.

Hope it helps,
rgds,soso

[Yateball]

I followed Soso's instructions for this game and it works perfectly, I originally had the same partition problem with XBC, first time ever I've had any problems with it.

Didn't even know about the ISObuster method but the game works perfect. Thanks a lot Soso!

[Dravor]

QUOTE(Yateball @ Jan 3 2007, 05:32 PM)

I followed Soso's instructions for this game and it works perfectly, I originally had the same partition problem with XBC, first time ever I've had any problems with it.

Didn't even know about the ISObuster method but the game works perfect. Thanks a lot Soso!

So is the only real change here that some of the new games will require a different unlock sequence?  I'm not as familiar with XBC, but after using it, it seems that Schtrom most likely works very similiar, except in that it hides all of the different steps (ripping game.iso, ripping the ss file and the two others, remerging all three)?

If so, shouldn't the fix be easy?

[sosotiit]

That is interesting,

The game has is info set slightly differently then the others it seems. Why this game would require verbatim and not others???  Some people in this thread succeeded with other brand.  But huge thanks for the info.

Not sure if from redline and schtrom standpoint it is only a question of unlock (because they must have been doing if before anyway). Not expecting it to be a big thing, but I honestly do not know by expertise, it is only intuition.

rgds,soso

[sosotiit]

It is the only one like that,
so like you not expecting to be big thing as far as correction.

rgds,soso