LIGHTNING UK!

The program isn't the issue here, it's the drive that's failing to do what's being asked of it. 'Invalid Address For Write' is almost always the response a drive gives after the program attempts to retry the write operation. The *first* error is the important one, not that.

Look again, the tabs are on the right side of the screen when you're in Build mode. The Advanced tab is home to the 'restrictions' one where you can tell the program to allow more than 8 directory levels.

The brand makes no difference. It's the disc id (media ID / MID) that's important and yours are the rubbish CMC ones. As I'm not seeing any supported write speeds listed in the log, the firmware may not support that mid at all. That happens when the drive is older than the mid.

http://forum.imgburn.com/index.php?showtopic=8000

You're trying to burn cheap 'RITEK' discs and your drive doesn't like them. Buy some decent verbatim MKM-003-00 ones as mentioned in the thread I linked you to.

Read the link I pointed you to.

Your friends are wrong. Leave the layer break setting on 'Calculate Optimal' and let the program read the correct value from the .DVD file. That's the way the program is supposed to work. Have a read... http://forum.imgburn.com/index.php?showtopic=8000

Do you have access to any other PCs you could try the disc in? If they do the same thing, one would assume the disc is at fault. If they don't, it's probably a setting on your machine somewhere (UEFI / BIOS related). Going back to your original disc... even with the rattling and grinding, does it actually boot?

That's correct

You can find old logs via the Help menu.

The 'Kernel Version' is important with Pioneer drives. There do loads of different versions but use the same main drive name identifier for most (either BDR-XXX or BDR-XXXM) and it's just the kernel versions that differ and prevent flashing of different firmware updates.

If you already own a Windows XP install disc, why are you following a guide to build a new one? For the purposes of just checking to see if you machine will boot one of them full stop, see what happens when you put your original one in the drive. If that boots up ok, there should be no reason a custom/updated one shouldn't boot... in which case, please post the log of you building/burning/verifying the disc.

Yes, that'll be copy protection. They don't need to protect every disc, just the one required to actually play the game - it's cheaper. I'm afraid we can't help you duplicate those discs... or any others that are copy protected.

A valid request... I assume you'd just want to 'continue' automatically? Shouldn't you be fixing whatever the problem is though?

Unless you specifically want a UEFI bootable disc (where you'd need a UEFI compatible board to actually boot it), stick with the previously forced option of '80x86' (meaning normal BIOS board). The guides don't cover UEFI (I don't have a compatible board). 'Patch Boot Information Table' is for Linux type boot discs (isolinux). When burning such discs, there's a boot information table in the boot image that has to be patched with offsets/locations of certain things (for the specific disc you're building) or the disc won't work. Google returns a fair bit of info on the 'boot information table' - here's one page talking a bit about it. http://littlesvr.ca/isomaster/eltoritosuppl.php Extract boot image does exactly what it says on the tin. It extracts boot images from existing media. So if you put in a bootable OS disc, you could extract the boot image from it and use it on the new one you're building. Not that I've ever compared boot images from pure x86 or x64 discs, but I'd assume they're the same. Unless the people that supplied your PC copied the entire contents of the Windows Vista/7/8 OS install disc to a folder on your drive, I doubt you'd find a file suitable for use as a boot image on a CD/DVD. I believe 'Load Segment' is to do with where the 'Sectors To Load' worth of data from the boot image gets put in memory. The BIOS or whatever then runs whatever's there and fingers crossed, the disc boots and does whatever it's meant to do. The 'El Torito' specs might give you more info on that.

It could be anything... bad disc, drive no longer in optimal condition (age/dirty)... who knows! You know as much as I do. The drive was asked to write some data to the disc and it failed to do what was asked of it - simply reporting a 'Write Error'.

Selecting the 'TAG' option for a song will make the program use the performer/track name from the file's tag/metadata - assuming it's in a format it supports. 'TAG' is a per song option, but you can do it at 'Session' level to enable it for every track already in that session. 'TAG' at 'Disc' level just uses the album artist/name from the first file in the first session's tag/metadata. Changing the 'Default' options does nothing for a disc you've already created a layout for, they'd just apply to discs you build in the future - like if you always want ImgBurn to use TAG/metadata info from files for CD-TEXT. Once you've saved the CUE file, open it in notepad and you should see all of the track name/artist info in there.

It's the disc information status and state of last session that's causing that. Try some different discs and see if your drive behaves the same way.

Without seeing a log from a burn where the disc doesn't work, it's hard to help. What folders do you see on the disc? Assuming you have the usual BDMV folder etc in the root, the issue could be coming from the source files.

The Lite-On drives only really work properly with a specific setting (drive setting, not program setting) enabled. Samsung drives don't have that setting and just don't work. Buy a Lite-On or the Optiarc 5280-CB Plus/Robot drive.

The first error is the important one and your drive reported a 'Write Error' - so it had some issue burning to the disc. Try some other discs if your drive frequently fails to burn those 'RITEK-BR3-000' ones.

Yes, i do quite well know what's in my installer and what you're telling me just doesn't add up. I still don't think you downloaded and ran that file. All that one does is include a 3rd party advert page or two during the normal installation wizard. Surely someone as clever as yourself would be able to locate and click the 'opt out' option on those pages?

Sorry but you must have run a different installer or program. Noting runs and scans your PC when you're just attempting to install ImgBurn. What's the file called that you downloaded?

Try here... http://forum.imgburn.com/index.php?/topic/21027-really/

You'd have to make the image with DAEMON Tools itself. It'll need it in its own format if it's to see both sessions properly.