XPost: microsoft.public.word.newusers, microsoft.public.windowsxp.general   
   From: MikeS@fred.com   
      
   On 04/06/2016 06:22, Steve Hayes wrote:   
   > On Wed, 25 May 2016 04:05:57 +0700, JJ  wrote:   
   >   
   >> On Tue, 24 May 2016 19:37:21 +0200, Steve Hayes wrote:   
   >>> I installed MS Office 2003 on my computer the other day, and since   
   >>> then it seems to run a lot slower, and it takes 20-30 minutes to boot   
   >>> instead of the usual 7 (Windows XP)*   
   >>   
   >> In my old system (1.6GHz 2-cores, 2GB RAM), it took about 2 minutes to boot.   
   >> A 7 minutes boot seems a lot is going on, or the PC or HDD is just slow.   
   >>   
   >> - Office 2003 minimum RAM is 1GB. If you only have 2GB of RAM and using more   
   >> than 500MB after boot up before Office 2003 is installed, it's likely that   
   >> you now have very little memory space left for applications. AFAIK, Office   
   >> installs an application that is run at startup. It sets up and pre-loads   
   >> files that are used by any Office suite applications so that the   
   >> applications would load faster. The disadvantage is that it consume memory,   
   >> in expense for faster application loading. If the total memory consumption   
   >> in the whole system is larger than the RAM capacity, there will be memory   
   >> data swapping to and from the disk, which slows down the overall system   
   >> performance. Fix: turn off and disable unneeded applications. i.e. no need   
   >> to run an application at startup if it's not used every day.   
   >   
   > Thanks for this.   
   >   
   > I've tried using autoruns, but it doesn't seem to make much   
   > difference.   
   >   
   > I'm thinking of doing the following:   
   >   
   > 1) Uninstalling MS-Office 2003   
   > 2) Restoring the System ?Restore point I created before installing it   
   > 3) Restoring the backups I made of the relevant disks before   
   > installing MS Office 2003.   
   >   
   > Any recommendations about the best order for doing those things?   
   >   
   >   
   The problems described are not caused by Office 2003 as such and the   
   comment "Office 2003 minimum RAM is 1GB" is nonsense. I have had it   
   running fine for years on several Win XP laptops one of which is 10   
   years old and has 512MB RAM. It is also working well on a Virtualbox Win   
   XP VM with only 384MB RAM which I run on a very modest Win 10   
   laptop/tablet with a 1.33GHz Atom processor.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)