LIGHTNING UK!

That's not how it works. ImgBurn doesn't have to deal with the size of things when closing the disc, the drive does. So your drive hasn't burnt/finalised the disc correctly.... which is to be expected I guess as we already know it failed to burn it and forced you to reboot when it was meant to be finialising the disc, rather than completing nicely and returning control to the program. I'd be amazed if you could actually read 20+ GB off that disc. I'd expect your drive to error our the second you try to read beyond the last LBA - which is 5898559 according to it (and therefore ~11 - 12GiB of data).

Just to explain that, it's due to the entire log from the most recent instance of ImgBurn being saved at the top of the file (but still with individual lines in oldest to newest order), rather than the bottom. I'd need to just be able to append to it so as to avoid writing out the entire file to the disc each time a line gets added.

The only way that would work is if it saved to a secondary log file. The layout of the current one doesn’t lend itself to writing line by line.

This is a support issue, so I've moved it to the appropriate forum. If you go into Read mode and put that disc in the drive, maybe something from the Disc Info box on the right will explain why DVDInfoPro is listing the size as it is.

It saves the contents of the log window to the file when it's closed down. So you'd only lose it by terminating the process in task manager or wherever.

Post the disc info of that disc when you’re in Read mode please.

Are they compressed in zip/rar format or similar? Extract them so you actually have an ISO image file and then burn it in Write mode.

The two are completely different. 'Create image file from files/folders' does exactly what it says it'll do. It takes a random bunch of files/folder on your drive (that you've added to the 'Source' box or disc layout) and builds an image file (.ISO file or whatever)... which is stored on your drive, not written to a disc. 'Write image file to disc' also does exactly what it says it'll do. It takes an image file (.ISO file or whatever) and writes/burns it to an optical disc using your writer/burner/optical drive. When the program ejects the drive tray and attempts to reload it, it's doing so between the writing and verifying stages. It has no effect on a disc working or not, just if it's verified it, you should know about any issues with the disc there and then. The correct mode to use depends on what you have/want to burn - if indeed you want to 'burn' at all. If you'd downloaded an ISO from somewhere, you'd use the 'Write image file to disc' option.

What are you burning them to disc with though? Surely not ImgBurn as that would make absolutely no sense. Your issue is nothing to do with what you're burning.

There will be a way to revert, you'll just need to use 3rd party tools or unlocked flashers. You may find something of use over at the MyCE forums. They deal with this kind of thing (firmware things).

Are you getting other 'supported write speeds' now, or still just 2.4x ? As per my previous reply, do you have any other discs? Boot into safe mode and see if you have the same problem.

That error is coming from Windows. It looks like something it blocking the Write commands or your drive is erroring out and something is then masking the real error code. It's weird that 16x media is only coming up as being supported at 2.4x. Normally that would mean the firmware doesn't support it. Do you have any other discs you can try?

I suspect they read my signature and thought it was aimed at them. It wasn't.

The booktype of that is still DVD-ROM. But then I'd expect it to be as it appear to come from (time wise) before I even said to burn it when the booktype left on 'normal' (DVD+R DL). In fact, it comes from before the previous log you posted. Post the full log of the burn & verify session please - and make sure it's from *after* I asked you to try changing that setting. There's nothing wrong with what ImgBurn is doing, so this is either down to your source files or the playback device just not supporting them.

Double sided blank DVD? That's no good to you. You need a double layer DVD.

Is it in a format you can play on something other than your pc? Some players won't play BD type content from something that looks like a DVD-ROM disc. So if you can't burn to a BD disc (which your drive can't), try turning off bitsetting when burning BD Video (AVCHD) to DVDs. You can do that via the 'Use Normal For BD Video Discs' option in the settings on the Write tab.

That certainly doesn't look like an empty disc to me. Seeing as it appears to be a CD-R, you obviously can't erase anything from it either. CD-R are 'WORM' (write once, read many) media and cannot be erased like how CD-RW media can. Use a new, blank disc.

Go into write mode with your disc in the drive and copy+ paste all of the disc info from the box on the right please.

There’s a post in the faq about this.

There is no way those names are coming from ImgBurn. From what I've read, the name is just a logical/virtual one and comes from the (hidden) desktop.ini file within the folder. The actual names of the folders are different, hence why you can 'explore' both of them.

Could you upload the ibb for me to examine please? Afaik, those folders are internal to windows explorer and the name comes from it reading 'desktop.ini' files within the folders.

Well, that depends on what you actually want/need/mean. I'm assuming they just want a bootable DVD or whatever, based on what they've already got on a USB stick. After all, an ISO is pretty much defined an optical disc image file. If they want to 'copy' their USB stick to another USB stick, ImgBurn is not the tool for the job. It's for optical devices. Some clarity here on what's actually required would help

It might work if you just follow the guide for making a Windows installation disc. It all depends on the files that are on the stick.

Wow, that's quite some project you're loading there! I assume you're using Advanced input mode for that? The trouble with Advanced input mode is that every single file gets recorded in the IBB file. So that's its original OS path+filename and its path+filename on the disc/image - and lot more processing has to be done, not to mention WINAPI calls to get the file size etc. They could mean the AV kicks in to check the file is ok.... sloooow! If those 74k files and folders were in some sort of directory of their own, you could just add the parent folder in standard input mode and it would probably load that project in a few seconds. Ok so that's just a workaround, but it's a much quicker fix than mine would be.

What’s he going to do? C2 related stuff to detect errors?