QUOTE(Wambla @ Dec 29 2005, 09:29 AM)

i don't think it's a just the booktype value on dvdrom...
From my experience on xbox1 ...MS at a certain point (2003?) added some extra bytes to the certificate in the xbe header to trigger a media check on the lead-in area of the dvdrom. Basically at the beginning of the MediaSpecific part of the lead-in area they recorded the time/date 32bits value present in the xbe header plus other data. Also they saved in the last 20bytes the SHA-1 of the lead-in except the lead-in-header and the last 20bytes, obviously.
There wasn't a way to set the MediaSpecific area during the burning of an xbox iso on dvdr.
So the media check was an hashing of the leadin area and a comparing of the result with the 20bytes stored at the end.
I don't have a 360 yet so I can't dig in it...but I have the feeling that it's not just the booktype and patching a firmware to just return a desired type it can be useless.
as krayzie said bitsetting/booktype (which can be changed) is not the same as media type (which cannot be changed)
as for the media checks in 03, im pretty sure those just check the media type, and they are actually a second set of media checks (the first appears in all xbox games, from launch on)
QUOTE(krayzie @ Dec 29 2005, 08:41 AM)

the xbox dvd code that is checked is put on the disc from factory. It's not something that can be added in the burning process.
thank you, that's what i needed to know.
i figured it wasn't this simple, otherwise someone would have already done it, but you never know.
time to dig up some specs on the DVD drive and see how feasable a firmware patch would be, since intercepting the signals on the SATA bus (1.5GHz LVDS) isn't all that easy.