"AMD" <email@example.com> wrote in message
> "Lang Murphy" <firstname.lastname@example.org> wrote in message
>> "ray" <email@example.com> wrote in message
>>> On Tue, 17 Jul 2007 10:50:51 -0700, AMD wrote:
>>>> I get Error 1310
>>>> Error writing to file c:\config.msi\25093.rbf. Verify that you have
>>>> 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
>>>> admin with full rights. So what is going on here?
>>> Since no one else can bother to give you a helpful suggestion, I'll try.
>>> FWIW - it won't cost a farthing to try out OpenOffice.org. It will
>>> probably do everything you need. OpenOffice.org is an open source office
>>> suite - a work alike of ms office. It imports and exports ms office
>>> formats as well as word perfect and several other formats.
>> I don't read your post as being any more helpful to answering the
>> original question about installing Office than the other posts. Your
>> "helpful" suggestion is "don't use Office." OK, what about the
>> WordPerfect Suite? Or Works?
>> To the original poster: try this link:
>> This KB article is specifically about Office 2000... but it can't hurt to
>> read it.
>> Good luck,
> Thanks for the link.
> I am installing from the pc so i tried the unreg and re reg of the
> installer thingy in method 2. did not work still.
Well... sorry bout that... I'm out of ideas. I haven't gone back and read
the other replies... u did try installing as admin? Kicking off the install
with "Run as Administrator"? Doesn't matter if you're logged on as admin...
when you try to run an app, it still runs in user context, I believe. Still
have to select Run as Administrator option by right clicking on install exe.
I've got Office 2007 running on two Vista Ultimate boxes here... might want
to try an Office ng...
I noticed you said that two different installs choked on two different file
names... well... if they're temp files, the names of which might be
generated on the fly, could be the same file... sounds like a permissions
issue... so.... try the Run as Administrator thing, even though you're
logged on as admin.