LIGHTNING UK!

No No Sorry but you really need to take a look at a forum that deals with this kind of stuff. This isn't an ImgBurn issue and so it's not really the best one to ask such questions on.

Sorry, I totally misread your original post. I thought that error had popped up when you were just burning normally. I'd expect it to fail if you did it manually - as it's not one that should be called on a CD. As you seem to have found out, ImgBurn always closes / finalises everything.

Nope, I have no plans. I just implement what I feel like implementing.

Hmm that's an odd thing to break! I'll look into it.

You could also make a .dvd file (plain text file with .dvd file extension) containing the text: layer0.dat layer1.dat or use the 'create dvd mds file' feature, add the two files and make a .mds file. Then load the .mds file in Write mode. Then imgburn will treat the 2 files as a single large file.

Post the full log please. I'm guessing your drive doesn't support the command used to determine the current media type and so it's using a 'fall back' function that just tries all the different close methods.

Hmm interesting... I had this issue with 98 / NT4 after I started using the TntControls for Unicode stuff. I updated TntControls a few times during the beta cycle and the problem went away. I did test it on NT4 before releasing it but I guess my version already had that file installed from my playing around during early beta testing. Weird that it didn't error out on 98 at the time of release though, and I made sure the msimg32 file didn't exist too! I've attached the msimg32.dll file to this post. Just stick it in the ImgBurn forlder or in your system dir. MSIMG32.zip

I doubt it, there's very little call for such things. Not only that, I've no idea what they are

Write a batch file to do the job and then add it to the scheduled tasks list in windows.

Yeah this is nothing to do with the ImgBurn program. Please visit the appropriate site for whatever tool you're using - it's not this one.

But incd only causes problems due to the type of software that it is. It won't affect ImgBurn any more/less than it would do any other burning software. Packet writing software is just pretty awful in general.

How exactly are you 'ripping' it ? ImgBurn's 'Read' mode will do a 1:1 copy of the disc to an image file. If you load up the image in ImgBurn as if you were going to burn it, what's does it say on the main screen for sector size / mode / type etc? Does ImgBurn see the image as being bootable? Read it again and copy + paste the log. Maybe we'll spot something.

It's only useful in the sense that we can see there's a problem with your drive burning to media - even decent media! (and we already kinda knew that) Now's a good time to run to the shops and pick up that 112 I'll be doing the same thing later on today

ImgBurn isn't there to allow you to copy movies (it won't, end of story), it's a burning tool and is a complex as a burning tool needs to be.

It might be locked or something. What's the exact file name / path? Maybe a Google search will bring up something about it.

You can already turn those off in the settings.

It compares it sector by sector. The MD5 stuff is just an added bonus. It's calculated but isn't used anywhere, only displayed in the log.

I wouldn't worry too much, I often leave the door shut on one of my pc's too and the drives don't seem to care that the tray won't open, they just give up trying to eject it after a few seconds.

1. Renaming ImgBurn.exe is the old way of doing it. Read the entire thread (after which, I'll probably delete it because it's basically out of date now) and you'll see there's a version of DVD Shrink that supports ImgBurn properly. 2. Read the Guides forum, it's all in there if you take the time to look.

You could indeed try the 2.4x ones. I prefer them to the 8x version anyway. That said, the drive (and the 8 series in general) is pretty old now, now might be a good time to start looking for a different one.

There is a 'Guides' forum with a guide that tells you how to use 'Build' mode, please read it.

Are you sure it's the failure to close that's the issue with your standalone? I see the drive isn't set to booktype to DVD-ROM - if possible, it should be. If it fails to close straight after the burn but works later on via the manual method, I don't see why/how your standalone would complain.

It can vary between different media/image types (sector sizes) and a firmware update could change the way the drive makes use of the buffer. Seriously, don't worry about it. Unless it's always on 0%, you're fine.

It wouldn't matter either way. I think it does though, but don't quote me on it!

Are you running it on a laptop or a normal PC? If it's a normal PC, why can't you just plug it in via IDE? Then you wouldn't have these issues