I know this may be a little off topic since it's not directly audio-related, but I know a lot of you are using burnatonce for CD-R/W burning so I thought I'd post anyway.

Since finding bao, I have bee using it for audio and data CD-R/W burning, using the 0.97a version. Up to now I had no problems, until yesterday. I needed to copy some DivX movie files from one PC to another that were not networked, so I decided to burn the files onto CD-R for transfer. I produced two coasters in a row using bao, which has never happened before with this system. The files are single AVIs, about 701MB in size each time. The CD-R's are 700MB/80min. rated for 52x (Traxdata brand), and recording was done at the drives rated max speed, 24x.

The system is a P4 3.06/533, 1GB dual-channel DDR 266 RAM, Intel E7205 Granite Bay chipset (ASUS P4G8X dlx m/B), latest Intel chipset drivers and Aplication Accelerator installed, XP Pro / SP1 with all current updates, Plextor 24x10x40 as master on secondary IDE channel, along with Sony DVD-ROM as slave. All drives are configured for their highest DMA transfer mode. Buffer underrun is enabled in both bao and Nero, and Plextools Pro 2.05 is installed. Adaptec ASPI 4.60 is installed.

I've had this burner for about 18 months and rarely if ever has it produced coasters, even when it was used in a slightly slower 1.6GHz P4 / i845 system. I immediately switched to Nero 5.5.10.42, and burned the same files to CD-R without any problems. I know Nero buffered the entire file before burning, but I'm not sure if bao is doing the same thing, maybe this could have been the reason? Below is the log file from bao, from the start of the session and the end. Although bao says something about buffer underrun, I doubt it since the buffer shows 100% full right up until the error.

Any suggestions?

TIA,

Chris

***************************************************

Cdrdao version 1.1.7 - © Andreas Mueller <andreas@daneb.de>
SCSI interface library - © Joerg Schilling
Paranoia DAE library - © Monty

Using libscg version 'andreas-0.5-UNIXWARE_Patch'

1,0,0: PLEXTOR CD-R PX-W2410A Rev: 1.04
Using driver: Generic SCSI-3/MMC - Version 2.0 (options 0x0010)

Starting write at speed 24...
Process can be aborted with QUIT signal (usually CTRL-\).
Turning BURN-Proof on
Executing power calibration...
Power calibration successful.
Writing track 01 (mode MODE1/MODE1 )...
Wrote 1 of 796 MB (Buffer 100%).
Wrote 2 of 796 MB (Buffer 100%).
Wrote 3 of 796 MB (Buffer 100%).
Wrote 4 of 796 MB (Buffer 100%).
Wrote 5 of 796 MB (Buffer 100%).
Wrote 6 of 796 MB (Buffer 100%).
.
.
.
.
Wrote 784 of 796 MB (Buffer 100%).
Wrote 785 of 796 MB (Buffer 100%).
Wrote 786 of 796 MB (Buffer 100%).
Wrote 787 of 796 MB (Buffer 100%).
Wrote 788 of 796 MB (Buffer 100%).
Wrote 789 of 796 MB (Buffer 100%).
Wrote 790 of 796 MB (Buffer 100%).
Wrote 791 of 796 MB (Buffer 100%).
Wrote 792 of 796 MB (Buffer 100%).
Wrote 793 of 796 MB (Buffer 100%).
?: I/O error. : scsi sendcmd: retryable error
CDB: 2A 00 00 05 65 8D 00 00 17 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: F0 00 03 00 05 66 23 0A 00 00 00 00 0C 07
Sense Key: 0x3 Medium Error, Segment 0
Sense Code: 0x0C Qual 0x07 (write error - recovery needed) Fru 0x0
Sense flags: Blk 353827 (valid)
cmd finished after 0.011s timeout 180s
ERROR: Write data failed.
ERROR: Writing failed - buffer under run?
ERROR: Writing failed.
Writer Device unlocked successfully.

scsi input/output error, buffer underun & an 18 month old burner maybe without burnproof.

maybe you have to use a lower write speed

Nevertheless, copy & paste to Burnatonce support forum is also possible

edit: typos

when only the writer-buffer is used (don't know if bao spend you xtra HD-buffer) then it could be empty very fast by using 24 writing-speed and an ol' writer maybe with little buffer (ok, you got that nice Plextor-drive, which is equipped very good I think).
Like you suggest yourself use Nero to have your extra-buffer.

BTW we all know that my drivel mustn't be the real solution, maybe the error is anything else

This Plextor has 4MB buffer AND buffer under-run protection. I do not thinnk it is a hardware problem, but maybe a problem in the way bao handles sending data to the drive or in the way it reads data from the hd. The drive is not heavily used, it has only burned 200 or so CD's, so I would not consider it's age to be a factor. Besides, I have many older burners of lesser quality (IMHO) than Plextor that still work reliably even after 1000's of burned cd's.

I will re-post this to the bao forum.