|
| If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|||||||
|
|
Thread Tools | Display Modes |
|
#1
December 14th, 2009, 10:21 AM
posted to microsoft.public.office.misc,microsoft.public.office.setup,microsoft.public.officeupdate
|
|||
|
|||
"Configuring Microsoft Office Basic 2007" every time I start
I added memory to my PC and Office 2003 started to misbehave (and it could
not find a CAB file that was on the CD) so I removed it and upgraded to Office 2007. Now every time I start my PC it spends time configuring itself. I might add iTunes is the same. It means starting the PC is an even more laborious process than usual. Oh, and I have some annoying update to XML something or other that does not install either, and does not go away. It is ironic that the extra memory was to improve perforamnce. Every step forwards involves two steps back. Apart from swapping to Apple (as my niece suggested), does anyone know of any fixes? 
|
|
#2
December 14th, 2009, 04:16 PM
posted to microsoft.public.office.misc,microsoft.public.office.setup,microsoft.public.officeupdate
|
|||
|
|||
|
"Configuring Microsoft Office Basic 2007" every time I start
In article , Bill Davy wrote:
I added memory to my PC and Office 2003 started to misbehave (and it could not find a CAB file that was on the CD) so I removed it and upgraded to Office 2007. Now every time I start my PC it spends time configuring itself. I might add iTunes is the same. It means starting the PC is an even more laborious process than usual. Oh, and I have some annoying update to XML something or other that does not install either, and does not go away. It is ironic that the extra memory was to improve perforamnce. Every step forwards involves two steps back. Try removing and re-seating the memory chip. I've had windows report that it was unable to access files on the disk after I've upgraded (but not properly seated) memory.
|
|
#3
December 15th, 2009, 08:55 AM
posted to microsoft.public.office.misc,microsoft.public.office.setup,microsoft.public.officeupdate
|
|||
|
|||
|
"Configuring Microsoft Office Basic 2007" every time I start
"Steve Rindsberg" wrote in message
... In article , Bill Davy wrote: I added memory to my PC and Office 2003 started to misbehave (and it could not find a CAB file that was on the CD) so I removed it and upgraded to Office 2007. Now every time I start my PC it spends time configuring itself. I might add iTunes is the same. It means starting the PC is an even more laborious process than usual. Oh, and I have some annoying update to XML something or other that does not install either, and does not go away. It is ironic that the extra memory was to improve perforamnce. Every step forwards involves two steps back. Try removing and re-seating the memory chip. I've had windows report that it was unable to access files on the disk after I've upgraded (but not properly seated) memory. I'll try that tonight though I would hardly expect the chip to pass the BIOS memory test if it was noisy. Worth a try though. Thanks, Bill
|
|
#4
December 15th, 2009, 01:17 PM
posted to microsoft.public.office.misc,microsoft.public.office.setup,microsoft.public.officeupdate
|
|||
|
|||
|
"Configuring Microsoft Office Basic 2007" every time I start
Bill Davy wrote: "Steve Rindsberg" wrote in message ... In article , Bill Davy wrote: I added memory to my PC and Office 2003 started to misbehave (and it could not find a CAB file that was on the CD) so I removed it and upgraded to Office 2007. Now every time I start my PC it spends time configuring itself. I might add iTunes is the same. It means starting the PC is an even more laborious process than usual. Oh, and I have some annoying update to XML something or other that does not install either, and does not go away. It is ironic that the extra memory was to improve perforamnce. Every step forwards involves two steps back. Try removing and re-seating the memory chip. I've had windows report that it was unable to access files on the disk after I've upgraded (but not properly seated) memory. I'll try that tonight though I would hardly expect the chip to pass the BIOS memory test if it was noisy. Worth a try though. Thanks, Bill Unless you ran a utility to test memory, you haven't tested it, the BIOS is merely a "memory check" to see what is installed.
|
|
#5
December 16th, 2009, 04:52 PM
posted to microsoft.public.office.misc,microsoft.public.office.setup,microsoft.public.officeupdate
|
|||
|
|||
|
"Configuring Microsoft Office Basic 2007" every time I start
"Bill Davy" wrote in message
... "Steve Rindsberg" wrote in message ... In article , Bill Davy wrote: I added memory to my PC and Office 2003 started to misbehave (and it could not find a CAB file that was on the CD) so I removed it and upgraded to Office 2007. Now every time I start my PC it spends time configuring itself. I might add iTunes is the same. It means starting the PC is an even more laborious process than usual. Oh, and I have some annoying update to XML something or other that does not install either, and does not go away. It is ironic that the extra memory was to improve perforamnce. Every step forwards involves two steps back. Try removing and re-seating the memory chip. I've had windows report that it was unable to access files on the disk after I've upgraded (but not properly seated) memory. I'll try that tonight though I would hardly expect the chip to pass the BIOS memory test if it was noisy. Worth a try though. Thanks, Bill OK, passed two hours of memory test without error. So, what gives? I did find something about changing the permissions for the registry entry for .pip but that seems a bit random.
|
|
#6
December 17th, 2009, 04:21 PM
posted to microsoft.public.office.misc,microsoft.public.office.setup,microsoft.public.officeupdate
|
|||
|
|||
|
"Configuring Microsoft Office Basic 2007" every time I start
OK, passed two hours of memory test without error. Oh well. Another nice theory goes down in flames. Still, it's good that you could eliminate bad/mis-seated RAM as the culprit. I did find something about changing the permissions for the registry entry for .pip but that seems a bit random. .PIP files hold config info for some of the office apps. It's worth a try ...
|
|
#7
December 17th, 2009, 04:54 PM
posted to microsoft.public.office.misc,microsoft.public.office.setup,microsoft.public.officeupdate
|
|||
|
|||
|
"Configuring Microsoft Office Basic 2007" every time I start
"Steve Rindsberg" wrote in message
... OK, passed two hours of memory test without error. Oh well. Another nice theory goes down in flames. Still, it's good that you could eliminate bad/mis-seated RAM as the culprit. I did find something about changing the permissions for the registry entry for .pip but that seems a bit random. PIP files hold config info for some of the office apps. It's worth a try ... I've found another "cure" at http://forums.techarena.in/office-setup/659180.htm so I will try that and report back next week.
|
|
#8
December 21st, 2009, 11:02 AM
posted to microsoft.public.office.misc,microsoft.public.office.setup,microsoft.public.officeupdate
|
|||
|
|||
|
"Configuring Microsoft Office Basic 2007" every time I start
"Bill Davy" wrote in message
... "Steve Rindsberg" wrote in message ... OK, passed two hours of memory test without error. Oh well. Another nice theory goes down in flames. Still, it's good that you could eliminate bad/mis-seated RAM as the culprit. I did find something about changing the permissions for the registry entry for .pip but that seems a bit random. PIP files hold config info for some of the office apps. It's worth a try ... I've found another "cure" at http://forums.techarena.in/office-setup/659180.htm so I will try that and report back next week. Nope. And no yellow triangles in the event log. Guess I'll have to live with it. Perhaps in an update one day they will fix the problem.
|
|
#9
December 21st, 2009, 04:28 PM
posted to microsoft.public.office.misc,microsoft.public.office.setup,microsoft.public.officeupdate
|
|||
|
|||
|
"Configuring Microsoft Office Basic 2007" every time I start
In article , Bill Davy wrote:
"Bill Davy" wrote in message ... "Steve Rindsberg" wrote in message ... OK, passed two hours of memory test without error. Oh well. Another nice theory goes down in flames. Still, it's good that you could eliminate bad/mis-seated RAM as the culprit. I did find something about changing the permissions for the registry entry for .pip but that seems a bit random. PIP files hold config info for some of the office apps. It's worth a try ... I've found another "cure" at http://forums.techarena.in/office-setup/659180.htm so I will try that and report back next week. Nope. And no yellow triangles in the event log. Guess I'll have to live with it. Perhaps in an update one day they will fix the problem. Sigh ... O well. Sorry to hear it.
|
| Thread Tools | |
| Display Modes | |
|
|
Linear Mode
