LIGHTNING UK!

You must have just gotten a bad burn. To be honest, I hate laptop drives, they're all a bit useless. What speed did you burn at? Have you tried other speeds? Have you tried burning it again full stop?! Try some DVD+R type discs, you might have more luck with those. Also, Taiyo Yuden 8x DVD-R (TYG02) are worth trying, they're what I use most of the time.

I need that debug log again but on a brand new disc please. The one you've got in there has already been written to (or at least attempted) - it's size is totally wrong for a new disc. SATA is a 1:1 relationship so master/slave doesn't really come into it. The only mode settings I've seen/know about for SATA are where you configure it as IDE(SATA), RAID or AHCI. You'd want the first one for optical drives.

The status bar message 'Disc Not Empty' should have given that away too. ('Disc ID' always shows up like that on -R media, that field is only used on the +R type)

Have you found the status bar yet?!

No, it's the bar at the bottom of the main window. It tells you about everything the program is doing.

The message in the status bar might give you a clue as to what's wrong.

The 'Clear Recent Files List' option isn't really anything to do with those other MRU options (they're internal) but I've now made it so it is. When the MRU value is empty, the program does actually use the volume label as the basis for the IBB file name. I've now changed that so the image file name is used first (but with the .ibb extension), then the volume label, then the mru value, then finally (if all else fails) 'My Project.ibb'.

Ok, I've added support for saving the LB selection (done during a 'Calculate' operation) to the IBB file. If the value then read back out from the IBB matches exactly with one of the available LB positions at the time of build/write it won't prompt the user. That should at least give you something you can use from a batch file btw, you also need to have specified the /START and /CLOSE switches via CLI for this option to become 'valid'.

These are drive issues and nothing to do with the program. I can't remember if 2.2 even knew how to detect errors during the finalisation stages, that might have been new in 2.3 You've got quite a new dye of DL disc there, are you 110% sure they're the same ones you used before? The 'brand' name doesn't mean anything.

Ah, I guess they fixed whatever was wrong with the S203B then when they made the S203N. When using an S203B, I'm lucky if it even burns MKM-001-00 at 2.4x without erroring out!

From that, nothing at all. What happened to the bit of you actually burning something?

Are you posting because your 4x DVD+RW won't burn faster than 4x?! If you want to burn faster find a disc that supports faster speeds. When you do, please copy + paste the log (from the log window - click the 'View' menu to enable it) if you run into a problem.

If the drive decides it wants to even up the layers, yes. All it does is send the command and then poll the drive every second to find out if it's finished. As soon as the drive says 'yes', ImgBurn will move onto the next thing. So if it's taking a while it's because of your drive. btw, use 4x on that drive, it produces much better burns than 2.4x Try scanning a couple in cdspeed and you'll see what I mean.

They're hit and miss, that's why they're cheap. Also, your drive is no longer the spring chicken it once was. These things don't last forever I'm afraid.

You don't need to check them, they're wrong - take my word for it! A proper set of DVD Video files is made up of something like: VIDEO_TS.IFO VIDEO_TS.VOB VIDEO_TS.BUP VTS_01_0.IFO VTS_01_0.VOB VTS_01_1.VOB VTS_01_2.VOB VTS_01_3.VOB VTS_01_0.BUP No VOB file is ever over 1GB in size. Sorry but that's as much info as I can give you. You'll have to look elsewhere for non burning related help - this forum does not and will not provide it.

If the info in the guide isn't working it's safe to assume your source files are messed up.

looks like we owe mmalves 10 bucks! bc2000, this is a drive/media issue, probably brought about by a call to the 'Send OPC Information' command. It's unfortunate but it happens. Go into the settings and on the Write tab, uncheck the 'Perform OPC Before Write' box.

Pioneers always bitset DVD+R DL automatically, there are no commands available to programmers to change that I'm afraid. You can use a tool known as MCSE (Media Speed Code Edit) to patch the firmware and enable it for all the '+' format discs though. You can get more info on that over at the cdfreaks.com forum in the special 'Pioneer' section.

Update your firmware and use better DL discs. http://www.pioneer.co.uk/uk/download.jsp?d...108_FW120EU.EXE Verbatim DVD+R DL 2.4x (MKM-001-00) made in Singapore.

You've got DMA issues. Change the cable going to the drive and make sure it's as short as possible - avoid connecting it to a jmicron controller if you can. Set the drive as master / slave, don't use cable select. Follow the DMA post in the FAQ to uninstall the IDE controller from device manager and reboot.

No. bin is typically just used by CD discs that have multiple tracks (where bin/cue is then used) - possibly with different sector sizes involved (although they'll all be the same within the bin file). An ISO is a bog standard image.

The 50GB is a different dye, the 25GB didn't seem to burn too well on the drive, that's why it died and failed to reinitialise it. It's the same thing that happens with DVDs. Some just work better than others. I have a H20L and I've had no problems so far with the Verbatim 25GB BD-RE discs. You can try and do a format on the disc, just click Tools -> Drive -> Erase -> Full. That may or may not work.

UDF 1.50 is only useful for data. The 'standard' one is 1.02 and it's what most devices would expect to see on a DVD. The UDF version is nothing to do with the booktype - and vice versa.

If the Ricoh's aren't working for you, try some Verbatim 2.4x DVD+R DL instead (MKM-001-00, made in Singapore).

More an issue with you! As a new member, your posts are moderated and not made visible until one of the senior members has ok'd them. If you're not even getting the splashscreen then the problem is out of my hands as it's not my code that's messing things up. Every time I've seen this problem in the past (and I probably haven't in a couple of years) it has been related to viruses or bad memory. Do a few of those online virus scans from different vendors and maybe a few spyware sweeps with the likes of Spybot and Ad-aware. Test your memory using MemTest86+