LIGHTNING UK!

Ok, at the point you're getting to, the program hasn't really loaded. In the 'Debug' menu, click 'Go' (or just press F5). Once you've done that, loads more stuff will scroll up on the screen.

You might need to start up a debugger - i.e. Microsoft's WinDbg and then load ImgBurn from within that. It should capture where the error is coming from.

Come back when you're a real person and not a joke spamming bot. Thanks.

My mate's had nothing but problems with that LiteOn drive too. I have the LH-18A1H model and since performing the initial firmware update, mine has been fine - it wouldn't burn MCC's before that. Oh and the filesystem is only wrong if it's a DVD Video disc - which I'm guessing it's not? If it is a DVD Video one, stop using the program that created/built the iso in the first place - it certainly doesn't look like ImgBurn did it.

Changing the order might have meant the OS had to redetect the drives - and hence fixed DMA.

It means your drive can't initialise the disc - this is an internal function and nothing to do with any software. Either the disc is just screwed or your drive's firmware can't cope - try updating it.

VCD/SVCD's contain multiple tracks and ImgBurn only supports images with 1 track / session.

It all really depends on where the errors are. If the drive has corrected some data in the EDC/ECC regions, it's done so because it's wrong in the image. However, the CD/Player might actually require incorrect data in those regions and so the 'fixed' disc might not work as expected. To make the drive burn uncorrected data you have to make it use the 'RAW' write type - which ImgBurn does not do/support.

When is doesn't list any supported write speeds, it's normally because the media id isn't in the firmware table at all - i.e. it has no idea HOW to burn that media (it's not supported).

Corny and Kenadjian are spot on, you should listen to them

Just one more.... I found some leftover debugging code in this newer 2.2.1 release that was stopping the emails from being delivered.

Ok, I've just cleared out the SQL tables so you can all start again from scratch now!

@zacoz, He means the 'count' of how many discs ImgBurn has burnt. @Peter, You're quite right, the program reads the current count from the registry when it starts and then writes back the new count at the end. If you run 2 copies of the program at the same time, whichever one you close last will be the one who's count is stored in the registry / ini file. The stats are not important enough to bother messing around with, they're simply there as gimmick.

It's a burning tool....so probably not, no.

Basically, Samsumg (using the identifier 'TSSTcorp') and LG (using the identifier 'HL-DT-ST') drive owners will automatically (and by default) have all their +R / +RW / +R DL media changed to look like a DVDROM disc via bitsetting. It's an ON/OFF option. (Again, ON by default) Either the program tells the drive to change the book type to DVDROM or it doesn't and the drive will do whatever it had already been told to do by other programs (or by ImgBurn's 'Change Book Type' screen). (Note: +RW bitsetting isn't supported by the LG drives though - so far as I can tell) The booktype commands are sent to the drive before each and every burn the program makes.

Yup, it sure will.

I found 5 mins to implement it, so DVDROM booktyping is now automatic for Samsung and LG drives - as they're the only ones that don't remember their settings.

I've got some 2-3x Panasonic ones and some 5x Verbatims. Both seem perfectly fine to be honest mate! What I'd really like are those super fast (10x or 12x, can't remember!) discs - but they're not available in Europe Anyone want to send me some?

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.