potomac

Thanks for the feedback. I did hit F8 immediately on the first attempt, but it had to erase first (DVD-RW) and seemed to take an inordinate amount of time logging that part. So I did it again and tried to catch it at the point where it was actually writing data; that is, when the buffers would show something. I'm not going any further with it. ImgBurn does the burning perfectly so I see no need to haul the drive out and try it somewhere else just for a cosmetic issue. Besides they - the drive and ImgBurn - have to work together in this system, not some hypothetical alternative. At least the problem is flagged. If anyone else mentions it, remember you read it here first! All the best.

Well, your idea of ill-behaved and mine differ. Dropping or ignoring commands that should have been passed on...? And if they were 'just doing their job' what was the point of updating them? Anyway, enough of that, please find debug log attached as per instructions. Debug.log

Hmmm...they'd have to be ill behaved to do that. Anyway, I've updated the drivers and infs in line with your suggestion, but the problem still remains. It occurs to me on reflection that both progress bars are probably wrong. On other installations I've seen the ImgBurn buffer progress bar fluctuate as well as the device one. Here, we have the ImgBurn buffer at 100% the whole of the time and the device buffer at 0% the whole of the time. And it's clearly cosmetic as the underlying engine is doing a perfect job of burning discs. Thanks for your help and guidance, but I think it's a problem for the author now.

You have me confused. Why would the RAID0 controller/software affect the operation of the optical drive?

No worries. I'm not sure what info you need precisely so I've attached a couple of Everest reports that I hope will cover everything. Please let me know if I've misunderstood. Optical.txt MoBo.txt

The samples shown are DVDs (DVD-R and DVD-RW). I'm not sure if CDs would produce the same results; they presumably would, but I don't have any blanks to try right now.

The progress bar is enabled, but not showing anything but zero (see attached screenshot). Odd, isn't it?

Hi Thanks for the tip. The drive's firmware wasn't up to date, which surprised me as the machine is only a couple of months old. I've now installed the latest code, but the 'problem' still remains. 'Problem' isn't really the word I want as everything works perfectly, apart from the progress bar! My suspicion is that the drive, being relatively new, is not exposing its buffer parameters conventionally. Maybe the author will be able to confirm. I wonder if anyone else is using this drive with ImgBurn on a W7 system? Very strange.

I'm using a CH08LS10 drive (BD Read/DVD Read,Write) on a Windows 7 system. Everything works fine: the data looks good, the graphs look good and the finished discs work/play just fine. The only thing is that during the burning process the progress bar for the Device Buffer never moves; it stays at zero the whole time. The ImgBurn buffer on the other hand stays at 100%. Clearly I don't have a problem other than that of curiosity. But why does the device buffer indication not work, can't ImgBurn read it? ImgBurn.log

Ah, I see. Forgive my confusion; I hadn't associated 'build' with 'write'. I suppose another way of doing it would be to put up this prompt before the 'do-you-want-to-erase' query. That way you'd still have the benefit of the warning, but without any interruptions while you grabbed a coffee. Thanks again, though. 'preciate it. -P

This one (see attachment). -P

Hi Well, the good news is that 2.4.3 has indeed fixed my problem with certain MP3s, in this case Diana Krall's "Quiet Nights". So I'm very pleased. On another note, just before a burn begins ImgBurn pops up a confirmatory dialog. There's been a number of occasions when I've been using rewritables, that I've given the go-ahead to erase existing content and then walked away. When I've got back instead of a finished disc I've found this confirmatory thing sitting there waiting for me. Is there a checkbox anywhere to turn it off? I've looked, but can't see anything that might apply. It would be handy to be able to do this, otherwise I have to hang around waiting until the disc has been erased so that I can click OK and confirm the burn. Thanks again for your help -P

Am I going on a long journey, too?

Hi I have the problem mentioned elsewhere in these forums, where an audio burn using MP3 files as the source is aborted with an EOF read error. I note that this problem is apparently fixed in 2.4.3, which I assume is beta. Nevertheless, is there any way I can get a copy of the fixed version and so save myself the trouble of having to install another type of burning software? Thanks -P