LIGHTNING UK!

Erm..... no! lol

You've probably hit the glitch in v2.0 with DL burns and 32k padding. Wait for v2.1

The buffer drops when WOPC kicks in to check the quality of the burn, it's totally normal.

That would only work if Build mode always worked with a single folder - which of course it doesn't. Depending on how you add them to the 'Source' box, the drop down list may contain some of the previously selected folders.

It meas you're attempting to write/read beyond what the drive considers the end of the disc.

Looks just like your drive (with that firmware version) doesn't support the media.

DellE1405, Just which guides were you looking at exactly?! There are like 4 new ones in the 'Guides' section that clearly show you how to burn from a bunch of regular files.

Cheers bootsector, donations are always very much appreciated.

Ok so it's just an ISO. Like I said earlier, if there's stuff missing, it's missing in the ISO file - and that's nothing to do with ImgBurn.

What's making the ISO in the first place? If the data isn't all there and ImgBurn didn't make it, it's not really ImgBurn's problem.

An entry where SPLIP = No is just the most obvious choice for a layerbreak position as normally the original one will be configured like that. It is by no means vital. The program will automatically mark a cell as SPLIP = No when you select it if it's originally set to 'Yes'.

Already done for next release. The image details prompt should also already show 'Volume Label: [Not Configured]' as a 2nd reminder.

You should NEVER ignore the layerbreak positions - unless you know exactly what you're doing and have a VERY good reason for it. If you only have 1 option, select it. It doesn't get much simpler!

Hmm a 'Write Error' in test mode... good effort! You might do well to find out the real model of that OEM LiteOn and use its firmware instead. OEM's tend not to do updates. I've never seen GSC media before but it certainly wouldn't hurt for you to try some decent 'known' (+ tried & tested) brands such as Verbatim MCC and Taiyo Yuden.

Yup, I fully understand what it is that you're after and why, I just need to know all the potential errors that Windows can throw up if a program tries to open a file that it's using. 'Access is denied' is an obvious one. There could also be ones like 'sharing violation' etc. I need to build up a rough list so I know exactly what to check for and what therefore what to apply the 'ignore' to automatically.

Hmmm... without doing any major checking as to why a file cannot be opened / read etc, I will add an option to not prompt when you get an 'access is denied' error. Is that the error you're typically seeing when files are in use?

Ok I've added a '/NOSAVESETTINGS' CLI switch.

1. Verify is persistent over multiple queued burns. 2. It's there because it's there. No reason to remove it. 3. That's not gui related but I get your point. It just displays whatever's in the filesystem. 4. Again, it's there because there's no reason to remove it. 5. That's not ImgBurn's job. Regional codes are also considered copy protection which of course ImgBurn will never touch. 6. Right click the 'label' text shown in the main gui. 7. Been done for a few weeks in beta version.

Put it this way, if you have something and you want to put it somewhere you have 2 possible outcomes. 1. It fits. 2. It's bigger than the place you want to put it. If it's number 2, you can either make 'something' smaller or make 'somewhere' bigger. 'Somewhere' can only be made so big, so there comes a time when 'something' has to be made smaller regardless.

I'm sure it's all possible by just checking/unchecking the right options on the 'Restrictions' tab. What are you after exactly?

All I could suggest is that you make a folder and copy the contents of each disc into it. Use that folder as the root for your cd image and copy the volume label of the first disc. If that doesn't work, you're pretty much stuck. Can't you contact the original author and ask for an updated version?

Nah, it just stops supplying the drive with data - so the burnproof type feature kicks in. So long as that works ok (no reason it shouldn't), the burn should continue just fine.

Press the cancel button!

I assumed we were already talking about build mode db. I'm not sure why you'd ever make a temp file for burning an ISO?! Nothing ever goes to a temp folder (except displaying IBG in DVDInfoPro), it's all done in memory. As it's reading lots of files from your hdd, maybe it is some sort of indexing issue - that or antivirus maybe? Have you done a transfer rate test of the drive under Vista to ensure it's running at full speed anyway? Maybe the drivers are limiting it or something.

Well, the guy didn't specifically ask anything about bitsetting!