LIGHTNING UK!

The thumbs.db files are created automatically by the OS. The second you browse a folder with pictures in, it'll just make another one. You can turn off the creation of thumbnails via the folder options, a reg setting, group policy etc... it all depends on which OS you're running. They might even be coming from a 3rd party app that's being used to enhance what the OS is already capable of - i.e. offering to provide thumbnails for formats that the OS doesn't support. If you have a problem with folders coming back after you've deleted them, run chkdsk on the drive and make sure you haven't just pressed ctrl+z or something to 'undo' the delete operation. If they come back and you can't delete them again, it's probably just windows getting confused... it does that from time to time. A restart will fix it (assuming it's not something that requires chkdsk).

If you edit it out, that means you're setting a SPLIP flag to true. Sometimes cells have that flag set to false for other reasons (not layer break related) and it should therefore be left unset. Don't always assume a non seamless cell is a left over layer break cell and remember that the layer break is *only* a physical thing on the media, there's no flag for it in any of the files. The way ifoedit shows non seamless cells as layer break cells is wrong - think of that mark as a very rough guide, nothing more. ImgBurn will never mark a cell as non seamless unless it's the one you pick for the LB (and haven't told it to use a seamless LB)... so it's fine to leave it updating the IFOs even when you've edited them manually yourself and set everything to seamless.

Are you trying to read the disc on one of the workstations that you've used the CDs on successfully? If not, try doing so. It could just be a drive issue. You could also try ignoring the read error and see what pops up next / how long the errors go on for.

Correct. Hence the bit about 'before writing it to the DVD' - where 'it' is what's in the memory. That checkbox just controls the layer break option - so setting the SPLIP flag of the selected cell to the correct value based on what you've selected (non seamless or seamless) - and that only happens if the flag isn't set correctly in the first place.

It only changes them in memory (before then writing it to the DVD), not the ones on your hdd.

Your version of ImgBurn is out of date - old versions are not supported. Your firmware is way out of date. Get the latest version from here: http://www.firmwarehq.com/Lite-On/SOHW-1633S/files.html That RITEK-S04-66 dye hadn't even been invented when your drive/firmware were created so no wonder it can't burn them. It's probably about time you got a new drive.

Post the entire log for that session please, not just a bit of it. If you're burning an image file (which is sounds like you are), use Write mode, not Build mode.

Could you post the MD5/SHA-1 of the BIN file please. Did it start off as a BIN/CUE image or did you convert it to one? If you're getting a lot more failures when you use CD-RW than you do when you use CD-R, stop using CD-RW If you get the exact same 'miscompare' errors (same LBA / sector addresses and positions within that sector) on CD-R and CD-RW, you probably just can't burn that image on your drive using ImgBurn. I seem to recall that some PlayStation 1 CD games had special codes in the subchannel area... ImgBurn doesn't ever burn subchannel data (not even if a *.sub file is present). If you have a game that relies on it being there, you might have to burn it using a different program - typically, CCD/IMG/SUB collections come from and should be burnt with CloneCD.

It didn't ever start again. It burns - 0 to 100% cycles the tray then verifies 0 - 100% If you pay close attention to the screen during those two stages you'll notice subtle differences in the design/layout. Not only that, the message in the status bar goes from 'Writing Sectors...' to 'Verifying Sectors...'. Both operations are totally different things.

I guess you don't really know what AWS means/does http://forum.imgburn.com/index.php?showtopic=4249

Post the entire log for that session please, not just a snippet. Whatever you might think, this is drive/firmware/media combo issue. Nothing else even comes into it.

List entries where an actual file name is specified means the LB will be at the start of the file itself. Other entries are based on data in the IFO and will point to a certain Cell in a certain PGC within the VTS set the IFO applies to. i.e. VTS_04 = an entry based on what's written in VTS_04_0.IFO - and will ultimately be a sector within VTS_04_0.VOB / VTS_04_1.VOB / VTS_04_X.VOB etc. Only the ones based on data in the IFO can be previewed. They're the ones pointing to actual video data. Generally speaking, you're far less likely to be offered LB positions at the start of files than you are ones based on IFO data.

That's fair enough, the disc info contained what I wanted to see. It isn't always mega important that a drive supports the booktype commands - a lot of them will automatically booktype DVD+R DL to DVD-ROM anyway. Unfortunately, your drive isn't one of them.

Do you have a burn+verify log from the LG when burning a DVD+R DL? Put an LG burnt DVD+R DL disc back in the LG drive and copy + paste all the disc info from the box on the right when you're in Read mode.

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

Sorry, no. You'll have to use one of the Virtual CD burner programs or a CD-RW.

Post the log please - as per the pink box up the top. Have a read of this too please so we don't end up wasting time later on. http://forum.imgburn.com/index.php?showtopic=8000

You shouldn't. Imagine discs are languages. Now imagine a drive can 'speak' 10 or so languages. Talk to it in an 11th variety and it's just going smile awkwardly and say 'yes' a lot.

Try using something like 'Media Player Classic - Home Cinema', PowerDVD, TMT etc. The image you burnt in that log is tiny. Are you sure it actually contains everything it's supposed to?

Firmware is like the OS (operating system) for your drive. Manufacturers release new versions to improve the drives ability to burn different discs and to fix bugs. It only take 2 seconds to Google 'firmware' and you could have found out what it was. It's just like using a dictionary to find the meaning of a word you've never seen before.

Yes. By 'working ok', I meant is it still stuck searching for devices or does it actually get past that point now?

Are you sure the original disc actually plays in 3D on your LG player? Either way, it's an issue with your source file. Sort that out, burn it again and it'll work just fine (assuming the original works).

I'd ditch the InCD stuff completely but maybe that's just me. They're the kind of drivers (filter drivers in this case) that stop programs from working. You can use the Filter Driver feature in ImgBurn's Tools menu to get rid of them. Is the program actually working ok now?

That's highly unlikely, the values are too perfect for it to be brand spanking new. Eject it and put a CD in the drive instead. Does it still claim it's a DVD+R DL? (notice the 'current profile' bit at the top of the disc info box)

All drives perform differently with different discs. I guess your LiteOn just does a better job of burning whatever dye/mid the kodak media uses than the LG does when burning at 4x. You might have more luck with the LG at a different speed - if any others are actually available. Do you have the latest firmware installed for the LG? Right click the drive selection drop down box in ImgBurn and have it check for firmware updates for it.