cdcops copy protection systems for software anti-piracy

Home > Products > Software Copy Protection > CD-COPS > Locking Operations

Step

Description

Input

Output

Customer realizes that CD-COPS can be applied either as a shell (envelope) protection added to the software product’s main executable file(s), using the automated wrapping utility provided, herein-after referred to as the “Wizard option”, or as an API protection implemented into the software product’s main executable file(s), by the use of various programming routines, libraries and modules, hereinafter referred to as the “API option”. It is Customer's sole responsibility to choose and decide which option to be used for CD-COPS to be applied into the software product. In this respect, MediaSoft shall prepare and provide the appropriate “Software Developer’s Kit” for the system to be implemented according to Customer’s sole decision and choice. Only Customer and MediaSoft shall be entitled to use the Software Developer’s Kit provided, for the system to be applied into Customer’s existing and future CD-ROM products.

Initial
decision
to use the
CD-COPS
locking

SDK

Upon Customer’s decision to use CD-COPS to protect a new soft-ware product, it shall send to MediaSoft two (2) identical CD-R copies of the software product in question, along with the CD-COPS Technical Form 1 and the CD-COPS Order Form 2, both duly filled in, signed and stamped by an authorized person, for MediaSoft to be acknowledged about the technical specifications and restrictions of the software product to be protected, as well as the CD-ROM quantity to be produced and the market details of the software product in question.

Ripe
decision
to use the
CD-COPS
locking

CD-Rs,
Form 1
&
Form 2

MediaSoft shall use Customer’s “Software Developer’s Kit” to implement, apply and embed the CD-COPS security features into the software product’s main executable file, according to the remarks and provisions stated in the CD-COPS Technical Form 1 submitted by Customer. MediaSoft shall transfer the content of the resulting protected software product on to a CD-R, hereinafter referred to as the “premaster”, and MediaSoft shall use the software tools needed and its related know-how to measure the premaster and calculate the temporary access code needed for the protected software product to run, and perform extensive exams and tests that shall verify the implementation correctness.

	In case that the tests shall indicate the presence of errors caused by the CD-COPS implementation, MediaSoft shall re-peat the related procedures, as many times as required until the protected software product be free of errors.
	In case that the tests shall indicate the absence of errors, MediaSoft shall send the premaster to Customer for further operational testing.

SDK,
CD-Rs,
Form 1
&
Form 2

Premaster
&
Temporary
Access Code

Customer shall use its duly qualified personnel to extensively examine and test the premaster to verify that implementation has been accomplished perfectly, and no operational conflicts or mismatches have occurred.· In case that the tests shall indicate the presence of errors caused by CD-COPS implementation, Customer shall acknowledge MediaSoft and the latter shall repeat the related procedures, for as many times as required until the protected soft-ware product be free of errors.· In case that the tests shall indicate the absence of errors, Customer shall send to MediaSoft the CD-COPS Technical Approval Form 3 duly filled in, signed and stamped by an authorized person.

Premaster
&
Temporary
Access Code

Form 3

Customer may assign the CD-ROM production of the protected software product to any CD factory, according to MediaSoft’s production quality restrictions and provisions.

Form 3

CD-ROM
production

Customer realizes that:

	All protected CD-ROMs produced out of the same glass-master are identical, and therefore, the same access code could be used for the protected CD-ROMs produced throughout the total production, to run safely, under maximum security and compatibility.
	The CD factory that shall produce Customer’s CD-ROMs, should press, and repress all the protected CD-ROMs in question, by the use of as many stampers as required, made out of the very same glass-master, to ensure that all CD-ROMs could use the same access code.
	In many cases of future re-pressings and pressings of big quantities, the CD factory might not follow this quality restriction, and use multiple stampers to accomplish the production task.

Customer affirms that:

	Upon the completion of the CD-ROM production process, and for each different stamper used for the production in question, it shall send to MediaSoft ten (10) sample discs, along with the CD-COPS Quality Control Form 4, duly filled in, signed and stamped by an authorized person.
	The sample discs to be sent to MediaSoft shall be gathered from various different points, well spread within the total length of the production in question.

CD-ROM
production

CD-ROM
samples
&
Form 4

7**

MediaSoft shall use the software tools needed and its related know-how to examine, test and measure the sample discs to validate the quality of the production proceedings followed, to verify the quality of the physical materials used for the disc production, and to extract and calculate the exact matching access code(s) needed for the protected product to run under maximum security and compatibility. MediaSoft shall send the access codes to Customer, via email and within one (1) working day upon receipt of the sample discs, the CD-COPS Quality Control Form 4, as stated above, and the payment confirmation of the related fees.

CD-ROM
samples,
Form 4
&
Payment

Final
Access Code

Customer realizes that:

	For security and compatibility reasons, MediaSoft and its associates release on a tactical and periodical basis newer, revised and upgraded CD-COPS Software Developer’s Kits to be used for implementation into customers software products.
	In case that re-implementation is required, MediaSoft shall implement, apply and embed CD-COPS into Customer’s software product, free of charge, and according to the provisions stated above.

Customer affirms that it shall not proceed to any future repressing of protected CD-ROMs, unless it previously informs MediaSoft soon enough, for the latter to examine and investigate if CD-COPS re-implementation into Customer’s software product is needed.

Ripe
decision
to proceed
to repressing

Possible
CD-COPS
re-implementation

(*) If Customer implements CD-COPS using the tools provided, then steps 3 and 4 should be voided.

(**) If Customer performs access code measurement using the tools provided, then step 7 changes in such a way that MediaSoft’s part shall restrict to operational supervision.

About CD-COPS
...to find out more about the leading software copy protection technology for CD-ROMS

CD-COPS References
...to find out who uses the leading software copy protection technology for CD-ROMS

CD-COPS F.A.Q.
...to get answers to your most commonly asked questions on CD-COPS

CD-COPS Operations
...to find out the operational steps to be followed for CD-COPS to be exploited

ToolBook Edition
...to find out how you can copy protect your ToolBook developed application

About DVD-COPS
...to find out more about the leading software copy protection technology for DVD-ROMS

About PDF-COPS
...to find out how you can copy protect your Acrobat created PDF files

Optimum Protection Finder
... to find out which security and protection technology serves your needs the best

Download Forms and Specs
...to get the most up-to-date information, specifications and forms

© 2004 - 2006, MediaSoft International. 8 L. Iasonidou Street, 54635 Thessaloniki, Hellas (Greece) Tel: +30 2310 202085, Fax: +30 2310 202067, Email: Info@MediaSoftInt.com To explore this site you should accept our Terms and Conditions of Usage

Full moon calendar and the next full moon dates