Command Workstation 5 and Mac Snow Leopard issue

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • pspahr
    Toner Schlep

    100+ Posts
    • May 2008
    • 227

    #1

    Command Workstation 5 and Mac Snow Leopard issue

    Hello all, long time no see. I've a question someone might be able to answer that so far searching the EFI site has yielded no answers to. One of my customers has Macs and all are running the prior OSX. One is using Snow Leopard and is the one in question. Through any of the others using CWS 5 they can connect, print, hold, and change properties to any file and send that file to either of the two fierys on their network without issue. The snow leopard box can open up both fierys, see submitted jobs in the hold and printed queues but cannot open any of those to edit properties and also cannot send the files that they or others have submitted to print. They are logged in as administrator to the fiery. I've not called EFI yet but may soon.

    I was thinking maybe an uninstall/reinstall might work. I was unable to find how to uninstall from a Mac other than with the Fiery Control Center. That is not installed on the Mac in question, or at least I am unable to find it. Any ideas on how that might be accomplished?

    As usual, thanks for any help provided.
    VectorLinux---Check it out!
  • D_L_P
    Self Employed

    1,000+ Posts
    • Oct 2009
    • 1196

    #2
    Typically the uninstall programs for Mac's will be on the same CD-ROM used to install it.

    Comment

    • cobiray
      Passing Duplication Xpert

      1,000+ Posts
      • Mar 2008
      • 1199

      #3
      Originally posted by D_L_P
      Typically the uninstall programs for Mac's will be on the same CD-ROM used to install it.
      x2

      If a reinstall doesn't solve it, is there a newer version available for use with Snow Leopard? I don't know what the version is up to by now, but perhaps there is a newer version than what you've got installed.
      the savin2535 is displaying well bet the hiter lamp is not shining and the lamp had been tested o.k.please kindly help.
      Samir: No, not again. I... why does it say paper jam when there is no paper jam? I swear to God, one of these days, I just kick this piece of shit out the window.
      Michael Bolton: You and me both, man. That thing is lucky I'm not armed.

      Comment

      • Ezekiel25:17

        #4
        Originally posted by pspahr
        Hello all, long time no see. I've a question someone might be able to answer that so far searching the EFI site has yielded no answers to. One of my customers has Macs and all are running the prior OSX. One is using Snow Leopard and is the one in question. Through any of the others using CWS 5 they can connect, print, hold, and change properties to any file and send that file to either of the two fierys on their network without issue. The snow leopard box can open up both fierys, see submitted jobs in the hold and printed queues but cannot open any of those to edit properties and also cannot send the files that they or others have submitted to print. They are logged in as administrator to the fiery. I've not called EFI yet but may soon.

        I was thinking maybe an uninstall/reinstall might work. I was unable to find how to uninstall from a Mac other than with the Fiery Control Center. That is not installed on the Mac in question, or at least I am unable to find it. Any ideas on how that might be accomplished?

        As usual, thanks for any help provided.
        pspahr..Use the link below to download the latest CWS5.x version (which supposedly resolves the Mac issues...). Enjoy...
        Fiery Command WorkStation 5

        Comment

        • pspahr
          Toner Schlep

          100+ Posts
          • May 2008
          • 227

          #5
          Much appreciated, fellas! I'm dl'ing the latest version....thought I had that one already. Oh well, stupid is as stupid tries to do, or some such nonsense.
          VectorLinux---Check it out!

          Comment

          • Kamelboi711
            Network Specialist
            • Mar 2008
            • 22

            #6
            Try using AppCleaner to uninstall the CWS then re-install it again...

            AppCleaner

            Comment

            Working...