LIGHTNING UK!

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!

Sounds like you're using discs your burner doesn't support. The error comes from the drive itself and basically tells me that it can't initialise the disc properly (it's unable to read the 'Table Of Contents' (TOC))

I knew DirectShow failed and the ACM fallback was actually tweaked especiallly for Linux/Wine burning so it would at least handle MP3 without erroring out! I could have sworn I actually created a disc under ubuntu but perhaps I was more concerned about it just loading / accepting the files. It really shouldn't be failing on the 'acmstreamconvert' function if all the other functions used to detect if the conversion is possible have worked. Naughty Wine! ACM isn't good at doing conversions from different sample rates, number of channels etc (it errors out) so it's far less flexible than DirectShow - but of course there doesn't appear to be any support for DirectShow decoding (at least not using the 'SampleGrabber' filter) within Wine. EDIT: I've since found + fixed an issue with the ACM fallback code. v2.4.1.0 should be ok

Like I said before, when I/O is stuck you can't terminate anything. Windows just doesn't work like that I'm afraid. The command your drive/machine is hanging on is one of the most basic / common ones and it REALLY shouldn't be a problem for it. Could you please post a copy of your 'Filter Drivers' listing. The option for that is in the Tools menu. You should also update the firmware on the drive. You're a good few behind now. http://www.liteonit.com/DOWNLOADS/ODD/LH-2...rmware/BL05.zip

The recommended settings are the default ones, that's why they're default

You ARE (or at least should be) given the option to retry... did you not do so?

The left is for data, the right is for audio. The tooltips will tell you that too hopefully!

Ok well that's not possible I'm afraid so I guess you're kinda stuck now. Maybe you can send off your cracked copy and get a replacement disc?

Please follow my instructions again, that log doesn't show/tell me anything I can use to assist you.

Well what are you trying to 'Verify' about it? If you want to check you read it off the source disc correctly, just put that disc back in again and verify it against that. You don't normally Verify a file, it's assumed that if the drive reported no errors during the read operation then the image is fine. Burning the file and then verifying that disc against the file isn't going to tell you anything. If you suspect issues with the file, you must verify it against the original disc (or rebuild it if it was based on files on your hdd).