how did you confirm this?

i didn't test the one dumped with robinsods. i just went with the one dumped with commodore4evas.

i am making a halo1 rip as well i can burn a extra SSs i dump with robinsods and test it with it.

i dumped my halo 2 ntcs with robinsods firmware and commodore4evas. they differ from 65F-7FE. The one i did with commodore4evas was only different 5DF-65E with the pal halo 2 ss he included.

I will dump it today with the hitachi memory dump.

nope.

I patched FDB5: F9FA00 -> 060000

i verified the PSN 60000 one by reading logical block address 30000 with DVDInfro Pro and it is in fact the security sector.

I patched F9FA00 in the firmware to 60000 and it doesn't work in my xbox it shows up as a video disc.

i get this output from you unlocked in windows

Read capacity io succesful. Returned data ->
00 3E 9B AF 00 00 08 00 - 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
Mode sense io succesful. Returned data ->
00 1A 00 00 00 00 00 00 - 3E 12 00 00 00 D1 01 00
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
Read DVD structure IO succesful. Returned data (only first few bytes) ->
06 64 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

am i patching the correct PSN value? did i miscalculate

oh ok. yea i overwrote the blank data i didn't insert the ss. it was definitely over writen.

The test disc i made i include the SS at F9FA00 and then those 2 other places.

The disc(Halo 2 NTSC) works fine with the orginal firmware but when i tried the patches it did not.

It did output some stuff. i forgot to save it. i will go do the testing again and post back my results.

yes i patched it in the firmware. i changed it to PSN 60000 and PSN 31B50 and tired both of them and neither worked with my xbox. i also tried using your unlocked on my samsung with the firmwares and the unlocker froze.


edit: i made sure to overwrite not insert. the drive still functioned normally on eject and load and everything. i will do more testing now. see if i can get it working.

i mean PSN 30000 to PSN 60600. the padded area of the iso. could you not put the SS in here. it would eliminate the PSN calculations because it will always be a certain offset from the begining and it would enable single layer media i think.

i put copies of my SS at PSN 60000 and PSN 31B50 after the video part of the disc on my orginal hotswap image. i tried patching the location to the security sector code to read from PSN 60000 and the other PSN 31B50 but it didn't work

i got a backup running with my own riped SS.

i tired patching the SS location to various points in the padding data before the game partition without it working. do you know what is needed to patch to make it read from a PSN in layer 0?

wouldn't manually setting the layer break to the padding + 1/2 game is size work better then leting the burning software do it. this will cause the game part of the disc to be split accross the layers evenly padded to a more central part of the disc. might get better loading times.

you could calculate it based on the layer break amd the size of the image. if you change the layer break the it would change the last psn

you could rip the extra dummy data from the image and then it is as simple as placing the ss.bin at the end of the file and then change the layer break for your burn to 1913776.

if you take your orginal layer break from the hotswap dvd. like for this example my chasing amy was 2057632 or 1F65A0 x 800h = offset FB2D0000 in the raw image. the layer break for the orginal xbox dvd was 1913776 or 1D33B0 x 800h = E99D8000 hex is the end of the layer 0 part of the game partition. so E99D8000 - FB2D0000 is the extra space on layer 0. The next layer begins at FB2D0000 and will have a blank space the exact same size as between E99D8000 - FB2D0000 then game layer 1 starts. you could remove both these sections of sectors and change the layer break to 1913776 and your image would work correctly.

you could then also remove the the blank space after the end of the game layer 1. your game image starts at 18300000 and is  7,027,228,672 bytes long or 1A2DB0000 + 18300000 = 1BB0B0000 which from there to the end file could be removed. 1BB0B0000 should be the end of game layer 1. The Security Sector would simply be tacked on the end of the file.

edit: this speeds up your burning a little. my hotswap dvd image was 7.82 GB while the built one was 6.92 GB(which would look the same as a dummy striped raw image). the game data in each layer is in the same position on the disc in ethier image when burned to disc.

The drives always want to be slave.
I think this is because they are slaves in the xbox itself. the harddrive being master.

my samsung has always set itself up as slave. it works on my ide-usb adapter though normally i have to set things to master for them to work on it.

lead in and lead out information isn't stored in iso. it is really just a raw binary sector dump of the data area of the disc from what i understand.

i haven't tried it so i dont' know if it will work. if you did do this you would need to pad the iso up the full size of a regular game partition for the layerbreak and SS PSN to be correct.

Hopefully a patch to read the ss from layer 0 will come out. i tried changing the PSN in the firmware to something in the first layer. when i burned my first dual layer i included the SS are a couple places in the null data between video and game parts of the disc. The firmware didn't work though =/ so i guess i might look at the disasm.

plus a little dummy data.

from what i understand when locked the video partition is read starting at PSN 30000 or offset 00h in a raw image. when unlocked it reads from PSN 60600 or 18300000h in our raw image.

I think a plug in for altus would be cool. since it can read unlocked drives and dump their files avoiding secturity sectors. perhaps a plugin would be possible to rip the iso from the unlocked drive but only rip the sectors the file table actually uses to store data. That should improve rip times alot.

http://rapidshare.de/files/19120496/xbox_1_unlocker.rar.html

i think it might be over at xbox-scene too i am not sure

heres my method to build a raw like image from the game and video part riped with your orginal xbox drive.

hook your xbox dvd drive up to your pc.
put in your game disc. use isobuster to rip the video part to iso. name it video.iso. it should rip really quick.
Then use theSpecialist unlocker to unlock the drive.
rip the iso like arakon instructions(don't swap just the software part).  name it game.iso

You will also need the Security Sector from your game. Arakon already covers this in his instructions.
name your Security Sector SS.bin

put these all in the same directory.
download the file attached. remove the .jpg from the name and then extract the rar
It contains 3 files.
build.bat - is a copy /b command to build the final iso.
IMAGE.dvd - LayerBreak=1913776 for the iso we're making
spacer.rar - extract this to spacer.bin used to space the video and game parts to correct sectors.

extract all these files in the same directory. run build.bat and it will copy video.iso + spacer.bin + game.iso + ss.bin into a file named IMAGE.000 which is the file IMAGE.dvd is set to burn with in CloneCD. the layer break is in the right position where the security sector is in the right place and the game data layers are in the correct place.

I guess i made the assumption that all Video and Game partitionss are consistant in their size between games. i assumed they are. This worked with halo 2.

my video size was 14,319,616 bytes
my game size was 7,027,228,672 bytes

the important thing i think is that the game partition start at offset 18300000h. i don't know if the video partition is even needed but i thought it would be better to have it.

someone else want to test my method. it worked fine for me. I have to admit i am a little blazed so forgive rambling

Edit: sorry the batch i included was one i tested where i was seperating the game into each layer. edit the build.bat to this
copy /b video.iso + spacer.bin + game.iso + ss.bin IMAGE.000

sorry its really simple but it works much quicker for me on the riping and burning games now.