c:\Config.msi problem

I have spent the last couple of days trying to install Adobe Photosho
CS4 on
a dual core Vista 64 system. I was receiving the dreaded message about
c:\config.msi not accessible. Search of the web revealed this occurs
regularly durnig various installs and many have "cures" revolvin
around
elevating priviledges, etc. I tried all the various suggestions an
kept
failing - at least 25 or 30 times.

My experience was that it hit randomly during the somewhat long instal

process of CS4. While some installs just keep going anyway, CS4 doe
not.
The config.msi folder stores rollback info during the install process
If no
rollback is required, I would assume that the files stored there are
unnecessary. Those installs that merely post the error and continu
seem to
be OK. CS4 won't do that.

I decided that whatever the bug was, it was a "race" condition of som
sort,
so I decided to slow my system down by running other things during the
install. Ultimately I had two videos and the Process Monitor utilit
going,
and the install finished successfully.

This is why the bug appears randomly across the universe - it i
dependent
on system speed and clearly exascerbated by multiprocessin
configurations.

I hope this is helpful to those of you who find this post by searchin
the
web, as I did

--
sherlocc

"sherlocc" wrote:

>
> I have spent the last couple of days trying to install Adobe Photoshop
> CS4 on
> a dual core Vista 64 system. I was receiving the dreaded message about
> c:\config.msi not accessible. Search of the web revealed this occurs
> regularly durnig various installs and many have "cures" revolving
> around
> elevating priviledges, etc. I tried all the various suggestions and
> kept
> failing - at least 25 or 30 times.
>
> My experience was that it hit randomly during the somewhat long install
>
> process of CS4. While some installs just keep going anyway, CS4 does
> not.
> The config.msi folder stores rollback info during the install process.
> If no
> rollback is required, I would assume that the files stored there are
> unnecessary. Those installs that merely post the error and continue
> seem to
> be OK. CS4 won't do that.
>
> I decided that whatever the bug was, it was a "race" condition of some
> sort,
> so I decided to slow my system down by running other things during the
> install. Ultimately I had two videos and the Process Monitor utility
> going,
> and the install finished successfully.
>
> This is why the bug appears randomly across the universe - it is
> dependent
> on system speed and clearly exascerbated by multiprocessing
> configurations.
>
> I hope this is helpful to those of you who find this post by searching
> the
> web, as I did.
>
>
> --
> sherlocc

And I have spoofed, and abused here for a long, long time.
But, I have been out-spoofed, and out-abused!
Congratulations to the Ultimate Spoofer / Abuser!
I hand over the Crown.

These are some of my Spoofs, and Aliases

Anti on Chicken Little(s)
Chicken Little Albright
Dan S-illy aka Barney Phife
Doctor Bee
General Paul Montgomery
General Paul Montgomery1
General Paul Montgomery2
General Paul Montgomery3
General Paul Montgomery4
General Paul Montgomery5
General Paul Montgomery6
General Paul Montgomery7
Hunting for JackA$$
Junk Yard Dog
Kotex Queen Clear Windows
Mick Murphy
Montgumdrop
Mr. Arnold
MontGumDropped1 Paul
Paul MontDenturesDropped
Paul Montgomery
Paul Montgomery 9000
Paul Montgumdrop
Pauly
Ringmonster
Sudden Impact
Tall Tales Albright
The Bee
The Big Ticket
The Hornet
Van Helsing the Albright Hunter


>

Paul Montgomery wrote:
> <http://www.hyphenologist.co.uk/killfile/anti_troll_faq.htm>
>
> Subject: 4.5 Personal attacks on individuals and groups.
>
> Selected individuals are subjected to quite vicious
> personal attacks throughout usenet. Examples are: "X#$
> X#$!" "is a X$#" "is a X$#!" "is a
> X$x" "in X$#" "is
> a X$X" "is a X#$" "is a V$X just
> like X$#" "X#$"
> "Sexually harassed by" "X#$" "X#$
> PARTY" "X$#" "hated
> wherever he goes!" "X#$
>
> As will be seen several of these are libelous, and
> thus illegal
>
> Groups such as the regular posters are attacked similarly,
>
> ------------------------------
>
> Subject: 4.6 Forgeries
>
> They regularly forge the identities of posters who they do
> not like. This can vary from badly spelled versions of
> their name and/or email address, to forgeries which the
> average reader would not be able to detect.
>
> At times this can reach a bizarre condition where they
> troll using a forged identity at a Breidbart Index of well
> over 20. They then at every opportunity call the victim a
> troll.
>
> Larting the offender is often effective because ISPs recognise
> the seriousness of this offence.
>
> Where Forgery is done via an anonymous remailer complaints
> to abuse@thelastremailerinthechain may well be effective.
> The remailers administrators do not like their facilities
> being misused, and have ways of combatting this. It is
> also worth registering with
> http://www.paracrypt.com/remailerabuse/
>
>

ok I had the same problem with lexware financial office with an update
via an **.msp*
and then I tried your tip with running some movies and that worked.

*Thanks a lot!*


--
deweso

Frustrating problem wasn't it! Race conditions are absolutely th
worst

I have 50 years of computer operating system experience and hav
learned a lot about problem isolation and workarounds. Working wit
computer systems is like scraping your knuckles restoring a classic car
Very, very frustrating along the way, but extremely satisfying when yo
produce the final product.

I posted my workaround in the hope that others like me would find i
and profit from it

I am glad that you did just that

Jac

--
sherlocc

You saved my day, and the least I could do is to show some appreciation.
:-) Additionally the lexware support is not the best, so I hope that
Google will show the next poor ba**ard who runs also that OS and has
difficulties updating what the answer might be *grin*


--
deweso