LIGHTNING UK!

Thanks, that one looks better. I guess with...

ok so when you build the cue it doesn't actually work properly but you save the cue file anyway and try to burn it - correct? That's when you get the 'in use by another process' error? Of course if you take a quick look at the 'Hint' text in that error box you'll see what the inital problem is.... you need to install an APE directshow filter. You can get the one I've tested with from here: http://www.free-codecs.com/download/RadLig...Show_Filter.htm

Do you also have a disc that's writable? As mmalves picked out, the size was all wrong for that DL disc in the log you posted but ImgBurn still let you try and burn to it - meaning it thought it was still empty. That's the one I'm interested in seeing the disc info for if you're able to reproduce the situation!

Burning images or just little files? I've done dummy image burning before (making ImgBurn skip the code where it actually burns to disc) and it easily maxed out my LAN... and that was up in/nearer the 40mb/s region.

Sorry, no.

Ok, what you need to do is put the disc in the drive that Nero made and ImgBurn burnt (i.e. from the top log) and then add that drive to the 'Source' box in Build mode. i.e. put the disc back in your E: drive and add 'E:\' to the source box in Build mode. Then click 'Build' to make a new ISO and burn that ISO to a new disc. That way we've got 2 discs with identical files, 1 of which you know works. So if the 2nd one doesn't it must be down to the filesystem implementation. If that's the case I'll get back to you with more instructions so I can figure out why

I didn't think it classed it as a failure with the options set like that... it shouldn't be asking you to acknowledge anything. I'll look into it.

Please do me a favour, put that same disc back in the drive (in Write mode) and copy + paste all the disc info text from the panel on the right.

Do your editing in the GUI, then save the project file. You don't write them by hand.

I honestly have no idea. The best thing you could do right now is treat yourself to a new (

It should be fine. Why aren't you burning it to a normal DVD-R or DVD+R disc? It's not big enough to require a DL one.

I don't think it's related to the drive at all. Drives follow the MMC specs so they *should* all behave in the same way. Yours is new so it definitely shouldn't have any of the problems that I might associate with drives that came out when the MMC specs were still in their infancy. Can you confirm that when you tried it on the ICH9 controller (whereby it didn't hang but you got a 'No Seek Complete' during the burn - right?), you were indeed running the v8.5.0.1032 Intel Matrix software/driver available from here: http://downloadcenter.intel.com/filter_res...mp;submit=Go%21 That marvell controller seems to be a pain to find a driver for! MSI don't seem to list any for it on any of their pages... weird! Could you please get a screenshot of what the controller is displayed as when looking in device manager? It'll either be in the ide/atapi controller branch or the scsi/raid one. Once you've done that, bring up the properties for it and get a screenshot of the 'Driver' tab. Then I just need one more from the 'Details' tab when 'Device Instance ID' is selected in the drop down box. That should be 3 screenshots in total. Thank you!

When your drive/drivers stop responding to commands you pretty much have to give up and cycle the power. It would appear that's just how I/O works in Windows. It's not ImgBurn that's hanging, it's something further down the chain. ImgBurn is just waiting patiently for a reply and isn't really in control at this point, hence why you can't close it. What do you have in your filter drivers list? (Look in the Tools menu within ImgBurn) Is your drive on a decent controller that supports optical drives properly? Do your controller drivers support optical drives properly? Are they up-to-date?

So you're saying that with 'Finalise Disc - Auto Retry' unchecked and 'Ignore Finalise Disc Errors' checked, the resulting disc still doesn't work?

There's an option to force a command to be sent prior to burning that invokes OPC. Even if it's off there's still a chance the drive will do it anyway and that's something the firmware has told it to do (i.e. nothing to do with ImgBurn) and cannot be avoided.

tsk tsk sticking with versions of a program that have known bugs because of that stupid old 'if it ain't broke, don't fix it' saying... what is the world coming to?!

You're building/burning to disc on-the-fly. (i.e. 'Output' is set to 'Device' rather than 'Image File') Build mode can do that OR it can build an ISO (which you'd then need to burn to disc in Write mode).

Nope, I've burnt APE files just fine. For whatever reason, the standard 'CreateFile' API command is failing on your PC when ImgBurn tries to use it to open that file. That is kinda interesting though because you said you made the CUE file yourself in ImgBurn yeah? What does the 'Create CD CUE File' window look like once you've added your files to it? Can you provide a screenshot? I'd be interested to see what the 'unlocker' program says is using the file - if anything. Please do give it a try, you can always uninstall it straight after.

That's the important one, ignore the others. btw, ImgBurn booktypes to DVD-ROM automatically on supported drives (which yours is - or rather 'can be' once you've configure it in the 'Advanced' section of the booktype window), so you don't need to do anything.

I guess if Roxio issued that exact command then it would also hang. Obviously it's not a command that *should* get stuck (or ImgBurn wouldn't work for anyone!) so it must be down to your drivers somewhere along the line. Optical drives do not like being on RAID controllers. Is yours actually running in RAID mode or is configured as AHCI in the BIOS? Even something as simple as updating to the latest Intel Matrix drivers could fix this... but really you want the drive off the RAID controller. As a side note, drives are fine when the ICH9

If that's the first one you've had fail, just ignore it. The drive is in complete control and so if it says it can't burn to the media, it can't burn to the media. If it starts happening with all the discs (are they made in Singapore?), you could try a new spindle and hope that they're better (get the made in Singapore ones - but still using MKM-001-00 dye!) or perhaps consider getting a proper 'full size' burner. Laptop drives are always pretty rubbish.

No, you're still at a dead end because you can't stop ImgBurn from finalising discs Turn off the finalise disc auto retries and it should be ok in your player though.

Ahh, deepburner doesn't actually finalise the disc at all, it leaves it open so you can add more to it. The drives only mess up when you finalise the disc. The 'working' retry thing is bogus and I very much doubt the drive actually does anything as a result of me repeating the command. Once the initial attempt has failed, the drive has already screwed the disc up and that's why it doesn't play nicely in all players.

You too MrWizard? Read the 'Pinned' topic at the top of this forum.