Club CDFreaks - Knowledge is Power - View Single Post

Orinoco · 20-04-2004

This was my first outing with DiscJuggler, so I downloaded FutureProof's Quick Guide and the latest Demo version of DJ [4.10.1140] from Padus and got to work. For a first attempt I tried to do another backup of Harry Potter + the Philosopher's Stone [SD2.40.010] just to test I'd got the settings correct. So far so good. Then it was on to SD 3.20 and this is how I got on ....

Title: Splinter Cell: Pandora Tomorrow

Read:
ASUS CRW-5232AS
DiscJuggler 4.10.1140

Write: [4x]
ASUS CRW-5232AS
DiscJuggler 4.10.1140

Success.

Well mostly - again. My first burn was to a Philips High Speed 700Mb CD-RW and the game authenticated every time I tried. I then burned it to a CD-R [TY Cyanine 700Mb] - of the 15 times I've tried to start the game I got 4 failures when the backup disk provided a .tmp file error.

This rather mimics the results I found with my FireBurner tests. However the percentage failure rate was higher. I ran another set of game startup tests with the FireBurner CD-R [previous CD-R from same spindle] and didn't have a single additional failure. Final stats were; FireBurner write 1/15 failures against a DJ write 5/15 failures.

I believe that the ASUS is a much better reader, and with DJ can read/write the pre-gap correctly so I hoped to get a better backup, one that didn't fail at all. I have to assume that either the individual media played a part in the failure or there was something else going on that I'd missed. In all the CD-RW tests I'd done there wasn't a single failure from either burn.

I looked back through the DJ log - which for some reason I'd saved in a notepad file

and found that DJ had supplied dummy blocks between 0:14:14 and 2:18:24 MSF and also between 64:00:11 and 70:58:39 MSF. Not sure how that correlates to the CloneCD sector report which was between the standard ranges [~800 and ~10,000]. However it looks like DJ picked up a heck of a lot of errors at the end of the disk that CloneCD didn't. Could this be significant? Well I have no idea the CD-RW didn't seem to care they were there but the CD-R did..........?

If anyone else can explain it, feel free..........

Conclusions:

FireBurner and DJ can both write SD 3.20.
The LTD-163D is still good enough to read SD3.20
The [or should that be my] LTR-40125S can't write SD 3.20

20-04-2004	#1 (permalink)
Orinoco CD Freaks Senior Member Join Date: Dec 2001 Location: Kent, UK Posts: 485	Discjuggler and SD 3.20 <a href='http://adstats.cdfreaks.com/www/delivery/ck.php?n=a13febf7&cb=INSERT_RANDOM_NUMBER_HERE' target='_blank'><img src='http://adstats.cdfreaks.com/www/delivery/avw.php?zoneid=30&cb=INSERT_RANDOM_NUMBER_HERE&n=a13febf7' border='0' alt='' /></a> This was my first outing with DiscJuggler, so I downloaded FutureProof's Quick Guide and the latest Demo version of DJ [4.10.1140] from Padus and got to work. For a first attempt I tried to do another backup of Harry Potter + the Philosopher's Stone [SD2.40.010] just to test I'd got the settings correct. So far so good. Then it was on to SD 3.20 and this is how I got on .... Title: Splinter Cell: Pandora Tomorrow Read: ASUS CRW-5232AS DiscJuggler 4.10.1140 Write: [4x] ASUS CRW-5232AS DiscJuggler 4.10.1140 Success. Well mostly - again. My first burn was to a Philips High Speed 700Mb CD-RW and the game authenticated every time I tried. I then burned it to a CD-R [TY Cyanine 700Mb] - of the 15 times I've tried to start the game I got 4 failures when the backup disk provided a .tmp file error. This rather mimics the results I found with my FireBurner tests. However the percentage failure rate was higher. I ran another set of game startup tests with the FireBurner CD-R [previous CD-R from same spindle] and didn't have a single additional failure. Final stats were; FireBurner write 1/15 failures against a DJ write 5/15 failures. I believe that the ASUS is a much better reader, and with DJ can read/write the pre-gap correctly so I hoped to get a better backup, one that didn't fail at all. I have to assume that either the individual media played a part in the failure or there was something else going on that I'd missed. In all the CD-RW tests I'd done there wasn't a single failure from either burn. I looked back through the DJ log - which for some reason I'd saved in a notepad file and found that DJ had supplied dummy blocks between 0:14:14 and 2:18:24 MSF and also between 64:00:11 and 70:58:39 MSF. Not sure how that correlates to the CloneCD sector report which was between the standard ranges [~800 and ~10,000]. However it looks like DJ picked up a heck of a lot of errors at the end of the disk that CloneCD didn't. Could this be significant? Well I have no idea the CD-RW didn't seem to care they were there but the CD-R did..........? If anyone else can explain it, feel free.......... Conclusions: FireBurner and DJ can both write SD 3.20. The LTD-163D is still good enough to read SD3.20 The [or should that be my] LTR-40125S can't write SD 3.20 __________________ Make it up..? Life is bad enough as it is. Why would I want to invent more of it! - Marvin Windows XP Pro SP2 + hotfixes, Core2Quad Q6600 2.4GHz, MSI P35 Platinum, 4096MB DDR2-800 (4x 1024MB), ASUS E616A2 (fw. 1.03), Pioneer DVR-111D (fw. 1.23), Hitachi Deskstar P7K500 500GB + 320GB 16Mb S300, Nvidia GeForce 8800GT (512Mb)