LIGHTNING UK!

For ImgBurn to do it automatically all the time, you need to go into that advanced area - otherwise you'll have to set it manually each time you burn - and that's just annoying!

I'm sure the bios update will come with instructions or they'll also be linked on the bios page, just take a read of them. Giga-byte probably has a website in your native language so perhaps you should lookup your motherboard model on that one - 'GA-EP35-DS3R'.

Oh you're READING a disc... if it won't read then it might be protected against copying - and we can't help you with that.

You need to post a log of a failed burn. At the moment though, I'd probably just say the drive doesn't like the CD's you're using. Make sure the firmware on the drive is up-to-date and invest in some decent Taiyo Yuden CD-R's.

Can't you just turn off ffdshow for mp3 files? It's not like it's required anyway as the media player can play mp3 files just fine without it. That said, if the burnt files sound odd then it's something that ffdshow (and the filters it uses) is doing and either the configuration needs fixing or its actual code does.

Install what new window?! I didn't think we'd spoken about reinstalling windows? Just go for installing the bios/drivers. Start with the bios, then install the Intel Chipset INF, then the Intel Matrix driver set (which may or may not actually install depending on the 'mode' your sata controller is in) and finally the JMicron driver.

Oh you want *me* to implement and autoupdater? I have no interest in that, sorry. Telling people that there's a new version and linking to the website is enough for me.

Ok well I guess this is the support page for your motherboard... http://www.gigabyte.com.tw/Support/Motherb...?ProductID=2743 On there you'll find a couple of bios updates (you only need the latest). You can then also update the driver for the 3rd party IDE controller via the file here... ftp://driver.jmicron.com.tw/jmb36x/Win2k_xp_Vista/ That's the official jmicron driver and I know that gigabyte kinda give their onboard controller the 'giga-byte' name so it *might* not install, in which case just download the one linked on the support page under 'drivers'. It's gigabyte v1.17.36 Versus JMicron v1.17.37 (or v1.17.38 beta - which is what I'm running) You can get the latest Intel Chipset INF drivers from.... http://www.intel.com/support/chipsets/inf/ and the Intel Matrix drivers from... http://support.intel.com/support/chipsets/imsm/

Keep to your own thread, it gets messy otherwise.

It defaults to 'Auto' so something else must have messed with it if there's no chance that you did (even accidentally).

What controller is your drive connected to? What motherboard do you have? What drivers have you installed for the controller? It's very important that if you're using a 3rd party controller (which you'd have to do if you have a recent motherboard because they (Intel ones at least) no longer come with an IDE port ) that you keep the bios up-to-date and use the latest drivers. Not all 3rd party controllers like optical drives very much.

laseractive, that's what happens when the I/O layer of windows gets hung up - NOTHING will get processed/open because everything needs I/O, hence you're forced to press the reset/power button.

I've no idea how to do a 'softlink' but I understand the concept. As you know, the silent install is an NSIS thing and it's /S I believe. What I don't allow is silent running of the actual program - i.e. trying to hide it.

Maybe your AntiVirus software or some type of anti spyware tool is conflicting with it. See if it loads up when you start windows up in safe mode.

I doubt that drive even knows about the MKM-003-00 dye, it's probably just using some default write strategy - and it's failing.

Make your own thread please and you might like to look in the faq about enabled I/O debug mode so I can see which command it's stuck processing (pressing F8 whilst it's open - and before you close it! - might be enough). Then just copy + paste the extended log. (you might need to go via a text file in notepad if it's too long and then upload the file) Oh and put it back on spti - probably best to uninstall and reinstall again.

Personally I'd have gone for Verbatim UltraSpeed CD-RW's, that's what I use. Drive wise, go for one of the new Optiarc models or something. You're probably better off visiting the cdfreaks.com forums and seeing what people have to say about the various new models from different manufacturers.

So if it's just the DL discs that don't work, go with swapping your Ricoh discs for some better quality Verbatim ones.

It might also help if you can tell us exactly what's changed (if anything) since you last burnt without any errors. i.e. you got a new burner, opened a new pack of discs, updated some drivers, updated the drives firmware. All those things are important when trying to troubleshoot. Of course the first thing anyone on this forum will tell you is that you're playing Russian roulette by using anything other than Verbatim DVD+R DL 2.4x (MKM-001-00) discs. That drive also only appears to support 4x, 6x and 8x on that media so setting the write speed to 2.4x isn't going to do anything, it'll still burn at 4x (as that's the slowest it supports). You could try the faster speeds, they might actually be better.

The ISO file is a container file and within it you should find the video_ts folder and all the other stuff. Burn the ISO in Write mode and then look at the disc in explorer / my computer...what do you see?

Post the entire log please.

Post the whole log please and make sure it's from v2.4.1.0

open the case and move the cable What drivers did you download / install? What motherboard do you have? (if you know)

So it's part of the indexing service really, doesn't sound that important to me?! Maybe you can use this info to disable it for your optical drives - you might need a disc in the drive first? http://nzpcmad.blogspot.com/2007/01/window...hard-drive.html There should certainly not be a 5 minute wait. The program retries the lock 5 times before erroring out, with a 1 second pause between each. If it's taking significantly longer than that then the OS is holding onto the function call for a LOT longer than it should do. Maybe it tries to ask the programs to let go of the handle and they're just not playing nicely - so the OS has control for 1 minute per request or something (which ImgBurn doesn't know about). I've never seen it take anything more than 5 - 10 seconds to bring up the error box or I might have already done something about it (i.e. not performed so many retries!)

That means you have the drive connected to a controller with bad drivers that don't support optical drives. Try and find an update for them or more the drive to a different controller.