LIGHTNING UK!

That one! A quick comparison of the logs would probably show if dvdfab uses different settings. There's not much you can do via CLI only so unless it's passing it's own settings ini file, there would be no real difference between running ImgBurn with CLI arguments and running it without (i.e. directly).

DVD 43 is nothing to do with ImgBurn and there's to be no talk about copy protection on this forum - sorry. If you have an actual problem with ImgBurn (when BURNING), we'll be happy to help.

Your drive is reporting a 'Write Error'. You could try slowing the burn down to 6x, 4x or 2.4x but really you should think about switching over to Verbatim media - simply put, it's better.

You'll probably find all I/O is locking up whilst windows deals with the request (ImgBurn isn't in control at this point) and so the buffer won't help. In any case, I've upped the limit to 512MB in the next release.

verify your burns too.

That's on the 'Appearance' tab within the display properties - it's called 'color scheme'.

You'd want some sort of DVD (re)authoring / editing package. ImgBurn is just a burning tool.

Try updating your firmware first. http://www.benq-eu.com/support/downloads/d...lk%2fg7v9%2ezip If it still doesn't work once you've updated that, get some better discs - Verbatim or Taiyo Yuden. At the moment the burning is running into some issue and then resetting itself (or being reset by the driver/OS) - probably due to a timeout.

It would have been the firmware up that did it. The other stuff wouldn't have made/doesn't make any difference.

Depending on the operating system you're running, the program takes it's look from the 'Theme' you're running. Take a look at the screenshots on the main website. http://www.imgburn.com/index.php?act=screenshots That's the program running under the default Windows XP theme in blue. There's also a silver and green version that you select via 'Display Properties' (Right click your desktop and choose 'Properties' off the menu that pops up). So basically what I'm saying is that the colours are not controlled from within ImgBurn, they're system wide and apply to all applications, windows explorer itself etc.

You've probably just got the wrong media for your drive. You want the 2.4x verbatim discs with the MKM-001-00 dye not the 8x ones with the MKM-003-00 dye. There's also a firmware update available for the drive here: http://support.us.dell.com/support/downloa...p;fileid=132121

Just pressing F8 makes it hang?! Sounds as if you have much bigger problems then as all that does is set a variable in the program to 'true'. I'd start by looking at any programs you're running that are supposed to keep you safe. i.e. antivirus, antispyware/malware etc. They're the ones that hook into the OS and therefore most likely to mess things up.

The look / colours come from your windows config and the theme you have running (applies to XP and Vista).

It doesn't look like your drive supports that media properly - the drive is getting on a bit now and won't support newer/faster media. Get yourself some 8x Verbatim or Taiyo Yuden discs. Of course you could always invest in a new burner, they can be picked up for under

You can't force a drive to do anything. ImgBurn is already asking it to burn at 2.4x if that's what you've selected. It can't do any more than that.

I don't think this is related to the drives at all, if it were, the 'Create image file from folders/files' would still work. Also, most the drive stuff is done in threads and so the GUI would still paint itself even if the drive code gets stuck. Your best bet would be to load the program, press F8 to enabled debug mode and then press one of the options on the mode picker screen. If it's I/O related the log window might tell us something, but really I need the last bit of text from the statusbar.

They'll be white if you put another window on top of them and then close it, I'm sure they shouldn't be otherwise. Do all the various options on the ez-mode picker screen make the program freeze? What software have you actually installed on that build of XP SP3? It's a bit of a weird issue for the entire app to get stuck like that... it's certainly not anything I've ever come across before.

You can't make an Audio CD image from the files using ImgBurn. The only way to do it would be to make the CUE file via the 'Create CD CUE Sheet' function, mount the CUE in DAEMON Tools and then create an image from the DT virtual drive using Read mode. That would get you another CUE/BIN file. (you can't have an Audio CD (CD-DA) as an ISO file) I'm not really sure why you'd want them as an image though, surely they're more flexible and easier to play when left as wav files?

I take it there's nothing useful written in the status bar? When frozen, is it consuming cpu cycles?

Ditto Happy Birthday!

We really need to see what the error says. Can you post the full log after it's actually failed? Oh and upgrade to the latest version of ImgBurn too. There's also a YYS7 firmware update available for the drive: https://sales.sony-semicon.co.uk/sunshine/i...;desc3=Firmware

Glad to hear it

You can actually get the A106 firmware for that drive from here: http://lgodd.lge.com/fwdrv/DVD-WRITER/GSA5163A106.exe Cut a long story short, ditch the Ritek discs and buy some Verbatim 2.4x DVD+R DL (MKM-001-00 dye) instead. The ones made in Singapore are the best.

It wasn't a silly example it was the truth and I'd hoped you'd actually follow it and get the whole idea... obviously not! The files you've got/are looking at are meant for easy burning. That's what an ISO does, it makes for easy burning. It's very hard for the user to f*** things up. Take a DVD Video disc for instance... You *could* just be provided with the raw IFO/BUP/VOB files and then be smart enough to know what those files are and the type of profile / wizard / options to use in your burning software to stick them on a disc *PROPERLY* so it's playable, or you could be given the ISO instead and not have to worry about anything - you burn it and it just works. Of course what this doesn't account for is idiots that make ISO images from files that aren't playable in standard devices - i.e. ones containing avi (divx etc) files. When that happens you just have to feel sorry for them and pray that they grow a braincell sometime soon.

Check you've got the correct options ticked for including 'Hidden' / 'Sytem' files and NOT the one that ONLY includes files marked with the 'Archive' attribute.