LIGHTNING UK!

Update DVD Flick and then you'll be using 2.4.2.0 anyway.

Maybe one day/year, yeah.

You could at least burn the BD-RE with ImgBurn though

Yup, it doesn't support those either. RITEK-S04-66 are rubbish compared to the mighty MKM-001-00 (Verbatim) anyway!

You need to convince your drive, not the program. The program gets the name by querying the drive. ImgBurn automatically closes discs, it's not something you need to do. If you have an open disc from another program, all you can do is issue all 3 of those commands. If they don't error out then the drive probably thinks it has dealt with them - again, this is a drive thing and ImgBurn has no say in the matter.

You said the BD-RE was burnt with Nero though. It won't be a fair test (between BD-R and BD-RE) until you've burnt the same content/folder to both types of discs in both programs.

1. That drive is getting on a bit now. Have you ever updated the firmware on it? Maybe the laser is dirty and it's not burning/reading as well as it should? 2. See above. 3. You can't burn DVD+ (plus) format media any slower than 2.4x. If it says 2.5 then it's just because that model of drive has a slightly higher RPM for that write speed and hence is burning slightly faster - there's nothing you can do about it. 4. Did you do anything to edit the actual content? If not, it's all in your mind. A straight 1:1 copy of a disc will be 110% the same as the original.

The burn + verify log would still help. Burning the verbatims at 8x or 12x should give you a disc that works just fine. If it's not then maybe it's the standalone that has the problem?

I can probably email you the file if you want, I just wasn't sure if I should 'host' it. I even made a batch file for it so that it unregisters the old one, backs it up, copies the new one and then registers it. All you have to do is run that and then reboot. Another thing to try out is unregistering your current l3codecx.ax file and letting DirectShow drop back to using the ACM method via its wrapper (and if that fails ImgBurn will use ACM directly anyway). Just type the following at a command prompt window: regsvr32 /u "%SystemRoot%\system32\l3codecx.ax"

Is the folder structure definitely correct for a BD disc? Look at it in IsoBuster or something and provide a screenshot with all the branches expanded.

Just to be clear... the crash happens when it gets to a certain file? And it's the same file on both machines? I don't know about the ax file, I would think it's the same for both windows versions... there's certainly no harm in trying it!

Yes, ImgBurn does all that automatically for you.

Oh if only things were as simple as everyone thinks they are *sigh*. It already tells you when the disc needs formatting/erasing in the status bar. The erase button is there because people sometimes like to erase without burning anything (to keep it empty for the next time they need it?) and some were too stupid to navigate the tools menu so I found a little bit of real estate and added the button. Erase is NOT a primary function of ImgBurn and has no progress screen etc. It only works when a user has selected a 'Mode' and a drive has been selected/made active. When it becomes a proper feature / function the little button that you obviously hate so much will no doubt go. You're obviously a programmer yourself, so where can I checkout some of your work? It must be AMAZING if you can spend all this time telling me how you think my GUI should look! Hell you could have probably written your own burning program in this time.

So l3codecx.ax crashed then - take a look at the last post in the FAQ (or if I add more before you read this, the one that mentions l3codecx.ax !) To be honest, I'm amazed this problem didn't show up during the intial decode pass that ImgBurn performs to get an accurate size/playback time of the file. It's only the same decode process being repeated so why did it work once and then fail the next time (during the actual burn) ?

Yes. You should tell WinRAR to NOT associate itself with ISO and IMG files. They're meant for burning directly to a disc, not extracting and then burning.

Was it really a RAR file or did you just use WinRAR to extract from an ISO file? If it's the latter, just burn the ISO with ImgBurn, you don't need to extract anything.

Yes, buttons with words on are great the first time you use a program but after that it's info you really don't need and you'll probably wish there was more room for other stuff. I can tell you right now that I won't be changing my little icons, I like them

If the IFO's are corrupt then your source files are faulty - sorry but that's not an ImgBurn problem as it just burns as-is.

Those errors are a bit too consistent and frequent to show a problem. You've probably got something running that's changing the data on the fly - hence the miscompare.

Tools -> Settings -> Write -> Write Type.

I'm not sure the drive would respond to a speed setting type command mid burn but I could try it. To be honest though I'm not sure how much call there would be for this type of thing. It's not something I'd do for 1 person.

nonono, You missed something important here... The audio support added in the previous wasn't meant for burning your own collection of audio files (contrary to popular belief, I'm not stupid and I realise that function needs a simple interface), it was meant for burning disc images from BIN/CUE files.

Mount it in daemon tools, rip the tracks in EAC to seperate files and then make a new CUE that points to the WAV files (in the correct order).

The problem was nothing to do with your converter, the drive just reset during the burn - probably due to a command timing out where it was unable to write to your media. That's where the Verbatim / Taiyo Yuden discs come in.

It's an optional step, but if you're going to calculate the final size of the project the program obviously needs to know where you want the layer break - as its position will change the final size. As things could then change before you hit the 'Write' button ImgBurn has to ask you to select/confirm your LB choice when you hit the Write button.