LIGHTNING UK!

To me, 'Mixed Media' suggests you've got a few different type of files on there that the player supports. i.e. pictures, music, videos. If you want to burn a DVD Video disc you need to feed ImgBurn some DVD Video formatted files (i.e. a VIDEO_TS folder containing IFO/VOB/BUP files). ImgBurn is not a conversion tool.

In the forum called 'Guides'. or linked in the bright red/pink section at the top of this screen. or linked in my signature. Take your pick. In any case, you burn DVD-R just as you would any other disc. The format doesn't make any difference to the end user, the program takes care of everything.

I don't expect you to know how the program works internally, but needless to say, no that's not how it works. Try actually clicking Cancel and then Pause during a burn, you'll get a box pop up warning you that it could ruin your burn if the burnproof feature doesn't work properly. (something like that anyway) That warning needs to be in there so automatic cancel = pause is simply not an option. Pressing the buttons in the Cancel box only sets a flag within the program. The various functions / threads check those flags (paused / terminated) every now and then. The pause one is only checked in a few places - pretty much just during an actual read/write and not the operations leading up to it, of which there are loads. I believe that the way in which the cancel button current works (popping up the confirmation box) is pretty much how any application would act. It's not like I'm doing anything new here. Right so anyway, we can probably go on about this all day long but I really can't be bothered. It's working how I want it to right now and I'm sorry but I've no intention of changing anything beyond what I've already mentioned. Once again, I'm sorry that you wasted a disc, but hey, it's just one disc! Next time I'm sure you'll double check you've configured the program properly before you start burning something. Happy new year to you.

As Cilla Black would say... Surprise Surprise!

But as you can understand, from an average user point of view the suggested thing of auto-switching into a pause state after "cancel" window is launched is rather simplifying than overcomplicating. (no need to double-click!) I know what you're getting at but I can't just have it so pressing the 'Cancel' button pauses everything! As mentioned before, I don't/can't/won't keep track of every single program state just so the program can behave in a million and one different ways when the cancel button is pressed. If I made it so everything paused the second the user pressed the cancel, I'd risk creating bad burns (excessive relinking) or instant coasters. That's the whole reason I added the 'Pause' button and put a big WARNING message up before it actually did anything. Clearly you haven't actually pressed the 'Cancel' button before or you'd have already known to expect the confirmation screen (I believe consistancy in a GUI app is very important). As such, you're basing your entire argument of wanting it to work in a different way based on that one bad experience! What about the 1000's of other people that have accidently clicked the 'Cancel' button and were very glad it didn't instantly create them a nice coaster? It's impossible to please everyone.

You're overcomplicating the cancel function. All pressing the red button does is bring up the cancel window. I'm not going to start remembering/checking every single possible state that the program could be in when this button is pressed, that's just way OTT. (Remember that ImgBurn is multi-threaded and can be doing several things at once.) If you can hit the red button and confirm you want to cancel before the buffer fills up, it will indeed cancel the burn before the actual writing starts. I can (have) tweaked that so that when it's checking to see if the buffer is full yet, the program won't accept that it is (and hence move onto the actual burning) if the 'Cancel' window is open.

What's your CPU usage at during the burn? I assume the buffers are all over the place during it?

Installing firmware is as complicated as installing any other program. Get the file, pick your drive and click GO.

Progress on erase functions is shown whenever the drive reports it. Just look in the status bar. As it's so unreliable, there's no real sense in putting up a progress bar and just faking some progress data to keep people happy.

It's 1 coaster on 1 discs that was totally avoidable. Hint for the day? Don't cancel a burn once it's started! If a disc needed erasing it would have prompted. YOU quit the burn so this is nothing to do with ImgBurn, sorry but you'll just have to try and get on with life as best you can.

Well if you know it's going to fail you can turn off the option to disable MCN in the settings. But that just hides the problem, not fixes it.

God knows how you're using other programs but it's not hard to get a folder structure like I say in the guide! You seem to be making things faaaaaaar more difficult than they actually are. You have the folders: C:\MY_DVD C:\MY_DVD\AUDIO_TS C:\MY_DVD\VIDEO_TS Just add the 'C:\MY_DVD' folder as the SINGLE entry in the ImgBurn's 'Source' box and that's it - NOTHING else! Do that and you won't even get any prompts. It'll go ahead and build you a nice DVD Video image. You don't need to mess with any of the settings anywhere.

Even so, if the drive isn't picked up (as is the case with ASPI), what use is it?! Put it back on SPTI and leave it. Does it do it with all discs you put in the drive? Even with different media codes? It could just be faulty. Have you tried updating the firmware?

Don't output to an ISO, just output to files and then use Build mode as per the guides.

The forum limit is set to 3 but the SQL application on the server is set to 4 I believe. I've changed the forum to 4 now so it matches and doesn't just return an empty set of results.

lol yup, that's it! My programming skill are just too much for them and they fall at my feet. Ahh it's a hard life!

At the moment 'ASPI' isn't even seeing your burner. Forget Adaptec ASPI, it's old and shouldn't be used on XP. SPTI is default and is what works best - leave it on that.

You need to reauthor the disc and join them together. This isn't something you can do with ImgBurn. Just Google 'join dvd' or something, you'll find some guides.

Well an ISO should really just be Mode1/2048 anyway so I just assume that's correct if all else fails.

I think it's only admin users that can query which processes are running - hence ImgBurn won't be able to tell that you are.

It's just because ImgBurn does a sanity check and looks for a valid 'known' file system within the ISO. As there isn't one in those ISO's, it complains.

There's never been a face change to ImgBurn. You're probably just in Build mode rather than Write mode.

Look in eventlog and see if it says the previous shutdown was unexpected. These kinds of errors are normally driver related (or the PSU giving up during the burn).

2.3.2.0 can't be forced, no. It's fixed in the next version.

System ASPI isn't really used these days, ignore it.