LIGHTNING UK!

DVDFlick forces the settings on you because it specifies an ini file that ImgBurn should read from and then tells it not to save changes. If you use the program in 'standalone' mode, you won't have these problems.

It reads as much as the 'read capacity' command reports. If it's off by a few sectors, ImgBurn won't read them. You can see pretty clearly in the log window / info panel on the right just how much the drive thinks is on the disc. What does it say compared to what you expect to be on there? Also, when you load the image to burn it, does it not report the full / correct size? There shouldn't be any reason for it to cut it short - unless the data isn't a full sectors worth - it'll truncate odd amounts of bytes.

Loads of the commands are failing with the error: E 16:27:45 SENSE Interpretation: Unknown (0xA8, 0x03) Contact pioneer and see what it means, they're the only ones that can tell you / help you.

The drive is either reporting rubbish or there's some form of corruption going on. Check you've got the drive on a decent 80 wire cable and that it's set on either master or slave (check it's position on the cable too). Then follow the DMA post in the FAQ. If it still won't work, use the 'Filter Drive' option in the Tools menu and copy to clipboard + paste all that info. You could also eject the disc from the drive, press F8, insert the disc and wait until it says it's empty before pressing F8 again. Save the log to a file and upload it.

If the drive doesn't like the media, there's nothing you can do about it I'm afraid. Software can't do anything until the hardware recognises it properly (which yours isn't). See if a firmware update fixes the issue, but failing that, you'll have to try some different discs.

Take a hint please.

This is nothing to do with ImgBurn, search Google or something.

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