Page 1 of 2 12 LastLast
Results 1 to 10 of 12
  1. #1
    Sharon is offline Junior Member
    Join Date
    Nov 2009
    Posts
    11

    Default Kodak Workshop and Snow Leopard

    Help! I am new this forum so please bare with me. I just upgraded to Snow Leopard. I had an issue with Kodak Workshop but followed instructions to install Java 5. Worked wonderful. But now when I try to create in imposition in workshop it will not launch into preps????? It's telling me "Couldn't successfully startup or quit the application because of a Mac OS Error. Result Code = -1700. Or another error message I get is "Couldn't complete the last command because of a Mac OS Error. Result Code = -1700.

    Anyone come across this before??????

  2. #2
    Joe
    Joe is offline Senior Member
    Join Date
    Aug 2007
    Posts
    567

    Default

    Can you launch Preps by itself outside of Prinergy? Also, what version of Preps are you using?

    Also, Snow Leopard does not have AppleTalk so that could possibly be playing a role in the problem.

    And what version of Prinergy?

    There is a small bug in Prinergy 5 that can give you fits if you are connecting to the Prinergy network shares as SMB via the IP address. The solution is to use the name of the server instead of the IP address.
    Joe
    OS: Mac OS 10.6.7 - RIP: Prinergy Connect 5.1.2.3 - CTP: Luscher XPose! 160 (2)

  3. #3
    Eric Biggins is offline Junior Member
    Join Date
    Sep 2007
    Posts
    1

    Default

    Sharon,

    Do you have Rosetta installed? If not, that may be your issue. I know Preps 5, (not sure about Preps 6) is still a PowerPC app, so it requires OSX to run Rosetta in the background which supports older PowerPC apps. The first time you try to launch Preps, the OS should alert you to whether or not you want to install it.

    I'm running 10.6, and Preps 5 works fine but I had to install Rosetta first.

    Cheers,
    Eric

  4. #4
    Sharon is offline Junior Member
    Join Date
    Nov 2009
    Posts
    11

    Default Can't launch Workshop now

    I was able to get into Preps last week. Now today for some reason when I try to open Workshop it automatically quits on me. Has this happened to anyone else?????

    This adjustment into Snow Leopard is killing me!

  5. #5
    jeytye is offline Junior Member
    Join Date
    Feb 2009
    Posts
    1

    Default

    Yes, same thing happen here. On PC workstation no problem but when in Mac OS 10.6 Snow leopard, it would just quit without any notice or message prompt.

  6. #6
    Sharon is offline Junior Member
    Join Date
    Nov 2009
    Posts
    11

    Default

    Have you figured out how to resolve it?

  7. #7
    Sharon is offline Junior Member
    Join Date
    Nov 2009
    Posts
    11

    Default

    Quote Originally Posted by Joe View Post
    Can you launch Preps by itself outside of Prinergy? Also, what version of Preps are you using?

    Also, Snow Leopard does not have AppleTalk so that could possibly be playing a role in the problem.

    And what version of Prinergy?

    There is a small bug in Prinergy 5 that can give you fits if you are connecting to the Prinergy network shares as SMB via the IP address. The solution is to use the name of the server instead of the IP address.
    I actually figured out the problem with this. The name of the file had a "#" sign in it. Once I renamed the file it was fine. Go figure.....

  8. #8
    Joe
    Joe is offline Senior Member
    Join Date
    Aug 2007
    Posts
    567

    Default

    Quote Originally Posted by Sharon View Post
    I actually figured out the problem with this. The name of the file had a "#" sign in it. Once I renamed the file it was fine. Go figure.....
    I ran into a different problem about a week ago due to the # sign in the file name. Prinergy refined it but wouldn't make the VPS.
    Joe
    OS: Mac OS 10.6.7 - RIP: Prinergy Connect 5.1.2.3 - CTP: Luscher XPose! 160 (2)

  9. #9
    Sharon is offline Junior Member
    Join Date
    Nov 2009
    Posts
    11

    Default

    Quote Originally Posted by Sharon View Post
    I actually figured out the problem with this. The name of the file had a "#" sign in it. Once I renamed the file it was fine. Go figure.....
    I am only in 4.2.3

  10. #10
    Sharon is offline Junior Member
    Join Date
    Nov 2009
    Posts
    11

    Default

    Im only in 4.2.3


Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

Sponsors