LIGHTNING UK!

Settings -> Write tab -> 'Prefer Format Without Spare Areas' Then do a full format.

fordman, You're not interpreting the debug log properly, that's all. The 'access denied' stuff is nothing to do with the actual locking. As mentioned a million and one times, process explorer will help you find out which app is also using the drive, preventing ImgBurn from taking exclusive use of it. DVD Fab seems to keep a handle open to all drives all the time, that's why the lock failed - and it's failed in ever version. I added a switch in 2.4.0.0 so apps that call ImgBurn via CLI (knowing full well they'll prevent it from locking the drive) can tell it to ignore the 'Access Is Denied' error. THAT is what fengtao seems to have added support for in his most recent release.

Actually no I've not changed those. EDIT: Have now

It's no biggie, just click Ignore / Continue if you say the drive has been able to burn those discs before. Maybe they're not quite good enough to pass OPC. I'd still look at updating the firmware on the drive and finding some better ones though.

So it just needs 'Entry VOBU Sector' and 'Last VOBU End' info added (complete with a conversion to MB) for Cell 7 of VTS_01, PGC 1? (Obviously that last bit changes but I use it as an example)

Yes

I thought IsoBuster was free? You just pay if you want a 'better' version.

Ok, it didn't take 5 mins to do so I've done it.

I'm not sure 'Bug' is the best way to describe this, it's 'by design' that the program won't build anything until you've added something to the Source box. Don't other tools do that too? I'll consider it a 'feature request' and it's not high up my priority list because it's very easy to add a dummy.txt file. Can't you just burn the ISO 'as-is' anyway?

FYI, exactly what it shows depends on what it needs to change to be 'compliant' - i.e. it only shows what needs changing.

Would this work?

Try speeding it up a bit! These days it's more about OVERspeeding and getting a great burn than burning as slow as possible. You might also like to mess around with the drives 'Advanced Settings'. i.e. Turn Force/Online Hypertuning on.

It doesn't adjust the GUI, just the internal settings (after GUI options have been applied) - as it sets some weird stuff that I don't want users to 'forget' to change back. Burn and calculate are totally seperate... or rather they're exactly the same but options selected during Calculate are not remembered (unless they do actually update the GUI). As for which settings are changed, it's the following: ISO9660 Interchange Level - Level X ISO9660 Character Set - ASCII ISO9660 Allow More Than 8 Directory Levels - Enabled ISO9660 Allow Files Without Extensions - Enabled ISO9660 Don't Add Version Number To File Identifier - Enabled and if the Joliet FS is present... Joliet Interchange Level - Level X Joliet Allow Files Without Extensions - Enabled Joliet Add Version Number To File Identifier - Disabled

Nope, it's for locking the burner so nothing else can access it and mess up your burn.

No so much with ImgBurn as your system! It retries 5 times with a second between each and I've never seen it take any length of time to fail once the API call has been made to perform the locking. So basically it should take 5 seconds before it errors out - assuming it fails all 5 times of course. The code behind it hasn't changed so I'd be very surprised if previous versions act differently. Are you sure nothing you've installed is using the drive but actually letting go of it (VERY slowly) so the lock can succeed?

Googling 'PreGap' will give you a better answer than I could. I know what it is in technical terms so far as burning is concerned though! WMP doesn't support CD-Text. Audio discs don't have names/volume labels. There's no file system to store one in. When ImgBurn loads the image (in Write mode etc), it makes one up based on CD-TEXT info if it's present. Use Ansi if you want to burn/mount the CUE files in other programs - not all of them can read Unicode ones. If you've no interest in that, set it to Unicode all the time.

DVD Flick and ConvertXtoDVD will both do the job. DVD Flick is free, ConvertXtoDVD isn't (but then it does more).

namchik, ok, will do. Can I just point out that the 'SOURCELANGID' should be 2057, not 1033 as it is in your translation. I've corrected the one you sent me and will upload it. I hope the other guy doesn't mind his not being used anymore... I'm taking you on your word that yours is 'better' !

Leave it on 1.02, it's the most compatible. Only change it (to 2.50 or 2.60) when burning HD DVD or Blu-ray. Just to be clear, when you say 'music' do you mean as an audio disc (CD-DA) ? If so, that's not done in build mode. We have a guide for burning Audio CD. If you just want MP3's on a disc as mp3 files (to play in players that support playing mp3 files), that IS done in build mode. For avi and mp3 etc as files, you might want to enable Joliet too incase the player doesn't support UDF.

'Sort Files By Source List Order' in the settings on the build tab.

BeyondCompare is another useful tool for this... I use it quite a lot - although not for this purpose

I'm working my arse off to get things ready for releasing 2.4.1.0 at the weekend. Hopefully I'll manage! Sorry for any inconvenience caused.

Phew, just finished fixing it! It's a real pain when you have no idea how anything works... not even the development environment! There's a bit of code that seems to scan starting at the beginning of the file - no matter which cells you tell it to play. As you can imagine, scanning for vob pack headers right at the start of an ISO is never going to work very well and that's why the window took ages to pop up (if ever). This fix applies to loading image files and when examining a burnt disc directly so hopefully all 3 ways of using ImgBurnPreview.exe will now work ok!

You'll just have to live with the ones you've already done I'm afraid. Well, that or burn them again. The choice is yours

It's all fixed now. Burnt an entire cd on it lastnight and it came out fine.