On 03/22/2010 04:58 AM, Jan van Hoek wrote:
>> I've had no 
>> problems using OOo 3.1.1
>  
> I had neither, until...
>  
>  
>> so OOo 3.2 (the current version)
>> should work
>  
> I've (re)tried to install OOo 3.2, but the install consistently just 
> hangs and produces, while using 25% CPU for hours, no workable version.
>  
> I've also tried a few workarounds that I saw on various forums, but to 
> no avail. For example, removing the "old" 3.1 version, or cleaning the 
> Windows Installer.
>  
> The only difference that MAY be relevant, is that I run a 64-bit version 
> of Windows 7. That is the only deviation that I can think of.
>  
> In other words, I'm still running OOo 3.1 without a problem. And as long 
> as I see no urgent reasons to make a move to OOo 3.2, I stay with that I 
> have.

As mentioned; I have 3.2.0 installed w/o issues on Win7 Home Premium
64bit (US English versions). I also had a previous 3.2.rc1 installed &
didn't bother to remove when installing 3.2.0 final.

Questions/suggestions:
1. When you try to install 3.2.0 do you have the OOo quickstarter
running? If so kill it first. Use the Ctrl-Alt-Del to start the task
manager and check for any soffice entries.
2. Check to ensure that your most recent java is fully up to date
(http://java.com - "Do I have Java") - if not update it to the latest
version (version 6 update 18).. Then download the Win OOo version
*without* java:
http://download.openoffice.org/other.html
Make sure this box is _unchecked_:
 Include the JRE to the download (this option is not available for Linux
32/64-bit Debian and Mac OS).
3. Are you logged in with admin privilages? If not, do so and try
installing. If it hangs, go back to the task manager and see if you can
tell which office processes are running. Note: it should not be
necessary to be admin to install, however this is how I installed mine
w/o issue, so just trying to 'replicate' my process.




---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to