Jump to content

Tilman

Members
  • Content Count

    16
  • Joined

  • Last visited

About Tilman

  • Rank
    Member
  1. Just wanted to let you all know that version 4.5.7 solved my problem and the backup script works perfectly fine now. Thanks a lot! Tilman
  2. Thanks for the pointers to the preview versions and change log. Let me assure you I am aware of these. But I prefer to wait for a release, and just wanted to know when to expect it so that I can plan a bit ahead. Remember, this is about my father's system, not my own. As it happens, my father is twenty-five years older than myself (I am not exactly young, either) and lives about four hundred kilometers away. Not an environment you want to test preview versions in.
  3. Looking forward to the new version. Do you have an idea when it will be available?
  4. May I suggest that you read the "Before asking a question" article in this forum? Its very first item answers your question.
  5. "Trojan.Gen" means that Norton applied some heuristic to decide the file "looks like" malware, without positively identifying it as such. It's a frequent source of false positives. If you see a file flagged as such you should check it with VirusTotal so see if other scanners also consider it malicious.
  6. You may want to be a bit more specific with your claim. Which exact download are you referring to, what leads you to believe it would contain a virus, and which virus would that be?
  7. That's great. Thanks for your work! As for the blocking process, once you know which file is in use you can either guess which program is using it, or find out using Sysinternals Process Explorer. That's good enough for me.
  8. Well, I didn't say I'd want it to skip them silently. But I insist it would be much better to at least back up the files it can, instead of aborting the whole operation and leaving me with no backups at all as it does now. In the case I presented, it would be the perfect solution if cdbxpcmd wrote a line "file ou.lck in use - skipped" to standard error or a log file and burned the remaining files and folders. Nothing would be lost. There's no need to back up a lock file anyway. There are many similar cases where the file that's kept open can be reproduced easily and doesn't constitute a reason for aborting the whole operation. Using shadow copies would certainly be nice, but I fear that's asking too much from a CD burning tool.
  9. Pity. It would be a nice enhancement for cdbxpcmd to either skip specific files, or any files it cannot access (because they are held open by another process, because of lacking permissions, or for whatever other reason there may be). Absent that, although your suggestion of making a copy with robocopy is a good one, I guess the easier solution might be to stop the StarMoneyOnlineUpdate service in my script before the --burn-data command, and start it again after the burning is completed. That's of course assuming it is a proper service which can be controlled through the sc command. I'll have to check that.
  10. After another remote debugging session, the mystery is solved thanks to SysInternals Process Explorer. (Thanks to darkchamber for the suggestion.) The file "C:\ProgramData\StarMoney 10\profil\ou.lck" is being kept open by a process called StarMoneyOnlineUpdate.exe, apparently StarMoney's update service. Of course there's really no need to back up that file. It's a simple lock file of size 0. Is there a way to tell cdbxpcmd to skip that file and just burn everything else in the "profil" folder?
  11. You mean I should try adding the -format:iso option to the cdbxpcmd command line?
  12. The problematic folder belongs to a specific application, StarMoney. That application wasn't running when I did the tests, so I'm reasonably sure no running application was accessing any file in that folder. On Linux I'd just use the lsof command to verify. Are you aware of an equivalent command on Windows?
  13. Thanks for your suggestions. They helped me to narrow down the problem to a specific folder which cannot be burned. It's the StarMoney profile folder: -folder[\StarMoney]:"%ALLUSERSPROFILE%\StarMoney 9.0\profil" If I remove that argument from the list, the --burn-data command works fine. If I try to burn only this folder, the Internal SDK error message is triggered again. As my father recently upgraded to StarMoney 10 I also tested: -folder[\StarMoney]:"%ALLUSERSPROFILE%\StarMoney 10\profil" That triggered exactly the same error. However if I burn only the documents subfolder with: "-folder[\StarMoney]:%ALLUSERSPROFILE%\StarMoney 10\profil\document" it works fine. So there seems to be something in the profile folder outside the document subfolder which causes CDBurnerXP to choke. Any idea what that might be? I'm attaching a directory listing (dir /a /s) of the profile folder in case it provides a hint. I'm inclined to exclude permission problems as copying the same folder to a USB stick with robocopy works without a problem. Thanks, Tilman dir-profil.txt
  14. I'm afraid I don't quite get your point. Are you referring to files or folders belonging to or needed by the software, or to files or folders I'm trying to burn to the DVD? And what is StarBurn? Is it part of CDBurnerXP?
  15. The --list-drives command lists a single drive, with drive number 0. Here's the transcript: Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. Alle Rechte vorbehalten. C:\Users\Dietrich>set CDCmd="%ProgramFiles(x86)%\CDBurnerXP\cdbxpcmd.exe" C:\Users\Dietrich>%CDCmd% --list-drives 0: TSSTcorp CDDVDW SN-208AB (D:\) C:\Users\Dietrich> Consequently, I added the argument -device:0 to all the cdbxpcmd commands in my script. That didn't change the behaviour in any way. The --burn-data command still outputs: An error (80040275) occured while executing the command: Internal SDK error: Note that the --eject command works fine, with and without the -device:0 argument. It outputs: Ejecting disc... and the DVD tray opens. The --load command does not work either, but I expected that, as notebook drives cannot pull in their tray. That's why I commented it out in my script. Is there any way to get additional diagnostic output from cdxpcmd to find out what's going wrong?
×
×
  • 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.