Thanks, I'll try it and see. Hopefully if I have a version previous to 6.52, I'll be able to find the update. I'm sure it's a validation or expiry date thing. I'll let you know. Maybe this will help others.
Well Matthias - hate to say, but it happens on 10.3, 10.4, 10.5 and 10.6. My problem is upgrading because it's a small shop and we'd have to buy four new Mac's with newer operating systems to run Quark 9. and/or 10. Then all the other old software or most of it would not be supported on the newer OS. Ah - computers!! Setting the system date back works. What I'm doing as a temporary measure is: 1. Set system date back one year. 2. Open Quark 6.5. 3. Move system date to auto. As long as Quark is open and I don't quit or it doesn't crash it's good for all day!! I'm sure on a Mac in Terminal (Utility) I should be able to eventually locate the little monster code and change and/or eliminate. Don't know how to do that yet, but I'm googling the problem. I do appreciate any help you have to offer.
We have no idea what causes it, could be something in the system, a validation code generated wrongly by one employee maybe etc. We need to find out the cause and that it is 10 years ago makes it harder. Once we know the cause we can comment on whether we can/will fix this.
Anyone who purchases QuarkXPress 8 at the regular price between February 23, 2011 and April 30, 2011 is eligible to upgrade to QuarkXPress 9 for free. Customers who purchased QuarkXPress 8 between January 1, 2011, and February 23, 2011, are entitled to a complimentary upgrade to version 9. Those who qualify should complete the QuarkXPress 9 upgrade redemption form. Buyers who wish to redeem the free upgrade need valid serial numbers and validation codes established between January 1, 2011, and April 30, 2011.
Programmers are (generally) not good writers and writers are (generally) not software developers. But companies expect both jobs to be done by the same person (or team of people). The result is either bad code or bad documentation or both.
The Pragmatic Programming publishers do it all in LaTeX and they even error check the source code samples with a linter or compiler to ensure they are correct. Entirety of everything is kept in git revision control. This allows for fast errata fixes and everything is PDF. They can send the book to be printed dead tree style but programming changes so fast by the time a paper book is printed and shipped whole chapters need to be rewritten. 1e1e36bf2d