LIGHTNING UK!

You can only do this via CLI. I left it out of the GUI on purpose (and won't be adding it I doubt)... it's a scary feature!

If the drive can't read the disc it'll stop them from playing. Drives aren't able to read discs if the disc is just generally crap or burn quality wasn't any good - and that's totally down to the drive/media/firmware. If the PC is able to see it as an audio cd then there's nothing actually wrong with the way it was created. As mentioned in my previous post, try burning at 16x or 24x. That should improve the quality of the burn and maybe your more picky players will be able to initialise the disc properly and play it.

Help menu -> ImgBurn Logs...

Try cleaning it. Are the verbatims the 8x (MKM-003-00) ones or the 2.4x (MKM-001-00) ones? That latter are likely to be more compatible.

The original poster already said that. :S

If you have a multisession disc you wish to copy, just make an image in Read mode and then use Write mode to burn it. You cannot make up your own multisession discs in the way you're probably wanting to - i.e. add a few extra files to a disc every day. Whilst I personally believe a USB pen is better for that kind of use, I will probably work on multisession support within Build mode for the next major release (v3 I guess).

You might just be using an RW that the drive's firmware simply doesn't support.

Bring up a command prompt window (running as admin user) and try typing in: net localgroup "Performance Monitor Users" "%USERNAME%" /add It basically does the same thing only involves using the keyboard rather than the mouse

You might like to try slowing the burn speed down to 16x or 24x too. It'll produce a better burn. Taiyo Yuden seem to make the best CDR's too. I ditched Verbatims (normally great for optical media) in favour of them a while ago and I've never looked back.

It doesn't really matter if it may or may not cause problems if you try to burn something different. The drive isn't playing nicely when the program tries to burn using SAO (the actual data being burnt is totally irrelevant) so (assuming it works) you're stuck with TAO anyway.

Try just the firmware first though

You could try changing the 'Write Type' to TAO, maybe your drive is so old that it doesn't like SAO (or at least not how I'm trying to set it up). That's what happens when the drive is ancient and doesn't comply with the MMC specs ImgBurn is built around

You could try using the TAO write type for burning, maybe the drive just doesn't like doing SAO onto those discs.

It would appear the 'expert' doesn't know as much about ImgBurn as he/she thinks they do. ImgBurn doesn't allow spanning in any way, shape or form.

Can you burn other discs ok (non DL ones) ?

What exactly is missing in Vista basic that the guide doesn't work? Is the group not in the list or can you not even get so far as seeing the list?

Normally SATA drives will show up as ATA, AHCI, SCSI or RAID (RAID being the worst one for it to be on). I'd don't recall ever seeing a computer report 'Fibre' before so something isn't right with your setup. That whole thing is wrong. You might be getting corruption on the entire structure, it's hard to say without looking at the exact response data. What I'd probably do now is put the drive in another machine and see if it does the same thing. Can I assume that if you flash the drive with the official firmware you have the exact same problem of the 'Last Recorded' info showing as HD DVD-RW or whatever? (you need to rule out the patched firmware).

As the ADIP and Last Recorded structures should be identical for blank media, I'm not really sure why your system is feeding garbage to ImgBurn. Have you figured out why the system is reporting that the drive is connected via Fibre rather than ATA/AHCI etc yet? Ignore the disc info in the panel on the right, the bitsetting dialog itself will tell you what the drive thinks it should do when it burns a disc.

It's not ImgBurn hating them, it's them hating ImgBurn! I'm not aware of a single command the program could ever send that causes them to mess up every time without fail... if there was then I'd try to work around it. All that's happening is ImgBurn is triggering some flaw in them... think of it as I/O stress testing

Hmm well you could try changing the single layer media profile to a huge value (as in, one larger than a DL disc), then the program would always think the image is single layer sized. Of course if you ever do any real burning you should put it back on DVD+R or DVD-R!

You can't and you shouldn't ignore layer break options anyway. Leave the DL ones until last and then go through them all and pick the right one for the project.

What drivers have you installed for your motherboard SATA controller? Try uninstalling them and just using the standard Microsoft ones. What do the IDE controller and SCSI/RAID controller branches look like in Device Manager? (try and get a screenshot or something) I don't think the 0xA8, 0x03 error is coming from the drive itself because the pioneer drive specs don't say the drive is capable of returning such an error code. Error codes from drives are normally all in the 0x00 -> 0x7F range and yours is 0xA8 - thus making it look like it's coming from some other device/driver.

Otpical drives don't like running on controllers working in 'RAID' mode. Make sure the SATA controller is configured as IDE/Standard in the BIOS (or AHCI if all else fails), but make sure it's not on RAID. Then get down the latest storage / sata drivers for your motherboard from the chipset manufacturers website. (i.e. Intel, NVIDIA etc)

I normally use 'hex workshop' but something like 'Beyond Compare' with the hex viewer plugin would work just fine too. When you know which bytes have been changed (and their offset from the start of the file - probably going to be in the first 2048 bytes of the file), open said IFO/BUP file in IfoEdit and see which field is at that location.

It changes them to correct things that are wrong... and that's only ever going to be the various offsets that are fixed by a quick 'fix/get vts sectors' type function (from the ifoedit days). It's not hard to compare the modified files against the originals and see exactly what's changed. Do that and you'll have your answers.