Burstnibbler Protection - Revision history

Enigma at 23:44, 19 February 2026

2026-02-19T23:44:01Z

← Older revision		Revision as of 23:44, 19 February 2026
Line 74:		Line 74:
	* Turbonibbler 2.2 has no copy protection.		* Turbonibbler 2.2 has no copy protection.

	A copy may ~~file~~ due to three things:		A copy may not work due to three things:
	* multiple speeds used per track		* multiple speeds used per track
	* sync length check		* sync length check

Enigma at 22:53, 17 March 2023

2023-03-17T22:53:37Z

← Older revision		Revision as of 22:53, 17 March 2023
Line 41:		Line 41:
	bits 111		bits 111

	This pattern applies to sector 0, 5 and 10 of track 10. Also note that the default sync length is between 32 and ~40, ~~wheras~~ the sync length of the "special" sectors is 160 (at speed 3).		This pattern applies to sector 0, 5 and 10 of track 10. Also note that the default sync length is between 32 and ~40, whereas the sync length of the "special" sectors is 160 (at speed 3).

	===== Burstnibbler =====		===== Burstnibbler =====

Enigma at 22:53, 17 March 2023

2023-03-17T22:53:23Z

← Older revision		Revision as of 22:53, 17 March 2023
Line 2:		Line 2:

	===== Disk layout =====		===== Disk layout =====
			Track 10 is written with the data area of three sectors at lower speed 0 instead of 3 (default for track 10). The sectors 1, 6 and 11 are missing, probably to compensate the track length for the three longer sectors. All sectors except 0, 5 and 10 are filled with zero.
	Track 10 is written with ~~a different~~ speed. The sectors 1, 6 and 11 are missing. All sectors except 0, 5 and 10 are filled with zero.

	Burstnibbler, Turbonibbler 4.0 and Filemaster check the existence of sector 0, 5, 10 on track 10. The track is read at speed 3, including the headers of sector 0, 5 and 10, except the data of sector 0, 5 and 10 is read at speed 0.		Burstnibbler, Turbonibbler 4.0 and Filemaster check the existence of sector 0, 5, 10 on track 10. The track is read at speed 3, including the headers of sector 0, 5 and 10, except the data of sector 0, 5 and 10 is read at speed 0.

	Example sector:		Example sector:
	sync 32 ; ~~we are~~ at default speed 3 here		sync 32 ; decoded at default speed 3 here
	; header		; header
	gcr 08		gcr 08
Line 28:		Line 27:
	bits 1111		bits 1111

	speed 0 ; speed change here		speed 0 ; decode speed change here
	sync 200 ; at speed 3 this sync shrinks to sync 160		sync 200 ; at decode speed 3 this sync shrinks to sync 160
	; data		; data
	gcr 07		gcr 07
Line 42:		Line 41:
	bits 111		bits 111

	This pattern applies to sector 0, 5 and 10 of track 10.		This pattern applies to sector 0, 5 and 10 of track 10. Also note that the default sync length is between 32 and ~40, wheras the sync length of the "special" sectors is 160 (at speed 3).

	===== Burstnibbler =====		===== Burstnibbler =====

	A autostart routine is used. After program start the drive seeks to		A autostart routine is used. After program start the drive seeks to
	* BurstNibbler 1.5 : track 2 sector 0		* BurstNibbler 1.5 : track 2 sector 0
Line 60:		Line 58:

	===== Turbonibbler 4.0 =====		===== Turbonibbler 4.0 =====

	In Turbonibbler 4.0 the protection is similar but different implemented. The file itself is just 1 block in size and using autostart starts a Mini-Loader. The Mini-Loader executes block track 18 sector 4 (and 18/3) using command "B-E" in the floppy drive. This code contains the actual loader that transfers Turbonibbler 4.0 to the C64. It starts at a fixed encoded block number. If following the block chain the loader reaches track 10 the same algorithm as for loading the blocks of Burstnibbler 1.5/1.9 is used: data block in speed $00, sync length check (without explicit upper limit) while the transfer to C64 is running.		In Turbonibbler 4.0 the protection is similar but different implemented. The file itself is just 1 block in size and using autostart starts a Mini-Loader. The Mini-Loader executes block track 18 sector 4 (and 18/3) using command "B-E" in the floppy drive. This code contains the actual loader that transfers Turbonibbler 4.0 to the C64. It starts at a fixed encoded block number. If following the block chain the loader reaches track 10 the same algorithm as for loading the blocks of Burstnibbler 1.5/1.9 is used: data block in speed $00, sync length check (without explicit upper limit) while the transfer to C64 is running.

