Of note: there's claims on VersionTracker that this is GM and not final (although there typically is no difference between the two) It's still not listed on Roxio's Website, however Roxio has a history of releasing/announcing software then waiting a few days to update their website.
I have been having some big problems with firewire drives since installing Jaguar.
I have a Que!Fire 8x4x32x CDRW that 10.2 refuses to see (hence I can't burn anything), but worked fine in 10.1.x.
I also have an ADS Firewire drive kit with a 60 GB ATA drive installed in it, and almost every time i reboot, 10.2 sees that there is supposed to be a drive, but says it cannot mount it or recognize the file system. (I have to reboot to 9.2.1 which sees it, then reboot again)
I think we both own the same model Que Firewire burner. I initially had problems with it in Jaguar also (never in 10.1). Jaguar does indeed seem to be much flakier with firewire support than 10.1 was. (Don't get me started on the firewire nightmares I'm having with 10.2 and Final Cut Pro!)
Anyway, when are you plugging in and powering up your burner? I've found that I can only get 10.2 to recognize my burner when I am already booted up, then plug in the burner to the mac, then turn the burner power on, THEN start Toast. Have you tried this? This is the only method that works for me with this burner. Try it and let me know if Toast recognizes it.
As for firewire HDs (I have 4 - all different brands and all the same problem in 10.2), I can only get Jaguar to recognize them if they are plugged in and turned on BEFORE booting. Go figure. Why in the world was 10.1's firewire support flawless and Jaguar's is worse than Os 9.0????
mine is the real thing. toast 5.1.4 running well in os x.2.0 after installing x.2.1 it quits when the big red button is clicked. seems like the version tracker model is not an official roxio update. i'm waiting for the roxio release.
Anyway, I can verify the fix. You must delete all vestiges of Toast from your computer; reinstall Toast 5.0 (booting into OS9) and immediately booting back into OSX and running the new 5.2 updater. THEN you can enter the registration info and it works beautifully now.
This should NOT be necessary, of course. Either this is a bogus final release or Roxio has screwed up with the updater.