LIGHTNING UK!

It's also the only way to perform a 'real world' verify - unless of course you don't ever intend on taking that disc out of the drive Sometimes drives can burn ok, but after cycling the tray, they decided the can't read back what they've written and fail to initialise (internally I mean) the media. As such, no software can read anything back from the disc as the drive always says it's 'not ready'.

Again, this comes down to something actually changing the error codes the drive is returning. I honestly can't see that happening! Driver wise, all you can do is get the latest chipset drivers and ata (application accelerator - might be called Raid Matrix or something now?!) software from the Intel site. That's what I do and (touch wood), mine is ok! Mine is the Intel 875 chipset, not sure what you have on that board (and I'm too lazy to search google )

No harm done. Sorry we couldn't help you.

Same difference really, it just can't write to the media. RMA time!

Eh?! Clearly that's the log of it FAILING to WRITE a disc - and it's not going to verify until it's written something properly! There are few things that look odd in that log but starting at the beginning.... go and update your drives firmware. http://forum.rpc1.org/dl_firmware.php?download_id=750 Get the 1S34 one.

I always use SPTI and therefore it undergoes the most testing! Stick with it unless you really have a reason to change! Glad you sorted out the crappy playback issue but I've no real idea why your buffer drops when you open something, it could be a virus checker or something. Basically it could be anything that locks out other processes while it does it's own thing. For the programs main buffer to drop off, it must be unable to read from the hdd quickly enough to keep it full. That's where the bigger buffer will help out. As you have plenty of RAM, that shouldn't be a problem. A second hdd away from the main OS drive would still be a good idea though

This isn't a 'problem' as such. One of the new features of ImgBurn is that it can parse the filesystem/IFO files and locate suitable places for a layerbreak. Normally, if you're using an MDS file, this is not necessesary because the layerbreak information can be taken straight from that. So in this instance, either you don't have the MDS file or the layerbreak position in the MDS file is not one that can be reused on an OTP disc - where it then falls back to the IFO parsing method. You just need to select the best place for the layerbreak out of the list you've got. It could well be that the options you've got are all the same - look at the LBA value - but they're in different PGC's or something. I decided (mainly because the app was new!) that it should show everything it found. This helps me figure out the best way to improve it and narrow down the results shown.

What are the choices? A screenshot may come in handy here

The only place a power calibration error should come from is a drive / media / firmware issue. Cables and stuff shouldn't really come into it. If you've read about lots of people burning the same media as you without a problem (and you're sure yours aren't fakes!), I guess you must just have a faulty drive. Take it back and demand they replace all the media you've wasted

It should have always been hardware related! Software isn't supposed to change the error messages a drive returns when something screws up.... that would be highly annoying! If you're worried, have tried loads of media and can't wait for an official firmware update, return the drive and get a different one.

Try not to burn from the same drive your OS is installed to. Also, ensure the burner is on it's own channel - away from the hdd you're burning from. If you do something that kicks the OS into doing some stuff, it may be running at a higher priority level than ImgBurn itself and so not only will it basically pause the ImgBurn process, it'll also take over the I/O. Windows can sometimes block out other processes when doing certain I/O functions and that's what's stopping ImgBurn from reading from your hdd. Try upping the buffer to 256mb or something. Perhaps that'll be big enough to stop it actually running out of data and burnproof kicking in. Also ensure your firmware it up-to-date. Burnproof kicking in should NOT mean you have a bad burn at the end of it! Are you using good quality discs?

You enable 'Show hidden Files' by opening explorer, clicking the 'Tools' menu, then 'Folder Options', then the 'View' tab. Select the 'Show hidden files and folders' radio button and uncheck the 'Hide extensions for known file types' checkbox.Then click ok. To remove the 'hidden' flag that's set on 1 specific file, right click it, click 'Properties', then uncheck the 'Hidden' checkbox. Then click ok.

Start -> Help -> Restore Point You should be fine with DT installed. I have no problems with it.

The buffer drops are just WOPC kicking in to check the burn quality is still ok. Nothing to worry about there Now keep installing your stuff until it breaks again... then you'll know what caused it!

Ah ok, your log was for a cd image (from your friend I guess). For a DVD image, changing the volume label wouldn't do anything to the EDC / ECC area - because ISO's don't contain that data in the first place! Obviously, as there is no EDC/ECC region, you wouldn't get a miscompare error like the one in your log! Yes try a perfectly clean rebuild. JUST install ImgBurn and then burn something.

No, you don't need to make an MDS file at all - and in any case, it still doesn't add layerbreak information to it. You'd just load the ISO in ImgBurn, it'll parse the IFO files at then time of burning.

Yup, if you're happy the cables and general machine config (bios wise) is ok.

The two apps are standalone, nothing gets deleted, uninstalled or overwritten. The bit you declined during the install of ImgBurn was nothing to do with the removal of DVD Decrypter, it was just to clean up your context menus so you didn't end up with 'Burn using DVD Decrypter' AND 'Burn using ImgBurn' when you right click an ISO image. Having both is pointless and as waste of space - hence why ImgBurn offers to clean it up for you. If the MDS file you have hasn't just been made by the 'Create DVD MDS File' option in the tools menu, the problem you're having with DL burns is that the images you're burning are from PTP DVDROM discs. You can't always burn such images onto an OTP disc because for OTP, Layer 0 must be bigger than (or the same size as) Layer 1. That is not true for PTP, where Layer 1 can be bigger than Layer 0. If the layerbreak position read from the MDS file is such that it cannot go on an OTP disc, the program has to attempt to move it. How well that works out is anyones guess! You should always use ImgBurn for DL burning now, it has other neat tricks that DVD Dec doesn't.

According to what I've read over at cdfreaks, BenQ forgot to add a write strategy for the MKM-001-00 discs into the firmware. That's why: 1) They only burn at 2.4x 2) They often fail to burn at all! Their next release should fix it.

I'd upgraded some of my UDF parsing code between dvd dec and imgburn. Only problem was, I forgot to update a certain variable with its replacement and it ended up making the 'file finding' function quit after reading info for about 39 files (which makes up 1 sector). As such, so long as the layerbreak position was in a file before number 39, it would be ok. After that, it wouldn't know those files existed and so program logic would prevent it from finding the layer break info in the IFO file.

Under newer OS's, I'm pretty sure Nero's ASPI DLL file is just a wrapper for SPTI - which is the default one in ImgBurn. As such, you'd need to install Adaptec's ASPI, ElbyCDIO or Patin-Couffin.

Well these errors are supposed to come directly from the drive. It seems very odd that some other program should be intercepting them and returning a bogus one! Have you tried using one of the other I/O interfaces? They may help you bypass whatever is causing the problem (if it's driver related). Otherwise I guess you have no choice but to rebuild again and test burn something before adding any programs back on. Maybe your IDE drivers (or lack of) are to blame... who knows!

Have you messed with the firmware on your drive? Power calibration errors are where the drive cant decided on the correct power lever to set the laser at for burning. That is most certainly a firmware issue. On the odd occassion it does get an ok (ish) level, it's still not good enough and that's why you're getting write errors. Stick with the official NEC firmware, at least then you can blame them when things go wrong!

Dragging this thread back up again.... Someone over at Doom9 had the same sort of problem. 5 mins later they'd emailed the 5mb chunk of ISO and 10 mins after that I'd found + fixed the problem. So I hadn't magically fixed it, but it has indeed been fixed now

[flame/sarcasm on] That would be the same as just burning normal files, as in 'data discs' as mentioned in a zillion other posts [flame/sarcasm off] Yes I hope this will indeed be possible one day.