LIGHTNING UK!

Then you must have done something to make windows change the letters (uninstalled the IDE controller perhaps?) because if that pic is newer than the logs, your burner is now E:.

It's not a windows disc so it doesn't contain a file system that ImgBurn understands. rename the file to .iso and ImgBurn will fallback to pretending it's a standard iso (mode1/2048)

Nero doesn't wait for the 'full format' to finish, I do. On BD-RE, I then write zeroes to all the sectors to make sure they're totally blank. (The DVD+RW full format seems to do this anyway). BD-RE and BD-RE DL share the same 'format' command. I see nothing in the MMC specs saying otherwise.

more logical, yes. more fun, certainly not!

Your log clearly shows the burner with the 'D:' drive letter.

The current profile info visible in that text is only used for that text. Before the erase operation starts, the command is issued again. It's weird that the drive would keep changing it's mind like that. Do you have any special software installed for burning/formatting BD discs? ie. anything that came with either of the drives? I haven't gotten around to buying any BD DL media for my H20L yet... maybe I should and we can compare results.

That window pops up when the drive isn't reporting nice info (the 'current profile') for the disc. Put it in the drive and copy + paste all the disc related info from the window on the right.

If you've never seen 'Father Ted' you probably wouldn't 'get' that one

Most people that visit this place do so in order to get an answer to a question - when they've got it they vanish. I'm not going to put my foot down for people that are here one day and gone the next. If the regular posters (i.e. me and the beta team) start complaining, that's when I'll put a stop to it. It's not like the images are hardcore porn, it's only what they'd see at any beach on holiday.

How you have the options set depends on how you like to work. If you want all the CUE's in one folder and the audio files in another, you need the preserve full pathnames option ticked or it won't be able to find the files (it only looks in the current folder for them). If you want to burn the CUE straight away, yes add it to the queue via the appropriate checkbox. Skipping is where the player can't read the disc. The only way to get away from that is to use decent media. Taiyo Yuden probably make the best CD's. They're all I ever use. btw if your discs are coming out blank, make sure you don't have the 'Test Mode' option ticked in the main window.

Does it play in the PC via media player?

You can't interrupt it, ImgBurn isn't actually doing anything. It's just asking the drive 'Are you done yet?' every second and yours is saying 'No' with the reason being 'Logical Unit not ready, Long Write in progress'. At this point (after 15 mins on a CD-R) you should probably remove the power from the PC to turn it off by force. Try the KPEY firmware update from here too: http://forum.rpc1.org/dl_firmware.php?download_id=2008

Put it this way, if it doesn't work, it won't be anything to do with ImgBurn. Your drive is fine. Make sure the firmware on it is up-to-date and that you're using decent quality double layer discs - which basically means Verbatim 2.4x DVD+R DL (MKM-001-00 dye) made in Singapore.

That's the thing, there aren't any physical errors on the disc. The program is just telling you that the content in those sectors doesn't match what's in the image file. If DVD43 is messing things up, disable it and see if the errors go away. If the errors move each time you verify then it's probably ram corruption.

Bad sectors would normally cause the drive to error out - yours isn't. Miscompares are generally where a program is modifying the data on-the-fly or you're suffering from corruption due to bad/overclocked ram.

If you're working from an image file I've no idea why one would work when the other doesn't. Compare the state of the disc (via the disc info window) before and after burning with each program. Are they the same? Booktype doesn't apply to BD media.

Well no matter how much data you supply, the program can't write part of a sector so either the PCM data ends perfectly at byte 2351 or it ends before it and the rest are left as zeroes. I don't really know about the whole taking data from other tracks thing... it seems kinda wrong to me. Do you plan to implement something like that? I'm on it right now Oh and I'd never include the filters in with ImgBurn. That's VERY messy.

If you convert to WAV then the gaps aren't added by ImgBurn - the decoded size should be a perfect match to what DS had estimated. I don't know all the in's and out's of audio but if the size isn't a multiple of 2352 (the sector size) then there's always going to be some 'zero' bytes inserted. I guess you're right though, the only way to get a 100% accurate size is to ignore the size reported by DS and do a dummy decoding process.

It doesn't cover the build mode options in the main window though donta... I had to check for myself earlier! lol Maybe we can convince Cynthia to go over those too That said, I'm sure it's been covered somewhere on the forum.

It's deffo a drive thing. Once the 'format' command has been sent to the drive, all ImgBurn does is poll it (via 'Test Unit Ready' and alike) to see when it's done. It's not doing any 'work', just playing a kid in the back seat of a car asking 'are we nearly there yet?' If the polling commands don't get back a typical response - i.e. 'Long Write in progress', it throws up the 'Potential WaitImmediateIO Deferred Error' message with the error the drive reported - in this case' Session Fixation Error'. The errors are 110% out of the software's control. It's purely a drive/firmware/media thing. Nero doesn't wait for the format to finish, that's why the 'Formatted' status is left in limbo. I default to making ImgBurn wait until it's completely done.

It's an easy mistake to make

Why not post the actual error so we can take a look for you?

It's already on high.

You must have 'Preserve Full Pathnames' checked.

I can't think why that would be the case. The slowest part of a PC is the drives I/O throughput and that's not going to change, CPU usage is normally quite low - although I'm not exactly testing it on such an old PC to check. I'd be interest to see what your CPU % usage is during burning on that machine with each version. There's a thread that does all the reading within the program and it should be running as quickly as the drive will allow for. At the end of the day, if the buffer empties out it's because the program can't read from your hdd quickly enough.