It all depends on how the specific FW hack you're using is done. Things that you'll need for sure:
* The *RAW* Security Sector ($FD021E). Raw means including the header, which contains the challenge.
* Responses to the challenges. Here the hacker can choose which method he uses. Either he makes a table with all responses or he creates an ISO with the security placeholders on it. However, the security placeholders contain bad sectors and these are used for 'timing'. A consumer burner can't write these bad sectors. So, you''ll need a table with the 'correct' timing values. There's currently no easy way for newbies to create such a table.
If you have all this security related data, then it depends on the way your specific hack is written how to include them into your ISO. For example, the SS has to be relocated to a certain new sector. So, you'll have to create the ISO with the SS on the sector that the hack expects it on. Meaning that you can't create an ISO without knowing which sector the hack wants the SS on. Meaning you can't create an ISO before you have a hack and some basic understanding/instructions.
Besides, currently there is currently no easy method for 'newbies' to rip the SS (especially not the RAW sector). There are several ways to rip this sector, either with modified firmware or using a program that uses the drive's debug commands to dump the sector from the drive's memory.
So basically, it is completely useless to start making your ISO's already This post has been edited by TheSpecialist: Apr 8 2006, 04:18 AM