LIGHTNING UK!

There's no way of doing it in ImgBurn though, no. Depending on how complex the CUE is and the changes you want to make, you might just be able to edit it in notepad.

How many discs have failed like this? Have you tried burning at 4x instead of 3x? (note: 2.4x isn't supported by your drive, so it used 3x instead) Assuming your discs are ok, that means your drive probably need cleaning or replacing. It shouldn't be having a problem burning (real Verbatim) MKM-003-00 discs. They're the best DL media available.

The other 6 mirrors host files without installcore... or at least were originally given a version without it. Opting to save or run makes no difference.

You can use something like this - http://implbits.com/products/hashtab/ That file isn't part of the ImgBurn download, but maybe it's something from installcore (a plugin used by the installer). It could be a false positive though.

Are you sure you downloaded the correct file? Does the MD5 of the file you downloaded match the one shown on the website?

Oops, I’ve muddled up some of my posts by saying video_ts when your topic title clearly states it’s an avchd image. So yeah, what you’re doing is burning Blu-ray style hd content onto a dvd. You should allow the program to make the changes it recommends.

Go into Build mode within ImgBurn and add H:\ to the source box.

The GUI will always show the speed you've selected, even if the drive will have ignored the request to use that speed. You've omitted the last couple of log entries where it would have showed the actual speeds your system/drive burnt at. It's not the program which forces one of the other speeds, the drive does. I cannot override the speeds it's designed to work at.

Virtual Clonedrive will do the job nicely... and it's free

If you can't make it output a VIDEO_TS folder (only an ISO), mount the ISO in a virtual drive and point ImgBurn's Build mode at the drive letter of that drive. You can then burn a disc (or create a new ISO) from the contents of it.

"Invalid field in CDB" is common after a retry of some sort - but then I'd expect to see a 'write error' before it and you don't appear to have one of those. I wonder if you're somehow missing out on the real error code. Perhaps a driver in the chain is swallowing it up and so it isn't reaching ImgBurn. Do you have anything in your filter driver list? You can view it (and copy+paste it) via the feature on the Tools menu.

The physical eject button/tray lock is a command you send to the drive, it has nothing to do with the locking abilities of the I/O interfaces. Both interfaces are, unless buggy, perfectly capable of gaining exclusive access to the drive and preventing other apps from trying to use them at the same time. Apart from when I'm testing a different interface for something specific, I'm always on SPTI. ElbyCDIO is great for XP and avoiding the need for admin rights, but XP also went EOL a long time ago.

ImgBurn burns (or puts into an ISO) exactly what you give it. Don't forget, an ISO is just like a box you put things into. It doesn't change what you put in it. ImgBurn doesn't retain or not retain a menu, because it doesn't know anything about menus. The menu is part of the BD Video specification and structure. If that's already in place within the files/folders you feed into ImgBurn, they should work just fine. If they aren't working, it's an issue outside of ImgBurn.

Does the new ISO come out to the same size as the original one? It's coming out to around 700Mb... marginally bigger than you could fit on a CD. Are you actually burning the ISO to disc and playing in a standalone player or just playing it via the virtual drive in your computer? If on the computer, what software are you using for that purpose?

ImgBurn burns as-is, so if you want a BD Video disc, you need to feed a compliant BD Video folder structure into ImgBurn. You’ll have to find another utility to convert your premiere file into the correct BD Video format and folder structure. Then just burn that with ImgBurn.

As mentioned above, that's common with Mirror 7. What about the other mirrors? Your topic title does state 'all mirrors'.

After a bit of Googling, it seems that sort of crash (Fault Module Name: StackHash_2264) is due to DEP. As mentioned before, if ImgBurn itself crashes, it generates a report and offers to send it to me. You aren't getting that and are instead getting a crash within the OS. I don't know if that sort of crash would produce a minidump or whatever, but there could be more info in the eventlog or perhaps available by a 3rd party app from the likes of sysinternals or nirsoft.

No

Only 1 mirror (7) has something that the AV could flag. I've no idea what you're downloading from the other mirrors, but it isn't the actual ImgBurn download.

You didn’t say anything about extra folders, just the volume label. Enable the other option for BD Video on that same tab.

“BD Video - Allow Unicode Volume Label” should do what you’re after. Windows limits the display of volume labels to 32 characters, so nothing we can do I’m afraid. If you want an image of the disc as the icon when you view it in explorer, you’ll need to create an appropriate autorun.inf file and configure it to point to an icon file that shows what you want it to show. Again, this is something outside of ImgBurn.

To be honest, I don't even know where that 8.3 name is coming from. Is Windows generating it or is it reading both file systems and that's coming from the ISO9660 one? Maybe open the disc in ISOBuster, navigate to the correct path within the ISO9660 file system and see what it's called. What settings have you selected within the ISO9660 restrictions tab? I'm guessing you've relaxed them to the max?

In that case, please try and see what's written in the log window and the status bar (of the main window) of the one that's supposedly crashed. That info will help pinpoint what it was doing at the time.

The program should tell you it has crashed and offer to send a log. Please do so.

Nope, it always closes them.