LIGHTNING UK!

LB issues normally only show themselves during playback. You must have a very picky drive if it just flat out refuses to play the disc at all!

I'm not sure that's a LB issue, it's probably a media readability issue.

I hope (s)he knew what I was talking about

The File I/O is done using standard Windows API calls, I'm not sure there's much room for improvement.

If UDF worked, it wouldn't be displaying the ISO9660 filenames. Joliet is limited to 64 chars in the filename - unless of course you relax the restrictions. You can also do that for ISO9660. It's really just down to you to figure out what works/looks best. You can't do anything with the discs you've already burnt - unless they're rewritables. Live with them or throw them in the bin.

Sorry, my mistake, I thought that feature worked differently to how it does I'm adding a new option to the 'Drive' submenu right now. (The same one that's in the 'ISO' menu)

Use the feature in the tools menu.

lol your media went from bad to worse! Get some decent Verbatim (MCC dye) or Taiyo Yuden discs. If it still fails with those, throw the drive in the bin.

Just click continue and it'll write anyway! No need to step back and revert to another program!

Indeed, don't use Shrink to make DL images, output to a VIDEO_TS folder instead and then use ImgBurn's build mode.

Now you've fixed the hardware issue (new 80 wire cable I assume?), follow the post in the FAQ about DMA. You just need to uninstall the IDE controller entry from within Device manager and reboot. You should also ditch the CMC media and get some decent Verbatim (MCC) or Taiyo Yuden stuff. Most modern drives will slow themselves down if they realise the burn quality is quite low on the media they're writing to.

There's obviously some issue getting the data to your cd/dvd burner, NOT getting it from the hdd into the software's buffer. Like I said, you'd be better off dropping the buffer size back down to 20mb / 40mb and letting Windows use the rest for whatever it needs it for. Besides messing with DMA stuff, there's not much you can do if the machine just can't get data to the drive quickly enough. (Of course DMA doesn't apply to the USB device though) Is your CPU usage high when burning? Have you tried creating an ISO and then burning that rather than burning lots of smaller files on-the-fly? Any luck on getting that IBG file? Just click on the 'File' menu, then 'ImgBurn Graph Data' -> 'Export'.

It's the same as burning any image. Open the program in Write mode, select your image, insert your blank disc and click the 'Write' button. There's a guide for burning images in the 'Guides' forum. You don't need to worry about booktype stuff, the Pioneer drives do it automatically.

Does the device buffer drop off slowly to 0 or is it always on 0? A log of the burn might come in handy, along with the IBG data file. As you've seen, the big buffer doesn't always help avoid buffer underruns - and of course it ties up RAM that the OS could otherwise be using. Interruptions normally stop transfers between the program (buffer) and the cd/dvd drive. Those between the hdd and the program (buffer) are fast enough to recover quickly.

There's to be no discussion of *anything* where decryption tools are involved.

Try some other discs (Verbatim or Taiyo Yuden), at the moment your drive is just complaining because it can't figure out a decent power level for the laser that it can then use to burn with. A cleaning disc might help too. Oh and whilst I have your attention, update ImgBurn. The latest version is 2.3.2.0

Ignore the JMicron bit, you have a Via controller on that board by the looks of it, not a JMicron one. So if anything, you should be looking for Via drivers.

Try the firmware update as suggested earlier. http://h10025.www1.hp.com/ewfrf/wc/generic...=reg_R1002_USEN

Looks like you're getting corruption on the entire bus. Change your cable (make sure you replace it with a decent 80 wire one). Put the drive on 'MASTER' and attach it to the end of the cable (the other end being attached to the motherboard of course!). Check your bios setting to make sure UDMA is enabled properly and finally, follow the DMA post in the FAQ.

Optical drives are never really 100% when hooked up to 3rd party controllers. Some do work much better than other though and some don't work at all. You've probably got a jmicron controller on your board, that's what most motherboard manufacturers use. What you need to do now is look in 'Device Manager' and find out exactly which chipset / model it is. If you open up the 'SCSI and RAID controllers' branch, you should see it listed in there. (If it's not in that one, look under 'IDE ATA/ATAPI controllers') Tell us what you see (or provide another screenshot of device manager with those branches expanded) and one of us will hunt out the latest drivers for you. They might just fix the issue if you're lucky! That is of course assuming it's *something* to do with that in the first place. It could just be a bad drive/media/write speed combo. I've no real experience of the 8x Verb DL discs, I always buy the 2.4x ones and they burn ok in my Pioneer 112.

Have you tried burning at any of the faster speeds the drive supports? The 965 chipset doesn't support the legacy IDE ports/connectors now so you're running the drive on a 3rd party controller. It might be an idea to visit the website of whoever makes it and look for some updated drivers.

No. Don't think of the layers as individual data containers or 2 different discs stamped together, they're not. To the software, it's all one big disc really. There's nothing to say a file won't cross (span) the physical layer break - i.e have some of it's data on the first layer and the rest on the 2nd. When you address the sectors of the disc, they just go up in sequence from the start of layer 1 to the end of layer 2. i.e. Start of disc (LBA): (start layer 1) 0, 1, 2, 3.... 14, 15.... (switch to layer 2).... 16, 17, 18... 29, 30, 31 (End of disc). All in all, the disc goes from LBA 0 to LBA 31, with the phyiscal layer break position somewhere inbetween.

If the hdd can keep up with the random access reading, yes. As you say, just open 2 instances of ImgBurn.

You're trying to do something that simply isn't possible! If you have an ISO file and only want *some* of it's content, it's down to you to remove it. ImgBurn simply burns exactly what it's given. Mount the ISO in DAEMON Tools or something and then just drag over the folders you want on the disc into the 'source' window. I suggest you put the options on the 'Media' tab back to their default values.

Your drive simply isn't burning the discs properly. Maybe it's time to ditch that old one and invest in something up-to-date?