LIGHTNING UK!

It only works if the ISO has been built for positioning at the exact LBA it'll end up being positioned at - i.e. all the fields in the file system must have the correct LBA offset.

That IFO file is in a VIDEO_TS folder yeah? Just drag + drop that folder to the 'Source' box in Build mode. If you have problems from there, please explain exactly what they are.

Discovery mode just burns from memory - you know that yeah? As such, it must be a hdd read speed issue then... or at least it is when you're trying to 'write' to the dvd burner at the same time. You could also try running process monitor (from sysinternals) and seeing which processes are performing file I/O on your machine. Maybe you'll spot something making a lot of drive accesses that really shouldn't be - like indexing or something.

It's kinda by design. The program is still doing stuff and will eventually return the normal error about the file being invalid or unsupported. All that's happening is that the quick image format checks have failed and so a really thorough one (testing for a sequence of known bytes within the first 80 sectors worth of data or so) will be taking place. It's slow going and I expect network file I/O latency etc makes things run even slower.

It just means the drive doesn't like the disc. If you can't get hold of another drive to try it in you'll just have to get another copy of the disc from somewhere.

ImgBurn isn't really aimed at mass duplication and I very much doubt I'll ever bother to support simultaneous burns.

burham, make your other thread please. Do not hijack other peoples.

If it burns and verifies when using UDF 1.02, the problem is with windows... it's probably getting confused and still thinks the blank disc is in the drive - i.e. it hasn't tried to read the disc again properly after the burn. Shut the machine down and try reading it again. If ImgBurn can read the disc, Windows should be able to too.

Sort file by source list order

Did you ever try with SP1 installed? A lot of people on here (myself included) have no problems with Vista. I can't speak for those with nvidia chipsets though as I only really use Intel based boards.

Some drives just don't like the 8x version as much as the 2.4x ones. (MKM-001-00 Vs MKM-003-00, the latter being the 8x variety) Assuming there are no firmware updates available for your burner, its ability to burn that media may continue to be hit and miss.

Enable the option in the settings and put them last in the 'source' list.

Maybe you can put the real LG firmware on it? It might be newer than your OEM one? Ask the guys at cdfreaks, they have more experience of that kinda thing. You can force an erase on it, just hit the erase button (in the destination box when you're in write mode) and tell it that it's a bdrw. You'll have to do a full erase though probably but try a quick one first anyway. It wouldn't be something like DAEMON Tools or Alcohol 120% cloaking it to look like a BDROM would it? I know that happens with DVDRW discs where they then look like DVDROM.

You get the drivers from the nvidia site.

Use UDF 1.02

The BSOD memory dump might actually give you a clue as to what's wrong. You could also try running Prime95 for a while and see if your machine can stand up to a proper stress test.

Do you have the latest nvidia chipset / ata drivers installed?

No, miscompares are not 'normal'. It's weird that you should be getting them at all to be honest. You expect to see errors reading back dodgy burns, not miscompares. It almost looks like corruption - either in memory (test your system with memtest) or with the controller running the hdds/optical drives.

Yes it's supposed to save the drive in the project file. Just delete that line - Open it in notepad.

Verify your burns and post a new log. (This will also tell us if your drive is booktyping to DVDROM) 8x might produce a better burn than 4x. I'm sure you already know that we recommend Verbatim and Taiyo Yuden media here. Everything else is rubbish in comparison.

Have you just burnt that disc? If not, maybe it's damaged. If you don't have the source ISO, just download it again and burn a fresh copy onto some decent CD's (Taiyo Yuden).

I meant in terms of nvidia, intel, jmicron, silicon image etc. I can tell from the model number that it's an sata drive Are you saying it reads discs ok but won't burn *anything* or that it will read/burn everything except your 'MKM-003-00' dye double layer discs?

It's a CD Extra disc yeah? Do you really need the data bit? That's the bit with the errors. If not, just extract the audio tracks in EAC or something and forget about the data session.

It's done so ImgBurn knows the exact size of the decoded file and therefore how long the track (or last track in your case) is. Without it you can just end up with silence / gaps in the music where there shouldn't be any.

What's the CPU % usage at when you're burning? It shouldn't be hard to get 20mb/s from your hdd - especially when it's an image file so something's obviously not right. I assume you've tried defragging? I'd also try removing the old cdrom from the system as these things have been known to slow the bus down compared to modern drives working on their own.