Jump to content

acadiel

Members
  • Content Count

    4
  • Joined

  • Last visited

Community Reputation

0 Neutral

About acadiel

  • Rank
    Newbie
  1. acadiel

    Toast 18

    What's bad is that I purchased Toast 17 just about two months ago. I've been fighting with Tech Support to get it to work since then. It just refused to launch (crashes). They told me at the end of June they were escalating to Engineering, and then nada. And then they come out with a new version that I must pay for to upgrade less than two months later. Sigh. I really want to find the email address of an executive at Corel and let them know just how frustrating their support infrastructure is.
  2. acadiel

    Toast 14 Will Not Open

    I just reinstalled Toast 12 (and the 12.1 patch) and it's opening up fine under 10.11.3. So, I'll just use that until they fix Toast 14. Otherwise, I'm going to pretty upset that I just spent $50 to update....
  3. acadiel

    Toast 14 Will Not Open

    I just filed a support ticket for this very thing. Been using Macs for 15 years. Know my way around troubleshooting and trying to get crap to work. Unfortunately, this crash IS a coding error in Toast itself. I've had it happen on multiple Macs with 10.11.3. A "bad kernel access" is the program misbehaving and trying to access something it shouldn't. Just for reference purposes, this is what I sent tech support: Just purchased a copy of Toast 14. Downloaded version 14.1 (latest according to your site, ~600MB). I can get to the main welcome screen, but as soon as I select "Mac Only" to burn a data CD, Toast crashes. System information: MacBookPro9,2 running 10.11.3 16GB RAM Resolutions attempted: 1) Uninstalling Toast folder 2) Removing all preferences from inside Library-Preferences 3) Rebooting 4) Reinstalling product 5) Rebooting again Crash logs state this: Process: Toast Titanium [1037] Path: /Applications/Toast 14 Titanium/Toast Titanium.app/Contents/MacOS/Toast Titanium Identifier: com.roxio.Toast Version: 14.1 [3862] (14.1) Code Type: X86 (Native) Parent Process: ??? [1] Responsible: Toast Titanium [1037] User ID: 501 Date/Time: 2016-01-31 12:25:12.101 -0500 OS Version: Mac OS X 10.11.3 (15D21) Report Version: 11 Anonymous UUID: BAA7E19A-CABB-C747-9C9F-BD83AE2E0015 Time Awake Since Boot: 730 seconds System Integrity Protection: enabled Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000001 Exception Note: EXC_CORPSE_NOTIFY VM Regions Near 0x1: --> __TEXT 0000000000001000-0000000000f68000 [ 15.4M] r-x/rwx SM=COW /Applications/Toast 14 Titanium/Toast Titanium.app/Contents/MacOS/Toast Titanium
  4. acadiel

    Toast 11.0.3 Issues With Two Drives

    I have Toast 11.0.3 on a Mac Mini 2.53 server (late 2009 model) running 10.6.8. I have this drive (Samsung) hooked up via USB: Samsung Drive and this LG Blu Ray Burner hooked up via Firewire in this case. Here's my issues: LG Drive: Can burn Blu-Rays just fine (I've used BD-R 25GB, BD-RE DL, and both work.) Verbatim DVD-R and +R SL work OK, as well as some old Office Depot CDRs. Toast refuses to recognize Verbatim 2X DL DVD+Rs at all in this drive. I can't even get it to recognize the Verbatim is inserted to burn it! This might be the drive, but it's happened with four packs of the Verbatims. Samsung Drive: Can try and burn a Verbatim DVD+R DL, and it gets to 99% (writing lead out), and then an error pops up (I need to do it again and write it down, but it states it's a "Mac OS" error.) Workaround: If I use Toast to burn my project to a disc image, Disk Utility can burn it just fine on the same Verbatim 2X DL DVD+R media. So... two questions: LG Drive: Why doesn't Toast see the Verbatim DVD+R DL? Drive issue, Toast issue, ?? Samsung Drive: Why does the lead out fail at 99% every single time on a Verbatim 2X DVD+R DL? And, why can I save the project to a disc image and then successfully burn it with Disc Utility? Maybe the Verbatim 2X DVD+R DL isn't the correct media to be using, but I've never had issues with Verbatim in the past... Thanks, all!
×