VERY weird burning issue with GTA3 & SD 2.51

vbimport
#1

Ok, I have had no problems backing up any sd version in the past. I have made copies of MOHAA, C&C Renegade, and GTA3 with clonecd and betablocker 1.01. Check this out. I just bought GTA3, and I immediately backed it up so i wouldn't lose the discs to scratches and such, plus it gives me a rush :wink: . Anyway, I managed to make 4 copies of it on different media (I've been testing different media for quality and SD 2.51 compatibility, no illegal stuff going on here). When I went to try my 5th copy using the same images, something went awry. The install cd works fine, because it has no protection, contrary to what people think. Anyway, when i went to test the play cd, i get the hanging at the rockstar logo load screen error. I double checked my previous copies, and they still worked fine. Keep in mind i used betablocker to patch the play cd image, and that I used the EXACT SAME settings every time. Since the reading was obviously fine because i made 4 working copies, I checked to see if it was the media. I used reliable fujifilm 700mb and verbatim 700mb cd-r's, ones that i had made previous successful backups on. Here's where i got scared and began to weep: THE BACKUPS DIDN'T work. I was always using the same settings, so i tried writing with AWS on and off (yeah i know, don't use betablocker and AWS on the same image, but i was fiddling around ok?) to no avail. Here's my hunch: the repetitive burning of the same image caused some sort of degredation to the integrity or content of the image. Has anyone heard tell of anything like this happening before? I just read another image and successfully "betablocked" the sd2.51 play disc image, and the burn process is at 53% right now. I'll let you know how it turns out. But man, there is some weird mojo going on here. I actually think i had the same problem with a max payne image i was storing on a backup drive. After i re-read the image, i was able to back the game up again. I'll let you know how it turns out.

P.S. - I didn't give any burner stats or settings because the backup process ran fine. I will let you know I used the settings reccomended by clony 2.0.0.6 and they worked the first 4 times, and i used betablocker, not AWS.

P.P.S. - On that note, I've been wondering. My NEC NR-7800A burner only partially does EFM encoding correctly (1 sheep), and betablocker 1.01 has always worked for sd 2.51. I've used AWS for safedisc 2, but never 2.51 or above. Will AWS work for my burner on SD2.51 and above? I know i should just test it, but My budget is tight, and every coaster i make takes away a little piece of my soul with it.... :wink:

Thanks for your time and contributions!!!!

#2

Okay, hereā€™s the scoop. I just finished the new burn, same problem of hanging at the rockstar logo. Iā€™m reading again with new settings and Iā€™m going to do a betablocker/AWS burn, but Iā€™m still really confused.

#3

The install cd works fine, because it has no protection, contrary to what people think.

sorry but the first and second disc of gta3 contain sd v2.51.021, disc 1 contains the .exe file wich IS safedisc encoded, and disc 2 contains the rest of the protection to run the game(eg.xxxxx01.tmp)

#4

ā€œMy budget is tight, and every coaster i make takes away a little piece of my soul with itā€¦ā€

Why you donā€™t then buy a cd-rw disc? :stuck_out_tongue:

#5

i am not doing the same as u(i donā€™t use betabloacker 'cos i got 2 SD2.51 capable burners), but i have had funny xperiences with sd 2.51??

When backing up MOHAA, i made about 3 working backups, then when i made more, some worked, and some didnā€™t?

i still dont know what the problem is but im not letting it bug me :slight_smile:

#6

Hey, thereā€™s definately something fishy going on now. I still used the same settings i was using before, except now Iā€™ve only managed to mak successfuly copies of my ORIGINAL backup. I use the same settings, but i canā€™t seem to make to make copies of the original disc, only other copies that I have already made. I still use betablocker 1.01, and the copies of the copy are fine, but My copies of the orignial arenā€™t working. Man, does anyone have any idea whatā€™s going on here?

#7

go ahead and post ur settings, dont be shyā€¦for some reason, it always helps to know how ur doing what ur doing.

#8

Ok, so here are the settings:

Read

Read retries: 0
Error Correction: Software
Speed: 4x
Audio and data extraction: Medium (Doesnā€™t matter, only applies to subs)
Regenerate Data Sectors: On
Fast Error Skip: Auto

Write

Speed: 4x
AWS: OFF
Always close last session: On
Donā€™t repair subs: OFF

(Patched with Betablocker 1.01)

#9

try a new image but with out beta blocker then have aws set on

#10

Iā€™m having a weird issue with GTA3 alsoā€¦ Iā€™ve made perfect working copies of MOHAA, without any problems. Clony tells me itā€™s also SD 2.51, so I thought it would be just as easy to copy GTA3. My mistake!

My burner is a LG 8320B, which I saw on several lists as totally EFM compatible, and able to burn SD 2.51. Whichever settings I use (Clonyā€™s, some Iā€™ve been seeing in the posts, my own), I can never make a working copy of the second disk, everytime I start the game it tells me to insert the correct cd.

Iā€™ve tried also betablocker, but to no availā€¦ same thing happens.

And thereā€™s also a funny detailā€¦ whatever speed setting I use in CloneCD 4, it always burns and reads at 8xā€¦ except for the reading of the protected sectors, of course.

Why the hell is GTA3 so ā€œuncopiableā€ when MOHAA doesnā€™t even break a sweat?

#11

buy a lite-on and your life becomes less stressfull:p

#12

pete_pt, i have the same burner. i thought i was making coasters of the same game (GTA2) until i tried the ā€œcoastersā€ on some different cdrives. worked fine!!! of course i destroyed the 5 working copies;) Futureprof posted a good tip to mount them in Daemon tools to test first, then youll know.

#13

