just wanted to know - I wondered why elby added the option to write the cuesheet as well when making the image file - perhaps now we can freelock our CloneCD images?

http://users.skynet.be/kingnero/leftstart/kn.jpg (http://users.skynet.be/kingnero)

ps new download: CloneCD Region Killer - enables the option to use AWS and Hide CDR media in CloneCD 4, even when registered in USA or Japan: check site

You don't need require those of what you say, but you already know it doesn't support it at all !

Ask the makers :laugh:

I think I don't completely get what you mean: At the CloneCD site, it said it added the feature of making cuesheets so other burning software could get along with the clone images, like nero and so.
Also D-tools needed that .cue so it could mount the image.
So i didn't think it was a dumb question (i didn't stated either you said so, i don't mean to offence no one), but why would you say ""but you already know it doesn't support it at all ! "" ???

and i know as well the principle of trial and error, just wanted to know some other opinions

perhaps some more opinions? I asked this elsewhere as well, but there they didn't seem to know for sure either.
the prob is in the fact that freelock alters the cuesheet, but not the actual image, and clone doesn't read the cue, so most probably it won't add the freelock data tracks?

pls correct me if i am wrong !!

well d-tools didnt need the .cue to use the image (it used the .ccd which is a cue sheet but is only compatable with clone [open one in notepad and you'll see what i mean])

anyway it would probably alow it to work with CDRWIN but you would not have the burining options like do not repair subchannel data, AWS, etc that clone CD has

I am pretty sure that the cue file is there so it workd with CDRWin, because the .img file of the clone cd file is basically the smae as a .bin file, so the cuesheet can tell cdrwin how to burn this file.

--As long as the image file doesn't include 96 bytes subchannel data,otherwise Cdrwin will give you a coaster (thanks to roadworker)

--now, d-tools supports the .ccd. one of the previous versions needed the cuesheet to mount the clonecd image

--The images made by cdrwin (.bin) and clone (.img) are the same. Both are RAW images which use 2352 bytes/sector

If I made any errors this far, correct me.
but the Q remains: will clone be able to add the freelock protection when it doesn't read the cuesheet?

i think that clone cd write Cdrwin image files now on the new version

bump - the Q still remains: will Clone write freelocked images? freelock works from within the cue, and does clonecd bases his writing on the cuesheet?

Clone CD only reads the CCD file when writing.

OK - that's what i wanted to hear ; means clone cannot write the freelock protection

BlindWrite can however write from CUE files.

AHA, this is interesting - I didn't know that - haven't used blindwrite, only the read app.
I'll give it a go -> Thx m8