LIGHTNING UK!

LFC is correct, ImgBurn only does booktype stuff when the user initiates it via the little book icon thingy in the GUI. I don't like the idea of always sending the booktype commands because then you need to keep tabs on which drives need it and keep adding new ones to the list. I prefer to stick with things that 'should' work forever without me needing to update the program for new model drives etc. As samsung and LG are the real problems, maybe I could just do it for those. The only thing stopping me is my own stubbornness as I've obviously already written the functions to be able to do it, it's just a case of me adding a line of code calling that function with the correct parameters!

Maybe that 'Burn to the brim' program will help you. Sorry but it's not functionality I can ever see being implemented into ImgBurn directly.

Yup, I'm with you both on the DMA thing. As Shamus said, check the FAQ.

Don't make the ISO with DVDstyler, just make it output to a VIDEO_TS folder. Then follow the guides in the 'Guides' forum and use ImgBurn's 'Build' mode to make your ISO/burn your folder directly to disc.

Yes of course it will still work, it wouldn't be an 'option' otherwise! It just means other programs can screw up the burn much more easily - including Explorer itself.

It tells the OS to only allow access to the drive from the process that initiated the lock. Other programs that try to access the drive will find they get an error back from the 'CreateFile' API call - as would be used by SPTI. Other drives ARE still accessible - you can test this by simply burning something and opening a 2nd instance of ImgBurn. It'll report the error with the 'locked' drive but the others will still visible / available for use. Perhaps the other program is not dealing with the 'CreateFile' API error correctly. Maybe it's seeing the error and just totally giving up instead of trying the next drive etc.

That directory depth issue can be overcome by enabling the appropriate option within the Advanced -> Restrictions tab.

No idea who actually makes your drive, it's one of those annoying unbranded ones. I'm sure you could search Google and find some info on it though. Look for a firmware update for it and try some other media. You might have more luck with DVD+R type Verbatim (Still MCC dye) discs. Basically, it just looks like your drive isn't burning to those properly - hence the errors when reading them back.

'Build' mode is NOT anything like 'Read' mode (as you know it in Decrypter). The two will never be the same, nor are they supposed to be.

I could have misinterpreted your initial post but are you saying ImgBurn won't load the image and just says it's invalid? Changing the file extension shouldn't do anything as ImgBurn doesn't work like that. If your PC can't even see / read the files on the disc (i.e. just via explorer), you've got a duff image.

Just click 'Help' -> 'ImgBurn Logs'. They're now saved by default.

ImgBurn always tries to finalise any discs it burns, there's never any need to do it manually. Why exactly do you think there is a problem?

Neither ImgBurn nor DVD Decrypter can burn multitrack images. ImgBurn just has a bug fixed with loading CD MDS files.

ImgBurn doesn't attempt to burn the MDS to a disc, it looks in the MDS file to see the name of the image file it's associated with and extract other little bits of info from it. So just load the MDS and if it supports the image format, it'll load up and you can go ahead and press the 'Write' button to burn it.

The DVD-R DL specification does not allow for manual positioning of the layer break. Many drives overspeed media to speeds beyond the 'rated' ones. i.e. 6x or 8x on 4x media. 4x or 6x on 2.4x media etc. It's all down to the drives and their firmware.

When you shrink it you're probably changing the info media player uses to identify the disc. Unable to identify the disc = no disc info / album art.

Seems to me that your drive can't even erase the +RW discs you're using. So now would be a good time to get some new ones that use a different dye.

Your drive appears to have had enough of burning (to that media anyway). Maybe it's broken? RMA it?

If the place you got it from didn't provide instructions for burning, you probably shouldn't be downloading it at all. Making an ISO from 1 file would add a few MB to the size, nothing more.

You cannot set the layer break position if you're using DVD-R DL media. It's a feature only supported by the DVD+R DL discs. If you can't move the layer break, you're forced to attempt to align things with the FIXED (physical) layer break - and that's almost never something you want to do. It also means that you can't make a proper copy of your disc - unless of course it was on DVD-R DL media in the first place (again, because the layer break position would be wrong). For actual burn quality, I'm sure the media is fine. It's just the limitations of the DVD-R DL format that's the problem. Also remember that you can't perform bitsetting on the minus format discs (DVD-R, DVD-RW, DVD-R DL etc) so if you're burning a DVD Video disc and have a picky standalone player, it probably won't work with that media anyway.

lol it doesn't matter how you phrase it, it's still not possible at this time due to the inner workings. (and they won't change / be changed unless I redesign everything - which again probably wont happen due to GUI size limitations). The IBB stuff doesn't open up new functionality, it just checks the checkboxes already found in the GUI, selects the right options in the drop down lists etc. For the files, each line in the backup list within the IBB is added to the source box via an automated click of the 'add' button. There's no clever stuff going on.

Sorry, no. If it's not possible via the GUI (which it's not), it can't be done via an IBB. It's just not how I intended ImgBurn to operate/be used. If you need a virtual folder tree where you can create folders and move things about etc, you have to stick with tools like Nero. Of course if I ever change my way of thinking (which is doubtful as the GUI basically doesn't allow for it! - size wise), this feature will of course be implemented anyway as the functionality will exist in the main GUI workings.

The verify errors are a little odd. It's hard to say if the drive has a problem burning the media or it if has a problem reading it back. The only way to tell is to build an ISO rather than going direct to disc. The burn + verify in the samsung and do another verify in another drive (if you have one of course!) Your players might work better with the discs if you perform bitsetting to make them look like DVDROM discs rather than DVD+R DL. For bitsetting, click the little book icon down the bottom right of the screen (when in Write mode) or on the Device tab when in Build mode. (Or do Tools -> Drive -> Change Book Type...) Configure that appropriate option on the samsung tab AND THEN burn your disc. It should then come out saying: rather than

Yes you should download the above file as that's the only one that will work with HP branded LG drives. You only have to download it and then double click it - it's an exe file.

Dont add the whole 'root' folder, just add the bits in 'My Documents' or whatever. You can't select a high level folder and then exclude lower level ones so you have to just add the right low level ones in the first place. i.e. If you have: My Docs\1 My Docs\2 My Docs\3 and you don't want My Docs\2, do not just add My Docs. Instead, add the 1 & 3 folders to the 'source' window / box.