Oh. Better be careful, then, if you haven't tried an install yet. The
number of months difference isn't as important as... the interaction of
the files inside "InstMsiA.exe". Perhaps one of them may need the newer
..dll under a particular circumstance.

YOU KNOW... there are many threads here about serious failures to
install Norton Anti-Virus 2004. Better make a full system backup before
trying it!

Checking Modified Date on about 7 of the files inside my own
McAfee-supplied "InstMsiA.exe" against what is in my system folders, it
seems everything is as old or older than what McAfee supplied. The
McAfee dates (as shown in WinZip) are all '00. I have some system files
(such as cabinet.dll & imagehlp.dll) of '99 (looking at Properties).
What could that mean? Why didn't the newer McAfee files replace older
ones? Can it be... McAfee extracted it's "InstMsiA.exe", used it's
files, then deleted them?

| Finally, did you happen to notice the date of that GoogleGroups post?
| Microsoft has done NOTHING about it! GRRRRRRR.

No, but I believe you. Yea, would be nice if MS did something about it.

| I wonder if XP has this
| same problem since they are more likely to have Installer 2.0.

I am more worried about my earlobes turning purple of XP-radiation.


--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
should things get worse after this,
PCR

"Anonymous" wrote in message
...
| I have not installed anything YET. I do plan to install Norton
Utilities
| 2004 and Anti-Virus 2004 soon, probably tonight. I do not expect any
| problems because the version downgrade was only from 2.0.2600.2 to
| 2.0.2600.0 which is a 5 month difference. If I do not post any
further
| replies, then I did not have any problems installing.
|
| BTW, as you probably already know, many programs come with their own
copy
| of Windows Installer 2.0. If you install any new programs with it,
you
| will be involuntarily "upgraded" to Installer 2.0. The best way to
avoid
| problems is to download that INSTALL.EXE file, extract the v2.0.2600.0
| MSISIP.DLL, and ZIP it into an archive. You can always delete the 8.5
MB
| INSTALL.EXE file. I already did. I was pretty tired last night when
I
| tried to install Installer 1.1 over 2.0. When I first looked at the
1.1
| Archive file, I thought there was an MSISIP.DLL file in there.
Looking
| again, however, I see there is no such file.
|
| Finally, did you happen to notice the date of that GoogleGroups post?
It's
| dated August 2002. This has been a known bug for 2 years, 4 months
and
| Microsoft has done NOTHING about it! GRRRRRRR. I wonder if XP has
this
| same problem since they are more likely to have Installer 2.0. I'll
bet
| you one MSISIP.DLL file XP has this bug too. LOL.
|
|
| PCR wrote:
| Interesting. I was worried a bit that I don't have a MSISIP.DLL at
all,
| any version. However, I see one of the solutions at that Google
search
| of yours is to delete that file. I guess you don't get one unless
you've
| taken Windows Installer v2.0, (which I have never found the need to
do).
|
| http://www.microsoft.com/downloads/r...eleaseID=32831
| Windows Installer v.2.0
|
| Using WinZip to look inside "InstMsiA.exe" downloaded to TEMP from
| there, it did indeed have an "msisip.dll". Extracting that into
TEMP,
| indeed it is v.2.0.2600.2.
|
| Also, I note the one/only "InstMsiA.exe" I had before this was in a
| McAfee "setup" folder. Looking inside, there is no "msisip.dll" in
that
| one.
|
| So, what you say has the ring of truth, BUT... well, I guess I'd
rather
| replace the file if I had one instead of just deleting it. ANYWAY...
|
| How are installations going, now that you've replaced yours?
|