Hard rebooted the laptop.Īttempt 2: Failed. I had time to answer ‘yes’ to uninstalling Acrobat 6.0 but that’s about all. DVD reader on the laptop didn’t appear to read the DVD after the first minute or so. Here’s why it’s taken so long and some solutions and locations of places that might be able to help if you have any of the same issues I had.Īttempt 1: Failed. It’s taken nearly a day and a half… And I’ve only got it installed-I haven’t tested if the darned thing actually works yet! BTW, my 5-year old laptop has Windows XP SP2 installed, some 7.5 GB free space, 512 MB RAM, meeting the recommended requirements from Adobe. Acrobat 6 is the lowest number for the upgrade-if you have Acrobat 5.0 you’re out of luck and will have to purchase at the full price, not the upgrade price.Īfter spending quite a few hours identifying and deleting some 4 GB (!) of data from my laptop and defragging it, I was ready to install. My current installation is Acrobat 6.0 Professional, so I’m making a bit of an upgrade jump with this one.
#UPDATE FOR ADOBE ACROBAT 9 PRO INSTALL#
I decided to install it on my laptop and test it out with Author-it and Word 2003 (in particular) before deciding whether to install it on my main production machine.
I pre-ordered Acrobat 9 Professional and received my DVD earlier this week.
#UPDATE FOR ADOBE ACROBAT 9 PRO UPDATE#
Update 14 August 2008: More issues with Table of Contents linking, and a solution… And I can confidently state that it works fine with Vista Ultimate 64-bit and Office 2007! Sometime in the next week or so Later, I’ll install it on my main machine. Update 26 July 2008: Better late than never… After dealing with the malware crisis and getting my new laptop, I FINALLY got to install Acrobat 9 on Vista on the new laptop. I will stand by the general comments I made, though, on the usefulness or otherwise of error messages. I’d like to thank Adobe Support for their testing and promptness in getting back to me when they said they would, and the Adobe Forums participants who also tested my files. Bottom line: It looks as though most of the issues documented in this post were the result of a bad local environment-lurking Registry entries etc.
0 kommentar(er)
