LIGHTNING UK!

ImgBurn is a burning tool, it's not a conversion program. You need to search Google for one of those.

The reg ones are lower level and physically disable the polling the OS performs.

If you have a real problem with it (which obviously you do), just turn off the 'perfer properly formatted +rw' option in the settings.

ImgBurn does disable this feature during burning anyway via the 'media change notification' option.

Gim, Let me explain how things work.... 1. ImgBurn issues a 'Test Unit Ready' command to the drive. 2. Drive responds 'Ready', or it it returns 'Not Ready' and gives and error code. 3a. If drive is 'Ready', ImgBurn goes ahead and tries to initialise the discs. 3b. If drive is 'Not Ready' ImgBurn puts 'Device Not Ready ([insert english translation of error code here])' in the status bar. There is no room for error, either the drive says it's ready or it says it's not ready. If it says it's not ready, NO software can do anything about it or access the media. So your drive is having problems initialising the media, it's nothing at all to do with ImgBurn, it's simply reporting the error. Eject the disc and reinsert it, it might work properly the second time around.

I don't recommend it because then explorer doesn't notice when the media in your drive changes. AutoPlay is what it does when it finds new media - i.e. play the dvd, open it as a folder in explorer etc. AutoInsert is the whole thing of noticing the media has changed. i.e. if you just look at the drive in my computer, the volume label of said drive will not update when you insert a new disc. VMWare issues the warning you mentioned about AutoInsert being enabled, ImgBurn does not. You must be confusing it with something else.

ImgBurn defaults to wanting properly formatted media - once formatted properly, it'll read 'Formatted: Yes' in the info panel on the right. If it doesn't say that, it's not properly formatted. Once formatted properly ImgBurn doesn't need to format / erase the media before you write to it, it'll just perform what's known as 'Direct Overwrite'. If another program messes up the format then I'm afraid that is its problem, not really ImgBurns.

Erm.... I don't recall ever adding an option for autorun/play anything into the installer! The option in ImgBurn is a little different to what you want windows to do, so I'd suggest you leave it enabled. You probably need some sort of autoplay repair tool. Even uninstalling the cdrom devices within Device Manager and then rebooting might work. Windows probably got confused and so is ignoring the autoplay options you've set in the properties of the drivers via my computer / explorer.

You're getting a 'Write Error', the other error only comes after that. Not much you can do as it's totally down to the drive HOW it burns the disc. For some reason, yours is just failing.

Looks to me like you've got 2 duff images.

Well your filter driver stuff is as clean as it could be. In that last log you're getting read errors, so either it's burning badly or it's reading badly (or a combination of the two I guess). Nothing obvious stands out (besides that 8x burning on 2.4x media that corny commented on above). Sorry but you're just going to have to keep messing with things until it works.

Get the 'Filter Driver Load Order' tool from www.bustrace.com and see which other drivers all your I/O stuff has to pass through before reaching the actual drive. Maybe there's a bad one in the list that's not playing nicely. Following the advice in the post about 'DMA' in the FAQ can also help fix the odd few problems. The verification errors in the first log post are all too similar for them to be fluke ones. It almost looks like the drive is reading 1 sector in front / behind itself. Are you sure you don't have any 'on-the-fly' tools running that might be changing that data?

Do you verify as part of the whole 'write' process? If not, now might be a good time to start.

Kakarotto, Sorry, my last post was just about explaining how ImgBurn works. I really can't say why your drive burnt at 8x when it should have burnt at 4x. ImgBurn sent it the numbers for burning at 1x, it would/should have disregarded those and defaulted to the nearest speed it supports on that media - i.e. 4x. Why it didn't is anyones guess.

It's probably your firewall or something. If you don't want the application to check for updates, tell it not to. Don't block it with your firewall. If you do block it, the WININET calls can take a while to fail and that's why it seems to hang.

Triangle's at it again!

Also, see if you can manually select the/an audio track on the ones that don't play with any sound. If it finds the video, it should find the audio too. If it doesn't, maybe something's not quite right in the IFO's or the VOB's.

If your drives / players are stuttering on playback it's a sign that they can't read the disc properly. Your drive might just not be very well matched to the media you're using, try a different type. i.e. if you were using the -R verbatims, get some +R ones and try those instead.

Yeah basically the burn was so bad that the TOC cannot be read (this is an internal drive function, not something ImgBurn performs) - or wasn't ever fully written in the first place - probably caused by the write errors etc. Nothing much we can do about it. Update the firmware and perhaps change to different media, that's all you can do. You need to find a combo of what works for you.

Your drive might not support SAO (session at once) burning and that's what ImgBurn uses. The drive probably dates back a good few years and ImgBurn just doesn't support it at this time (it probably predates the MMC specs).

ImgBurn will always tell the drive to burn at whatever speed you have selected. It's then down to the drive to say if that speed is one of the 'supported' ones or not. If it's not a supported speed it'll just use (or at least should do!) the closest speed to it.

Blimey that's insane! I thought all the appropriate flags were already being passed to that API so that it displayed the box in the new explorer format. I assumed it would already be resizeable as a default windows thing.... I guess not! (I also see you're not getting the 'places' bar on the left of that 'open' dialog box). Thanks for picking up on it. EDIT: Ah yes, I was correct in my thinking. The box would normally be resizeable from just adding the flag to make it use the new 'explorer' format - only because I've also quite recently added a 'hook' to it (so I can position the box etc) the resizeable flag must then be added manually. This has now been done ready for the next version.

Depending on which one you mean, it's part of the main screen, I can't change the size. Hit the little green arrow and it'll grow a bit. If you mean the std windows open file dialog boxes, they already are resizable. There are too many options within build mode to make a queue system feasible right now.

It's doesn't delete it if the burn fails. ....but, a failure on the sync cache / finalise disc bits is not considered a burn failure. Hence why it says operation completed successfully in the log. That's the bit I need to fix, not the delete bit so to speak.

Sorry, I've been sitting on this new version for a while now. I've not been able to spend much time on it lately and I still have 1 or 2 tiny things to finish off before I can release it. When they're done, it's done.