Installing Office XP Standard on a new computer

[LarsTjelle]

I have renewed my computer and want to re-install my Office XP Standard
version 2002. This is a retail version I puchased from the US while living
in Japan.
On the new computer, I have installed the old C:drive on which Office was
installed before. I now have a new HDD on which WinXP Pro has been installed
an the old HDD has become drive D:
However, when I put the CD-ROM in to install, I get an error message saying:
"Error 2721 An internal error has occured. (VerifyUnicodeInstallPathnameOK)".
Puttng the CD in another computer starts the installation process without
error.
Any thoughts?

 

[JoAnn Paules [MVP]]

Fair warning: I know squat about what this means but I found the following:

This error has been reported to occur when running from a UNC path- try
mapping a drive to the share to eliminate this as a potential issue (UNC
paths are supported so this should not be a problem).

 

[JoAnn Paules [MVP]]

Fair warning: I know squat about what this means but I found the following:

This error has been reported to occur when running from a UNC path- try
mapping a drive to the share to eliminate this as a potential issue (UNC
paths are supported so this should not be a problem).

 

[JoAnn Paules [MVP]]

Fair warning: I know squat about what this means but I found the following:

This error has been reported to occur when running from a UNC path- try
mapping a drive to the share to eliminate this as a potential issue (UNC
paths are supported so this should not be a problem).

 

[JoAnn Paules [MVP]]

Fair warning: I know squat about what this means but I found the following:

This error has been reported to occur when running from a UNC path- try
mapping a drive to the share to eliminate this as a potential issue (UNC
paths are supported so this should not be a problem).

 

[JoAnn Paules [MVP]]

Fair warning: I know squat about what this means but I found the following:

This error has been reported to occur when running from a UNC path- try
mapping a drive to the share to eliminate this as a potential issue (UNC
paths are supported so this should not be a problem).

 

[JoAnn Paules [MVP]]

Fair warning: I know squat about what this means but I found the following:

This error has been reported to occur when running from a UNC path- try
mapping a drive to the share to eliminate this as a potential issue (UNC
paths are supported so this should not be a problem).

 

[JoAnn Paules [MVP]]

Fair warning: I know squat about what this means but I found the following:

This error has been reported to occur when running from a UNC path- try
mapping a drive to the share to eliminate this as a potential issue (UNC
paths are supported so this should not be a problem).

 

[JoAnn Paules [MVP]]

Fair warning: I know squat about what this means but I found the following:

This error has been reported to occur when running from a UNC path- try
mapping a drive to the share to eliminate this as a potential issue (UNC
paths are supported so this should not be a problem).

 

[LarsTjelle]

Fair warning: I know squat about what this means but I found the following:

This error has been reported to occur when running from a UNC path- try
mapping a drive to the share to eliminate this as a potential issue (UNC
paths are supported so this should not be a problem).

Thank you for the answer, I am afraid I understand just as little of it as
You ;-) But thanks anyway. Baybe somebody else cab shed some light on this
technical jibberish?

 

[LarsTjelle]

Fair warning: I know squat about what this means but I found the following:

This error has been reported to occur when running from a UNC path- try
mapping a drive to the share to eliminate this as a potential issue (UNC
paths are supported so this should not be a problem).

Thank you for the answer, I am afraid I understand just as little of it as
You ;-) But thanks anyway. Baybe somebody else cab shed some light on this
technical jibberish?

 

[LarsTjelle]

Fair warning: I know squat about what this means but I found the following:

This error has been reported to occur when running from a UNC path- try
mapping a drive to the share to eliminate this as a potential issue (UNC
paths are supported so this should not be a problem).

Thank you for the answer, I am afraid I understand just as little of it as
You ;-) But thanks anyway. Baybe somebody else cab shed some light on this
technical jibberish?

 

[LarsTjelle]

Fair warning: I know squat about what this means but I found the following:

This error has been reported to occur when running from a UNC path- try
mapping a drive to the share to eliminate this as a potential issue (UNC
paths are supported so this should not be a problem).

Thank you for the answer, I am afraid I understand just as little of it as
You ;-) But thanks anyway. Baybe somebody else cab shed some light on this
technical jibberish?

 

[LarsTjelle]

Fair warning: I know squat about what this means but I found the following:

This error has been reported to occur when running from a UNC path- try
mapping a drive to the share to eliminate this as a potential issue (UNC
paths are supported so this should not be a problem).

Thank you for the answer, I am afraid I understand just as little of it as
You ;-) But thanks anyway. Baybe somebody else cab shed some light on this
technical jibberish?

 

[LarsTjelle]

Fair warning: I know squat about what this means but I found the following:

This error has been reported to occur when running from a UNC path- try
mapping a drive to the share to eliminate this as a potential issue (UNC
paths are supported so this should not be a problem).

Thank you for the answer, I am afraid I understand just as little of it as
You ;-) But thanks anyway. Baybe somebody else cab shed some light on this
technical jibberish?

 

[LarsTjelle]

Fair warning: I know squat about what this means but I found the following:

This error has been reported to occur when running from a UNC path- try
mapping a drive to the share to eliminate this as a potential issue (UNC
paths are supported so this should not be a problem).

Thank you for the answer, I am afraid I understand just as little of it as
You ;-) But thanks anyway. Baybe somebody else cab shed some light on this
technical jibberish?

 

[LarsTjelle]

Fair warning: I know squat about what this means but I found the following:

This error has been reported to occur when running from a UNC path- try
mapping a drive to the share to eliminate this as a potential issue (UNC
paths are supported so this should not be a problem).

Thank you for the answer, I am afraid I understand just as little of it as
You ;-) But thanks anyway. Baybe somebody else cab shed some light on this
technical jibberish?

 

[JoAnn Paules [MVP]]

This would be my wild guess:

Since you had Office installed on the original hard drive, maybe there's
something forcing your install to look at the new hard drive and it see a
conflict in the mapping. Did you uninstall Office from the original drive?

--

JoAnn Paules
MVP Microsoft [Publisher]

 

[JoAnn Paules [MVP]]

This would be my wild guess:

Since you had Office installed on the original hard drive, maybe there's
something forcing your install to look at the new hard drive and it see a
conflict in the mapping. Did you uninstall Office from the original drive?

--

JoAnn Paules
MVP Microsoft [Publisher]

 

[JoAnn Paules [MVP]]

This would be my wild guess:

Since you had Office installed on the original hard drive, maybe there's
something forcing your install to look at the new hard drive and it see a
conflict in the mapping. Did you uninstall Office from the original drive?

--

JoAnn Paules
MVP Microsoft [Publisher]