I had the same problem trying to install office 2007 on vista but also got an
error 2203 message as well. Spent 5 hours on the phone with MS Product
support and they could not fix. tried downloading a clean file, same problem,
so issue was not the CD being damaged. Changed file extensions to .old, gave
access to everyone to everything, still did not work. If you find an answer,
MS would like toknow as well. They finally told me they would have to involve
the Vista Product support team and call me back. It has been two days and
still no answer. Now, All I want to know is HOW DO I GET MY MONEY BACK FOR
THE SOFTWARE?
"AMD" wrote:
> "ray" <ray@zianet.com> wrote in message
> news
an.2007.07.13.03.38.43.913040@zianet.com...
> > On Thu, 12 Jul 2007 17:21:05 -0700, AMD wrote:
> >
> >> "Jupiter Jones [MVP]" <jones_jupiter@hotnomail.com> wrote in message
> >> news:e87OhlCxHHA.1484@TK2MSFTNGP06.phx.gbl...
> >>> Differing errors suggest damaged/dirty media or drive.
> >>> Bad memory can also cause it.
> >>>
> >>> If the same media was used for other installation, clean it.
> >>>
> >>> Otherwise since this is a Windows Vista newsgroup, try an Office
> >>> newsgroup:
> >>> http://aumha.org/nntp.htm
> >>>
> >>> --
> >>> Jupiter Jones [MVP]
> >>> http://www3.telus.net/dandemar
> >>> http://www.dts-l.org
> >>>
> >>>
> >>> "AMD" <g@g.com> wrote in message
> >>> news:%236XQhlBxHHA.4652@TK2MSFTNGP05.phx.gbl...
> >>>>I get Error 1310
> >>>>
> >>>> Error writing to file c:\config.msi\25093.rbf. Verify that you have
> >>>> access to that directory.
> >>>>
> >>>> Everytime I try to install Office 2007 Pro in Vista Ultimate I get this
> >>>> error, but I have gotten a different filename the 2 times I tried to
> >>>> install. Works fine on my other pc running windows xp. in vista i am
> >>>> full
> >>>> admin with full rights. So what is going on here?
> >>>
> >>
> >>
> >> Installs fine in windows xp.
> >> i posted in an office group with no reply.
> >
> > Suggest you try OpenOffice.org - won't cost you a farthing to check it
> > out.
> >
>
>
> thanks, but that doesn't answer my question.
>
>