I rarely use toast anymore. I’m still on version 15. But I’m going to burn a couple of DVDs soon and I’m wondering if there’s anything worthwhile in the current version 20? Does it make good use of the M1 processor or is the version 15 adequate?

---

Ukulele music I couldn't find anywhere else.
[colquhoun.info]

I've got v19 on my M2 (and the M1 before it). I don't use it for anything more than basic burning/copying. I upgraded when there was a bundle deal (similar to this current deal: [bundlehunt.com] )

I find that to stay somewhat current/compatible, it is good to jump on a deal like this every few years, just to stay somewhat close to current and in-support. But functionality-wise? I don't get the sense they are really adding much in the way of new features.



Edited 1 time(s). Last edit at 05/25/2023 03:18PM by clay.

I got v20 last year because I saw a deal for $19, and I was moving to a new machine. The version on my old machine was like v10 or v11, so I figured it was a good time to upgrade. I still burn the occasional CD/DVD, and recently got an M-disc compatible burner. I'll probably use it to backup stuff to those.

Does today's Toast burn blue rays? It used to take some under the hood shenanigans.

....isn't French Toast.....upgraded toast......???

---

_____________________________________

I reject your reality and substitute my own!

I ended up using Toast 15 to burn the bluray. I couldn't find anything on the Roxio website to indicate version 20 was functionally better at doing this particular test. Yay for old programs!

---

Ukulele music I couldn't find anywhere else.
[colquhoun.info]

Quote
davemchine
I ended up using Toast 15 to burn the bluray. I couldn't find anything on the Roxio website to indicate version 20 was functionally better at doing this particular test. Yay for old programs!

Yeah, yay! for old programs. Especially sometimes when they have a feature not retained in newer versions. At a previous job we kept an older PC around with a CD burner and an old version of Toast to duplicate some OS installer discs. The discs used a valid format under the ISO 9660 and the Red through Orange Book specs for CD-ROMs and that older version of Toast would make bootable copies. But a later version of Toast would rewrite some of the descriptors to match a later extension of the specs even when an exact copy was requested when duplicating. Duplicated discs using the newer version would not boot.

Quote
JoeH
At a previous job we kept an older PC around with a CD burner and an old version of Toast to duplicate some OS installer discs. The discs used a valid format under the ISO 9660 and the Red through Orange Book specs for CD-ROMs and that older version of Toast would make bootable copies. But a later version of Toast would rewrite some of the descriptors to match a later extension of the specs even when an exact copy was requested when duplicating. Duplicated discs using the newer version would not boot.

Have to make a disk image or iso from the original to preserve specs. Copying the "disc" to another disc is just copying the data.

---

Quote
Tiangou

Quote
JoeH
At a previous job we kept an older PC around with a CD burner and an old version of Toast to duplicate some OS installer discs. The discs used a valid format under the ISO 9660 and the Red through Orange Book specs for CD-ROMs and that older version of Toast would make bootable copies. But a later version of Toast would rewrite some of the descriptors to match a later extension of the specs even when an exact copy was requested when duplicating. Duplicated discs using the newer version would not boot.

Have to make a disk image or iso from the original to preserve specs. Copying the "disc" to another disc is just copying the data.

Even those copies would change the areas required to make the disc bootable for that OS and hardware. Disc images didn't keep the same header information, just the data after that. As I recall the information was in the system area before the data sections used by ISO 9660. ISOs created from the discs and the copied back to CD-Rs would be missing that. The older Toast version would do a full copy using what it called a SCSI to SCSI copy. Only change from a bit for bit copy was that ECC errors detected and corrected during a sector read would be written out to the copy



Edited 1 time(s). Last edit at 05/27/2023 12:52PM by JoeH.

Quote
JoeH

Quote
Tiangou

Quote
JoeH
At a previous job we kept an older PC around with a CD burner and an old version of Toast to duplicate some OS installer discs. The discs used a valid format under the ISO 9660 and the Red through Orange Book specs for CD-ROMs and that older version of Toast would make bootable copies. But a later version of Toast would rewrite some of the descriptors to match a later extension of the specs even when an exact copy was requested when duplicating. Duplicated discs using the newer version would not boot.

Have to make a disk image or iso from the original to preserve specs. Copying the "disc" to another disc is just copying the data.

Even those copies would change the areas required to make the disc bootable for that OS and hardware. Disc images didn't keep the same header information, just the data after that. As I recall the information was in the system area before the data sections used by ISO 9660. ISOs created from the discs and the copied back to CD-Rs would be missing that. The older Toast version would do a full copy using what it called a SCSI to SCSI copy. Only change from a bit for bit copy was that ECC errors detected and corrected during a sector read would be written out to the copy

This is strange to me.

I never had the problem you're describing when I used a dmg to master a bootable disc. Yes, there's a "bootable" bit for bootable Mac media, but that bit should be present in the dmg made from bootable media and copied back to disc with Toast.

---

Quote
Tiangou

Quote
JoeH

Quote
Tiangou

Quote
JoeH
At a previous job we kept an older PC around with a CD burner and an old version of Toast to duplicate some OS installer discs. The discs used a valid format under the ISO 9660 and the Red through Orange Book specs for CD-ROMs and that older version of Toast would make bootable copies. But a later version of Toast would rewrite some of the descriptors to match a later extension of the specs even when an exact copy was requested when duplicating. Duplicated discs using the newer version would not boot.

Have to make a disk image or iso from the original to preserve specs. Copying the "disc" to another disc is just copying the data.

Even those copies would change the areas required to make the disc bootable for that OS and hardware. Disc images didn't keep the same header information, just the data after that. As I recall the information was in the system area before the data sections used by ISO 9660. ISOs created from the discs and the copied back to CD-Rs would be missing that. The older Toast version would do a full copy using what it called a SCSI to SCSI copy. Only change from a bit for bit copy was that ECC errors detected and corrected during a sector read would be written out to the copy

This is strange to me.

I never had the problem you're describing when I used a dmg to master a bootable disc. Yes, there's a "bootable" bit for bootable Mac media, but that bit should be present in the dmg made from bootable media and copied back to disc with Toast.

Well this was a problem with CD-ROMs meant to boot VMS on VAX systems. The bootable bit you are referring to for Mac media is within the ISO 9660 data region, for the ones for VMS the bootable instructions were within the 32 KB region just before that. I don't remember all of the details, but it was possible to recreate that, took a page worth of commands when I read about it 20 or so years ago. Before that the Roxio software would just copy all sectors when doing a SCSI copy, and that included that initial 32 KB region. After an update it would always write that sector to a later standard instead of just copying it.

Ah!

A VAX would need a DEC boot block.

A properly-mastered dmg would record the boot block, but Toast might not write it to exactly the right place on disc for the DEC to pick it up because consumer disc capacities and block sizes are larger than used on the VAX, so the data would be present, but not in the right location, and the copy of the disc, itself, might not even be readable on the VAX.

You're right that a "SCSI" copy (bit-copy) would have worked back in the day. Have not had that feature in any Mac disc burning software (that I know of) for a very long time.

---