|
|
Fix Quark QLA server after Java update
Or how about you fix that problem how I fixed it when I had to use QLA: Get individual licenses. QLA is an awful piece of junk. It never worked right on my Xserve. It wasted hours of company time, and was NOT worth the saving for the site licenses. We lost many times more money in lost productivity. The copies of InDesign we bought "just in case" were the best decision ever.
Quark and Individual Licenses??!
Individual licenses aren't really a practical solution for large installations or dynamic environments where frequent reformatting may occur (labs, intensive designer usage) - keeping track of, much less retyping those 64-character long activation codes are a nightmare. In such situations QLA is a better solution by far; it's also nice for workgroups where many people use Quark infrequently because it allows you to install the app on every computer that might run it; you just can't run it on more machines than you are licensed for simultaneously.
Also... give QLA dedicated hardware...
I'd also recommend not running QLA on important hardware that serves other functions. Put it on an old Blue and White G3 or iMac tucked away somewhere... heck, even a Mac mini if you have the money lying around; but the idea of running QLA on a server performing other tasks is quite unpleasant precisely because of it's numerous performance issues. |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:Hints1 new Hints in the last 24 hoursComments last 2 daysNo new commentsLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.09 seconds |
|