LIGHTNING UK!

Nope, max is max. It'll burn as quickly as the drive will let it. How are your buffers? Always at 100% or there-abouts? How is your plextor connected to the PC? IDE, USB, Firewire?

All I can say is that it's in testing! When we're happy it's at least semi bug free (I had to change a lot to get unicode working), it'll be released. Best I can offer right now is 'November' !

ImgBurn isn't really designed for burning to multiple drives and it would be a pretty big job to change that, sorry. I'm not saying it'll never happen, just that it won't be happening any time soon.

You've probably got hotlinking enabled on your hosting server - so you can't link to it on another website.

Sorry, no. This forum is for supporting ImgBurn, which is a burning tool and nothing to do with copying DVD's etc.

v2.1.0.0 only handles ansi characters I'm afraid. The next release supports unicode. It's unusual that a normal looking file name like that would fail though. Why isn't it just named using a minus sign in the first place?!

Naughty thing, glad you sorted it I just checked mine, I'm running 6.1 already! phew!

1.216?! Surely the average value can't be that high? Even when I use XP's search for files thing mine only goes as high as 1. If yours is at 1.216 all the time then that could explain things. Search google for 'Average Disk Queue Length' and see what Microsoft has to say about it. You might find some pointers on how to troubleshoot it. Maybe running chkdsk and defrag would be a good start.

Ok so it's easy to see some glitches in that file around the 1.3 GB mark but it's not exactly all over the place the entire time - which is what I was kinda expecting. I think this issue is just something you're going to have to fix yourself via some problem solving and a lot of trial and error. Something is happening that's preventing the program from reading enough data from the hdd to sustain a pretty measly 4x write speed. You just need to find out what that is Maybe take a look in perfmon.msc and see what your typical 'average disk queue length' is. You should be able to just watch the graph! At the moment mine is on 0.002.

In theory, BURN Proof should be far along enough now that a little 'bump' doesn't cause any issue at all. A PIPO/Disc Quality scan in DVDInfoPro/CD Speed should tell you one way or the other. To be honest, I'm not even sure if you can issue a 'set streaming' command in the middle of a write sequence, the drive would probably just reject it and say it's busy writing! Unless you've got a gigabit network I'd suggest you stick to 4x / 6x burning all the time anyway. At 8x, that's 8 x 1385 = 11,080 kb/s which I would say is totally maxing out a 100mbit one.

and yet your buffers are all over the place? It's ok for the device buffer to drop down now and then, most drives do that when they perform wopc stuff. The one just marked 'Buffer' however should NOT drop off below maximum. Yours must be or the buffer recovery thing would never kick in. Do you have DVDInfoPro downloaded / installed? ImgBurn produces these little 'IBG' files which you can open/display in DVDInfoPro. It shows buffer usage, cpu usage, write speed, verify speed etc all on pretty graphs. If you could show us one of those from you burning it might help. If you don't auto export imgburn graph data the easiest way to show it in dvdinfopro is to click the little disc + information speech bubble just below the 'destination' box on the front screen. Or you can click 'File' -> 'Display Graph Data using DVDInfoPro'.

The whole threshold level thing isn't really the problem here. You need to find out why your internal program buffer and device buffer is falling right down low so that it triggers the buffer recovery - which is where the threshold level comes into play. What's happening on your PC that's so stressful it can't read from the HDD and burn at 4x?! Or did you change the buffer size to 1MB or something? Do you have any free RAM or are you always working in the swapfile virtual memory?

You could probably just go by the information panel once you've clicked 'Calculate'. It shows you the number of folders / files that will be in the image. You could also mount the ISO in DAEMON Tools and view it like a normal drive via Explorer.

That '(Speeds: 4x)' bit means they're the speeds supported by the drive (with that firmware) on that media. So you only have your drive / firmware to blame I'm afraid. As blutach said though, don't use ANYTHING other than Verbatim DVD+R DL media.

You'll find somewhere selling Taiyo Yuden discs where that's the brand name, or you buy some using the TYG02 / TYG03 / YUDEN000-T02-00 / YUDEN000-T03-00 dyes. i.e. Verbatim / Plextor / Panasonic. If you buy them online you should be able to see the media id codes on the website. Most decent sites list them.

I suspect your AV prog is just giving you a false positive on something in the NSIS installer. They're always having that problem the poor guys! Do you ever update your AV? My Symantec program complained about the NSIS installer a few months back but then they fixed their defintions and the problem went away. If you download it from http://www.imgburn.com/ you will be virus free.

I've no idea what the difference is, sorry! Can I ask, have you tried actually burning something and playing it? i.e. Do you know for a fact that it doesn't already work? What exactly are you burning? AVI's or DVD Video?

Windows always changes the drive name to CD Drive when you put a blank in. It's because it's empty and it doesn't understand blanks very well. So basically ignore explorer and just trust your burning programs to do their job. Even though you've burnt a few of them ok, they're probably really bad burns. There's a very fine line between not working and working very badly. You're hovering right over it.

Sorry to have to tell you this but you need to ditch the Prodisc junk media and get yourself some decent Verbatim (with the MCC dye) or Taiyo Yuden media.

The whole program actually supports unicode now, I've spent quite a lot of time on it You just need to wait for the next release (2.2.0.0) - and before you ask, I've no idea when that'll be

Sorry, I don't give dates if I can help it, I never meet them! It's not the end of the world if it veriifies against real data so I certainly won't be rushing the next release just for this

It's very rare for the entire program to lock up, most the code is done in thread - especially the burning stuff - so the GUI one should always be responsive. Did you have to terminate the process or something? Maybe even do a full reset of the comp?

I very much doubt the I/O error is anything to do with the layer break position. Post the log so we can see what's happening and what the exact error was.

In theory it shouldn't be possible to tick the delete option if test mode is enabled. There *might* be an issue if you do it via the CLI stuff though, I've not traced the code thoroughly enough to say either way. EDIT: Ok, no I really don't think it's possible at all! Which means the burn (+ any verify?) must be going ok. It then does as it's told and deletes the image. If you're not verifying your burns, now would be a good time to start!

Blu will help with this I'm sure, but you're probably better off asking in the IFO Editors forum at Doom9.org ! Out of interest, is that the only option you're given?