In news:[email protected],
Rob Clement <[email protected]> typed:
> Is it just my machine AMD 2.0 Ghz running windows Vista
> seems to take a very long time installing Ooo 3.2.1.
>
> Thanks
>
> Rob

Well, yes, it is, and err, no, it is not. You have to remember that you're 
installing a pretty large and complex program with OO.o. It can -seem- 
longer when compared to, say, installing MA Office and all of its OO.o 
comparable programs (word processor, spread sheet, database, excel, draw, 
etc etc etc.. Where with MSO you install the Office portion and then the 
Word, then Excel, then Power Point, then Access and ... but there's no disk 
swapping with OO.o; it does it all in one throw, so to speak.
   Yes, OO.o does take a comparatively long time to install, but not 
inordinatly so unless something (background tasks, not enough RAM, etc. 
etc.) else helps to slow it down. You don't give a timeframe, but I just 
installed 3.2.1 before responding here and it didn't seem any slower or any 
faster than any of the past installs I've done of past versions.  Other than 
the installation I did nothing else on the machine because I knew it took a 
fair amount of time to install it and I prefer to watch, so if something 
goes astray, I know more about when it happended and what t was doing, 
thanks to the status report all during the install.
   After all, how long IS too long for an install? <g>.  There's a finite 
amount of work that must be done and that of course takes a finite length of 
time. Everything from your RAM amount to cpu speed/cpu load to hard drive 
rpms and more all comes into play for the install. I'm guessing but it must 
have been around 7 minutes for my install and I have a 3 GHz cpu, GHz Front 
side Buss, 4 Gig RAM, 10,000 rpm SATA hard drives and my page file on a 
separate physical hard drive and probably a few other things I'm not 
thinking of.

HTH,

Twayne`




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

Reply via email to