LIGHTNING UK!

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.

v2.5.8.0 doesn't have any way of getting around that prompt. I have already added another command line parameter that can, but it'll only be available in the next release... whenever that might be.

Something like lupasrename should work.

Have you tried doing a full format on that discs? If you already have, you should give up with that and switch to different media. Your drive really doesn't like that one.

Ok so the drive no longer recognise a blank one of those discs? You’ll have to try some other discs or get another drive. Cleaning the drive may help... but it also might not. Haha.

Post the log from ImgBurn and post the info Ch3vr0m mentioned from within ImgBurn's drive/disc info window on the right please. Just load the program, go into Write mode, put one of the (new) blank discs in and copy + paste everything from that window on the right.

not sure why or how you'd be picking ImgBurn for use on a Mac.... seeing as there isn't a Mac version. Unless you actually meant 'Machine' when you wrote 'Mac'? This thread looks a lot like spam to me but I'll give you the benefit of the doubt for now.

Where did you download it from? Which mirror site?

Ok, so it's a pressed (silver) disc then, not a 'burnt' one? It could be a form of copy protection, yes. The name of the file the problem sector belongs to certainly has a random looking name, but maybe that's normal for that disc? You could just keep ignoring the error (click 'continue') and let it fill the bad sector with zeros.