P
Pegasus
Point taken - I overlooked the crosspost.
Henk Jol said:
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
P
Pegasus
Point taken - I overlooked the crosspost.
Henk Jol said:Pegasus wrote:
snipThis group looks at Windows 2000 setup issues. Have you
tried an MS Office newsgroup?
As you can see in the header: yes.
Because it is a complex setup related issue I crossed the message to the
relevant os ng as well.
[Followup set to microsoft.public.office.setup]
P
Pegasus
Point taken - I overlooked the crosspost.
Henk Jol said:Pegasus wrote:
snipThis group looks at Windows 2000 setup issues. Have you
tried an MS Office newsgroup?
As you can see in the header: yes.
Because it is a complex setup related issue I crossed the message to the
relevant os ng as well.
[Followup set to microsoft.public.office.setup]
P
Pegasus
Point taken - I overlooked the crosspost.
Henk Jol said:Pegasus wrote:
snipThis group looks at Windows 2000 setup issues. Have you
tried an MS Office newsgroup?
As you can see in the header: yes.
Because it is a complex setup related issue I crossed the message to the
relevant os ng as well.
[Followup set to microsoft.public.office.setup]
P
Pegasus
Point taken - I overlooked the crosspost.
Henk Jol said:Pegasus wrote:
snipThis group looks at Windows 2000 setup issues. Have you
tried an MS Office newsgroup?
As you can see in the header: yes.
Because it is a complex setup related issue I crossed the message to the
relevant os ng as well.
[Followup set to microsoft.public.office.setup]
P
Pegasus
Point taken - I overlooked the crosspost.
Henk Jol said:Pegasus wrote:
snipThis group looks at Windows 2000 setup issues. Have you
tried an MS Office newsgroup?
As you can see in the header: yes.
Because it is a complex setup related issue I crossed the message to the
relevant os ng as well.
[Followup set to microsoft.public.office.setup]
P
Pegasus
Point taken - I overlooked the crosspost.
Henk Jol said:Pegasus wrote:
snipThis group looks at Windows 2000 setup issues. Have you
tried an MS Office newsgroup?
As you can see in the header: yes.
Because it is a complex setup related issue I crossed the message to the
relevant os ng as well.
[Followup set to microsoft.public.office.setup]
P
Pegasus
Point taken - I overlooked the crosspost.
Henk Jol said:Pegasus wrote:
snipThis group looks at Windows 2000 setup issues. Have you
tried an MS Office newsgroup?
As you can see in the header: yes.
Because it is a complex setup related issue I crossed the message to the
relevant os ng as well.
[Followup set to microsoft.public.office.setup]
P
Pegasus
Point taken - I overlooked the crosspost.
Henk Jol said:Pegasus wrote:
snipThis group looks at Windows 2000 setup issues. Have you
tried an MS Office newsgroup?
As you can see in the header: yes.
Because it is a complex setup related issue I crossed the message to the
relevant os ng as well.
[Followup set to microsoft.public.office.setup]
P
Pegasus
Point taken - I overlooked the crosspost.
Henk Jol said:Pegasus wrote:
snipThis group looks at Windows 2000 setup issues. Have you
tried an MS Office newsgroup?
As you can see in the header: yes.
Because it is a complex setup related issue I crossed the message to the
relevant os ng as well.
[Followup set to microsoft.public.office.setup]
P
Pegasus
Point taken - I overlooked the crosspost.
Henk Jol said:Pegasus wrote:
snipThis group looks at Windows 2000 setup issues. Have you
tried an MS Office newsgroup?
As you can see in the header: yes.
Because it is a complex setup related issue I crossed the message to the
relevant os ng as well.
[Followup set to microsoft.public.office.setup]
P
Pegasus
Point taken - I overlooked the crosspost.
Henk Jol said:Pegasus wrote:
snipThis group looks at Windows 2000 setup issues. Have you
tried an MS Office newsgroup?
As you can see in the header: yes.
Because it is a complex setup related issue I crossed the message to the
relevant os ng as well.
[Followup set to microsoft.public.office.setup]
P
Pegasus
Point taken - I overlooked the crosspost.
Henk Jol said:Pegasus wrote:
snipThis group looks at Windows 2000 setup issues. Have you
tried an MS Office newsgroup?
As you can see in the header: yes.
Because it is a complex setup related issue I crossed the message to the
relevant os ng as well.
[Followup set to microsoft.public.office.setup]
P
Pegasus
Point taken - I overlooked the crosspost.
Henk Jol said:Pegasus wrote:
snipThis group looks at Windows 2000 setup issues. Have you
tried an MS Office newsgroup?
As you can see in the header: yes.
Because it is a complex setup related issue I crossed the message to the
relevant os ng as well.
[Followup set to microsoft.public.office.setup]
P
Pegasus
Point taken - I overlooked the crosspost.
Henk Jol said:Pegasus wrote:
snipThis group looks at Windows 2000 setup issues. Have you
tried an MS Office newsgroup?
As you can see in the header: yes.
Because it is a complex setup related issue I crossed the message to the
relevant os ng as well.
[Followup set to microsoft.public.office.setup]
P
Pegasus
Point taken - I overlooked the crosspost.
Henk Jol said:Pegasus wrote:
snipThis group looks at Windows 2000 setup issues. Have you
tried an MS Office newsgroup?
As you can see in the header: yes.
Because it is a complex setup related issue I crossed the message to the
relevant os ng as well.
[Followup set to microsoft.public.office.setup]
P
Pegasus
Point taken - I overlooked the crosspost.
Henk Jol said:Pegasus wrote:
snipThis group looks at Windows 2000 setup issues. Have you
tried an MS Office newsgroup?
As you can see in the header: yes.
Because it is a complex setup related issue I crossed the message to the
relevant os ng as well.
[Followup set to microsoft.public.office.setup]
B
Ben Tupper
The problem most likely is that there are still some remnants of the
previous installation embedded in the Registry. The Microsoft utilities
don't do a very good job of removing these. You can manually edit and purge
the Registry (very dangerous), or you can download a shareware program
called RegVac, which isn't perfect, but does a much better job than the MS
programs. For tips on editing the Registry you can do a Google search for
"Registry Hacks." There are also good instructions on editing the Registry
in the Symantec NAV knowledge base. Not directly relevant to Office 2003,
but a good general outline on how to approach the Registry. Make a good
system backup before you begin.
Good luck!
Ben
previous installation embedded in the Registry. The Microsoft utilities
don't do a very good job of removing these. You can manually edit and purge
the Registry (very dangerous), or you can download a shareware program
called RegVac, which isn't perfect, but does a much better job than the MS
programs. For tips on editing the Registry you can do a Google search for
"Registry Hacks." There are also good instructions on editing the Registry
in the Symantec NAV knowledge base. Not directly relevant to Office 2003,
but a good general outline on how to approach the Registry. Make a good
system backup before you begin.
Good luck!
Ben
B
Ben Tupper
The problem most likely is that there are still some remnants of the
previous installation embedded in the Registry. The Microsoft utilities
don't do a very good job of removing these. You can manually edit and purge
the Registry (very dangerous), or you can download a shareware program
called RegVac, which isn't perfect, but does a much better job than the MS
programs. For tips on editing the Registry you can do a Google search for
"Registry Hacks." There are also good instructions on editing the Registry
in the Symantec NAV knowledge base. Not directly relevant to Office 2003,
but a good general outline on how to approach the Registry. Make a good
system backup before you begin.
Good luck!
Ben
previous installation embedded in the Registry. The Microsoft utilities
don't do a very good job of removing these. You can manually edit and purge
the Registry (very dangerous), or you can download a shareware program
called RegVac, which isn't perfect, but does a much better job than the MS
programs. For tips on editing the Registry you can do a Google search for
"Registry Hacks." There are also good instructions on editing the Registry
in the Symantec NAV knowledge base. Not directly relevant to Office 2003,
but a good general outline on how to approach the Registry. Make a good
system backup before you begin.
Good luck!
Ben
B
Ben Tupper
The problem most likely is that there are still some remnants of the
previous installation embedded in the Registry. The Microsoft utilities
don't do a very good job of removing these. You can manually edit and purge
the Registry (very dangerous), or you can download a shareware program
called RegVac, which isn't perfect, but does a much better job than the MS
programs. For tips on editing the Registry you can do a Google search for
"Registry Hacks." There are also good instructions on editing the Registry
in the Symantec NAV knowledge base. Not directly relevant to Office 2003,
but a good general outline on how to approach the Registry. Make a good
system backup before you begin.
Good luck!
Ben
previous installation embedded in the Registry. The Microsoft utilities
don't do a very good job of removing these. You can manually edit and purge
the Registry (very dangerous), or you can download a shareware program
called RegVac, which isn't perfect, but does a much better job than the MS
programs. For tips on editing the Registry you can do a Google search for
"Registry Hacks." There are also good instructions on editing the Registry
in the Symantec NAV knowledge base. Not directly relevant to Office 2003,
but a good general outline on how to approach the Registry. Make a good
system backup before you begin.
Good luck!
Ben
Ask a Question
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.