How to copy various protections
#21
(03-06-2016, 01:52 PM)admin Wrote: Does the original disk work?  If the original disk is write protected (no notch), are you making sure that you are write protecting the image file in VICE?

The original works no problem. I also tried write protecting the image file and no luck... but it appears it has something to do with the image file or VICE as I made a copy directly to another disk and it worked fine on my original C64, so it gets copied to a disk... The only thing surprising is that there are plenty of other Rapidlok protected games that run fine from a .G64 file but I can't make this one (Card Sharks) work from a .G64 file generated from the SuperCard Pro...and there is nothing really special about it... it is a Rapidlok V6 game... The only other thought I had is that I think I read somewhere in the forum that you could only create .G64 images of disk made with index... I ended up trying both ways Index or Splice and the image never worked so far in Vice...
Reply
#22
I will see if I have Card Sharks.
Reply
#23
If you post a link to it, I can take a look and see what might have gone wrong. Based on your description, it's something on the key track (36).
Reply
#24
(01-15-2014, 09:05 PM)Hi, Ive tried to copy Xevious in both Index and Splice Mode and no go.  Btw, I finally got my SCPro working...had managed to pickup 3 Floppy Drives.  Panasonic 475-4 and 475-2 and a Canon.Even tried BurstNibbler 1.9 which almost worked...gonna try 1.7 which I had the most success with.Heck I even tried a V-Max Copier called Revolution V which identified the V-Max Version as being V-Max! 1 but said it couldn't copy it.  Nice tool

-Mark.

LordCrass Wrote:
Here's a cheat sheet on my experiences with making a copy/image various C64 protections as of v.99:

I always leave the option for "index sensor" set to "required" for both reads and writes.

Rapidlok: tracks 1-36 in SPLICE mode. Even though the disks are mastered to the index hole, the key track requires the SPLICE handling for writing back to a real disk. For a G64 image, tracks 1-36 INDEX mode works.

V-Max: tracks 1-40 INDEX mode should work for almost all of these. There are a few I've encountered that had the directory track unaligned and required SPLICE mode (Rastan and Renegade). After Burner requires SPLICE mode.

Vorpal 1: tracks 1-35 SPLICE mode.

Vorpal 2: currently requires reading in SPLICE mode, 2 revolutions and then writing back out manually from the analyzer after specifying start/end. Hopefully added to SPLICE handling in a future release.

EA track 2 PirateSlayer: Some of these disks are mastered to the index hole and can be copied in INDEX, but some (eg. Skate or Die!) are not. Use the SPLICE mode when in doubt, tracks 1-35.

EA fat track 34/35: tracks 1-33 INDEX mode. Tracks 34-35 in INDEX mode with half-tracks enabled. Have "wipe tracks" turned off when writing 34-35. Writing out the whole disk with half-tracks will generally result in a copy full of errors that won't load. You will need to image 1-35 with half-tracks and INDEX mode if you want to make a G64.

Xemag fat track 35/36: Same as EA fat track, but use SPLICE mode as all Xemag disks I've seen so far are aligned about 1/8 of a rotation off the index mark. There's at least one Xemag game that has the fat track on track 6/7 (F-15 Strike Eagle).

Bounty Bob Strikes Back: Copy tracks 1-11 with INDEX mode on and half-tracks on. Copy tracks 12-35 with INDEX mode on and half-tracks off. Make sure to write-protect the copy or it will fail to load. Currently, the byte count protection on track 12 will very likely fail if you write the copy on a drive that spins at a different rate than the one it was read from. If this happens, the title screen will appear but it will hang on the "Player 1" screen when you try to start.

Others: The majority of original disks can be mastered with the INDEX mode option enabled, but if you encounter difficulty, or are unsure, leave this option disabled and let the software determine where the data is. Always leave half-tracks off unless you know the protection uses them, and even then, only copy the half-tracks and surrounding full tracks with this option enabled.

I've noticed that some of my originals show up with errors when read from the PC HD drive; errors that don't appear when reading the same disks with the 1541. I'm not sure why, but it may have something to do with the smaller read/write head of the HD drive being a little more finicky about the data it reads.
Reply
#25
Okay, I managed to copy Xevious (finally) along with Summer Games II but not sure what worked since I kept switching things up.  Might've been Index to Track 38 AND cleaning heads often.

Still cannot Backup S.Games II Backside...can't even read the directory of the Copy on the 1541.

Tried Index and Splice.
Reply
#26
Moved.
Reply
#27
Moved.
Reply
#28
Norton's is not a C64 /128 program. You can use IBM360 format for this disk.
Reply
#29
Technically, any disk can be duplicated using ANY of the settings. All disks use heads and tracks, and since two heads are always used with tracks (that can be adjusted depending on the TPI drive), any disk type can be used.
Reply
#30
(01-15-2014, 09:05 PM)LordCrass Wrote: EA fat track 34/35: tracks 1-33 INDEX mode. Tracks 34-35 in INDEX mode with half-tracks enabled. Have "wipe tracks" turned off when writing 34-35. Writing out the whole disk with half-tracks will generally result in a copy full of errors that won't load. You will need to image 1-35 with half-tracks and INDEX mode if you want to make a G64.

Racing Destruction Set, which uses the same protection, could be successfully reproduced on a Mitsumi D503 48 TPI drive in INDEX mode. The fat track does not rely on half tracks.
Reply




Users browsing this thread: 1 Guest(s)