LIGHTNING UK!

I will look into why /ERASE isn’t working for BD-R formatting.

I've only done it a couple of times (many many years ago), but I seem to recall it's actually the formatting process that enables defect management with BD-R. So you format the disc with spare areas enabled and then burn with 'BD-R Verify Not Required' disabled in order to have the drive use defect management when burning BD-R. EDIT: Yes, that's basically what I said in my post above from 7th March 2012. So you need to format the disc to enable it.

You're better off contacting Acronova. They're in the best position to support their own products. BS_Robots_Connect is only supposed to return: // BS_ROBOTS_OK If the function succeeds with no error. // BS_ROBOTS_ERROR If the function fails with any error occurred. It's actually returning 'BS_ROBOTS_BUSY' (402) So I guess, internally, it's trying to do something which is taking longer than expected? (or maybe it's totally stuck). Can you see the drive itself in the program? Is the device found in Device Manager ok? The drive itself and the robot side of things - I'm sure that would have an entry too.

Is that drive still being manufactured or are you buying used ones? Any particular reason to buy that model? They all work, so go for something different.

Not an issue I've ever run into myself and I doubt it's one I could ask you to faithfully reproduce. There is a degree of caching of the file info within the program - icon index within the system image list included, so perhaps that's what's causing it. The properties page always makes a fresh call to get the icon index, so that explains why that always works. I will make pressing F5 (refresh) ignore and rebuild the cache when enumerating the items.

Nothing has happened to your files, they’re exactly as they’ve always been. Turn on ‘show file extensions’ within explorer, you’ll see the file is still a cue file. Just right click it and open it in notepad. As DB has already told you, the name you’re seeing there is purely due to the ‘friendly’ file association name (description).

Please put a new blank disc in the drive, go into Write mode and then copy + paste everything from the box on the right of the main window.

You're making a double layer disc / image. Pick a layer break position and click OK.

Verify when you burn and post the log please.

The link to the file in the first post works fine. You can always just use something like Audacity to reduce the volume and resave the file yourself too.

You aren't burning an Audio CD, so your player needs to support playing flac files from a data disc. Does it?

Maybe you just need to install Madflac? It's mentioned in the guide (last page/post)

It's a buffer used for when reading the files from the source location. The files have to be read and processed, building up the file system that then gets written to the disc in nice little disc sector sized chunks (via the I/O buffer I mentioned before). So it's an input buffer rather than an output buffer.

The speed it resumes at would be down to the drive. It's probably slowed itself down because it's realised your machine can't keep up at the original speed for whatever reason.

It's on Page 2 of the I/O tab in the Settings.

You burnt them as a data disc? as in, you have flac files on the disc or you made an audio cd? if you still have actual flac files on the disc, they’d have been written as-is. No data gets lost. if you burnt an audio cd, the directshow filters installed on your pc would have handled the conversion into the format required for an audio cd. Perhaps one of those misbehaved.

Drives are built around the mmc specs. That’s how you communicate with them. There might be a higher level call you can make that either uses cached data from the OS or issues the two calls in the background on your behalf, I’ve no idea about that though as I work with the actual mmc commands.

Something in your directshow filters list must be causing this. make a new cue with one of the problem files and right click it in the list so you can view the filters list. please let me know what it says.

I don't recall it having command line usage for that, no. ImgBurn follows the MMC specs and uses SCSI_PASS_THROUGH_DIRECT via DeviceIoControl. From the MMC specs, you'd probably want the 'GET CONFIGURATION' command and the 'DRIVE SERIAL NUMBER' feature.

The first error is the important one, not a thing that pops up after a retry. Your drive reported a ‘write error’ while trying to burn the disc. So, it didn’t like something about it. if there’s no better firmware you can use, there’s little you can do about it. if it’s a fluke failure, try another disc. If it keeps failing, you could try enabling the ‘perform opc before write’ option to see if it enables the drive to do a better job. Enabling defect management is also an option, but that slows down the burn and uses up disc space.

I’d always use Sao/dao. I do recall a few discs needing raw-dao 96 due to early copy protection efforts, and of course, ImgBurn doesn’t support that.

Blimey, that’s a definite ‘check the code and see what’s going on’ type of question. Leave it with me and I’ll get back to as soon as I can.

You need the right sort of drive and the right discs for it to work. I’m afraid your log snippet isn’t big enough to tell us either bits of info.

All the message boxes within the app behave the same way (they flow through one function). Generally speaking, the 'owner' window parameter of the MessageBox Windows API call is set to the one that's active when they're displayed. For the 'operation successfully completed' ones, that would be the main window. I'm not sure why it would be going behind the log window as I'd expect it to be centred relative to its owner. Where is your log window in comparison to the main window? Is it maximised? I don't really recall it being a problem, but we are going back 10+ years!

Get rid of the /MAKEIMAGEBOOTABLE one, like I mentioned in your other thread, it doesn't exist. Please also remove the /START one. When you've done that, run the command again and check the config on the Advanced -> Bootable Disc tab within Build mode. Post a screenshot of how it's been configured based on your CLI parameters.