Add me to the list of people with strange problems with MOHAA.

My problem is a little different. I can only making working backups on CD-RW media. CD-Rs will not work. Iā€™ve tried 5 different brands. I use CloneCD 4 (4.0.06 I think) with the default Game profile. I select max speed for Read/Write but the read operation takes 12.5 minutes. Since my Cyberdrive 36X does not support correct writing of regular EFM patterns I had to use AWS. Later Daemon Tools confirmed the image.

Iā€™ve made about a dozen and a half coasters but CD-RWs are fine and always work in two writers and one CD-ROM. I donā€™t need to use ā€œHide CDR Mediaā€. Is this because the media is CD-RW?

#14

Originally posted by phsstpok
[B]Since my Cyberdrive 36X does not support correct writing of regular EFM patterns I had to use AWS. Later Daemon Tools confirmed the image.

Iā€™ve made about a dozen and a half coasters but CD-RWs are fine and always work in two writers and one CD-ROM. I donā€™t need to use ā€œHide CDR Mediaā€. Is this because the media is CD-RW? [/B]

  • D-Tools can only confirm you have or donā€™t have a RAW image. In most cases a SD2 image can be read RAW but you just canā€™t write it correctly[*]Are you saying that ā€œHideā€¦ā€ is off when playing from the burner?
#15

Originally posted by FutureProof
[ul][li]Are you saying that ā€œHideā€¦ā€ is off when playing from the burner?[/ul] [/li]Yes. Thatā€™s exactly what I am saying. I uninstalled MOHAA and reinstalled it from the backup copy (CD-RW). It runs perfectly. I donā€™t even load CloneCD Tray so ā€œHide CDRā€ is definitely off.

#16

Originally posted by FutureProof
[ul][li]D-Tools can only confirm you have or donā€™t have a RAW image. In most cases a SD2 image can be read RAW but you just canā€™t write it correctly[/ul] [/li]This brings up another question. Elsewhere at CDfreaks forums I found a link for an SD2.51 EFM test writing ISO. If I understand correctly one burns the image and can then read back the image then this demonstrates that oneā€™s burner can correctly write EFM encoding. My burner failed this test yet I was able to make a backup copy of my CIV3 (Safedisk 2) disc. I was able to do this before I learned of the AWS and the region trick (Iā€™m in the USA).

Does Safedisk 2 use that regular bit EFM pattern thing? I had the impression that if my drive canā€™t write the patterns correctly then even Safedisk 2 shouldnā€™t work (unless AWS is used).

Please help me understand my results.

#17

Originally posted by phsstpok
Since my Cyberdrive 36X does not support correct writing of regular EFM patterns I had to use AWS.
You got the burner after this one :CW-058D 32x12x48? The 36x isnā€™t listed on Olliā€™s site yet. Why RWs work and Rs donā€™t? I have no idea

btw, Iā€™ve seen your Nick elsewhereā€¦where was that?

#18

Originally posted by FutureProof
You got the burner after this one :CW-058D 32x12x48? The 36x isnā€™t listed on Olliā€™s site yet.
Yup, Itā€™s the CW068D, the one after 32X and before the CW078D (40X I think and available in Europe). I think my burner has more than than just a firmware update to the CW058D. My burner has the same firmware version number (or one of the 58ā€™s firmware updates), 110D. The CW068D has six Z-CLV zones instead of five, and seems to have a very conservative speed curve. It only averages 27X for a 700MB burn which I think the same as the 32X drive yet my drive does reach 36X.

There are other strange things about this burner. When I try Nero CD Speedā€™s CD Quality check it reports, ā€œThis drive seems incapable of returning error informationā€¦Continue anyway?ā€. If I do continue I always get like 40% errors (not 40 errors, 40 percent) on every disc, even originals, yet all my game backups work, all my music CD-R/CD-RWs are free of audible errors, the Advanced DAE check says, 99.9% (on generic media). Somewhere I got the error message, ā€œthis drive cannot report C2 errorsā€ or something like that. (I canā€™t remember the application in which I got this message). Still, everything seems to work (except SD2.51 backups on CD-Rs). Very funky, this drive.

Iā€™m about to try EAC to see how it does with ā€œperfectā€ audio copies (backups, of course).

#19

Originally posted by phsstpok
<trimmed> Elsewhere at CDfreaks forums I found a link for an SD2.51 EFM test writing ISO. My burner failed this test yet I was able to make a backup copy of my CIV3 (Safedisk 2) disc.

civ3 isnt 2.51, so this does not apply

#20

Originally posted by ckin2001
[B]
quote:

Originally posted by phsstpok
<trimmed> Elsewhere at CDfreaks forums I found a link for an SD2.51 EFM test writing ISO. My burner failed this test yet I was able to make a backup copy of my CIV3 (Safedisk 2) disc.

civ3 isnt 2.51, so this does not apply[/B]

Ckin2001, you misunderstand my meaning. I was not trying to say that because I could make a CIV3 copy that I should not be having problems. Iā€™m not that naive.

What I was trying to say, is that I already learned that my writer cannot correctly write EFM regular bit patterns at all, and that I thought Safedisc 2 also uses this technique (although not as effectively as 2.51). I didnā€™t understand the results I was getting.

I should have mentioned that the Safedisk2 ISO test also failed.

I can understand how I could get a working copy (but not 1:1) if I used AWS. What I canā€™t understand is how I got a working copy without it using it on a drive that seems to have problems.

Am I wrong about this? Doesnā€™t Safedisk 2 use these EFM tricks?

Maybe I used the ISO images incorrectly. I just wrote them to a CDRW and tried to use CloneCD to make a copy. CloneCD was unable to make an image.