floele

It means that you are trying to burn 174 minutes of audio to a regular 80 min disc. There is no type of audio disc that would allow you to burn this large amount of audio.

Please post which exact error you are getting (preferably screenshot).

If you want to archive, do not use optimal media other than maybe specialised discs like M-Disc.

We'll have another update some time I guess, there is nothing too urgent though.

IIRC, the hash used for the certificate goes beyond what WinXP can process. You probably have to use a more modern OS to verify the signature.

CDBurnerXP will convert all files as necessary before burning them as audio disc. So you should not have to take care of that yourself.

Did you try changing the file system to UDF?

The error code basically says "no data", which is probably caused by not adding any data to the disc using CDBurnerXP. It doesn't have a "finalize only" feature. But you can check the disc information window to find out if the disc is indeed not finalized. After 20 years your discs might also have become unusable. Since DVD+R are not particularly uncommon, the situation you describe might be an indiciation for this having happened. Again, you can use the disc information window to determine whether any data can still be detected on the disc. If you look for more permanent storage opt

Is there a particular file that is always affected by the issue?

The command line version won't be able to do it if the GUI can't. I suppose a lack of error handling leads to this issue. I would recommend converting the files to a different format with a suitable application.

You try to burn files that don't fit on a DVD-R, so you need to use a BD.

I don't think that CDBurnerXP will get a major UI update at this point, unfortunately.

There is no license, it's freeware.

In this case you probably have no burning device available at all. Depending where you are in the application, you would usually have a combo box with all devices available for selection.

The burning library changed quite a few years ago (don't remember when exactly) so if you had the issue before the change, then it is most likely fixed.