Welcome to the MacNN Forums.

PowerCube · Dec 26, 2002, 04:10 PM

I already posted this in 3rd party, but no replies, so possibly someone in here might have a solution

When trying to copy data or burn a backup cd in Toast 5.2 under OS X, I receive an error message that states....................

"couldn't complete the last command
Mac OS error
result code = -5000"

But, when burning or copying in OS 9.2.1, using the same application, there are no error codes, and everything works fine.

HOWEVER, when LAUNCING Toast in OS9, I receive a similar error message with a different result code of "31002". After clicking the OK button, Toast proceeds to launch without further incident, and, as stated above, will burn or copy cd's without fail.

I have tried deleting the data file, and re-entering the cd key, to no avail, and permissions appear to be ok. I'm stumped. This is happening under OS X.2.x.

Does anyone have a clue as to WTF is going on?

Mediaman_12 · Dec 26, 2002, 04:19 PM

No Idea. I have done a variety of things with the OSX version of Toast on both my old system (350mhz G4 with PC CDR drive) and my new (duel GHZ G4 Quicksilver). Duplicating DVD's (PS2 Backups), Backing up files to both DVD-R & CDR Media, Creating Audio CD's from a bunch of MP3's, all without a hitch.
Are you running the latest version of Toast (mine is Toast Ti 5.1.4)?

tooki · Dec 26, 2002, 06:15 PM

PowerCube is running the latest version (5.2). You're not.

tooki

Mediaman_12 · Dec 26, 2002, 06:30 PM

Originally posted by tooki:
PowerCube is running the latest version (5.2). You're not.

tooki

Hummm? So I may not want to do that upgrade then

Cipher13 · Dec 26, 2002, 08:47 PM

5.2 wouldn't even launch for me, so I went back to 5.1.4.

You'll have the 5.1.4 app in your Toast folder still, I think. Use that. Ditch 5.2.

PowerCube · Dec 26, 2002, 10:02 PM

Yeah, I guess I'll try that. Have to look around for an old back-up cd, though, as I think I deleted the old 5.1.x folder after upgrading.

issa · Dec 27, 2002, 04:54 AM

Toast 5.2 runs and burns just fine on my 1GHz PowerBook, both under Mas OS X 10.2.3 and 9.2.2. Being different hardware, this info is likely not much help to you. But at least you know that 5.2 doesn't just crash and (not) burn on all systems.

Sven G · Dec 27, 2002, 06:30 AM

... According to http://www.macerrorcodes.com, the -5000 code you reported is an "access denied" error: maybe you should fix some permissions? See the details...

PowerCube · Dec 27, 2002, 08:03 AM

Thanks for the link, Sven, I was looking for information like that.

I repaired permissions after the X.2.3 upgrade, but I guess I will have to try again.

Person Man · Dec 27, 2002, 10:05 AM

Originally posted by Mediaman_12:
Hummm? So I may not want to do that upgrade then

Toast 5.2 works perfectly for me, too.

867 MHz QuickSilver G4 (single processor), SuperDrive (upgraded firmware), Mac OS X 10.2.3, and 1.12 Gb RAM.

Nai no Kami · Dec 27, 2002, 01:42 PM

Every Toast for OS X have had the same problem on me:
When I burn an ISO Multisession CD and then I want to add data and import the last session to merge it with the new one, I get a "Power ON or Device Reset message". The curious thing is that I have never experienced that error when I launch it in OS 9. Hence, I conclude the OS is the culprit.
Does anyone have the same problem as me? (Blueberry iBook, Predator USB 1.1 CD-RW).
I am currently running 5.2 and, save for the problem descripted above, I have further problems.

Leia's Right Bun · Dec 27, 2002, 03:21 PM

Originally posted by Cipher13:
5.2 wouldn't even launch for me, so I went back to 5.1.4.

You'll have the 5.1.4 app in your Toast folder still, I think. Use that. Ditch 5.2.

That is because you were using a pirated serial number and toast figured that out remember.

Version 5.2 is great!

Angus_D · Dec 27, 2002, 05:46 PM

Originally posted by PowerCube:
Thanks for the link, Sven, I was looking for information like that. I repaired permissions after the X.2.3 upgrade, but I guess I will have to try again.

I had that once, kept trying to burn an image, then realised it was owned by someone else. I was very annoyed with myself

Developer · Dec 27, 2002, 06:15 PM

Originally posted by Leia's Right Bun:
That is because you were using a pirated serial number and toast figured that out remember.

I doubt that.

I have a legit copy, and one of the 5.1.x versions did crash for me. 5.2 works fine again.

Cipher13 · Dec 27, 2002, 11:36 PM

Originally posted by Leia's Right Bun:
That is because you were using a pirated serial number and toast figured that out remember.

Version 5.2 is great!

That may be plausible, if my copy wasn't legit, which it is.

Leia's Right Bun · Dec 28, 2002, 12:16 AM

Originally posted by Cipher13:
That may be plausible, if my copy wasn't legit, which it is.

Well it is showing the EXACT signs of the actions it takes when it is pirated. So in that case you better open the package contents, remove the serial and try again.

Cipher13 · Dec 28, 2002, 12:19 AM

Originally posted by Leia's Right Bun:
Well it is showing the EXACT signs of the actions it takes when it is pirated. So in that case you better open the package contents, remove the serial and try again.

Very odd. We bought a few copies of it at work. I'll try one of the other serials from a different copy.

Thanks for that... wasn't aware it took such actions when it thought itself to be pirated. I assumed the app was just buggy.

Leia's Right Bun · Dec 28, 2002, 01:26 AM

Originally posted by Cipher13:

Thanks for that... wasn't aware it took such actions when it thought itself to be pirated. I assumed the app was just buggy.

Many people complained that 5.2 crashed on startup. All it was really doing was quitting if it found a pirated serial. SOME people with legit serials also had it quit. Roxio said in that case to open the package contents, locate the serial file (I forget the name of it) and then relaunch toast and put a legit one in again. You can find the file name on MacFixit or Roxio.

kennedy · Dec 29, 2002, 08:09 PM

Originally posted by Leia's Right Bun:
Many people complained that 5.2 crashed on startup. All it was really doing was quitting if it found a pirated serial. SOME people with legit serials also had it quit. Roxio said in that case to open the package contents, locate the serial file (I forget the name of it) and then relaunch toast and put a legit one in again. You can find the file name on MacFixit or Roxio.

I think its roxio.dat... just delete it. This is discussed at length in the reviews of the 5.2 update at versiontracker.com.

Brian

macmike42 · Dec 29, 2002, 09:54 PM

Originally posted by Leia's Right Bun:
SOME people with legit serials also had it quit.

Interestingly enough, if you remove the Rox.dat file and re-enter the exact same pirated serial, it starts up without a hitch. I only know this because someone told me, of course.

Don't pirate software! Don't do drugs! Stay in school!

wataru · Dec 30, 2002, 01:22 AM

Originally posted by macmike42:
Don't pirate software! Don't do drugs! Stay in school!

Drink your school! Stay in milk!

Shibby · Dec 30, 2002, 08:06 AM

I had the same problems when updating to 5.2. i gave up but eventually tried it again still no luck but found this on Roxio's site give it a try follow it exactly and all should work well.

http://www.roxio.com/en/support/roxi...otes.html#TIPS