Difference between revisions of "Cosmetic Disk Id"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
This is no copy protection, but influences handling within an emulator when used in D64 format. | This is no copy protection, but influences handling within an emulator when used in D64 format. | ||
| − | When mounting a D64 in an emulator it uses the Id bytes read from the directory | + | When mounting a D64 in an emulator it uses the Id bytes read from the directory also for each sector header. The sector header data is not present in the D64 and the emulator generates that data itself. |
| − | Some games use a disk id in the directory that | + | Some games use a disk id in the directory that is different from the sector header ids. Typically the id bytes in the directory are changed to represent a nicer directory. |
When such disk is converted to D64 the emulator uses the wrong ids for the sector headers and loading will fail. | When such disk is converted to D64 the emulator uses the wrong ids for the sector headers and loading will fail. | ||
Latest revision as of 20:18, 1 November 2022
This is no copy protection, but influences handling within an emulator when used in D64 format.
When mounting a D64 in an emulator it uses the Id bytes read from the directory also for each sector header. The sector header data is not present in the D64 and the emulator generates that data itself.
Some games use a disk id in the directory that is different from the sector header ids. Typically the id bytes in the directory are changed to represent a nicer directory. When such disk is converted to D64 the emulator uses the wrong ids for the sector headers and loading will fail.
This problem is not present when a G64 is used. The disk can also be copied with a program that includes the sector header data.
