Jump to content


  • Content Count

  • Joined

  • Last visited

About darkchamber

  • Rank
  1. I agree with Tilman. This is great news and definitely a huge improvement for everybody, who is using the command line API of CDBurnerXP. Thanx so much for listening to our feedback and implementing this changed behavior.
  2. That would be great. Could you also print the name of the process, which locks the files? Or more importantly: skip these files and burn all the other files? Thanx for your great work!
  3. I fully agree with you, Tilman. I also found it extremely annoying that CDBurnerXP wouldn't burn anything in that case. Even worse: it doesn't tell you, why. It could at least print a list of locked files in such situations. That would have been very helpful for tracking down the issue.
  4. I wouldn't want it to skip all files it cannot access and store on CD/DVD. This would finally mean that an unknown number of files wouldn't be backed up without my knowledge. Of course there could be some specific error code and error/warning output with a lost of files that haven't been stored to the medium, but that would still be a mediocre solution to the problem. The main question would be to have CDBurnerXP access the shadow copies of such files on Windows. This would allow it to read the files even if they are opened in another program.
  5. Good to see that you was able to find out about the culprit using Process Explorer. I'm afraid there is no command line option available for CDBurnerXP to exclude individual files. What I would probably do is copying the folder to another location before calling CDBurnerXP. Using the command line tool Robocopy for that would allow you to exclude files easily. Then you could burn the copied folder and specify the desired location in the CD's folder hierarchy. It's a workaround, but it would help you getting the result you are looking for.
  6. You could use the "Process Explorer" by SysInternals. It features a search function (look out for a toolbar button with a spy glass), where you can enter a fragment of a file name (or directory name I think) and it will show you all matching processes. That might help... It's a pity that CDBurnerXP doesn't provide more information about such error conditions.
  7. I receive this same error, when any of the files in that directory is opened in another application. Try to make sure that no running application is accessing any file in any of the directories you have specified on the command line for burning with CDBurnerXP's command line interface. Let us know, if that solves the problem.
  8. Hi, Thank you for getting investigating this issue. The insteresting thing is that when I select the ISO/Joliet file system for the DVD+RW the DVD gets finalized. That somehow contradicts the statement you posted before, right? After all a DVD+RW could never be finalized, no matter which file system is used - UDF or Joliet. But this is not the case. Even if a UDF DVD+R or DVD-R would be finalized, this wouldn't help in my use case. My goal is burning a DVD with the most important files every other week. Having 3 disks and overwriting each of them after 3 rotations. Using non-rewritable DVDs would mean producing a lot of DVDs with confidential data that would need to be recycled/disposed after a short time. What do you think about the fact that Joliet formatted DVD+RWs can be finalized as it seems, but UDF formatted ones can't? Do you have any other idea, how I could workaround this limitation? I mean, Joliet works, but I had to adjust (shorten) a lot of pathes to meet the path length limitations of the Joliet format and I need to check that as new files are created in the directories I'm burning to the DVD+RWs. That's a bit nasty...
  9. Hi, I tried the new version. The result was the same. This is the disc info dialog after burning the DVD:
  10. Unfortunately it doesn't solve the problem. Is there anything I can do in terms of logging/tracing that would help you?
  11. Hi, does this preview version address the closing/finalizing issue in particular? In the meantime I found out that adding the option to use the ISO/Joliet file system instead of UDF also solved the problem. With this file system the disks are finalized. However I would love to use UDF, because Joliet comes with significant limitations regarding path and filename length.
  12. Hi, I tried that, but the option for finalizing the disk seems to be ignored - just like the name for the disk. See my post here: https://forum.cdburnerxp.se/topic/9898-command-line-burning-does-not-close-disk-and-name-is-not-set/. I would really appreciate, if anybody could tell me, if I'm doing anything wrong on that command, or if this is a bug in the software.
  13. Hi, you are right: without closing/finalising the disk it won't be accepted by regular playback devices. Even the operating system will probably say there is no content on the disk. If you open a CD/DVD burning program it will recognise the existing sessions and ask you, what to do: to ignore them or to keep them. You will want to finalize disks in order to use them on any other device.
  14. Hi there, I'm trying to automate the task of burning a few folders onto a DVD RW using CDBurnerXP's command line interface. The command looks like this: cdbxpcmd.exe --burn-data -device:1 -close -folder[\backup\fotos] :\temp\dvd-backup-test -speed:10 -name:backup -verify Burning works fine and also verification afterwards. But I cannot list the content of the disk. When I open CDBurnerXP's UI it tells me that the disk is not closed/finalized. I should choose to continue using the existing session or to ignore it. But since I used the -close option it should be closed. What's wrong here? Also the title/name of the DVD is empty / not set according to CDBurnerXP. However I specified the name "backup" in the command. Any help is highly appreciated. The DVD needs to be finalized in my scenario. Thanx & regards.
  • 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.