Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Fix Quark QLA server after Java update' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Fix Quark QLA server after Java update
Authored by: themacuser on Apr 26, '06 05:52:03PM

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.



[ Reply to This | # ]
Quark and Individual Licenses??!
Authored by: gabester on Apr 26, '06 08:43:45PM

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.

Not that running QLA is much better... I was all for InDesign and recommended it over Quark to customers until CS2 came out and the same kind of product activation stuff is included for InDividual licensed copies. Fortunately Adobe volume licensing has a low enough threshhold that it's much less of an issue. What would be nice would be software that when sold didn't punish legitimate customers in the vain attempts to discourage piracy.

QLA has many longstanding issues, however, and it would be nice if Quark made efforts to fix these. In the meantime, I will probably be using this hint sometime in the near future when I inadvertently upgrade J2SE and then realize that QLA is broken... or with some other app I'm not even aware of yet.
g=



[ Reply to This | # ]
Also... give QLA dedicated hardware...
Authored by: gabester on Apr 26, '06 08:46:21PM

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.



[ Reply to This | # ]