Regards my problem with laptop not able to use msi files--

XP Pro

I associated msiexec with the msi file.
When I open the msi file, I get a list of the commands syntax for msi.

Any more ideas, please.
Regards
buddy b

On Sat, 18 Oct 2008 03:06:47 -0400, buddy b <buddyb@yippy.ti.ye> wrote:

>I associated msiexec with the msi file.
>When I open the msi file, I get a list of the commands syntax for msi.
>
>Any more ideas, please.

Don't know why you would need to do this but if you did why would you think that would be the only thing wrong?

I'd try from command line:

msiexec.exe /i "fred.msi"

If that works then the association is incorrect, you couls use SysInternals "process explorer" to see the command line that your association
generated.

In any case its probably wise to download Windows Installer from Microsoft and simply install that.

Bye,
Dennis
Dennis Bareis [Microsoft MVP] (dbareis@KillSpam.gmail.com)
http://dennisbareis.com/
Freeware Windows Installer creation tool (+ "ORCA automation"):
http://makemsi.dennisbareis.com/

On Sun, 19 Oct 2008 09:52:19 +1100, Dennis Bareis
<dbareis@newsgroup.nospam> wrote:

>On Sat, 18 Oct 2008 03:06:47 -0400, buddy b <buddyb@yippy.ti.ye> wrote:
>
>>I associated msiexec with the msi file.
>>When I open the msi file, I get a list of the commands syntax for
msi.
>>
>>Any more ideas, please.
>
>Don't know why you would need to do this but if you did why would you
think that would be the only thing wrong?
>
>I'd try from command line:
>
> msiexec.exe /i "fred.msi"
>
>If that works then the association is incorrect, you couls use
SysInternals "process explorer" to see the command line that your
association
>generated.
>
>In any case its probably wise to download Windows Installer from
Microsoft and simply install that.
>
>Bye,
>Dennis
>Dennis Bareis [Microsoft MVP] (dbareis@KillSpam.gmail.com)
> http://dennisbareis.com/
>Freeware Windows Installer creation tool (+ "ORCA automation"):
> http://makemsi.dennisbareis.com/



Dennis, Thanks.
I looked at your web page.
I don`t want to make an msi file, I want to install the program
contained in a msi file from Netflix.

Shouldn`t XP pro be able to run the msi file I d/led ? I have no problem
with XP Home.

msiexec.exe /i "fred.msi
What/who is fred? name of the file?
I`ll try that, too.

I d/led the installer and will install tomorrow after checking the KB #
as I would think it would be already installed.

Thanks very much for the info
Regards
buddy b

On Sun, 19 Oct 2008 09:52:19 +1100, Dennis Bareis
<dbareis@newsgroup.nospam> wrote:

>On Sat, 18 Oct 2008 03:06:47 -0400, buddy b <buddyb@yippy.ti.ye> wrote:
>
>>I associated msiexec with the msi file.
>>When I open the msi file, I get a list of the commands syntax for
msi.
>>
>>Any more ideas, please.
>
>Don't know why you would need to do this but if you did why would you
think that would be the only thing wrong?
>
>I'd try from command line:
>
> msiexec.exe /i "fred.msi"
>
>If that works then the association is incorrect, you couls use
SysInternals "process explorer" to see the command line that your
association
>generated.
>
>In any case its probably wise to download Windows Installer from
Microsoft and simply install that.
>
>Bye,
>Dennis
>Dennis Bareis [Microsoft MVP] (dbareis@KillSpam.gmail.com)
> http://dennisbareis.com/
>Freeware Windows Installer creation tool (+ "ORCA automation"):
> http://makemsi.dennisbareis.com/


Dennis, Hi.

I did all you suggest.
When I dbl click on the msi file, I still get the list of commands for
cmnd line operation.

The association now is "windows installer".

Hope you have more ideas?
Wonder if I should reinstall windows or just forget it?

Thanks
Regards
buddy b

Hi,

On Sun, 19 Oct 2008 23:41:33 -0400, buddy b <buddyb@yippy.ti.ye> wrote:

>
>Dennis, Hi.
>
>I did all you suggest.

Then what was the command line "proces explorer" showed you?

>When I dbl click on the msi file, I still get the list of commands for
>cmnd line operation.
>
>The association now is "windows installer".

I ran assoc/ftype commands from a command prompt, suggest you do the same,
this is my output:

C:\Tmp> assoc .msi
..msi=Msi.Package

C:\Tmp> ftype msi.package
msi.package="%SystemRoot%\System32\msiexec.exe" /i "%1" %*


Bye,
Dennis
Dennis Bareis [Microsoft MVP] (dbareis@KillSpam.gmail.com)
http://dennisbareis.com/
Freeware Windows Installer creation tool (+ "ORCA automation"):
http://makemsi.dennisbareis.com/