Speedlock - Revision history

Dlfrsilver: /* Disc */

2025-06-15T14:16:37Z

Disc

@@ Line 116: / Line 116: @@
 Speedlock was also available in disc version.
-One version called "[[8k Speedlock]]" relied on the fact that the CPC's hardware (specifically, the [[765 FDC|µPD765]] disk controller) could read 8 Kbyte sectors even though it was typically only possible to store more than 6,250 bytes on 300 rpm double density diskettes. Attempting to write an 8 Kbyte sector would cause the system to over-write its header block.
+One version called "[[8k Speedlock]]" relied on the fact that the CPC's hardware (specifically, the [[765 FDC|µPD765]] disk controller) could read 8 Kbyte sectors even though it was typically only possible to store more than 6,250 bytes on 300 rpm double density diskettes. Attempting to write an 8 Kbyte sector would cause the system to over-write its header block, because it requires to slow down the write speed (what the duplicator is doing. when examined with a flux tool like AUFIT, you can see that speedlock tracks are 'density variation' type. the density is higher due to the slower write speed used).
-It was written here that "the format was either devised or done on an Atari ST or an IBM PC compatible machine (since the CPC share with them the same FDC controler). The main difference being that an ST or PC can write more data per track than a CPC." This contains several inaccuracies. The Speedlock team in fact wrote the diskettes using diskette interfaces custom-modified for this purpose. Also, an Atari ST also has 6,250 bytes/track although used a WD1772 disk controller, while the PC has over time been based on a variety of formats (e.g. HD was 360 rpm 15 sectors etc.) and controllers (e.g. NEC µPD765 or Intel 8272A or 82072A.
+It was written here that "the format was either "devised" on an Atari ST or an IBM PC compatible machine (since the CPC share with them the same FDC controler, but not written on them since the Atari ST and IBM PC are unable to perform writetrack, they can only do sector write).
-Another statement written here was: "In itself, a 'Speedlock track' exists in 2 versions, used at the discretion of the duplicator, one use a CRC, and the other not." This is inaccurate, in the sense that it was never at the discretion of the duplicator. There were at least two separate versions, one of which may have involved a CRA issue.
+"The main difference being that an ST or PC can write more data per track than a CPC."
 A 'Speedlock track' consists of only 512 bytes declared for the sector while all the remaining data is spanned in a huge GAP section. When copied on a CPC, the FDC only stores the 512 first bytes as declared in the CHRN, and discards the remaining contained in the gap section. Those tracks have an EDC (Error Data Checksum) because only 512 bytes are used to calculate the data checksum as well as an illegal data field size. Several other protection mechanisms existed on such tracks, including special codes written by the Trace 1006 duplication equipment commonly in use at the time: these codes could not be written by standard Amstrad disc drives.

Muckypaws: /* Disc */ Corrected missing entry for the Argonauts 8K Sector Speedlock Copier

2024-01-28T23:57:14Z

Disc: Corrected missing entry for the Argonauts 8K Sector Speedlock Copier

← Older revision		Revision as of 23:57, 28 January 2024
Line 129:		Line 129:

	2. Executioner's utility Xexor included a 'brain file' solution to crack individual games before copying them.		2. Executioner's utility Xexor included a 'brain file' solution to crack individual games before copying them.

			3. The Argonauts (Jason Brooks') 8K Disk Copier was sold both through Nemesis and Personally, it worked by approaching the issue the same as Tape to Disk copying the game code to standard sectors after the "Hack" and then copying protected sectors which contained level data at the end of the disk tracks. This can be found on the Git Repo: https://github.com/muckypaws/AmstradCPC

Nich: Added link to µPD765 page

2022-02-15T10:55:29Z

Added link to µPD765 page

← Older revision		Revision as of 10:55, 15 February 2022
Line 116:		Line 116:
	Speedlock was also available in disc version.		Speedlock was also available in disc version.

	One version called "[[8k Speedlock]]" relied on the fact that the CPC's hardware (specifically, the µPD765 disk controller) could read 8 Kbyte sectors even though it was typically only possible to store more than 6,250 bytes on 300 rpm double density diskettes. Attempting to write an 8 Kbyte sector would cause the system to over-write its header block.		One version called "[[8k Speedlock]]" relied on the fact that the CPC's hardware (specifically, the [[765 FDC\|µPD765]] disk controller) could read 8 Kbyte sectors even though it was typically only possible to store more than 6,250 bytes on 300 rpm double density diskettes. Attempting to write an 8 Kbyte sector would cause the system to over-write its header block.

	It was written here that "the format was either devised or done on an Atari ST or an IBM PC compatible machine (since the CPC share with them the same FDC controler). The main difference being that an ST or PC can write more data per track than a CPC." This contains several inaccuracies. The Speedlock team in fact wrote the diskettes using diskette interfaces custom-modified for this purpose. Also, an Atari ST also has 6,250 bytes/track although used a WD1772 disk controller, while the PC has over time been based on a variety of formats (e.g. HD was 360 rpm 15 sectors etc.) and controllers (e.g. NEC µPD765 or Intel 8272A or 82072A.		It was written here that "the format was either devised or done on an Atari ST or an IBM PC compatible machine (since the CPC share with them the same FDC controler). The main difference being that an ST or PC can write more data per track than a CPC." This contains several inaccuracies. The Speedlock team in fact wrote the diskettes using diskette interfaces custom-modified for this purpose. Also, an Atari ST also has 6,250 bytes/track although used a WD1772 disk controller, while the PC has over time been based on a variety of formats (e.g. HD was 360 rpm 15 sectors etc.) and controllers (e.g. NEC µPD765 or Intel 8272A or 82072A.
Line 126:		Line 126:
	Various methods were attempted to circumvent this protection, including:		Various methods were attempted to circumvent this protection, including:

	1. A hardware modification to the Amstrad CPC and a special copy program		1. A hardware modification to the Amstrad CPC and a special copy program .

	2. Executioner's utility Xexor included a 'brain file' solution to crack individual games before copying them.		2. Executioner's utility Xexor included a 'brain file' solution to crack individual games before copying them.
	~~<br>~~

Sam-can: Corrected accuracy, fixed language.

2022-02-13T05:43:31Z

Corrected accuracy, fixed language.

← Older revision		Revision as of 05:43, 13 February 2022
Line 116:		Line 116:
	Speedlock was also available in disc version.		Speedlock was also available in disc version.

	One version called "[[8k Speedlock]]", relied on the fact that the CPC's hardware could ~~reliably~~ read ~~but not~~ write ~~8k sectors~~.		One version called "[[8k Speedlock]]" relied on the fact that the CPC's hardware (specifically, the µPD765 disk controller) could read 8 Kbyte sectors even though it was typically only possible to store more than 6,250 bytes on 300 rpm double density diskettes. Attempting to write an 8 Kbyte sector would cause the system to over-write its header block.

	the format was either devised or done on an Atari ST or an IBM PC compatible machine (since the CPC share with them the same FDC controler). The main difference being that an ST or PC can write more data per track than a CPC.		It was written here that "the format was either devised or done on an Atari ST or an IBM PC compatible machine (since the CPC share with them the same FDC controler). The main difference being that an ST or PC can write more data per track than a CPC." This contains several inaccuracies. The Speedlock team in fact wrote the diskettes using diskette interfaces custom-modified for this purpose. Also, an Atari ST also has 6,250 bytes/track although used a WD1772 disk controller, while the PC has over time been based on a variety of formats (e.g. HD was 360 rpm 15 sectors etc.) and controllers (e.g. NEC µPD765 or Intel 8272A or 82072A.

	In itself, a ~~speedlock~~ track exists in 2 versions, used at the discretion of the duplicator, one use a CRC, and the other not.		Another statement written here was: "In itself, a 'Speedlock track' exists in 2 versions, used at the discretion of the duplicator, one use a CRC, and the other not." This is inaccurate, in the sense that it was never at the discretion of the duplicator. There were at least two separate versions, one of which may have involved a CRA issue.

	A ~~speedlock~~ track ~~consist~~ of only 512 ~~byte~~ declared for the sector~~, and~~ all the remaining data is spanned in a huge GAP section.		A 'Speedlock track' consists of only 512 bytes declared for the sector while all the remaining data is spanned in a huge GAP section. When copied on a CPC, the FDC only stores the 512 first bytes as declared in the CHRN, and discards the remaining contained in the gap section. Those tracks have an EDC (Error Data Checksum) because only 512 bytes are used to calculate the data checksum as well as an illegal data field size. Several other protection mechanisms existed on such tracks, including special codes written by the Trace 1006 duplication equipment commonly in use at the time: these codes could not be written by standard Amstrad disc drives.
	When copied on a CPC, the FDC only ~~store~~ the 512 first bytes as declared in the CHRN, and ~~discard~~ the remaining contained in the gap section. Those tracks have an EDC (Error Data Checksum), because only 512 bytes are used to calculate the data checksum, as well as an illegal data field size.

	~~There~~ were ~~two methods~~ to ~~get around~~ this:		Various methods were attempted to circumvent this protection, including:

	1. A hardware modification to the Amstrad CPC and a special copy program		1. A hardware modification to the Amstrad CPC and a special copy program

	2. Executioner's utility Xexor included a 'brain file' solution to crack individual games before copying them. <br>		2. Executioner's utility Xexor included a 'brain file' solution to crack individual games before copying them.
			<br>

Sam-can: Fixed various language issues.

2022-02-13T05:18:55Z

Fixed various language issues.

← Older revision		Revision as of 05:18, 13 February 2022
Line 7:		Line 7:
	== Cassette ==		== Cassette ==

	It was a ~~modified version~~ of ~~the Spectrum's~~ cassette routines ~~with protection added~~.		The Speedlock cassette loader was a combination of an encryption system and advanced cassette routines. It is often recognized by its blue and black stripes in the border during loading.

	~~It is often recognised for it's blue/black stripes in~~ the ~~border during loading~~.		Certain hacking software, such as [[Soft-Lok]] and [[Bonzo Blitz]], attempted to follow the protection development to created unprotected versions of the protected software.

	~~Later versions had multicoloured stripes for the leader/pilot tone, and then blue/black stripes for the data.~~		The Speedlock tape protections in their Amstrad CPC versions use 3 different types of encoding :

	~~As the protection system continued to evolve, programs such as [[Soft-Lok]] and the [[Bonzo Blitz]] were upgraded to break the protection.~~

	The ~~speedlock~~ tape protections in their Amstrad CPC versions ~~only~~ use 3 different types of encoding :

	Speedlock type 2 (1984-1986):		Speedlock type 2 (1984-1986):
Line 59:		Line 55:
	*Xevious		*Xevious

	* In order to determine if a game use a speedlock v4 or v6, you need to check the baudrate with CSW2CDT.

	~~a speedlock~~ game with a ~~baudrate~~ of 1900 ~~bauds~~ is ~~a speedlock~~ v4. A ~~speedlock~~ v6 will ~~never be beyond~~ 1675 ~~bauds~~.		A Speedlock-protected game with a baud rate of 1900 is Speedlock v4. A Speedlock v6 will not exceed 1675 baud.

	Speedlock type 4 (1900 ~~Bauds tapes~~) (1986-1988):		Speedlock type 4 (1900 baud) (1986-1988):

	*Arkanoid Revenge of Doh,		*Arkanoid Revenge of Doh
	*Basket Master,		*Basket Master
	*Crazy Cars,		*Crazy Cars
	*Deliverance Stormlord II,		*Deliverance Stormlord II
	*Gryzor,		*Gryzor
	*Mercenary ~~L'evasion de~~ Targ ~~(specific speedlock)~~		*Mercenary: Escape From Targ
	*Renegade (Hitsquad),		*Renegade (Hitsquad)
	*Road Runner,		*Road Runner
	*Robocop,		*Robocop
	*Stallone Cobra,		*Stallone Cobra
	*Tank,		*Tank
	*Target Renegade,		*Target Renegade
	*Tarzan (specific ~~speedlock~~)		*Tarzan (specific Speedlock)
	*The New Zealand Story,		*The New Zealand Story
	*World Games		*World Games

	Special speedlock : *Nigel Mansell GP => the main code ~~use a speedlock~~ v4, while the ~~levels use a speedlock~~ v2.		Special speedlock : *Nigel Mansell GP => the main code is protected by Speedlock v4 while the level data uses Speedlock v2.
			To determine whether a game uses Speedlock v4 or v6, check the baud rate with CSW2CDT.
	Speedlock ~~type 6 (1675 bauds) (1988-until~~ the ~~CPC death):~~

	~~Before hand, please note~~ that ~~the~~ data ~~levels can be using~~ either the ~~spectrum~~ variant 2 scheme, or the ~~sinclair spectrum~~ one.		Speedlock type 6 (1675 baud) (1988-until the CPC death):
			Note that level data may use either the Spectrum variant 2 scheme, or the Sinclair Spectrum one.

	*Altered Beast,		*Altered Beast
	*Back To the Future III,		*Back To the Future III
	*Bad Dudes vs Dragon Ninja,		*Bad Dudes vs Dragon Ninja
	*Batman the Movie,		*Batman the Movie
	*Darkman,		*Darkman
	*Fighter Bomber,		*Fighter Bomber
	*Guerrilla War,		*Guerrilla War
	*Hammerfist,		*Hammerfist
	*Monty Python Flying ~~circus,~~		*Monty Python Flying Circus
	*Mutants 64k,		*Mutants 64k
	*Ocean Beach Volley,		*Ocean Beach Volley
	*Operation Wolf,		*Operation Wolf
	*Operation Thunderbolt,		*Operation Thunderbolt
	*P47 Freedom Fighter,		*P47 Freedom Fighter
	*Rainbow Islands,		*Rainbow Islands
	*SDI (~~activision~~)		*SDI (Activision)
	*Shinobi,		*Shinobi
	*Star control,		*Star control
	*Stormlord,		*Stormlord
	*Super Wonderboy in ~~monsterland,~~		*Super Wonderboy in Monsterland
	*The Addams Family 128k,		*The Addams Family 128k
	*The Ninja Warriors,		*The Ninja Warriors
	*The Untouchables,		*The Untouchables
	*Turrican II The Final Fight,		*Turrican II The Final Fight
	*Typhoon,		*Typhoon
	*Wizball,		*Wizball
	*Cabal		*Cabal
	*Midnight Resistance		*Midnight Resistance

Sam-can: Accuracy corrections.

2022-02-13T05:07:05Z

Accuracy corrections.

← Older revision		Revision as of 05:07, 13 February 2022
Line 1:		Line 1:
	[[Category:Copy Protection]]		[[Category:Copy Protection]]

	'''Speedlock''' is the name of a disc and cassette copy protection designed by Dave Looker ([[DJL]]) ~~and Dave~~ Aubrey-Jones.		'''Speedlock''' is the name of a disc and cassette copy protection designed by Dave Looker ([[DJL]]), David Aubrey-Jones and Simon Berry.

	~~Earlier versions mentioned "DJL Software" later versions mentioned "Speedlock Associates"~~.

			Earlier versions mentioned "DJL Software", while later versions mentioned "Speedlock Associates".

	== Cassette ==		== Cassette ==

Dlfrsilver at 01:21, 27 May 2017

2017-05-27T01:21:26Z

← Older revision		Revision as of 01:21, 27 May 2017
Line 16:		Line 16:
	As the protection system continued to evolve, programs such as [[Soft-Lok]] and the [[Bonzo Blitz]] were upgraded to break the protection.		As the protection system continued to evolve, programs such as [[Soft-Lok]] and the [[Bonzo Blitz]] were upgraded to break the protection.

	The speedlock tape protections in their Amstrad CPC versions only use 4 different types of encoding :		The speedlock tape protections in their Amstrad CPC versions only use 3 different types of encoding :

	Speedlock type 1 :		Speedlock type 2 (1984-1986):

	*11 A Side Soccer		*11 A Side Soccer
Line 60:		Line 60:
	*Xevious		*Xevious

	Speedlock type 2 :		* In order to determine if a game use a speedlock v4 or v6, you need to check the baudrate with CSW2CDT.

			a speedlock game with a baudrate of 1900 bauds is a speedlock v4. A speedlock v6 will never be beyond 1675 bauds.

			Speedlock type 4 (1900 Bauds tapes) (1986-1988):

	*Arkanoid Revenge of Doh,		*Arkanoid Revenge of Doh,
Line 67:		Line 71:
	*Deliverance Stormlord II,		*Deliverance Stormlord II,
	*Gryzor,		*Gryzor,
	*Mercenary L'evasion de Targ,		*Mercenary L'evasion de Targ (specific speedlock)
	*Nigel Mansell GP,
	*Renegade (Hitsquad),		*Renegade (Hitsquad),
	*Road Runner,		*Road Runner,
Line 75:		Line 78:
	*Tank,		*Tank,
	*Target Renegade,		*Target Renegade,
	*Tarzan,		*Tarzan (specific speedlock)
	*The New Zealand Story,		*The New Zealand Story,
	*World Games		*World Games

	Speedlock type 3 :		Special speedlock : *Nigel Mansell GP => the main code use a speedlock v4, while the levels use a speedlock v2.

			Speedlock type 6 (1675 bauds) (1988-until the CPC death):

			Before hand, please note that the data levels can be using either the spectrum variant 2 scheme, or the sinclair spectrum one.

	*Altered Beast,		*Altered Beast,
	*Back To the Future III,		*Back To the Future III,
	*Bad Dudes vs Dragon Ninja,		*Bad Dudes vs Dragon Ninja,
	*Batman the Movie,		*Batman the Movie,
			*Darkman,
	*Fighter Bomber,		*Fighter Bomber,
	*Guerrilla War,		*Guerrilla War,
Line 106:		Line 114:
	*Typhoon,		*Typhoon,
	*Wizball,		*Wizball,

	~~Speedlock type 4 :~~

	*Cabal		*Cabal
	*Midnight Resistance		*Midnight Resistance

Dlfrsilver: /* Cassette */

2016-02-25T15:59:05Z

Cassette

← Older revision		Revision as of 15:59, 25 February 2016
Line 25:		Line 25:
	*Arcade Flight Sim.		*Arcade Flight Sim.
	*Arkanoid		*Arkanoid
			*Army Moves UK
			*Batman
	*Beach Head		*Beach Head
	*Beach Head II		*Beach Head II
			*Bounty Bob Strikes Back
	*Bmx Simulator		*Bmx Simulator
	*Death Stalker		*Death Stalker
	*Express Raider		*Express Raider
	*Fruit Machine Sim.		*Fruit Machine Sim.
			*Galivan
	*Grand Prix II		*Grand Prix II
	*Green Beret		*Green Beret
Line 38:		Line 42:
	*International Rugby		*International Rugby
	*Italian Super Car		*Italian Super Car
			*It's a Knockout
	*Kong Strikes Back		*Kong Strikes Back
	*Kung Fu Masters		*Kung Fu Masters
Line 48:		Line 53:
	*Pro Tennis Sim.		*Pro Tennis Sim.
	*Raid!!		*Raid!!
			*Rambo First Blood Part II
	*SAS combat Sim.		*SAS combat Sim.
	*Super Heroes		*Super Heroes
	*Super Stuntman		*Super Stuntman
	*Super Tank		*Super Tank
			*Xevious

	Speedlock type 2 :		Speedlock type 2 :

	*Arkanoid Revenge of Doh,		*Arkanoid Revenge of Doh,
	*Army Moves UK,
	*Basket Master,		*Basket Master,
	*Crazy Cars,		*Crazy Cars,

Dlfrsilver: /* Cassette */

2016-02-25T15:55:24Z

Cassette

@@ Line 4: / Line 4: @@
 Earlier versions mentioned "DJL Software" later versions mentioned "Speedlock Associates".
 == Cassette  ==
@@ Line 13: / Line 14: @@
 Later versions had multicoloured stripes for the leader/pilot tone, and then blue/black stripes for the data.
 As the protection system continued to evolve, programs such as [[Soft-Lok]] and the [[Bonzo Blitz]] were upgraded to break the protection.
 == Disc  ==

Dlfrsilver: /* Disc */

2015-12-19T19:24:39Z

Disc

← Older revision		Revision as of 19:24, 19 December 2015
Line 20:		Line 20:

	One version called "[[8k Speedlock]]", relied on the fact that the CPC's hardware could reliably read but not write 8k sectors.		One version called "[[8k Speedlock]]", relied on the fact that the CPC's hardware could reliably read but not write 8k sectors.

			the format was either devised or done on an Atari ST or an IBM PC compatible machine (since the CPC share with them the same FDC controler). The main difference being that an ST or PC can write more data per track than a CPC.

			In itself, a speedlock track exists in 2 versions, used at the discretion of the duplicator, one use a CRC, and the other not.

			A speedlock track consist of only 512 byte declared for the sector, and all the remaining data is spanned in a huge GAP section.
			When copied on a CPC, the FDC only store the 512 first bytes as declared in the CHRN, and discard the remaining contained in the gap section. Those tracks have an EDC (Error Data Checksum), because only 512 bytes are used to calculate the data checksum, as well as an illegal data field size.

	There were two methods to get around this:		There were two methods to get around this: