Unexpected results with Sims Unleashed

I just got the Sims Unleashed to test the new Safedisc v2.80.010
Ive done one test run so far and the results were sort of “un-expected”.
I read to image with my Plextor 4012A (FW 1.01) using the Safedisc profile by G@M3FR3@K in this thread. I then burnt the image to a TDK 10x CDRW disc via my Lite-On 16102B (FW OSOK) again with the same Safedisc profile from G@M3FR3@K.
The resultant copy works from the Lite-On but doesnt work in my Plextor or my LG DVD-Rom. This has happend to me with CD’s burnt with my Plextor before but never with CD’s burnt in my Lite-On. Its early days at the moment as that was my first attempt at this game. I know about the success with DiscDump but im sure that if Clone CD can do it then its better for all of us.

Bulk, I assume you used the no-AWS profile and it’s interesting that you, at least, had a partial success.

I wonder if anyone has tried clonecd with FES completely off. That way, whilst the reading process would be slow, the image ought to be accurate enough to get a working copy (since there wouldn’t be any tricks used to speed up the process).

Given that discdump succeeds and, apparently, so too does discjuggler, why shouldn’t clonecd also succeed so long as FES isn’t used?

Originally posted by philamber
[B]
I wonder if anyone has tried clonecd with FES completely off. That way, whilst the reading process would be slow, the image ought to be accurate enough to get a working copy (since there wouldn’t be any tricks used to speed up the process).

Given that discdump succeeds and, apparently, so too does discjuggler, why shouldn’t clonecd also succeed so long as FES isn’t used? [/B]
FES “off”: VeNoM386 has talked about this on and off for a few years and I guess he still maintains that DJ is the best error reader soft app, too.

I’m not sure but maybe a CDRW disc is the way to go with CloneCD for the moment, both for new SecuROM and new SafeDisc2, given the success to date. I have about a dozen different speed and brand rewitables which I’ll try CloneCD + Unleashed on. Ugh. Shokin’ add-in but my 11 yo thinks it great.

Another thing bearing in mind is that at least one UT2003 success was from a backup anyway and I suppose, we’ll see the usual rash of successes that come from cracked .ISOs. I also suspect one Unleashed success with CloneCD was from a cracked .ISO as well.

I’m trying to move house but have completed my Unleashed tests with CCD v4 & 3 with no success on CD-R. I’ll try CD-RW next; then DiscJuggler. DiscDump still not working on my Win98SE :frowning:

Yes I used the no AWS profile. I also used Software error correction with the Plextor.

[CloneCD ReadPrefs]
ReadSubData=0
RegenerateData=0
ReadSubAudio=0
AbortOnReadError=0
FastErrorSkip=1
ReadSpeedData=0
ReadSpeedAudio=0
IntelligentBadSectorScan=0
SectorSkip=100
NoErrorReport=0
FirstSessionOnly=0
AudioQuality=0
[CloneCD WritePrefs]
DontRepairSubchannelData=0
AlwaysCloseLastSession=1
AmplifyWeak=0
WriteSpeed=0

Those are the settings.
Buffer underrun protection was enabled and I burnt in RAW DAO mode.

I 09:14:06 Read Speed for Data Tracks: Maximum
I 09:14:06 Read Speed for Audio Tracks: Maximum
I 09:14:06 Read SubChannel Data from Data Tracks: No
I 09:14:06 Read SubChannel Data from Audio Tracks: No
I 09:14:06 Fast Error Skip: Yes
I 09:14:06 Don’t report read errors: No
I 09:14:06 Intelligent Bad Sector Scanner: No
I 09:14:06 CD contains CD-Text: No
I 09:14:06 Reading Track 1… (Blocks 0-335411)
W 09:14:08 If you don’t expect read errors on this CD, disable “Fast Error Skip”!
W 09:14:08 Failed to read Sector 823
W 09:14:08 Failed to read Sector 824
W 09:14:08 Failed to read Sector 844
W 09:14:08 Failed to read Sector 869
W 09:14:08 Failed to read Sector 890
W 09:14:08 Failed to read Sector 910
W 09:14:08 Failed to read Sector 915…

W 09:14:17 Failed to read Sector 10037
W 09:14:17 Failed to read Sector 10057
I 09:18:46 Duration of operation: 00:04:40
I 09:18:46 Average Speed: 2811 kBytes/s (15.97)
I 09:18:46 Reading finished!

This is the burner log file.

I 09:23:52 Starting copy from C:\Images\Sims Unleashed.ccd to LITE-ON LTR-16102B
I 09:23:52 Write Speed: Maximum
I 09:23:52 Don’t repair SubChannel Data: No
I 09:23:52 Amplify weak sectors: No
I 09:23:52 Write Simulation: No
I 09:23:52 Buffer Underrun Protection: Yes
I 09:23:53 Writing Session 1 LeadIn…
I 09:24:21 Writing Session 1 image file…
I 09:31:48 Writing Session 1 LeadOut…
I 09:31:54 Flushing buffers…
I 09:31:54 Duration of operation: 00:08:01
I 09:31:54 Average Speed: 1721 kBytes/s (9.78)
I 09:31:56 Writing finished!

I still havnt had a chance to burn with the Plex yet.

i have the sims unleashed and i made i working copy with ClonyXXL and cloneCD…and for people who want to use just the image u need to use deamon tool latest version…also for the second cd just use the same clone setting as cd 1.

I tried Total Club Manager 2003 (Safedisc v2.80.010) and it doesnt partially work like my Sims Unleashed. When I run from my Lite-On i Get the error message to insert the correct CD but when I play from my Plex or my LG DVD-Rom no such error message occurs.
I had some wierd bad sectos at the ned of the disc which I cant explain.
Here is the log.

