Verification and nerocmd

vbimport

#1

We’ve been using nerocmd in an automated image backup system. I just found out yesterday that the exitcode can be 0 (EXITCODE_OK) and a log file containing “OK” is created even if verification fails. Ouch. We’ve had 41 sporatic failures in the past two months, after working flawlessly for over a year (which is why nobody thought to double check the log files).

Is there an “official” way to determine if the verify phase fails?
Is this a bug, or a feature? :wink:
Barring that, is there a way to determine – or specify – the name of the neroerrxxx.txt file that’s created? (So the burner program can examine it, looking for trouble.)

TIA

Here are excerpts from relevant log files.

This is a successful run:
#############################
8591.log (our log file)

          -- Calling external burner program...
          -- NERO: Creating parameter file.
          -- NERO: Calling nerocmd.exe with "C:\Program Files\FpiBurnCd

erocmd.exe" “@C:\Program Files\FpiBurnCd\Log\8591.par”
25Apr05 05:53 – NERO: back with condition code 0
– External burner exited sucessfully.
[NOTE: above line also means “Nero_8589.log” contains “Ok”]
#############################
8591.par (nerocmd parameter file)

–write
–tao
–real
–verify
–nero_log_timestamp
–drivename D
–error_log “C:\Program Files\FpiBurnCd\Log\Nero_8591.log”
–iso 8591 “g:\Working\8591.ready”
#############################
Nero_8591.log

Ok.
#############################
neroerr20050425055322.txt

5:53:16 AM #25 Text 0 File UDFCompilationImpl.cpp, Line 1347
5:53:16 AM #26 Phase 80 File APIProgress.cpp, Line 235
Data verification completed successfully
#############################

This is an unsuccessful run:
#############################
8589.log (our logfile)

          -- Calling external burner program...
          -- NERO: Creating parameter file.
          -- NERO: Calling nerocmd.exe with "C:\Program Files\FpiBurnCd

erocmd.exe" “@C:\Program Files\FpiBurnCd\Log\8589.par”
25Apr05 05:25 – NERO: back with condition code 0
– External burner exited sucessfully.
[NOTE: above line also means “Nero_8589.log” contains “Ok”]
#############################
8589.par (nerocmd parameter file)

–write
–tao
–real
–verify
–nero_log_timestamp
–drivename D
–error_log “C:\Program Files\FpiBurnCd\Log\Nero_8589.log”
–iso 8589 “g:\Working\8589.ready”
#############################
Nero_8589.log

Ok.
#############################
neroerr20050425054314.txt

5:40:08 AM #29 VERIFYERR 6 File UDFCompilationImpl.cpp, Line 1646
Read error on CD file
8590.ready\B26-842.011.DCR
5:40:16 AM #30 VERIFYERR 6 File UDFCompilationImpl.cpp, Line 1646
Read error on CD file
8590.ready\B26-842.012.DCR
[snip --read errors on 18 files out of 91 files]
5:43:09 AM #55 VERIFYERR 13 File UDFCompilationImpl.cpp, Line 1345
Status summary
5:43:09 AM #56 Phase 81 File APIProgress.cpp, Line 235
Data verification failed
#############################


#2

That’s true, verification errors are not considered as burn errors in NeroAPI. Untill now. In the next web release of Nero this will be changed, so NeroCMD will report burn failure also if only verification failed.
You can only force NeroCMD to add year,month,day,hour,minute and seconds to neroerr.txt file by --nero_log_timestamp command line parameter, but you are not able to change the location or set user defined name to it.
Additionally, if --error_log <log filename> parameter is set, NeroCMD will write burn errors or ‘OK’ on success into specified file, where your application can look up the result.


#3

“… if --error_log parameter is set, NeroCMD will write burn errors or ‘OK’ on success into specified file…”

The problem is, --error_log IS set (see the listing, above), but Nero only writes ‘OK’, even if there were errors.

Ok, it’s a “feature”.

Maybe now the boss will let me give up on this clunky interface on Windows go back to writing CD’s directly from a bash script.