LIGHTNING UK!

It'll be out when it's done. No you can't set the write offset.

Any of them that work / you have installed (or can install).

Sorry, forget that - too late now, I know! The problem was in general parsing of APE tags and I've fixed it.

Is there any chance you could email me the first 5mb or so of the file?

Try cleaning it with a cleaning disc. Have you always been using that exact media? Try some Verb DVD+R's instead.

It's pretty unusual to have the burn thread crash like that, it means there's some sort of memory access issue. The log/screenshot don't really give anything away that would help me figure out exactly where this is happening. Whilst it could be an nvidia driver thing, it's not erroring out in the same way for you that it does for other people. If I'm to try and help any more, the best thing you could do now is try using one of the other I/O interfaces and see if the same thing happens. After that I'll probably have to send you a debug build to try. btw, you don't need to restart to eject the disc, just load ImgBurn again and tell it to eject it (it'll unlock the tray before doing so).

My guess is that it's timing out because the controller thinks it's running RAID. You wouldn't want command taking ages (5 seconds!) so it just cancels them when they do. Until you can get your controller / drivers thinking they're in SATA mode (rather than AHCI or RAID), you're stuck. If you can't do that, get yourself a Silicon Image 3512 PCI controller card off ebay for

If you still have trouble with the TDK's post another log and I'll try and dig mine out so we can compare.

I've got a couple of the 50gb BD-RE ones and my drive has burnt those ok in the past. I might also have some single layer ones but I don't use them as I prefer the verbs I'm guessing the BD-RE used in the log is the one that came with the drive? I didn't even bother to open mine!

You've got debug mode enabled, don't turn it on (as it's not supposed to be on) and you won't get them. Debug mode is for my usage really, not yours. The files being output are what directshow outputs + my own wav header. The files aren't used at all, they're simply there for debugging purposes.

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

The code was missing, it'll play a sound in the next version.

I see no mistake in my original post

I can't see a point in it either.

I have that very same drive and it has no problem with Verbatim media, I've seen several posts where people have been using other discs and the drive hasn't worked very well. So my advice to you is to get Verbatim discs!

It's a drive/firmware/media issue so something about one of those 3 needs to change. Personally I'd start with checking there are no firmware updates available from your laptop manufacturer. Then I'd buy a new spindle of the 2.4x verbs (MKM-001-00 dye, made in Singapore) * This is important! * Failing all that, try running a cleaning disc on the drive. and if all that fails I'd buy an external burner.

They look different to me. So your drive is reporting a write error when trying to burn to the media.

Press the left windows key + break click Advanced system settings click startup and recovery settings uncheck automatically restart The next time it BSOD's you'll see the message on the screen, write it down and restart manually. Report what you see in this thread. You can also just open the memory dump in windbg and see what it says.

That disc has been used before, you need to use a brand new disc so we can see the real error. Have you tried new discs at faster speeds? i.e. 4x or 6x Have you tried using MKM-001-00 media instead of MKM-003-00? They're the 2.4x verbs rather than the newer 8x ones. Make sure you go for ones made in Singapore too.

In any case, copying rental discs is a big no no. Backing up original discs you own is one thing (and perhaps legal in some countries), I'm pretty sure copying rentals is illegal everywhere.

The disc is probably protected against casual copying.

Is the value to the right in brackets when you've got it set to 'AUTO' really not at all obvious? What do people think it is if not the speed?

It wasn't that at all. We haven't needed ASPI since the Windows 95/98 days. The first error is due to you using media your drive doesn't support properly - update the firmware on it and buy better discs. The second error is because you're trying to read a protected disc - and ImgBurn cannot do that.

You can't.

An NEC that old would use the RICOH command set, not the NEC one.