I 22:00:40 Starting copy from PLEXTOR CD-R PX-W4012A to C:\Images\TCM.ccd
I 22:00:40 Read Speed for Data Tracks: Maximum
I 22:00:40 Read Speed for Audio Tracks: Maximum
I 22:00:40 Read SubChannel Data from Data Tracks: No
I 22:00:40 Read SubChannel Data from Audio Tracks: No
I 22:00:40 Fast Error Skip: Yes
I 22:00:40 Don’t report read errors: No
I 22:00:40 Intelligent Bad Sector Scanner: No
I 22:00:40 CD contains CD-Text: No
I 22:00:40 Reading Track 1… (Blocks 0-343517)
W 22:00:42 If you don’t expect read errors on this CD, disable “Fast Error Skip”!
W 22:00:42 Failed to read Sector 1205
W 22:00:42 Failed to read Sector 1221
W 22:00:42 Failed to read Sector 1222
W 22:00:42 Failed to read Sector 1234
W 22:00:42 Failed to read Sector 1259
W 22:00:42 Failed to read Sector 1297
W 22:00:42 Failed to read Sector 1300…
…W 22:00:49 Failed to read Sector 8999
W 22:00:49 Failed to read Sector 9011
W 22:00:49 Failed to read Sector 9027
W 22:00:49 Failed to read Sector 9036
W 22:00:49 Failed to read Sector 9048
W 22:00:49 Failed to read Sector 9061
W 22:00:49 Failed to read Sector 9073
W 22:00:49 Failed to read Sector 9089
W 22:00:49 Failed to read Sector 9090
W 22:00:49 Failed to read Sector 9118
W 22:00:49 Failed to read Sector 9143
W 22:00:49 Failed to read Sector 9152
W 22:00:49 Failed to read Sector 9159
W 22:00:49 Failed to read Sector 9180
W 22:00:49 Failed to read Sector 9205
W 22:00:49 Failed to read Sector 9228
W 22:00:49 Failed to read Sector 9253
W 22:00:49 Failed to read Sector 9265
W 22:00:49 Failed to read Sector 9266
W 22:00:49 Failed to read Sector 9282
W 22:00:49 Failed to read Sector 9307
W 22:00:49 Failed to read Sector 9310
W 22:00:49 Failed to read Sector 9335
W 22:00:49 Failed to read Sector 9344
W 22:00:49 Failed to read Sector 9369
W 22:00:49 Failed to read Sector 9372
W 22:00:49 Failed to read Sector 9397
W 22:00:49 Failed to read Sector 9413
W 22:00:49 Failed to read Sector 9414
W 22:00:49 Failed to read Sector 9426
W 22:00:49 Failed to read Sector 9451
W 22:00:49 Failed to read Sector 9489
W 22:00:49 Failed to read Sector 9492
W 22:00:49 Failed to read Sector 9517
W 22:00:49 Failed to read Sector 9530
W 22:00:49 Failed to read Sector 9546
W 22:00:49 Failed to read Sector 9559
W 22:00:49 Failed to read Sector 9571
W 22:00:49 Failed to read Sector 9592
W 22:00:49 Failed to read Sector 9608
W 22:00:49 Failed to read Sector 9633
W 22:00:49 Failed to read Sector 9662
W 22:00:49 Failed to read Sector 9678
W 22:00:49 Failed to read Sector 9703
W 22:00:49 Failed to read Sector 9715
W 22:00:49 Failed to read Sector 9724
W 22:00:49 Failed to read Sector 9728
W 22:00:49 Failed to read Sector 9741
W 22:00:49 Failed to read Sector 9753
W 22:00:49 Failed to read Sector 9782
W 22:00:49 Failed to read Sector 9798
W 22:00:49 Failed to read Sector 9823
W 22:00:50 Failed to read Sector 9844
W 22:00:50 Failed to read Sector 9860
W 22:00:50 Failed to read Sector 9885
W 22:00:50 Failed to read Sector 9897
W 22:00:50 Failed to read Sector 9898
W 22:00:50 Failed to read Sector 9939
W 22:00:50 Failed to read Sector 9960
W 22:00:50 Failed to read Sector 9967
W 22:00:50 Failed to read Sector 10005
W 22:00:50 Failed to read Sector 10018
W 22:00:50 Failed to read Sector 10043
W 22:00:50 Failed to read Sector 10046
W 22:00:50 Failed to read Sector 10059
W 22:00:50 Failed to read Sector 10080
W 22:00:50 Failed to read Sector 10087
W 22:00:50 Failed to read Sector 10108
W 22:00:50 Failed to read Sector 10121
W 22:00:50 Failed to read Sector 10149
W 22:00:50 Failed to read Sector 10150
W 22:00:50 Failed to read Sector 10162
W 22:00:50 Failed to read Sector 10178
W 22:00:50 Failed to read Sector 10191
W 22:00:50 Failed to read Sector 10203
W 22:00:50 Failed to read Sector 10224
W 22:00:50 Failed to read Sector 10251
W 22:00:50 Failed to read Sector 10272
W 22:00:50 Failed to read Sector 10297
W 22:00:50 Failed to read Sector 10300
W 22:00:50 Failed to read Sector 10313
W 22:00:50 Failed to read Sector 10342
W 22:00:50 Failed to read Sector 10354
W 22:00:50 Failed to read Sector 10367
W 22:00:50 Failed to read Sector 10383
W 22:00:50 Failed to read Sector 10395
W 22:00:50 Failed to read Sector 10404
W 22:00:50 Failed to read Sector 10416
W 22:00:50 Failed to read Sector 10429
W 22:00:50 Failed to read Sector 10445
W 22:00:50 Failed to read Sector 10457
W 22:00:50 Failed to read Sector 10458
W 22:00:50 Failed to read Sector 10486
W 22:00:50 Failed to read Sector 10503
W 22:00:50 Failed to read Sector 10524
W 22:00:50 Failed to read Sector 10536
W 22:00:50 Failed to read Sector 10549
W 22:00:50 Failed to read Sector 10565
W 22:00:50 Failed to read Sector 10577
W 22:00:50 Failed to read Sector 10578
W 22:00:50 Failed to read Sector 10603
W 22:00:50 Failed to read Sector 10606
W 22:00:50 Failed to read Sector 10640
W 22:00:50 Failed to read Sector 10647
W 22:00:50 Failed to read Sector 10668
W 22:00:50 Failed to read Sector 10709
W 22:00:50 Failed to read Sector 10710
W 22:00:50 Failed to read Sector 10722
W 22:00:50 Failed to read Sector 10747
W 22:00:50 Failed to read Sector 10760
W 22:00:50 Failed to read Sector 10767
W 22:05:13 Failed to read Sector 326402
W 22:05:14 Failed to read Sector 326708
W 22:05:14 Failed to read Sector 326709
W 22:05:14 Failed to read Sector 327322
W 22:05:14 Failed to read Sector 327323
W 22:05:14 Failed to read Sector 327388
W 22:05:14 Failed to read Sector 327476
W 22:05:14 Failed to read Sector 327497
W 22:05:14 Failed to read Sector 327585
W 22:05:14 Failed to read Sector 327586
W 22:05:14 Failed to read Sector 327651
W 22:05:14 Failed to read Sector 327652
W 22:05:14 Failed to read Sector 327673
W 22:05:14 Failed to read Sector 327674
W 22:05:14 Failed to read Sector 327849
W 22:05:15 Failed to read Sector 327915
W 22:05:15 Failed to read Sector 327936
W 22:05:15 Failed to read Sector 327937
W 22:05:15 Failed to read Sector 327958
W 22:05:15 Failed to read Sector 327959
W 22:05:15 Failed to read Sector 327980
W 22:05:15 Failed to read Sector 328025
W 22:05:15 Failed to read Sector 328068
W 22:05:15 Failed to read Sector 328069
W 22:05:15 Failed to read Sector 328112
W 22:05:15 Failed to read Sector 328113
W 22:05:15 Failed to read Sector 328156
W 22:05:15 Failed to read Sector 328157
W 22:05:15 Failed to read Sector 328178
W 22:05:15 Failed to read Sector 328200
W 22:05:15 Failed to read Sector 328222
W 22:05:15 Failed to read Sector 328288
W 22:05:15 Failed to read Sector 328289
W 22:05:15 Failed to read Sector 328310
W 22:05:15 Failed to read Sector 328332
W 22:05:15 Failed to read Sector 328354
W 22:05:15 Failed to read Sector 328376
W 22:05:15 Failed to read Sector 328420
W 22:05:15 Failed to read Sector 328441
W 22:05:15 Failed to read Sector 328485
W 22:05:15 Failed to read Sector 328486
W 22:05:15 Failed to read Sector 328507
W 22:05:15 Failed to read Sector 328529
W 22:05:15 Failed to read Sector 328530
W 22:05:15 Failed to read Sector 328574
W 22:05:15 Failed to read Sector 328595
W 22:05:15 Failed to read Sector 328596
W 22:05:15 Failed to read Sector 328617
W 22:05:15 Failed to read Sector 328618
W 22:05:16 Failed to read Sector 328661
W 22:05:16 Failed to read Sector 328683
W 22:05:16 Failed to read Sector 328684
W 22:05:16 Failed to read Sector 328705
W 22:05:16 Failed to read Sector 328706
W 22:05:16 Failed to read Sector 328707
W 22:05:16 Failed to read Sector 328727
W 22:05:16 Failed to read Sector 328728
W 22:05:16 Failed to read Sector 328749
W 22:05:16 Failed to read Sector 328771
W 22:05:16 Failed to read Sector 328815
W 22:05:16 Failed to read Sector 328816
W 22:05:16 Failed to read Sector 328837
W 22:05:16 Failed to read Sector 328838
W 22:05:16 Failed to read Sector 328859
W 22:05:16 Failed to read Sector 328860
W 22:05:16 Failed to read Sector 328881
W 22:05:16 Failed to read Sector 328882
W 22:05:16 Failed to read Sector 328925
W 22:05:16 Failed to read Sector 328926
W 22:05:16 Failed to read Sector 328947
W 22:05:16 Failed to read Sector 328948
W 22:05:16 Failed to read Sector 328949
W 22:05:16 Failed to read Sector 328969
W 22:05:16 Failed to read Sector 328970
W 22:05:16 Failed to read Sector 328991
W 22:05:16 Failed to read Sector 329013
W 22:05:16 Failed to read Sector 329014
W 22:05:16 Failed to read Sector 329035
W 22:05:16 Failed to read Sector 329036
W 22:05:16 Failed to read Sector 329057
W 22:05:16 Failed to read Sector 329058
W 22:05:16 Failed to read Sector 329079
W 22:05:16 Failed to read Sector 329080
W 22:05:16 Failed to read Sector 329101
W 22:05:16 Failed to read Sector 329102
W 22:05:17 Failed to read Sector 329123
W 22:05:17 Failed to read Sector 329124
W 22:05:17 Failed to read Sector 329145
W 22:05:17 Failed to read Sector 329167
W 22:05:17 Failed to read Sector 329168
W 22:05:17 Failed to read Sector 329189
W 22:05:17 Failed to read Sector 329190
W 22:05:17 Failed to read Sector 329211
W 22:05:17 Failed to read Sector 329212
W 22:05:17 Failed to read Sector 329233
W 22:05:17 Failed to read Sector 329234
W 22:05:17 Failed to read Sector 329255
W 22:05:17 Failed to read Sector 329277
W 22:05:17 Failed to read Sector 329278
W 22:05:17 Failed to read Sector 329299
W 22:05:17 Failed to read Sector 329300
W 22:05:17 Failed to read Sector 329321
W 22:05:17 Failed to read Sector 329322
W 22:05:17 Failed to read Sector 329323
W 22:05:17 Failed to read Sector 329343
W 22:05:17 Failed to read Sector 329344
W 22:05:17 Failed to read Sector 329365
W 22:05:17 Failed to read Sector 329366
W 22:05:17 Failed to read Sector 329387
W 22:05:17 Failed to read Sector 329388
W 22:05:17 Failed to read Sector 329409
W 22:05:17 Failed to read Sector 329410
W 22:05:17 Failed to read Sector 329431
W 22:05:17 Failed to read Sector 329453
W 22:05:17 Failed to read Sector 329454
W 22:05:17 Failed to read Sector 329475
W 22:05:17 Failed to read Sector 329476
W 22:05:17 Failed to read Sector 329477
W 22:05:17 Failed to read Sector 329497
W 22:05:17 Failed to read Sector 329498
W 22:05:18 Failed to read Sector 329519
W 22:05:18 Failed to read Sector 329520
W 22:05:18 Failed to read Sector 329521
W 22:05:18 Failed to read Sector 329541
W 22:05:18 Failed to read Sector 329542
W 22:05:18 Failed to read Sector 329543
W 22:05:18 Failed to read Sector 329563
W 22:05:18 Failed to read Sector 329564
W 22:05:18 Failed to read Sector 329565
W 22:05:18 Failed to read Sector 329586
W 22:05:18 Failed to read Sector 329587
W 22:05:18 Failed to read Sector 329607
W 22:05:18 Failed to read Sector 329608
W 22:05:18 Failed to read Sector 329630
W 22:05:18 Failed to read Sector 329651
W 22:05:18 Failed to read Sector 329652
W 22:05:18 Failed to read Sector 329674
W 22:05:18 Failed to read Sector 329675
W 22:05:18 Failed to read Sector 329695
W 22:05:18 Failed to read Sector 329696
W 22:05:18 Failed to read Sector 329717
W 22:05:18 Failed to read Sector 329718
W 22:05:18 Failed to read Sector 329719
W 22:05:18 Failed to read Sector 329739
W 22:05:18 Failed to read Sector 329740
W 22:05:20 Failed to read Sector 330818
W 22:05:20 Failed to read Sector 330840
W 22:05:20 Failed to read Sector 330884
W 22:05:20 Failed to read Sector 330906
W 22:05:21 Failed to read Sector 331876
W 22:05:21 Failed to read Sector 331877
W 22:05:22 Failed to read Sector 331942
W 22:05:23 Failed to read Sector 332825
W 22:05:23 Failed to read Sector 332826
W 22:05:23 Failed to read Sector 332847
W 22:05:24 Failed to read Sector 333819
W 22:05:26 Failed to read Sector 334837
W 22:05:27 Failed to read Sector 335701
W 22:05:27 Failed to read Sector 335702
W 22:05:27 Failed to read Sector 335768
W 22:05:27 Failed to read Sector 335790
W 22:05:27 Failed to read Sector 335791
I 22:06:00 Duration of operation: 00:05:19
I 22:06:00 Average Speed: 2527 kBytes/s (14.36)
I 22:06:00 Reading finished!

