B
Bill Karwin
I'm using Windows 2000 SP4, and it has forgotten how to run an .msi
file. When I double-click on an .msi file, or if one is launched from a
setup.exe application, it opens the .msi file in my text editor (vim).
I can right-click on an .msi and one of the context menu choices is
"Install". That runs the .msi and it seems to have the correct
association. But I can't just run an installer from its setup.exe,
which make me think that some environment or options might not be
getting set right.
I found this page with advice:
http://www.winnetmag.com/Article/ArticleID/14612/14612.html
So I checked ftype and assoc, and everything appears to be correct:
C:\> ftype Msi.Package
Msi.Package="%SystemRoot%\System32\msiexec.exe" /i "%1" %*
C:\> assoc .msi
.msi=Msi.Package
I also tried uninstalling Microsoft Installer and reinstalling it, but
this hasn't fixed anything.
Does this ring a bell with anyone? Is there a way I can restore my
system to associate .msi files correctly (short of an operating system
reinstall)?
Regards,
Bill Karwin
file. When I double-click on an .msi file, or if one is launched from a
setup.exe application, it opens the .msi file in my text editor (vim).
I can right-click on an .msi and one of the context menu choices is
"Install". That runs the .msi and it seems to have the correct
association. But I can't just run an installer from its setup.exe,
which make me think that some environment or options might not be
getting set right.
I found this page with advice:
http://www.winnetmag.com/Article/ArticleID/14612/14612.html
So I checked ftype and assoc, and everything appears to be correct:
C:\> ftype Msi.Package
Msi.Package="%SystemRoot%\System32\msiexec.exe" /i "%1" %*
C:\> assoc .msi
.msi=Msi.Package
I also tried uninstalling Microsoft Installer and reinstalling it, but
this hasn't fixed anything.
Does this ring a bell with anyone? Is there a way I can restore my
system to associate .msi files correctly (short of an operating system
reinstall)?
Regards,
Bill Karwin