pokopiko,
> Hi, fordman...
> I am sorry
YES, you are!
> I did not know that your Red Alert version has non-interleaved
> subchannel data! I could beg you to tell us where you got it
> from, but I guess you want to keep your little secret.
OK, you continue to ratchet this up and I'm trying hard not to stoop to your level. I have concluded one of the following must be true:
1. You are clueless
2. English isn't your first language, which would explain why you couldn't read and understand what I wrote.
If number 1 is true, then I cannot help you. If number 2 is the case, then OK, I understand. I would have equal trouble with a language which is not my native language. But I would also VERY careful to understand what I was reading (try SYSTRANS or something) before throwing barbs.
If you read and UNDERSTAND my original message, my only reference to red alert was to mention that my 3.3.4.1 version worked fine copying that title, but failed on the bootable data CD that I downloaded. Gee, how did you get confused? Oh, I'm sorry, I didn't know YOU had a Red Alert 2 CD that was bootable!!! Can you tell me where you got THAT?
> I also did not know that you discovered the undercover NINTH
> subcode (the other eight subcodes are covered nicely in an old
> friend's article at _http://beam.to/telstar -you can get it from
> there if you want to check them and submit you new subcode...
> that is if you'll be able to pass his tricky javascript gimmicks! )
> which can affect/modify data put in a normal data track... BTW
> the up to now known eight subcodes cannot alter data stored
> in a normal track, no matter which the mode of the track is, or if
> the subchannel data are interleaved or not.
Look, my only point regarding subchannels (ON THE ERDCOMMANDER CD!) was that CloneCD writes a .ccd file, an .img file and a .SUB file, regardless of whether you tell it to read subchannel data or NOT, and a .cue file if you tell it to. CDRWIN uses the .cue and .img file ONLY, and does not refer to the .sub file when burning the image. I agree that the .img file is the same content whether CloneCD or CDRWIN burns it. So, why does CloneCD produce a CD on which a file/sector is inacessible while CDRWIN does not? Other than a bug in the logic of the program itself, what is different??? Well, the .ccd file has essentially the same purpose as a .cue file has for CDRWIN, but the .ccd file does have a lot more information it. Hmmmm, maybe some of that info is corrupt? OK, now what else is different? Oh yeah, there's a .sub file that CloneCD produces whether or not you tell it to read subchannel data. OK, do you propose that the .sub file is empty or not used when CloneCD writes to CD? Well, CloneCD complains if it's deleted, renamed, etc... So, since you're the subchannel code expert, PLEASE tell us what this file is used for with a plain old data CD, and explain why CloneCD needs this file if subchannel data is not used when writing the image.....Hmmmmmmmm?
> Also it would be nice if ytou somehow decided if your imaged
> clone thingy is Red Alert or ERDCommander...unless you're not
> quite sure which-is-what.
See above, READ carefully what I wrote....
> BTW an experienced Clone user that leaves AWS on by default,
> or leaves the "dont repair subchannel data" box on by default
> is rather an experienced coaster maker. And your habbit of
> converting all your cue/bin images to ISO is also a trademark of
> the default coaster maker- simply this does NOT work a lot of
> times, period.
No kidding. AGAIN READ what I wrote. I asked why Ollie would have AWS on by default in HIS default profile!!! I always had it turned off by default in CloneCD 3.3.4.1. I simply did not notice that he had it on by default in CloneCD 4, so that was the first thing I did when I found the CloneCD burned CD was corrupt. Clear enough!? I also explained that I tried other burners, and even another computer with CloneCD in demo mode, with the same results....Geez....
> So please, do me a favour, check the basics at cdrfaq.org,
> check too the article at Telstars' site to see why at hell your
> ninth subcode was left out (maybe on purpose, after an Oliver
> Kastl suggestion?!), after that PLEASE RECHECK YOUR CLONE
> SETTINGS (key included) and let us know on the
> developments...
See above. You were way off track with this. I never claimed to find a "ninth subcode." I think you may have an overactive imagination...
> Finally i don't use CloneCD as I have better stuff to use, but i
> would gladly post ways to reg it, and not only that one but also
> ultimate crap like Fireburner, Gear Pro and Hotburn. It's my
> bloody right to do so and I don't expect anyone (including you)
> to object... although I may exclude the program vendors, under
> some circumstances...
Look you were helpful enough to point me to the correct older keygen that still works for all CloneCD versions. Thank you again. My point was you had some nerve admonishing me for posting a thread about problems with a keygen enabled CloneCD when you used the keygen and reported it worked, and helped to point others to it. You are correct that it's your right to post info about how to reg the programs, and even though you didn't say so, it is also your perogative (though not your right) to use the keygen as you admitted you did. Just don't chide me for doing so! Also, you claimed that the keygen worked, and if it enables some CD corruption code as punishment in CloneCD, then that would be an indication that it does not work, which was the subject of your original thread on the keygen - i.e. does it work or not....
I don't want a "war" with you. I welcome intelligent discussion aimed at discovering the cause of this difference in how CloneCD and CDRWIN burned the ERDCommander CD. I was simply looking at the differences in the data files themselves as an answer....no more than that. Now that I've installed CloneCD on a clean (never had CloneCD on it) machine and achieved the same results, then I must conclude that it has something to do with a bug in CloneCD or a corruption in the data files that CloneCD uses that CDRWIN does not (.ccd/.sub).
If you'd like to be part of the investigation/solution, I invite you do download the image and burn it yourself. Then post whether you can access the diskeeper server installation .exe on the resulting CD. Burn with a program that handles .bin/.cue files and test that too, and post your results.
Above all else, try to treat people with respect. I am a 38 year old Chemical Engineer and I DO happen to have quite a bit of computer experience and am consulted regularly by coworkers and friends, build computers for friends, etc. I'm sure you are also experienced and competent, so let's not call that into question, eh?
Ford Man