I cant see any scratches or obvious anomolous markings.

Originally posted by philamber
I wonder if anyone has tried clonecd with FES completely off. That way, whilst the reading process would be slow, the image ought to be accurate enough to get a working copy (since there wouldn’t be any tricks used to speed up the process).

FES completly off didnt produce a working backup of Total Club Manager 2003. I guess its DiscDump for now and maybe Clone CD soon. :frowning:

Originally posted by saitoh183
i have the sims unleashed and i made i working copy with ClonyXXL and cloneCD…also for the second cd just use the same clone setting as cd 1.

Does Sims Unleashed have 1 disc or 2?

@ Bulk
The read errors at the end of the disc are most unusual. I’ve never heard of something like that previously with a safedisc cd. Does Sims Unleashed have something similar?

it’s 2 but the second disc doesn’t have any protection so u can just do a straight disc2disc

Bulk, you had an unusual amount of bad sectors. Safedisc usually doesn’t have that many, definitely not in the 300000+ range. Perhaps your disc is scratched? Am I correct or is the 300000+ range a part of Safedisc 2.8?

Originally posted by philamber
[B]
Does Sims Unleashed have 1 disc or 2?

@ Bulk
The read errors at the end of the disc are most unusual. I’ve never heard of something like that previously with a safedisc cd. Does Sims Unleashed have something similar? [/B]

