| Author: | Vesa Paatero (registered user: 1 posts ) |
|---|---|---|
| Date: | Sun, Sep 23rd, 2012 @ 08:02 ( . ) |
Hi everyone, Back then (in early nineties I guess) I tried to obtain a copy of Autoduel in spite of the warning somewhere in the accompanying materials that the game disk (side A or 1) could get broken if copying is attempted... And guess what: It did! The C64 Preservation Project's database says about Autoduel that the copy protection is based on checking whether track 6 is unformatted. However, I haven't found any description or theory explaining how a copy protection that breaks the original is accomplished. I suppose it doesn't always happen, otherwise it would be more widely known. If I remember correctly, the broken disk behaved so that a read error (and the stepping motor making the typical noise) occurred as because of the copy protection, but after the copying attempt the drive stopped with the light blinking. (On the other hand, I can't be sure whether it was exactly the same read error.) The copying attempt was performed using a 1541-II disk drive. The software was either Fast Hack 'em or a similar one whose name I don't remember -- the only one we knew of that seemed to be better than Fast Hack'em in whole-disk copying. So, could the copy protection scheme be based on something bad happening when the whole-disk copier reads those areas on track 6 that are normally never read? .. or reading them in an order different from the game software? Anyway, the detrimental change should affect areas that _are_ always read. Strange. Breaking my friend's game in spite of the warning was somewhat traumatic, I have to admit... Fortunately, my friend had bought the disk second-hand as part of a larger bunch of games, and a cracked version of the game appeared within our reach a little later. However, the cracked version had a bug that caused the game to crash occasionally, which was very bad in that game because saved games would get lost also unless explicitly backupped by copying side B of the game disk. To this day it is unclear to me whether the crashing bug was already present in the original version or only in the piratic one. Any ideas or similar experiences? Regards, Vesa |
 | Author: | Pete Rittwage (registered user: 558 posts ) |
|---|---|---|
| Date: | Sun, Sep 23rd, 2012 @ 14:27 ( . ) |
There is no way a normally functioning copy program can damage an original while trying to copy it. Now, plenty of people have accidentally swapped their original for their copy during the process. If you do that, and it's not write-protected, then you can damage it. |
 | Author: | hyper active (registered user: 296 posts ) |
|---|---|---|
| Date: | Mon, Sep 24th, 2012 @ 20:22 ( . ) |
Hi. While not directly copy related, I am aware that certain titles from OziSoft that use later versions of their loader, which I've dubbed "Heystack" can be damaged by quickly opening and closing the drive door while the areas on tracks 36, 38 and 39 are being checked. I believe this is what caused my copy of uridium to break. I've also seen some cyan loader titles that have been bought in Australia that seem to have been engineered to only load a certain number of times before breaking. However, I see no reason why simply trying to copy a disk would ruine it. |
 | Author: | JimDrew (registered user: 23 posts ) |
|---|---|---|
| Date: | Tue, Oct 30th, 2012 @ 17:35 ( . ) |
If the disk is write protected, it does not matter what you do with the drive door, it would be physically impossible to damage the disk. |