LIGHTNING UK!

Ok, so what I need then is the image that's uefi bootable. I download the image you said you'd used as your source image... But if that in fact isn't uefi bootable, I guess I needn't have done so.

It turns out that I need roughly the first 12000 sectors from the mkisofs image in order to look at the boot catalogue. That equates to 24,576,000 bytes. So 25MB will do it if that's possible please? Sorry, I don't know the answer to your question. It would probably depend on what it's meant to be for the file you're pointing it to as the boot image. Normally you'd get the information from a disc that works.

Can you also upload the same first chunk of the working ISO... Assuming the one on there now is the non working one? Oh and you should have pressed the 1999 button on the iso9660 restrictions tab. The Joliet restrictions don't apply as you aren't adding that one. I'd stick with udf 1.02 too.

The first megabyte of each image should be enough to examine things. If it isn't, I'll let you know.

Maybe you need to adjust the iso9660 restrictions / settings so it can use longer file names etc. Basically so it's the same as whatever ISO level 4 in mkisofs is.

Your drive is reporting a write error, so it's having trouble burning to the discs you're using. Try setting the write speed to 8x rather than max or use some different discs.

I'd have expected number 1 to work. Which parameters are you passing to mkisofs? That should give us a clue. Beyond that, I'd have to examine a chunk of each image and see how they differ.

What was the I/O error in safe mode? If a command doesn't complete successfully and just hangs, there's nothing much I can do about it I'm afraid. You'd have to mess around with ports, controllers and drivers until you find a combination where it behaves itself.

ImgBurn relies solely on DirectShow for any conversion required. There's no way for it to get smarter as it works the only way it can. You provide directshow with the source file and tell it the format you require. It then attempts to pull in the required codecs to make that happen. I have no way of knowing if it's a good or bad conversion (if any quality is lost etc), I only know if it succeed or fails to convert to the required output format. Unless a tool uses the exact same method, it's unlikely to run into the same problem.

I expect it's the monogram ones. What's the exact format of the wave file you're trying to add? Does it match what I've said above is required for CDDA? If you google 'disable directshow filter' you'll find various tools that let you accomplish the task. Check 'programs and settings' within windows too as you may be able to uninstall a codec pack or two from within there.

When you create the cue file, right click the track (once added) and have ImgBurn display the directshow filters being used by your system. If your system is poorly configured, directshow could be using a filter that's negatively affecting the quality of what eventually gets burnt to the disc. In order to limit any processing required for burning, stick to 44,100Hz, 16 bit, stereo files. That's what CDDA is.

Probably for troubleshooting. The way they're configured effects what the program does.

The real setup file makes use of a plugin called OpenCandy. Some AV software will flag it as a potentially unwanted program. If you don't have the real setup program (check the md5), you might have one that really does contain a Trojan. I don't know what you've downloaded.

I've never come across one, so I've no idea. Try read mode and then write mode. It's only 1 disc if it doesn't work

Often when an empty sector is returned to the program and reported as a miscompare, it's because the drive has failed to complete the read request properly (it should have errored out) or because something is messing up the contents of the buffer between the drive filling it and the program accessing it.

I guess you can't. You'd need to obtain a recovery disc from elsewhere. Maybe contact the manufacturer?

Oh dear, I forgot just how old XP is! 2.50 is pretty much the standard for BD media but any will work. Yes, go for a lower one.

You could use ISO buster to examine the disc and find the file it errored out on. You can then find the LBA for that file in the appropriate column. Every file before that LBA should be readable.

That just shows the disc is unreadable. Not all that surprising for Ritek DL media, that's why everyone recommends Verbatim MKM-003-00 double layer media. This is nothing to do with OpenCandy. The program doesn't know or care what you've done with it as the plugin is only used by the installation wizard.

It is what it is with this I'm afraid. Your machine is running out of system resources. Make an ISO and burn that rather than burning on the fly. It's much safer! Don't include ISO9660 on the disc and switch to udf 2.50.

1. It's fine. 2. No 3. Just click OK 4. It doesn't seem to need it, it's already being changed to DVD-ROM. 5. It's not worth worrying about if 3x is working... and it appears to be as the disc burnt and verified ok. If you run into problems, buy the recommended Verbatim MKM-003-00 discs. 6. No

Post the logs of you burning and verifying DL media with each version please. (Oldest and current) The current version must have been used for burning millions of DL discs around the world by now. If there was really a problem (I know there isn't), it would have come up long before now. It would also help if you tried Read mode on the discs in your entertainment drive so we can see the errors being reported.

It's what's visible in the top line of the disc info box on the right. Just leave off the firmware version and bit in brackets at the end.

Yes, that's correct. Same goes for DVD+R Vs DVD-R

There are a few things I'd try, but you'll have to ignore that you've not touched anything and just go with it. Things can just fail for no reason. So... Try another port on the MB - stick to the Intel chipset and not any 3rd party one that might also be present. Try another cable (take it out of your other optical drive if need be). Make sure you have the latest bios installed for your MB. Try the SATA controller in AHCI mode rather than IDE/ATA. Try the drive in another PC.