Jump to content


  • Posts

  • Joined

  • Last visited

beerslayer's Achievements


Newbie (1/14)

  1. More information: Apparently I did have a file whose total path name was over 107 characters. I tried renaming a couple of things and suddenly I was able to switch to ISO9660 successfully (I hope). There is still a problem in that the software does not correctly identify the problem, indicate which filename(s) it objects to, and give me a clear path to resolving the problem. "Internal SDK error" is not helpful.
  2. I've been using CDBurnerXP for years, and never had an unresolvable problem, until now. I'm trying to burn a bunch of .mp3 files onto a CD. The CD is rated for 700MB, and there are 685MB worth of files, so there should be plenty of room. Problem is that CDBurnerXP defaults to the UDF filesystem, which the stereo in my car will not recognize. Any disks burned using UDF are unreadable there. So I try to change the file system to ISO9660, since I know ISO9660 disks work fine. To do this, I go to Disc -> Change file system..., which brings up the dialog "File System Settings". In that dialog, I use the top dropdown menu to choose "ISO9660 / Joliet", at which point it lists two limitations: no files greater than 4GB, and no file/directory names longer than 107 chars. Well, I guarantee there are no files greater than 4GB (the total compilation size is 685MB, as I mentioned above). If there are any file names longer than 107 chars, I can't find them. At any rate, despite listing these limitations, the program allows me to click the OK button. When I do, however, I get an error reading, "The file system type cannot be changed, because of the following error: Internal SDK error:". (Notice that this error message ends in a colon, but nothing follows it.) I cannot dismiss the File System Settings dialog any way other than clicking Cancel or setting the file system back to UDF. If there is some file that is violating the rules, such as one with a name containing some other character that is not permitted, I expect that the software would notify me about it and suggest a change, but it doesn't. I just get this useless error message. I have no way that I can find to enforce the change to ISO9660, and as mentioned UDF is useless to me. (Is there a way to make it not be the default?) I hope this is an easily fixable bug. I'd hate to have to go find something else to do this relatively simple job.
  3. True, it wouldn't prevent the OC .dll from being extracted by the installer like all the other files. But that isn't what I suggested. What I would prefer is for the OpenCandy code to not be executed on my system. Extracting the file to a temporary folder is not an issue, so long as it is deleted with all the other temporary files extracted by the installer, and so long as none of the OpenCandy code is executed. Over-optioned? I don't think users would mind one more choice if it determines whether or not some extra program unrelated to CDBurnerXP is executed during installation. I also don't think people will object to whatever files might be extracted, so long as the code isn't executed. The OC-free installer might be a workaround, but it doesn't solve the problem of allowing users to make the choice while reducing your work load. I'd think it would be easier to maintain one installer with a choice built into it, rather than maintaining two separate installers. As for revenue, I can't argue that issue, other than to make the point that a reduced user base (due to fears (valid or not) about OpenCandy, and due to a reputation (valid or not) for including spyware as a result of including OpenCandy) might also reduce your revenue in the long run. Anyway, I hope you'll give this some more consideration.
  4. I sympathize with your desire to earn a little something for your work, Flo, but I have to admit I have my concerns about OpenCandy as well. It may or may not be perfectly safe. I don't know. Their privacy policy may or may not be honest. I don't know. But I would rather not put it on my system - that way I know that it's not having any effect. Maybe I'm paranoid. I don't know. But ultimately it's your choice and I wouldn't dream of taking that away from you. Without going into the question of what xyzware categories OpenCandy might or might not fit into, you ask: how can we make it more acceptable? My feeling is that rather than maintaining two separate installers (which will probably be a pain), perhaps it would be simpler to put an option screen in the installer that asks the user something like, "We have partnered with OpenCandy to offer you some special deals on other software. Would you be interested in seeing more about these deals?" or whatever seems fitting, and then on the same screen offer a checkbox "Yes, I'm interested" (which could even be pre-checked). If the user unchecks this box, then do not run ANY OpenCandy code during installation; otherwise run it normally. This would portray OpenCandy as potentially useful to those who might want it (and there might actually be some people out there who would find it useful), but would give those of us who don't want it some way to avoid it completely. Most people would probably just leave the box checked and click Next without bothering to read it anyway, just like they did with Gator/GAIN and Cydoor... At any rate, I've been using CDBurnerXP for years and I think it's a great piece of software. I hope this issue won't change that!
  5. I hope so! I love CDBurnerXP and would hate to have to start trying to find something else I can rely on instead, but this bug is obviously a show-stopper for me and makes the program pretty much useless for my needs. Is there any information I can provide that might help you track this problem down and fix it?
  6. Hi, I've been using CDBurnerXP for years and until today I've never had a problem that couldn't be resolved with it. But this one has me baffled. I'm running Vista SP1 on a fairly modern laptop with plenty of RAM, etc. This morning, I decided to upgrade my CDBXP from the 4.0.0.x (don't recall exactly what version I had) to the latest currently available, Upgrade seemed to go fine, without any problem. Next, I tried to assemble an audio CD exactly as I've done it many times before with the 4.0.0 version of CDBXP: I take the three fairly long .mp3 files (about 24-25 minutes and 3-4 MB each) and use Audacity to convert them to 44.1K bit rate. This results in three new .mp3 files of about 11-12 MB each. I then add these three new .mp3 files to an audio CD compilation and burn them onto a standard CD-R disc. Only, with the new version of CDBXP, this procedure results in three audio tracks of about 11-12 minutes each. Roughly half of the audio track is completely missing from the audio CD. CDBXP generates NO error message and claims to have completed successfully, and I didn't even notice the problem until I tried to play back the audio CD. Then I tried burning one again and noticed that only about 300MB of data was being written to the audio CD - there should have been about 600-650MB. The original (converted to 44.1K) .mp3 files are just fine, and play correctly to full length in any player I use them in, so I don't see how they can be part of the problem. This procedure used to work fine with the 4.0.0.x version of CDBXP, so I don't think it's a drive incompatibility either. Has anyone else had this problem? Any suggestions for workarounds?
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.