LIGHTNING UK!

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.

Yes, LIGHTNING UK! and LIGHTNING UK! are the same guy... i.e. me.

It does it all automatically when you burn so don't go out of your way to do it manually

This has already been added for the next version.

There really isn't much anyone can do until you get hold of a dump file or at least more info about the BSOD. Tell the OS not to reboot automatically on error and maybe you can write out what the blue screen says (as cynthia mentioned). The bad drivers normally cause issues during burning, not just as the application is being closed. Drivers generally are the only things that can BSOD a machine though, programs will just crash and the OS recovers from that just fine - unless you happen to be using Win95 or something! (which I know you're not) Obviously it hasn't happened to any of us lot (myself or the beta team) so it's something local to your PC, you just need to figure out what it is.

Verifying an image file... that's a novel idea! You're doing something ImgBurn is not to be used for and it cannot be discussed on this forum. Sorry. For your own peace of mind though, if a drive doesn't report any errors during a read then it's safe to assume it's fine and all data is present and correct (drives provide ample error checking). Verifying burns is a good idea, verifying reads is pretty pointless.

It's ok now, I found the problem and fixed it. It seems the 'wide' (unicode) version of the compare function puts filenames starting with '_' before those starting with normal 'A-Z'. This is actually wrong as '_' comes after uppercase letters in the ASCII character set. For that reason, the I386 folder will not be parsed correctly by the installer and hence it just reboots. (The I386 folder contains a file called '_DEFAULT.PI_') You'll have to hold out until 2.4.1.0 is released which I'm sure will happen within the next 7 days. Sorry and thank you for reporting the issue and getting me to look into it properly.

The UDF spec has nothing to do with the physical layout of files on the disc. When you copy loads of files over, I've never actually taken the time to see how windows does it. i.e. an entire branch at a time or level by level. Both are possible by ImgBurn so take your pick as to how you want the disc to be laid out.

Are you sure the boot block is only 2k? The one I did the other day was 16 sectors, not 4. You need to look in the log to see that info when you extract it from the original.

Update to v2.4.0.0 too.

Please try buring with the SPTI I/O interface, it might actually provide us with real SenseArea data from the burner rather than reporting 'No Additional Sense Information' - which we can't tell anything from. Post a new log when you've done that. Also, as every other DL related thread on this forum will tell you... ditch the Ritek discs and buy Verbatims. (DVD+R DL 2.4x MKM-001-00 made in Singapore)

Does 2.4 really add anything that you couldn't handle in 2.3?! I'd have expected 2.3 to still be the default in programs since 2.4 doesn't work. No you can't specify a command line decoder, ImgBurn uses DirectShow and the filters are inserted automatically via some 'Intelligent Connect' thing that Windows handles. You'd have to check the 'Merit' levels of your filters to make Windows use the right ones. 1. I'm pretty sure it already does what you've just said. If you click 'Tag' on the Disc item then the filename is taken from the CD-TEXT fields (Basically making it '[Performer] - [Album Title].cue') 2. There's no real support for doing what you're doing (i.e. there's no 'Burn an Audio CD mode'). All that was added to ImgBurn was the ability to burn CUE files - so there NEEDs to be one even if it's just shoved in the 'temp' folder. I knew it wasn't an ideal way of doing things, but it was that or nothing. The Quick OK button just tells the program to make up the filename itself based on what it would use as a default name in the 'Save As' box anyway. You never get to see the actual Save As box.

What you really need to work out is why DirectShow can't handle that file (the ACM method is a fallback - and I've now fixed the issue with that... sorry!). The standard XP filters cannot handle v2.4 ID3 tags so ensure you're not using those in your files.

I believe the '+G' is written to the subchannel area and ImgBurn doesn't write to that bit I'm afraid.

Remove MxlW2k and pxHelp20, then reboot and try again.

It closes and finalises. The disc is read-only after burning.

I already said it but I guess I should put it in writing... Happy Birthday!