LIGHTNING UK!

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.

Ok I've finally found an image to let me replicate it. I'll do some debugging and try to see what's up. It's not my program though so I don't know if I'll be able to fix it.... I'll keep you posted.

If you install over the top then settings are preserved. Only if you uninstall will they get removed. Also, it could be a project you've loaded that changed the setting, or a 3rd party app that calls ImgBurn for burning. Either way, at least you will know what to do next time it happens

When you say it's loading but not displaying, where in task manager is it visible? Just on the 'Processes' tab or on the 'Applications' tab too? The next time you notice it's not popping up, take a quick visit to the temp folder and grab a copy of the ini file passed to the previewer exe. Then have a go at calling it yourself from a command prompt window and see if it does the same thing. i.e. ImgBurnPreview.exe "ImgBurn_Preview.ini" Also, when it doesn't work for a given image, will it never work no matter how many times you terminate + retry it?

If you take 'GWA4164B' and put it into Google, the first result certainly doesn't look promising! Maybe the drive has just had it?

Nope, it's deffo NOT on by default. Never has been.

Looks like a bug in the drives firmware to me. Is that the only drive you have? The same initialisation commands are issued for all drives so it's a good way to check if it's a system wide thing or not. (i.e. unplug the one that doesn't work and try it with the others)

You've ticked 'Preserve Full Pathnames'. Simply untick it.

It's already been done. http://www.imgburn.com/index.php?act=download

99% of people wouldn't even know what FAT32 was if you hit them round the head with it.

No problem here... any chance of a screenshot of the LB + preview windows clearly visible?

It shouldn't need a 'retry' to make it finalise properly, that's the whole point TSST drives are by far the worst for this problem. Have you tried changing the 'Write Type' yet as mentioned earlier? Or enabling 'DVD+R Reserve Track' ? I'd be interested to see if those discs then played on your standalone. btw, what are you burning there... I ask because you're only using the ISO9660 file system rather than Joliet or UDF. Is there a reason for that? If you've got a working (in the standalone) disc anywhere, make an image in Read mode and then use that as your source to burn in Write mode - just to rule everything else out.

The firmware won't fix the locking problem, that's software/OS related.

I've no real interest in implementing multisession support as I personally feel it's a waste of time. If I want my files on media where I can keep changing them then I'll use a USB pen or maybe mess around with a FAT32 formatted DVDRAM disc.

ImgBurn always finalises discs when they're burnt. That kind of mutisession is not possible and you'll have to use a different tool I'm afraid. The option in the settings is so that no matter how much (little) you burn on a DVD+R, it'll tell the drive to pad it out to a pre-definded amount (roughly 1gb I think). This helps make it more compatible with readers. It's nothing to do with the issue you're facing.

A screenshot of what you're seeing would also help.

Try flashing it again, I have the B107 on mine and it's been fine.

Damn, more invisible PIE/PIF spikes! Fancy seeing if CDSpeeds actually shows them? I'm not sure I have any Sony D11 discs or I'd run a few through my S203B to compare. Do you have any other media that also fails... maybe I'll have those?!

You've got some rogue pif spike in there (that's not even visible on the graph), the burn quality is the same on both otherwsie! Don't scan at max speed. Use 4x. Change the 'Scale' fields to Auto. btw, cdburnerxp might not catch the errors that ImgBurn is catching. As an end user, you've no real way of knowing as you have to snoop on the I/O calls. I don't hide anything from the user, what you see is what you get. If the drive reports an error then you'll know about it. Not all software works like that. ImgBurn also has a whole load of options that you can mess around with to see if it helps you out with your drive. For example: Write Type DVD+R Reserve Track