Syncr0l0k - Revision history

Enigma at 00:46, 7 March 2022

2022-03-07T00:46:45Z

Enigma at 00:45, 7 March 2022

2022-03-07T00:45:24Z

Enigma at 00:44, 7 March 2022

2022-03-07T00:44:49Z

Enigma at 18:12, 27 October 2019

2019-10-27T18:12:43Z

Enigma at 18:11, 27 October 2019

2019-10-27T18:11:51Z

Enigma at 18:10, 27 October 2019

2019-10-27T18:10:05Z

Enigma at 18:08, 27 October 2019

2019-10-27T18:08:47Z

Enigma at 18:08, 27 October 2019

2019-10-27T18:08:29Z

Enigma at 17:01, 19 July 2019

2019-07-19T17:01:22Z

Enigma at 17:00, 19 July 2019

2019-07-19T17:00:44Z

@@ Line 1: / Line 1: @@
-Description by LordCrass
+===== Description by LordCrass =====
 This awful little protection writes to the disk. It writes to t/s 19/02 and that must succeed or it tries over and over. Then it tries writing to t/s 20/02. This must fail or it tries over and over again. The protection seems to be based on physically damaged sectors that need to return errors when attempts are made to write to them. I tried erasing the sector header for 20/02 to see if it would fool the protection, but it doesn't work. The protection checks that some of the sector was written (first 6 bytes at the minimum must match). After it writes to track 20, it reads it back to verify it. The data it writes is a pseudo-random byte taken from the timer, so it's different each time you load the game. When it reads it back, at least 6 bytes must match what it thinks it wrote, but the whole sector cannot match. If it does: protection failed. Unless someone can think of a way to damage the sector in an image to the extent that a U2 write command will only partially work, this won't function in an emulator. And unless you can physically damage a real disk at the right spot, this won't work remastered either. On the other hand, it's an easy crack to remove the protection check entirely. There's only one little method used to hide it (check $179F in the main program for the self-modifying code that hides the protection check at $17A2).
-Additional Information from Atari 8 Bit Preservation Forum ([https://community.a8preservation.com/t/flak-physical-copy-protection/564/12 Iljor]):
+===== Additional Information from Atari 8 Bit Preservation Forum =====
   I contacted the author, Yves Lempereur and I asked him about the protection:

@@ Line 5: / Line 5: @@
 Additional Information from Atari 8 Bit Preservation Forum ([https://community.a8preservation.com/t/flak-physical-copy-protection/564/12 Iljor]):
-''I contacted the author, Yves Lempereur and I asked him about the protection:
+ I contacted the author, Yves Lempereur and I asked him about the protection:
 ==== Pages that refer to this protection ====
 {{Special:Whatlinkshere/Syncr0l0k}}

@@ Line 2: / Line 2: @@
 This awful little protection writes to the disk. It writes to t/s 19/02 and that must succeed or it tries over and over. Then it tries writing to t/s 20/02. This must fail or it tries over and over again. The protection seems to be based on physically damaged sectors that need to return errors when attempts are made to write to them. I tried erasing the sector header for 20/02 to see if it would fool the protection, but it doesn't work. The protection checks that some of the sector was written (first 6 bytes at the minimum must match). After it writes to track 20, it reads it back to verify it. The data it writes is a pseudo-random byte taken from the timer, so it's different each time you load the game. When it reads it back, at least 6 bytes must match what it thinks it wrote, but the whole sector cannot match. If it does: protection failed. Unless someone can think of a way to damage the sector in an image to the extent that a U2 write command will only partially work, this won't function in an emulator. And unless you can physically damage a real disk at the right spot, this won't work remastered either. On the other hand, it's an easy crack to remove the protection check entirely. There's only one little method used to hide it (check $179F in the main program for the self-modifying code that hides the protection check at $17A2).
 ==== Pages that refer to this protection ====
 {{Special:Whatlinkshere/Syncr0l0k}}

@@ Line 3: / Line 3: @@
 This awful little protection writes to the disk. It writes to t/s 19/02 and that must succeed or it tries over and over. Then it tries writing to t/s 20/02. This must fail or it tries over and over again. The protection seems to be based on physically damaged sectors that need to return errors when attempts are made to write to them. I tried erasing the sector header for 20/02 to see if it would fool the protection, but it doesn't work. The protection checks that some of the sector was written (first 6 bytes at the minimum must match). After it writes to track 20, it reads it back to verify it. The data it writes is a pseudo-random byte taken from the timer, so it's different each time you load the game. When it reads it back, at least 6 bytes must match what it thinks it wrote, but the whole sector cannot match. If it does: protection failed. Unless someone can think of a way to damage the sector in an image to the extent that a U2 write command will only partially work, this won't function in an emulator. And unless you can physically damage a real disk at the right spot, this won't work remastered either. On the other hand, it's an easy crack to remove the protection check entirely. There's only one little method used to hide it (check $179F in the main program for the self-modifying code that hides the protection check at $17A2).
-==== Software using this protection ====
+==== Pages that refer to this protection ====
 {{Special:Whatlinkshere/Syncr0l0k}}

@@ Line 5: / Line 5: @@
 ==== Software using this protection ====
-{{Special:Whatlinkshere}}
+{{Special:Whatlinkshere/Syncr0l0k}}
 [[Flak]]

← Older revision		Revision as of 18:08, 27 October 2019
Line 4:		Line 4:

	==== Software using this protection ====		==== Software using this protection ====
		+
		+	{{Special:Whatlinkshere}}

	[[Flak]]		[[Flak]]