Line 70:		Line 67:

	===== Filemaster =====		===== Filemaster =====

	Filemaster uses the same copy protection method as Turbonibbler 4.0.		Filemaster uses the same copy protection method as Turbonibbler 4.0.

Line 76:		Line 72:

	===== Notes =====		===== Notes =====

	* Turbonibbler 2.2 has no copy protection.		* Turbonibbler 2.2 has no copy protection.

Enigma at 22:47, 17 March 2023

2023-03-17T22:47:07Z

@@ Line 5: / Line 5: @@
 Track 10 is written with a different speed. The sectors 1, 6 and 11 are missing. All sectors except 0, 5 and 10 are filled with zero.
-Burstnibbler, Turbonibbler 4.0 and Filemaster check the existence of sector 0, 5, 10 on track 10 (speed 0).
+Burstnibbler, Turbonibbler 4.0 and Filemaster check the existence of sector 0, 5, 10 on track 10. The track is read at speed 3, including the headers of sector 0, 5 and 10, except the data of sector 0, 5 and 10 is read at speed 0.
 ===== Burstnibbler =====
@@ Line 20: / Line 57: @@
 Since these tracks are rather empty compared to normal written ones it could happen that a copy has too large gaps between the sectors (if they are not evenly distributed). In this case the regular DOS routine that waits for the next sync times out (20 ms).
-* Read sector 5 track 10 at speed 0
+* Burstnibbler 1.9: Read data of sector 5 track 10 at speed 0
 ===== Turbonibbler 4.0 =====

Enigma at 22:18, 17 March 2023

2023-03-17T22:18:26Z

← Older revision		Revision as of 22:18, 17 March 2023
Line 4:		Line 4:

	Track 10 is written with a different speed. The sectors 1, 6 and 11 are missing. All sectors except 0, 5 and 10 are filled with zero.		Track 10 is written with a different speed. The sectors 1, 6 and 11 are missing. All sectors except 0, 5 and 10 are filled with zero.

			Burstnibbler, Turbonibbler 4.0 and Filemaster check the existence of sector 0, 5, 10 on track 10 (speed 0).

	===== Burstnibbler =====		===== Burstnibbler =====
Line 28:		Line 30:
	Compared to the Burstnibbler protection the sector on track 10 with the different speed is part of the loaders block chain and thus part of the Turbonibbler program data.		Compared to the Burstnibbler protection the sector on track 10 with the different speed is part of the loaders block chain and thus part of the Turbonibbler program data.

	* ~~Read~~ sector 10 on ~~track 10 at speed 0 and sector 5~~ track 10 at speed 0		* Reads data sector 10 on track 10 at speed 0

	===== Filemaster =====		===== Filemaster =====
Line 34:		Line 36:
	Filemaster uses the same copy protection method as Turbonibbler 4.0.		Filemaster uses the same copy protection method as Turbonibbler 4.0.

	* ~~Read~~ sector 5 track 10 at speed 0		* Reads data sector 5 track 10 at speed 0

	===== Notes =====		===== Notes =====

Enigma at 21:47, 17 March 2023

2023-03-17T21:47:11Z

← Older revision		Revision as of 21:47, 17 March 2023
Line 17:		Line 17:

	Since these tracks are rather empty compared to normal written ones it could happen that a copy has too large gaps between the sectors (if they are not evenly distributed). In this case the regular DOS routine that waits for the next sync times out (20 ms).		Since these tracks are rather empty compared to normal written ones it could happen that a copy has too large gaps between the sectors (if they are not evenly distributed). In this case the regular DOS routine that waits for the next sync times out (20 ms).

			* Read sector 5 track 10 at speed 0

	===== Turbonibbler 4.0 =====		===== Turbonibbler 4.0 =====