Originally posted by CCDKing
Bulk, you had an unusual amount of bad sectors. Safedisc usually doesn’t have that many, definitely not in the 300000+ range. Perhaps your disc is scratched? Am I correct or is the 300000+ range a part of Safedisc 2.8?

Well the Sims Unleashed doesnt have these “bad sectors” as you can see from the log files previously in this thread. Im going to take this game back and exchange it for another one to see if I get the same results. Its wierd how Sims Unleashed works in the Lite-On yet I dont get the same results with TCM even though they are the same version of Safedisc. Whats slighty baffling is when I play the backup of TCM in the Lite-On I get an error message to insert the correct CD. I was expecting that, but when I play the backup in other drives the game just bombs out with no such error message.

Just do what Philamber does, use Discdump, and burn your image with Fireburner. However, I like to burn the image with CD Mate instead. Either works.

Originally posted by CCDKing
Just do what Philamber does, use Discdump, and burn your image with Fireburner. However, I like to burn the image with CD Mate instead. Either works.
Yes. I know that, that works, but I was trying to get Clone CD to work thats all. :slight_smile: It seems as though everything works except Clone CD. CD Mate works from scratch too but it takes longer for a read than Clone CD or DiscDump. I havnt yet tried Alcohol.

Originally posted by Bulk
I havnt yet tried Alcohol.

