Thanks Merv - you raise some interesting points. This has become even more of an issue since I have just produced my first 400 page PDF manual from Word 2000, with hundreds of misaligned links. There was an issue with Word cross references producing links that are offset, but I think this was fixed. This is different - links on the same page can start off OK, then randomly become half a line or a whole line from where they should be, but then are aligned at the bottom of the page.
 
I've also noticed that Acrobat 6.0 Pro is a lot slower opening and scrolling through PDF documents. I am using a 500 MHz Intel PC with 512MB ram, not fast by current standards, but good enough to multitask several other large apps.
 
I think the 'Downgrade Rights' issue is important enough to request a clear answer from Adobe. Microsoft make their policy (unusually) clear (www.microsoft.com/licensing/downloads/ downgrade_chart.doc) so that multi-user companies can manage their licenses. For instance: 'All system software licenses acquired through the Select or Open License programs are granted the right to downgrade (use a prior version)' BUT 'Application licenses acquired via the OEM channel follow rights granted in the OEM license.  OEM licenses do not typically grant downgrade rights'.  I had to uninstall 4.0 before installing 5.0, then again before installing 6.0, because Adobe warns against trying to run different versions on the same machine. So I would have to install 4.0 on a different machine, which I am sure would be against the EULA. But I have five licenses, so perhaps I am OK as long as no more than five versions are in use at any one time? I do not want to upgrade my other users until some of these issues are sorted out.
 
Steve
-----Original Message-----
From: Merv Leeding [mailto:[EMAIL PROTECTED]
Sent: 01 July 2003 12:16
To: [EMAIL PROTECTED]
Subject: [PDF-Basics] Using old versions

G'day

If no-one has found any workarounds for these issues, I would rather use
Version 4.0 for editing. But does the Acrobat license allow you to use an
older product after upgrading?

What normally happens is that when you upgrade you are required to keep the whole package (older versions plus upgrades) which becomes your "license". What is almost always prohibited is selling older version to others and this is understandable.

Upgrades often require use of the early package so that in itself implies you are still licensed for the whole package. Again, it is a common and reasonable practice to run the old and new versions while gaining experience with the new version. If the new one was incompatible with hardware then it would again be reasonable to be able to use the old one.

What may no longer be available, certainly after a period, is to get support on an older version.

Now I have deliberately couched that in terms of what is widely accepted with software. End users should always recognize that licenses, particularly where copyright is concerned, may have rights that flow from original copyright law, but a license is a contract and when you accept a contract, you accept the provisions in it. In this case I would say you are OK unless there is a clear prohibition in the text of the license.

I can understand Adobe being surprised by the question since it is far removed from the greater issue of piracy through sale of upgraded software.

I can cite on example of a license prohibition that probably dates back to around 1985. Lotus 123 came with two diskettes labelled "Program" and "Backup". The license was explicit but bear in mind that it was copy protected and had to stay in the floppy drive while the program was in use.

(I don't vouch for the exact words but this would be farily close. We had to order a replacement diskette at the company where I worked.)

"You may not use the Backup diskette unless and until the Program diskette becomes faulty. You may then use the Backup diskette while you send the Program diskette for replacement. As soon as a replacement is received you must discontinue using the Backup diskette."



Regards
Merv Leeding

Reply via email to