Line 26:		Line 28:
	Compared to the Burstnibbler protection the sector on track 10 with the different speed is part of the loaders block chain and thus part of the Turbonibbler program data.		Compared to the Burstnibbler protection the sector on track 10 with the different speed is part of the loaders block chain and thus part of the Turbonibbler program data.

	* Read sector 10 on track 10 at speed 0		* Read sector 10 on track 10 at speed 0 and sector 5 track 10 at speed 0

	===== Filemaster =====		===== Filemaster =====

	Filemaster uses the same copy protection method as Turbonibbler 4.0.		Filemaster uses the same copy protection method as Turbonibbler 4.0.

			* Read sector 5 track 10 at speed 0

	===== Notes =====		===== Notes =====

Enigma at 21:40, 17 March 2023

2023-03-17T21:40:43Z

← Older revision		Revision as of 21:40, 17 March 2023
Line 25:		Line 25:

	Compared to the Burstnibbler protection the sector on track 10 with the different speed is part of the loaders block chain and thus part of the Turbonibbler program data.		Compared to the Burstnibbler protection the sector on track 10 with the different speed is part of the loaders block chain and thus part of the Turbonibbler program data.

			* Read sector 10 on track 10 at speed 0

	===== Filemaster =====		===== Filemaster =====

Enigma at 18:13, 27 October 2019

2019-10-27T18:13:14Z

← Older revision		Revision as of 18:13, 27 October 2019
Line 42:		Line 42:

	Description contributed by markusC64 from Forum-64, translated by enigma.		Description contributed by markusC64 from Forum-64, translated by enigma.

			==== Pages that refer to this protection ====

			{{Special:Whatlinkshere/Burstnibbler Protection}}

Enigma at 16:38, 9 August 2019

2019-08-09T16:38:52Z

← Older revision		Revision as of 16:38, 9 August 2019
Line 3:		Line 3:
	===== Disk layout =====		===== Disk layout =====

	~~In tracks 2 to~~ 10 ~~the sectors 0, 5 and 10 are~~ written with a different ~~(for these tracks wrong)~~ speed ~~$00 and use up more space~~. ~~Thus the~~ sectors 1, 6 and 11 are missing. All sectors except 0, 5 and 10 are filled with zero.		Track 10 is written with a different speed. The sectors 1, 6 and 11 are missing. All sectors except 0, 5 and 10 are filled with zero.

	===== Burstnibbler =====		===== Burstnibbler =====

Enigma at 15:49, 5 August 2019

2019-08-05T15:49:08Z

← Older revision		Revision as of 15:49, 5 August 2019
Line 20:		Line 20:
	===== Turbonibbler 4.0 =====		===== Turbonibbler 4.0 =====

	In Turbonibbler 4.0 the protection is similar but different implemented. The file itself is just 1 block in size and using autostart starts a Mini-Loader. The Mini-Loader executes block track 18 sector 4 (and 18/3) using command "B-E". This code ~~is a~~ contains the actual loader that transfers Turbonibbler 4.0 to the C64. It starts at a fixed encoded block number. If following the block chain the loader reaches track 10 the same algorithm as for loading the blocks of Burstnibbler 1.5/1.9 is used: data block in speed $00, sync length check (without explicit upper limit) while the transfer to C64 is running.		In Turbonibbler 4.0 the protection is similar but different implemented. The file itself is just 1 block in size and using autostart starts a Mini-Loader. The Mini-Loader executes block track 18 sector 4 (and 18/3) using command "B-E" in the floppy drive. This code contains the actual loader that transfers Turbonibbler 4.0 to the C64. It starts at a fixed encoded block number. If following the block chain the loader reaches track 10 the same algorithm as for loading the blocks of Burstnibbler 1.5/1.9 is used: data block in speed $00, sync length check (without explicit upper limit) while the transfer to C64 is running.

	Thus, Turbonibbler 4.0 appears in the memory of the C64 without any code related to copy protection.		Thus, Turbonibbler 4.0 appears in the memory of the C64 without any code related to copy protection.