LIGHTNING UK!

That is indeed odd! Not much goes on inside the main thread besides the drawing of stuff and so there should never be anything that takes AAAAAAAges to complete - before then allowing then next paint message to be processed. All the I/O stuff is done in threads (well, most of it).

Erm..... maybe

You want ImgTool Classic, not ImgTool Burn.

lol yeah, that's what's supposed to happen! The program appears to be working just fine. You put your disc in, select your image and then click on the big 'Write' button.

Unless Stomp doesn't check the image against the data, it should fail on both of the burnt discs. There is no reason for a disc burnt with ImgBurn to behave any differently to one burnt with DVD Decrypter. Maybe your image burnt with DVD Dec had already had all the bits removed and so AnyDVD isn't actually doing anything in the way of changing what the drive is reading.

I will probably try to add an option to just have it work like the old version (i.e. just check the sectors are readable, rather than comparing their content to that of the file). That way, if you're not fussed about comparing to the file, you won't need to mess with AnyDVD each time.

This would only be used for DVD-RW and DVD+RW. Clearly you can't format write once media! In such cases, ImgBurn isn't any use to you anyway. It prepares the disc for burning images, it doesn't format it so that it can accept files via programs that do 'drop to disc' type stuff.

The verification is only failing because AnyDVD is changing the contents of the sectors on the fly to remove things like PUO's etc. You don't need to disable it when you burn, just when you verify - but of course verify generally happens straight after burn so it's best to disable it over the entire process

It wouldn't even read back in the PC?! Forget about playing it for now, can't explorer even see the contents of the disc? Booktype stuff will help with standalone players but it shouldn't make any difference to a PC. Also, it might be an idea to enable the 'Verify' option for after the burn. At least then you'll know if the disc contains everything it should do and that it burnt correctly.

Hmm...where on earth did you get the idea you needed Administrative privileges from?!

Are you sure you don't have HDD (DMA) issues then? Your burner is on USB which rules DMA problems out for that one, but if the main buffer is up and down all the time, maybe your hdd isn't running as it should be. Quite simply, if the 'Buffer' goes up and down all the time, the program cannot read data from the HDD quickly enough. It should be on 100% (rock solid) all of the time.

Not useful to you perhaps but not everyone works how you do. You should be thankful it has any sort of queuing system, it is FREE remember! Adding support for multiple drives etc is something I'd already thought about and will probably be added in a future version.

The old version didn't compare against a file, it just checked the disc was readable. Could you please copy + the entire log. You don't need to burn the disc again or anything, just switch to Verify mode, put in your burnt disc and try again. Also note, a 3rd party background app could be changing the disc on the fly without you knowing - and hence what my program thinks it is reading from the drive is not actually what's on the disc.

I'm not a professional programmer I also don't use Microsoft tools for development. All the components in Borland tools make use of something called an AnsiString... and that (as you can tell from it's name), only supports Ansi characters. I don't believe there are WideString (Unicode) versions available at this time, perhaps in the next version of the development environment they will have addressed this issue. In the mean time, sorry!

If all the buffers in the program are behaving themselves (i.e. at 100%), the drives WOPC routines must be kicking in big time. oh do all programs look as messed up as that screenshot because you've changed the default windows font size? That would drive me nuts, I'd rather change resolution down a bit if I couldn't read the text properly!

Sorry, my mistake the font makes it look like a 0 (zero), not O Your firmware is ok, but I have seen a 47P9 floating around.

What's your CPU usage like during the burn? We must have burnt thousands of discs between 1.0.0.0 and 1.1.0.0 and all our graphs are perfect. Something tells me the program 'may' not be the problem. Try updating your firmware, yours seems VERY out of date. http://forum.rpc1.org/dl_firmware.php?download_id=2143

I've made no attempt to make anything support unicode... so it's quite possible it doesn't work! Do you have a small image (i.e. 5mb - or can you please make one?) so that I can see what you mean and try to fix it. Thanks.

Use PgcEdit to create the image and burn. ImgTool Classic is great, but it won't work properly for double layer images.

or better still.... PgcEdit because it can deal with double layer discs properly too

Excellent news

Sorry, it can't. The IFO would have to be made bigger, which of course means the ISO would have to be rebuilt.

Just load the image, it should automatically pick up the LB info. Double check this theory by right clicking on the 'Sectors' value once you've loaded the image and displaying IFO layer break information. (or via Tools -> ISO -> Display IFO Layer Break Information)

Hmmm raining much?! and to think I quite fancied a trip over to Oz for a bit of sun!

I'm nice to people that listen. Others get my back up and then I'm a bit rude, sorry. 30 posts later in the thread and you're still getting 'Write Errors'. Those messages come direct from the drive. You can't write a disc in any other way, so different software doesn't even come into it. Read the MMC specs from www.t10.org if you want to know more. You'll see there are 3 commands to write data to a disc. Write (6), Write (10) and Write (12). They're all just variations of each other. You'll notice from the I/O Error box that I happen to use Write (10). That's the most widely used/accepted one. I send a Write (10) command to your drive, providing some data to write, it's coming back saying it CANT write to the media. I'm amazed there is actually ever any room for discussion on this type of problem. You could buy some TY discs to try, that's about the best CD media you can get and probably your best chance of draining the last bit of life from your CDRW.