LIGHTNING UK!

Hmmm... weird! Can you try the disc in another drive and see how it gets on with it?

https://www.google.co.uk/search?q=record+screen+windows+10 'Windows Key + G' looks like it'll do the job on Windows 10.

You could try a different write speed if 'max' keeps failing. Check the list of 'supported write speeds' in the log you provided or refer to the info box on the right of the main screen when you're in Write mode with one of those discs in the drive.

So what is the reply windows doing exactly? Does it expand when you click it....even if only for a second? But then it goes back to the one line version? Any chance you can take a screenshot (or a video) of it doing it? There must be something funny going on.

As mentioned in your other thread, when you run into the situation where you can't get the 'reply' box to come up properly, try pressing F12 and see if anything is written in the 'console' tab of the developer tools. Other things to try... Close your browser down and reopen it. Log out and log in again Clear your browser's cache / cookies. Best option is to log out, clear cache, close browser, reopen browser, log in again.

If it happens again, you'll know what to do. Well, that and press CTRL+F5 to force a refresh before trying to click in the reply box again.

Please post the log so we can see what's actually happening.

I use Chrome exclusively and have never had a problem replying to posts. Looking at that thread, nobody said they had problems with Chrome on these forums. dbminter said he'd had problems with Chrome on the Macrium Reflect forums. You may need to open up the developer tools (press F12) and see if you're running into errors when you click your mouse in the reply box. If you have something running that's blocking the forum software from working as expected (the little 1 line reply box turns into a bigger box with more features once clicked), that could be why you're running into issues.

There no ‘mode’ for it. It would basically be an image conversion mode.

4x and 8x aren’t supported speeds. It would have burnt both of those at 10x.

You can’t use that initial cue to build a backup image. It can only be used to burn a disc. If you want to save that stuff so you can burn another copy some time, either keep a copy of the audio files alongside the cue or use Read mode on the burnt disc to get a new bin/cue set.

This is something related to DirectShow, not ImgBurn itself. What sort of files are you trying to add? It looks like you have some iffy filters installed or something. That specific log doesn’t mention the filter dll being used as part of the ‘connect’ process, but maybe it’s visible in another one of the crash logs?

It's probably easier if you just google for the various sector formats/structures possible on a CD. There's Mode 1, Mode 2 Form 1, Mode 2 Form 2 and CD-DA. If you look at the TOC info, you'll see if it has multiple tracks or a non Mode 1 track. If it isn't single session/track/mode 1, use BIN. That's what the program defaults to anyway, so just go with what it suggests. If you want to faithfully reproduce (or emulate) the disc, you should keep its sectors in the format they're supposed to be in.

M4a seems to have 2 codecs associated with it. AAC and ALAC. So even if something says it supports M4A, it doesn’t meant it’ll support both codecs. As your OS install can’t decode the files you’re feeding it (well, feeding into ImgBurn), that tells us you need another codec installed on the system. It sounds like you’ve got it working ok now having installed that DirectShow filter, so that’s good. [emoji1303]

None of these packages are from Microsoft. Anything not supported ‘out of the box’ requires 3rd party DirectShow filters. Having Googled a bit for ‘alac DirectShow filter’, this one got mentioned a lot. http://dsp-worx.de/?n=15

What type of audio files are you actually trying to use? File extension / codec please.

That disc only has a single, mode 1 track on it, so ISO would be the default extension / format. Iso is mode 1 / ‘user data’ of a sector - 2048 bytes per sector. Bin is for raw sectors - 2352 bytes per sector. That’s why the bin is bigger.

There’s overhead of the file system(s) you decide to use on the disc.

Were you using the same drive you're having issues with in one of your threads? Beyond that, I've no idea.

DVD-R holds more. Same for DVD-RW. As taken from the Media Testing section of the forum... DVD-R Free Sectors: 2,298,496 DVD+R Free Sectors: 2,295,104 DVD-RW Free Sectors: 2,298,496 DVD+RW Free Sectors: 2,295,104

I figured you'd just zip it over multiple floppies or something. Another option would be to remove the hdd from that machine, hook it up to another (more recent one!) and back the drive up properly. You may run into issue with the program not being able to read some of the 'in use' files if you're trying to backup the OS drive from within that same OS. ImgBurn is not a hdd backup tool.

I pretty sure even the latest (2.5.8.0) works on 98SE.

Discovery mode is for zero filling discs (burning all zeros to them) - used when running disc quality checks. Don’t use it for anything beyond that. The size reported by the program is what the drive reports. If it’s changing, either your drive is messed up or you’ve got some 3rd party software messing around with the response. The program isn’t actually ‘counting’ the sectors itself.

It depends on how your player plays them. It might read their ID3 tags and arrange them into albums. It might then order them by track number from the ID3 tag or by name if that isn't available. At the end of the day, it's a data disc. The files are sorted into alphabetical order within the file system. If your player doesn't make use of the ID3 tags, that's the order it'll end up playing them in and that's when renaming the files to fit your desired order is required. If media player works for what you want, it would make sense to use that instead.

Unfortunately, there’s no way to specify the name of the data file when using CCD. That’s why ImgBurn has to rename its usual ‘bin’ file to ‘img’. The CUE file can then just be told to use the img file. Back when ImgBurn (or perhaps its predecessor) came about, DAEMON Tools was a much simpler application. It grew and grew, had a few driver issues (which slowed down real optical drives) and people liked the basic nature of virtual clone drive. There’s no doubt that Daemon tools is more capable and fully featured (both in terms of features and its ability to faithfully emulate a physical drive), but if VCD works for you, that’s great.