I wouldn’t bother. Word from reliable sources is that it doesn’t work with sd2.8x, or, at least, not with a Litey.

Originally posted by philamber

I wouldn’t bother. Word from reliable sources is that it doesn’t work with sd2.8x, or, at least, not with a Litey.

Ok. It is still worth a try though. :smiley:

Ok, I dumped an image using clone cd, standard Game CD Profile. It works perfectly in Daemon Tools 3.17. I tried to burn it to a disc using CloneCD Game CD Profile at both full speed (ASUS 1610A) 16x and half speed 8x. the splash screen apears when I run the game, and when it dissapears and would normally go into the game, I get an error message instead.

AppName: sims.exe AppVer: 1.7.0.0 ModName: ~df394b.tmp
ModVer: 0.0.0.0 Offset: 0004dfe2

That’s the Error that pops up in Windows XP. I’m assuming that the disc image is correct because I can use it in Daemon Tools. Is that not correct? And if it is correct, why doesn’t the burn work? (Reading it in a Pioneer 16x DVD-116) I also have a lite-on I haven’t tried yet, because it’s not a great reader, the ASUS is both a good reader and writer. Both the ASUS and Lite-on are reported to write correct EFM bit patterns. Anyone else seen this particular error? Any ideas what the problem is?

Originally posted by BlueJeans
[B]It works perfectly in Daemon Tools 3.17.

I get an error message instead.

AppName: sims.exe AppVer: 1.7.0.0 ModName: ~df394b.tmp
ModVer: 0.0.0.0 Offset: 0004dfe2 [/B]
“Works perfectly…” means that that if emulation is off (red icon) then the image is RAW. Get that right and the problem remains one of writing SD2 correctly.

The error message is the protection’s way of telling you that something’s not right in the backup :wink:

Ya, I know it’s supposed to be red, no emulation. It is, and in Daemon tools it works, so I guess I’m having problems writing the new SD2, ok, why am I having a problem writing it? I have a good writer, the ASUS 1610A and the Lite-ON 24x. I tried burning at 8x, no matter what it gives me that error. No ideas on why I’m having trouble burning a correct image?

I have the ASUS 16x, 40x & 48x. I have only got a working backup of Unleashed with the 48x using CloneCD. The SD2 is hard to defeat (unless you use DiscDump or DiscJuggler)

Originally posted by FutureProof
I have the ASUS 16x, 40x & 48x. I have only got a working backup of Unleashed with the 48x using CloneCD. The SD2 is hard to defeat (unless you use DiscDump or DiscJuggler)
Add CD Mate.