Print

[sosotiit]

Is that your first backup? if not are other backup working fine?
after you finish, try schtrom 3.1/tools/stealth check to see if all pieces are there.
If it is you first, Iwould try with another game if you have one, make sure the rest of the process is OK   .

rgds,soso

[sosotiit]

pre burn on the iso ( or .000) image on your disk.
soso

[sosotiit]

too big,
are you sure you have removed the selection of NME compatible?
before burning, run the test again

rgds,soso

[TWilly]

OK...I see it, under the SS merger app.  Uncheck the Create NME compatible ISO.  Yes this was checked.  OK I will redo the merge without it and see what happens.  Thanks!

TW

[StrictPuppet]

QUOTE(TWilly @ Feb 18 2007, 05:19 AM)

Have I done something wrong or do I have to modify the 360 firmware? (which I have not done)

If the drive has not been flashed with modified firmware, there is no way your backup will ever boot, no matter how you make it.

[sosotiit]

you can look in the faq section of hacking/technical dvd-rom forum ( Releases and Tutorials ) and this doc here.

Also suggest you give a look at the posting rules, many discussion on XBL to be careful.

AS far as the fw being detected?? who knows. One strict rule at XS, only original (no Bup) to be played on Live.
and yes the warranty is gone.

rgds,soso

[StrictPuppet]

CODE

Found ODD: TSSTcorp DVD-ROM SH-D162C TS04 at [G]
   Additional Info: XB360 KREON V0.81
Getting media info [G]
   Uknown Partition size. Used bytes = 5.32 MB
   Media Type: DVD-ROM
   Bytes Used: 5.32 MB (5,578,752 bytes)
<*unlock drive again*>
Getting media info [G]
   Media Type: DVD-ROM
   Bytes Used: 6.81 GB (7,307,001,856 bytes)

Not sure if this has been mentioned yet or not, just adding it to the list...

[sosotiit]

HI strictpuppet,
yes and most of the new games have the new smaller video partition, so I am guessing that a good part of the new releases will have this problem.
Redline and schtrom are working on this , question of time only for this to be resolve.
rgds,soso

[andjelko]

When backing up Crackdown - I use xbc v2.3 to create ss.bin, pfi.bin, dmi.bin.  I twice click unlock drive in drive tools and then extract the current partition.  I then take these files and use xbox 360 stealth (included with xtreme 4.2) and run build360 with video provided and I get image.000.  I then run ss merger 1.7b with my current partion game iso and the ss, pfi and dmi created earlier.  Turn NME off and insert video iso image.000.  All goes well except when I run stealth check.  I get "unable to determine the validity of the PFI sector"  with other checks coming back ok.  I haven't tried to burn this yet.  Was wondering what I was doing wrong or if I should be concerned.

Using SH-D162C with kron 0.81.

Thanks.

[sosotiit]

the pfi is also slightly different, try the imag stealth check in schtrom which I beleive is ok for that new PFI.
anyway it should be correct.
rgds,soso

[Rippster]

NME 1.2 with Crackdown

I picked up Crackdown yesterday and figured I would try and make a backup of it. Well, like everyone has said here, Schtrom gives the error that it is not an XBox disc. I hit this forum and after getting home from work, I’m happy to say I made a perfectly working backup.

My Specs:

XBox 360 with Samsung MS28 Drive
NME 1.2 Chip Installed

PC:
Pioneer 111D
Samsung D163A w/ Kreon .80

I used SDEENS method although logically the other methods listed here should work as well.

Once you’re done using SDEENS method from line #28 and the SSMERGER settings from line #25, you will have an image you can use NME Associat0r on. I started to do the SS extraction and insertion method but figured I would just first give the little application a chance to just Convert. Wham Bam, the conversion went off perfectly creating an image set at 7.525.056KB. I then let CloneCD burn it and it works great.

Hope this helps any of you NME users out there.

Ripp

[sosotiit]

you mean conversion with associator "convert" tab instead of "merge" tab or do you mean with ssmerger?

thks for the info, soso

[andjelko]

QUOTE(sosotiit @ Feb 21 2007, 01:24 PM)

the pfi is also slightly different, try the imag stealth check in schtrom which I beleive is ok for that new PFI.
anyway it should be correct.
rgds,soso

thanks for your response sosotiit.  When you say the pfi is different I'm assuming that when xbc2.3 verifies pfi - the fact that its slightly different is why the check comes back as failed (again this is for pfi only).  Is this a limitation of xbc 2.3 - and don't get me wrong the software is great and I appreciate all the help and software thats been provided.

[sosotiit]

QUOTE(andjelko @ Feb 21 2007, 11:16 AM)

thanks for your response sosotiit.  When you say the pfi is different I'm assuming that when xbc2.3 verifies pfi - the fact that its slightly different is why the check comes back as failed (again this is for pfi only).  Is this a limitation of xbc 2.3 - and don't get me wrong the software is great and I appreciate all the help and software thats been provided.

yes there is a small bug in 2.3, it makes it tell that something is wrong when in fact it is just the a different format of a valid PFI. Redline knows about it , and pretty sure it will be fixed in the next release he mentioned in his thread.

rgds,soso

[sosotiit]

file size is OK,
run the stealth check of  Schtrom  to see if all pieces are seen?

if so your prob may have nothing to do with the image.
how is it burned: drive/media to be used on which x360 drive/fw?

rgds,soso