 | Author: | JimDrew (registered user: 23 posts ) |
|---|
| Date: | Wed, Mar 07th, 2007 @ 09:58 ( . ) |
Since the object to duplicating protection is being able to determine the write spice(s), it is important to be able to read the track and shift the data to determine where the splice occurs. The only thing we are concerned about is this. With the EPYX stuff (perhaps others), the "weak bits" created by the write splice is actually checked as part of the protection. They expect this data to change and never be the same or it won't load. They use this point to start their data reads when loading/sending their data too.
|
|