david gideon

I can now answer my own question. I took advantage of a sale price and bought Toast 20 online. After installing it (this time no errors that some component wouldn't load like I got when I tried to run T17 on my M1 mini) I found that it recognized sd2 files and would add them to a CD, then would save that CD as a Disk Image file .sd2f. However, when I went to Mount Disk Image and selected the image file I just made, it let me select the file, but on hitting the button to mount it, the dialog box disappeared but nothing mounted. Toast just ignored it. So it's confirmed: Toast 20 makes CD disc images that it can't mount. Brilliant.

Guide to Toast 20: https://help.corel.com/toast/v20/en/official-help/index.html#page/toast%2Fh1-introduction.html%23

The guide for Toast 20 has a section describing how this is done. But this capability has been broken or inconsistent in recent versions. Does anyone know if it finally works again in Toast 20?

Thanks for the info. I'm investigating some other ways to mount disk images but haven't had a chance to actually try them out yet. Will also look into 'Burn'.

Is there any new info on this? Mounting cd disc images is important to what I do. I installed Toast 17 on a brand new M1 mini because I read that Toast has been M1 compatible since v17 which I own. The installation went without problems except for a quick note during the process that some Corel something or other needed to be updated. On the M1 Toast can read sd2f files, it can write sd2f files, but try to mount one and nothing happens. I just sits there. I see from the Toast 19 discussion that the problem is still going on there too. Is this just a lost cause? Is there a workaround, some way for Toast to write a different kind of cd image that maybe WILL mount on an M1 Mac?

Finally the just-released update has fixed this CD-image mounting bug, at least for me. Hooray.

Yes the latest update finally solves the awful CD-image mounting bug. Hooray!

Problems not addressed, let alone solved, after nearly a full year. I guess Toast is pretty much a dead duck.

It looks like they decided to renew their domain because the bias website is back up as of today. You should be able to authorize your software now, not sure that you even need use the 'alternate authorization' method it might work more smoothly the standard way since the servers appear to be back online.

Well no sooner do I report the above than the domain for bias-inc.com comes up as having expired just a coupla days ago! So I guess unless they renew it (which they probably would've done by now if they intended to) the authorization process is permanently unavailable. This means that newly obtained software cannot be made to work. Currently authorized software will continue to function on the computer(s) it's authorized for. But it cannot be run on any other computers because there is no way to authorize additional machines to run the software. I'm not looking forward to the day when I need to switch to a new computer, and all my Bias software becomes worthless.

Bias's authorization servers have gone down for a few relatively brief periods (just recently they were down for a day or two), but they are up now and usually are most of the time. As far as I can tell it's still possible to authorize Bias products via bias-inc.com. It's possible that a bundled version of a Bias app uses some different authorization procedure and that may be an extra kink in the procedure.

So nothing has been done on this? I'm constantly quitting Toast and swapping out prefs files in order to use discs of different sizes. Since this bug has been present since Toast 11 appeared and apparently Roxio or whoever has for sure known about it for nearly two months why has nothing been done to address it? (For that matter I also have the bug of not being able to mount .sd2f files reported in another thread, and that one has been around just as long.) Grumble grumble grumble.

That sounds like good news! Thanks much and I'll keep my fingers crossed.

I remember trying 'disc info' but don't remember how it read and do remember that it didn't do anything to fix the problem. I have several previous incarnations of Toast but from what I can tell they all use the same prefs file...I have only Toast 10 on my Mac mini and it of course burns 70m CDs w/o problem, but I haven't tried switching between 10 and 11 on my main machine. A good idea and will look into it this weekend. Thanks!

Well, after upgrading from Snow Leopard to Mountain Lion, doing a complete reinstall of Toast 11, and applying the latest update, I figured I try once again to get it to let me make an 80m CD. Here's a shocker...the problem remains. Nobody from Roxio or Corel or whoever's in charge these days cares to help me solve it so I did some more testing and at least came up with another data point about when it happens. To recap, T11 insists that audio CDs are 650mb and wants to split everything more than that onto 2 CDs even if I have a 700mb blank inserted. Only trashing prefs and restarting gets it to see 700mg as the capacity of the CD. What's new is this: If after trashing the prefs and getting it to accept 700mb as the size I burn a 700mb CD, then the next project will retain that and let me burn another 700mb CD. However, if I insert and burn a 650mb CD T11 then thinks that is the size of whatever new project comes next, and splits any content beyond 650 onto two CDs...even when I have a 700 CD blank inserted and ready to use. The only way to get it to recognize 700mb blanks again is to quit, trash prefs, and restart. I think one reason some people haven't been able to reproduce this problem is they may not have any 650 blanks handy; they are much more uncommon than they used to be, but I still use them because for critical audio work they are a tad more reliable than 700s. So if all you have are 700mb blanks, T11 will never misbehave. It will always read and recognize 700mb. But as soon as you burn to a 650mb CD it writes some gobbledegook to the prefs file and considers every audio CD you want to burn from there on to be limited to 650. Since this didn't happen with any previous version of Toast how hard can it be to isolate and correct it? Whether it's hard or not, nobody at Toast HQ has cared about it for over a year now. And I wouldn't be surprised if T12, if and when it comes out, will inherit this problem also. Meanwhile, I'm hoping someone who's expert enuff at what's in the prefs file and can get their hands on a few 650mb CD blanks, can duplicate and/or isolate what's going wrong and maybe get the attention of the support dept. They aren't listening to me that's fer sure!