LIGHTNING UK!

It would be good to know what drive you have too. Put one of your blanks in the drive and copy + paste everything from the little window on the right.

Well yeah, maybe a future firmware update will fix it... who's to say?!

Sorry I thought you'd already done that. By all means go back and test that, but like I say, I can't think of a single reason why it should magically work.

My link or Blu's one? If you used mine, it didn't work or you selected the wrong drive!

If something doesn't fit, ImgBurn only ever pads with 'nothing' (zeroes, digital silence, whatever) so hopefully that would mean it doesn't cause a click? By 'doesn't fit' I'm referring to when DirectShow reports one size for the file and the amount it decodes comes up a little short (in sector terms). Digital silence is also used for pre/post gaps. Are you burning PCM/WAVE data or decoding stuff?

The other way is to make an ISO and force the layer break position via the option in the settings before burning in Write mode.

FYI, the latest 'test' 20A3S firmware (direct from someone at liteon) is available here: http://www.4shared.com/account/dir/5572060...t_Firmware.html You want the 9V63WIN.rar one.

hmm verify failed so the drive thinks the disc is a coaster.

Sorry then but I'm all out of ideas. That command hasn't changed (they never do!) so it makes no sense at all that it's just not accepted when sent from the 2.4.0.0 exe.

I looked for firmware updates but I think the S in AD-7190S means it's SATA, PATA. The 7190S doesn't even exist according to http://www.sonynec-optiarc.eu/en/support-s...-ad-series.html but I know it's the same as the 7191S but without lightscribe. The latest for the 7191S is still 1.01. You could cross flash it to a LiteOn DH-20A3S and be done with it!

You get the real pioneer firmware from the pioneer website. Extract the zip and you'll see 2 files. Load up the non exe one into MSCE ( http://ala42.cdfreaks.com/ )and tick the option to enable bitsetting. Load the exe up and flash away

Is this on every burn you do? How many have you tested? If you re-enable the 'Verify' option, does it pass ok?

Personally I'd go for the real Pioneer one and use MediaSpeedCodeEdit to patch in the bitsetting stuff.

Not quite... 'can't get a fix on' is the same as 'can't lock onto'. (Think 'satellites' ) So basically it's trying to position the laser over a certain something on the media but is unable to do so. In very basic terms, it could be trying to write to sector 2 but keeps landing on sector 1 or 3. Just give clicking 'Continue/Ignore' a shot and if you than get another error message later on, get back to us with that one

It means the drive can't get a fix on whatever it's trying to write to. Is the firmware up-to-date on the drive? Are you using decent discs? Maybe the Plextor doesn't handle the command very well, in which case just click ignore/continue and let it try burning to the disc anyway.

Deffo start with the firmware update - they're VERY important. You might have more luck if you burn at a speed closer to the one the media is rated at. 8x or 12x really. 8x on 8x media is normally fine. I tend to use 8x or 12x on 16x media - but every drive / media id is different. The burn went fine and the verify proves your pc drive can read it ok. As such, playback on the PC should work fine. Your standalone might just be fussy - or require bitsetting as mentioned earlier. Problem is, Pioneers don't support that by default on DVD+R media, only DVD+R DL. You'll have to patch the firmware to make it work.

Ok so the drive is failing to write to the media. That's generally why every DL related post you'll see on this forum tells the poster to use Verbatim 2.4x DVD+R DL discs. They work where others fail.

Your drive is probably too old to support them, that's all. N/A of course standing for 'Not Applicable'. Do a 'Disc Quality' scan of that disc using the freeware tool CDSpeed from www.cdspeed2000.com and post up a screenshot for us to look at.

IMO, it's a waste of time. You are of course free to do whatever you like though! There was a bug in 2.3.2.0 in the ISO9660 file system code that prevented DVD Video images working on some players. This was fixed in 2.4.0.0.

Sorry, we don't discuss that stuff on this forum.

Maybe it's rejecting all the email as spam... I really have no control over that I'm afraid. Add the forum address to your address book and then maybe it'll get through. (look at your confirmation email)

Not that I'm aware of. The message in the log is just there so people are aware that AnyDVD potentially modifies data on-the-fly during a Verify operation and that can cause 'miscompare' errors that wouldn't otherwise be there.

Just as I expected, there are a number of tweaks / fixes that needed to be done to v2.4.0.0 so v2.4.1.0 will be out within the next 7 days I'd say.

Correct, they're all the same. Yes it adds the AUDIO_TS folder automatically. The only time they'd be different is when you have other files/folders you want in the image - in which case you need to use option 1 so it picks those up.

btw, do not pass over what others have said. Doing a simple file copy to check your backups is not as good as the built in Verify function. The verify tests every sector is readable (i.e. same as a file copy) but it also checks the actual data in the file matches what it's supposed to be.