LIGHTNING UK!

Post the log please. If the disc contains multiple sessions, the program will have created a multisession image. You can't tell the program to only read certain bits of the disc, it always reads the entire thing. So assuming the disc is what you say it is, I expect whatever you're using the examine the image with is at fault here. Try actually burning the image back to a CD-RW.

That's all down to the speeds a drive reads that media type at. Most bd probably read at at least 4x and that's just shy of 16x DVD speed - which of course a drive would only reach at the end of a single layer disc (if that).

When I made my initial comment, it's was purely based on the 1x transfer rate speeds of each media type. 8x DVD is faster than 2x BD That wasn't taking into account the drive not always burning at that exact speed (i.e. burning at 6x and then jumping to 8x). I also didn't consider the verify stage as that involved thinking about too many unknowns! (the read speed)

It's always written but the creation date can't be after the modified or last access date/time (and there's code in place to ensure that can't happen). Would that fit with the files you're seeing issues with? If you enable the 'Allow Non-Compliant File Creation Dates' option on the Advanced -> Restrictions -> UDF tab, the program will behave differently. Maybe you'll find this thread useful? http://forum.imgburn.com/index.php?/topic/14556-imgburn-not-always-preserving-file-date-stamps/

If it was an image you needed to burn with CloneCD, it wouldn't just be an ISO anyway. An ISO wouldn't contain the info required by a proper 'RAW' mode burn. At this point, I'd have to say it's either the source image that's the problem or your playback device (either the chip being detected or it not liking the discs very much).

If it's saying it can't read a file on your C: drive, you should start by checking a file with that exact name actually exists in that location. After that I'd probably run chkdsk on the drive and do a full surface scan. If the file is unreadable, your drive might be dying.

The game could be detecting your chip if it isn't a stealth one. Some games may require 'RAW' mode burning... which ImgBurn doesn't do. Try something like CloneCD and see if you run into the same problem.

Ok so the Optiarc overburning was never actually designed (and properly tested) to work with anything other than the decent Verbatim discs. If others work, it's more luck than anything. You've messed with the default settings to enable 'Perform OPC before write', disable 'Burnproof' and use a custom layer break position. Put them all back on their default values. The .DVD file supplies the correct layer break position (when set to 'calculate optimal'), you shouldn't be messing with it yourself. I doubt changing any of those will give you a working disc, so you're going to have to just buy the discs you know you should have bought anyway - Vetbatim 8x (MKM-003-00).

Try updating the firmware on the drive. http://www.firmwarehq.com/Lite-On/iHBS112%2B2/files.html Is the disc scratched / dirty at all? If so, clean or replace it. Your disc is currently unreadable, hence the failed reads and miscompares. You might also like to do another full erase/format on it.

You need to post a log showing you burning and verifying the discs.

That log doesn't show anything that looks like a problem. Try and find the right bit of the log.

Yes. Not all file systems support those time stamps. Sometimes the OS will make it up based on values from other fields.

2.5.7.0 came bundled with the ask toolbar so that wasn't perfect either. Opt out of offerings during install, follow OpenCandy's FAQ on how to not get any offers in the first place or just extract ImgBurn.exe from the setup program using something like 7-zip. You aren't without options.

What has she told you to burn to a disc? An image file (ISO) ? Follow the 'how to write an image file to disc' guide in the guides forum.

I don't know what you're talking about in your first post about something scanning your PC. Maybe you clicked on an advert and downloaded something other than ImgBurn itself? As for your follow up post.... Well, Opencandy is an advertising platform. It inserts a 3rd party product offer page or two within the installation wizard. You're free to opt out of them if you so wish. Good luck finding any sort of free app these days that doesn't offer you something in the way of a toolbar or browser. Even Adobe flash player and Sun's Java have done that for years.

I'm sure there are lots of things you could do, but you asked about making a bootable CD. I don't know if dldiag5 would run within Windows PE, that's something you'd have to test for yourself.

You need a bootable floppy disc image or an actual bootable floppy disc that you can then take an image of. The boot image needs to be one that loads DOS drivers for your optical drive - unless you can add the hdd diag program to the bootable floppy disc (before you take an image of it) / image (if you can edit it in the likes of WinImage)... and that would depend on the size of the diag program and how much free space there is. Then you add the diag tool exe to the 'Source' box on the left of the ImgBurn's Build mode screen and add the boot image to the 'Advanced' -> 'Bootable Disc' tab. Then burn it. Use a rewritable disc as it probably won't work correctly the first time Personally I'd go with Hiren's Boot CD / Ultimate Boot CD or a bootable USB stick!

It isn't exactly simple to do. You'd be better off finding a boot cd that's already got the tool on it. I'm sure it'll be on Hiren's boot cd or the ultimate boot cd.

It's actually showing the media id of the disc in that log... it wasn't in the previous one. Something weird is / was going on!

Try attaching it to the actual mainboard sata controller and not the jmicron one. If you must use the jmicron one, try it in ahci mode and install the latest driver from here... ftp://driver.jmicron.com.tw/SATA_Controller/Windows/

The first error is the important one and your drive returned a 'write error'. So it ran into an issue burning to the discs you're using. I doubt your drive can actually overburn double layer discs successfully (burnermax being enabled ok means nothing) and there's even less chance of it working if you keep using the discs you're using. Everywhere tells you to use Verbatim MKM-003-00 ones.

That's probably the one I also came across the same issue with. I updated my build, made a new CD and it worked ok. Any idea on the size of the disk you were attempting to use with it?

Take a screenshot and attach it in your post - you'll have to use the full reply method ('more reply options' button), not the quick reply box. Different drive settings (the hypertuning stuff) and OPC may improve the burn quality but you'd have to mess around burning and scanning to find which combination produces the best results. I've only taken the time to find what appears to work the best for Verbatim 8x 'MKM-003-00' discs.

You'll have to ask the person that made the guide... I have no idea. The current version of ImgBurn has more options for large files when using the ISO9660 file system... your version is old and out of date.

Post the screenshot of kprobe's scan result rather than the summary text please. That looks like a bad burn to me. Why not buy the Verbatim 8x discs everywhere / everyone tells you to buy?