LIGHTNING UK!

I guess none of the others issue it, or they fail silently. Just turn it off in the settings, no big deal. It's the 'Disable Media Change Notification' option.

I believe PIE's should be no higher than 280... (and that's very bad anyway). So you're well out of spec. Yes, ditch that disc and reburn it.

Your drive doesn't like burning to, and then reading back from those discs. It's a sure sign of a very low quality burn. Ditch them and buy some other discs. I very recently had to RMA one of my drives because that's all it ever kept saying. It had totally lost the will to burn, poor thing

Ok, the only way to make that cancel window appear is to click the 'stop' button when the program is doing something, or to close the main form (or have some other program try and close it) - i.e. via the top right cross (X thingy). So basically I'm guessing you'd finished a burn, clicked 'ok' to the 'completed successfully' box, and then immediately clicked the X. In doing that, you'd have actually closed (well, tried to) the program before all of the thread cleanup code had finished running. The program kinda remembers that you've clicked the X if it's busy doing something... it then normally checks if you have, once the lengthy operation has finished, and acts upon it if it has. I've jumbled a couple of lines around in the code to make this less likely to happen in the future. Still, you'd have to be super quick with the mouse to make it happen as it stands, I guess that's why you've not been able to reproduce it!

Hello everyone, nice to meet you

Thanks for the confirmation

I'd be interested to see a PIPO scan of that media if you have one handy! Just wondering if the 716 is anything like the 708 (I tested them with the 716 in the 'media' forum)

Hmm that's most odd then. The only thing I changed that could have caused this issue is the amount of data I read at a time from the hdd. As you're saying the 'Buffer' is always full, that means it's reading from the hdd just fine. The problem is then sending it to the burner. Just humour us and follow the DMA/slow burning related post in the FAQ. i.e. uninstall your ide controller and reboot. EDIT: ok, just looked at the IBG files, it's not a dma problem. 1.2.0.0 is burning fine and then it looks like plextors WOPC is kicking in - or something else is using the bus/channel and stopping it burning at full speed. You'll then notice it jumps back to 4x for the 2nd half of the disc, before then messing up again.

Which buffer is at 0% (or near it) when you burn?

It should delete if it's not used / called elsewhere in the queue. I will double check though... program logic became a little complicated in the end and I may have fixed one thing and broken something else.... i.e. this! Thanks Oh and once in the queue, the option you set in the queue is the one that gets used. i.e. when you add an image, it will auto check the delete box IF that settings one is checked. After that, the delete option in the settings is never looked at.

Oh well monteca820ce, I tried! Maybe your machine just doesn't support the command or something. It is valid and I couldn't improve it now if I tried! (It's very basic!)

Indeed, I do have FS/IFO parsing I guess... but it's much easier to treat the image as a whole rather than something made up of lots of little files! And as you said, doing it sector by sector, I can check non file/user data too.

You're spot on shamus ImgBurn 1.0.0.0 and all version of DVD Decrypter ONLY checked the physical disc for read error (by reading every sector). ImgBurn 1.1.0.0+ compares what's read from the media against the image file itself. So in order to get a proper byte by byte verify, you just need to leave the settings on their default values. i.e. 'Verify against image file' should be ticked. You're burning an ISO file, so that's what it's compared against. I do not deal with things on an 'individual file within image' level.

A bug to myself! lol BDS2006 exe's that are then compressed with UPX are crashing under this OS. I guess it would also effect 95 and possibly Windows Me. As ImgBurn.exe is compressed by UPX, you need to decompress it. You can get v1.25 from http://upx.sourceforge.net/ Extract the upx.exe to the same folder as ImgBurn.exe and run the following CLI. Upx -d ImgBurn.exe All will be well in the world once you've done that. The next release will not use UPX - I'll probably use PECompact instead (I've tested that and it works ok).

Ok, it's almost 1am but I've had a quick look around the code and I think I've now added all the extra 'if' statements I need to in order to properly check/allow for the /TESMODE cli switch. I'll do some proper testing in the morning.

Damn it! This is all due to where I'm acknowledging that testmode has been enabled via CLI. It's kicking in after the normal checks for media type etc because I didn't want the CLI parameter to actually change the checkbox in the main GUI. All boils down to a lack of testing in this area. CLI is not something I generally concern myself with - as I never use it!

No, there is no way to do a test and then a write. As for actually burning in test mode...well you are using DVD+R there and I'm sure you know the DVD+R format doesn't support the test/simulation feature However, it should have displayed an error to that effect... will have to check why you didn't get it! (if you're saying you didn't ?)

The layerbreak position ImgBurn has picked up looks ok to me. Ignore what scenarist is saying for the LBA... however it's doing its calculation, it's the same as ImgBurn's one. btw, the discs we buy are all OTP. No point building a PTP image.

Details, downloads etc on the main website. http://www.imgburn.com

Looks like your drive doesn't fully support those discs. Try updating your drives firmware to the 1.20 version, you're way behind. http://forum.rpc1.org/dl_firmware.php?download_id=1898

Well, as this program only deals with burning images, you tell whatever program you're using to output to an ISO and then burn that. Sorry but I (we) cannot help you with the 'ripping' part, you'll need to look elsewhere for that info.

Quite simple, you don't. ImgBurn burns images in the same way DVD Decrypter used to. Nothing more - well, apart from additional burning features of course.

LiteOn 8xx series... dunno, probably not!

Update your drives firmware with the PDS7 version. http://forum.rpc1.org/dl_firmware.php?download_id=1965

Because one is a DVDROM and the other is a writable disc. That's just the way it is.