I'm running Vista Home Premium (32-bit) and installed a codec pack to try
and improve on Vista's ability to play certain video files. After
installing, IE7 will no longer open any links for MPG or MPEG files. Other
file formats seem to open the media player just fine as usual. I
uninstalled the Codec pack (Vista Codec Pack) but that didn't help. The
actual MPG Codec is fine as files play with no problem directly from the
media player (WMP 11) if d/l'd first, and they also open/play fine from
Firefox. When clicking on a link that I see the following:

"Internet Explorer cannot display the webpage

Most likely causes:
You are not connected to the Internet.
The website is encountering problems.
There might be a typing error in the address. "


I've tried making sure that the file associations are correct, checked my
proxy settings, made sure Internet connections was checked in Media player,
etc all to no avail. I've also checked and the codecs are installed in WMP.
I've also googled this until my eyes bled - no help.

How can I make IE remember how to open an MPG/MPEG file?

Thanks in advance.

-Riff

dont use codec packs!!!

Do a system restore to a time before you installed the pack,
then download the following cobination that works very well

real alternative
Quicktime alternative
koepi xvid
and gomplayer to play all the rest that media player cant.

Also keep this in mind, since they will be releasing a version for vista
soon: divx [url]http://www.divx.com/[/url]

In the meanwhile gomplayer can play everything if you install the real alt.
and quick alt I have below.

Links :
[url]http://www.free-codecs.com/download/Real_Alternative.htm[/url]

[url]http://www.free-codecs.com/download/QuickTime_Alternative.htm[/url]

[url]http://www.free-codecs.com/download/Koepi_XviD.htm[/url]
or [url]http://www.koepi.org/xvid.shtml[/url]

[url]www.gomplayer.com[/url]






"Riffrafter" <sve@skads.com> wrote in message
news:egXLRqNdHHA.4392@TK2MSFTNGP03.phx.gbl...[color=blue]
> I'm running Vista Home Premium (32-bit) and installed a codec pack to try
> and improve on Vista's ability to play certain video files. After
> installing, IE7 will no longer open any links for MPG or MPEG files.
> Other file formats seem to open the media player just fine as usual. I
> uninstalled the Codec pack (Vista Codec Pack) but that didn't help. The
> actual MPG Codec is fine as files play with no problem directly from the
> media player (WMP 11) if d/l'd first, and they also open/play fine from
> Firefox. When clicking on a link that I see the following:
>
> "Internet Explorer cannot display the webpage
>
> Most likely causes:
> You are not connected to the Internet.
> The website is encountering problems.
> There might be a typing error in the address. "
>
>
> I've tried making sure that the file associations are correct, checked my
> proxy settings, made sure Internet connections was checked in Media
> player, etc all to no avail. I've also checked and the codecs are
> installed in WMP. I've also googled this until my eyes bled - no help.
>
> How can I make IE remember how to open an MPG/MPEG file?
>
> Thanks in advance.
>
> -Riff[/color]

Er... if you are planning on downloading and using iTunes, then that comes
with quicktime bundled so you can skip the quicktime alternative in that
case. If you have no plan on installing iTunes, install the quicktime
alternative.


"Riffrafter" <sve@skads.com> wrote in message
news:egXLRqNdHHA.4392@TK2MSFTNGP03.phx.gbl...[color=blue]
> I'm running Vista Home Premium (32-bit) and installed a codec pack to try
> and improve on Vista's ability to play certain video files. After
> installing, IE7 will no longer open any links for MPG or MPEG files.
> Other file formats seem to open the media player just fine as usual. I
> uninstalled the Codec pack (Vista Codec Pack) but that didn't help. The
> actual MPG Codec is fine as files play with no problem directly from the
> media player (WMP 11) if d/l'd first, and they also open/play fine from
> Firefox. When clicking on a link that I see the following:
>
> "Internet Explorer cannot display the webpage
>
> Most likely causes:
> You are not connected to the Internet.
> The website is encountering problems.
> There might be a typing error in the address. "
>
>
> I've tried making sure that the file associations are correct, checked my
> proxy settings, made sure Internet connections was checked in Media
> player, etc all to no avail. I've also checked and the codecs are
> installed in WMP. I've also googled this until my eyes bled - no help.
>
> How can I make IE remember how to open an MPG/MPEG file?
>
> Thanks in advance.
>
> -Riff[/color]

Click Start > type "Internet Options" > hit Enter

This should open the Internet Properties dialog > click 'Advanced' click the
"Reset" button under "Reset Internet Explorer settings', this will make IE
like new again.
--
Andre
Blog: [url]http://adacosta.spaces.live.com[/url]
My Vista Quickstart Guide:
[url]http://adacosta.spaces.live.com/blog/cns!E8E5CC039D51E3DB!9709.entry[/url]
"Riffrafter" <sve@skads.com> wrote in message
news:egXLRqNdHHA.4392@TK2MSFTNGP03.phx.gbl...[color=blue]
> I'm running Vista Home Premium (32-bit) and installed a codec pack to try
> and improve on Vista's ability to play certain video files. After
> installing, IE7 will no longer open any links for MPG or MPEG files.
> Other file formats seem to open the media player just fine as usual. I
> uninstalled the Codec pack (Vista Codec Pack) but that didn't help. The
> actual MPG Codec is fine as files play with no problem directly from the
> media player (WMP 11) if d/l'd first, and they also open/play fine from
> Firefox. When clicking on a link that I see the following:
>
> "Internet Explorer cannot display the webpage
>
> Most likely causes:
> You are not connected to the Internet.
> The website is encountering problems.
> There might be a typing error in the address. "
>
>
> I've tried making sure that the file associations are correct, checked my
> proxy settings, made sure Internet connections was checked in Media
> player, etc all to no avail. I've also checked and the codecs are
> installed in WMP. I've also googled this until my eyes bled - no help.
>
> How can I make IE remember how to open an MPG/MPEG file?
>
> Thanks in advance.
>
> -Riff[/color]

Hi, I am the developer of the Vista Codec Package.

Although this issue will be fixed in the next release (v438),
the following registry entries will fix it for you now.
Remember that when creating a registry file,
it must end in a blank line to be functional.

[CODE]Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\.mpeg]
"Content Type"="video/x-ms-mpeg"

[HKEY_CLASSES_ROOT\.mpg]
"Content Type"="video/x-ms-mpeg"[/CODE]


I'm sorry to those inconvenienced.


Shark007

Why would you set those values? The OS should set them perfectly as
"video/mpeg". You should generally not touch those.

Beyond that, "x-" is deprecated and reserved for experimental types, and
"ms" implies vendorness which isn't applicable to MPEG. So video/x-ms-wmv
means Video type: Experimental by Microsoft file type WMV.

Please don't set these. They should be
video/mpeg

You should not adjust any set "Content Type" on the system without really
good reason. =)

Thanks!
-Zach
--
Speaking for myself only.
See [url]http://zachd.com/pss/pss.html[/url] for some helpful WMP info.
This posting is provided "AS IS" with no warranties, and confers no rights.
--
"Shark007" <thom007********.com> wrote in message
news:Shark007.2oukb1@no-mx.tabletquestions.com...[color=blue]
>
> Hi, I am the developer of the Vista Codec Package.
>
> Although this issue will be fixed in the next release (v438),
> the following registry entries will fix it for you now.
> Remember that when creating a registry file,
> it must end in a blank line to be functional.
>
>
> Code:
> --------------------
> Windows Registry Editor Version 5.00
>
> [HKEY_CLASSES_ROOT\.mpeg]
> "Content Type"="video/x-ms-mpeg"
>
> [HKEY_CLASSES_ROOT\.mpg]
> "Content Type"="video/x-ms-mpeg"
> --------------------
>
>
>
> I'm sorry to those inconvenienced.
>
>
> Shark007
>
>
> --
> Shark007[/color]

Well Zach, the answer is quite simple.

The original poster mentions my codec pack as a cause for the issue presented. I realize you don't condone codec packs and that is your right, but the 'hack' i presented will fix the posters issues even though my codec package did not change the original values.

Shark007

Oh totally - I'm interested in an amicable relationship here, and there's
nothing in your pack that jumps out as technical badness to a quick
once-over. I'm here solely interested in stability and Things Workin', so I
think we're on the same page. =)

The hack you presented wasn't correct, though-- it should be:
===
Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\.mpeg]
"Content Type"="video/mpeg"

[HKEY_CLASSES_ROOT\.mpg]
"Content Type"="video/mpeg"
===

Capische? I'm not certain who's resetting those to something strange (I'd
be interested to know and get them to stop that), but the above are the
correct values. Setting Content Type to alternate values could potentially
trigger anti-spoofing logic in certain contexts, so it's relatively
important to get those right or at least cohesive within a given association
environment. =)

-Zach
--
Speaking for myself only.
See [url]http://zachd.com/pss/pss.html[/url] for some helpful WMP info.
This posting is provided "AS IS" with no warranties, and confers no rights.
--
"Shark007" <thom007********.com> wrote in message
news:Shark007.2ouns0@no-mx.tabletquestions.com...[color=blue]
>
> Well Zach, the answer is quite simple.
>
> The original poster mentions my codec pack as a cause for the issue
> presented. I realize you don't condone codec packs and that is your
> right, but the 'hack' i presented will fix the posters issues even
> though my codec package did not change the original values.
>
> Shark007
>
>
> --
> Shark007[/color]

We are on the same page.

Only problem is, the poster already has the original values you posted, but what ever is the cause of his issue, the values i posted, will get the poster functioning again. I really doubt the values I posted will have any detrimental effects on the systems overall functionality.

You are also correct, there is the pontential for exploitation, however that is quite remote in my opinion.

Ah - I see what you're trying to do here - you're just trying to bypass the
issue by triggering a security exception: given what you're saying, you're
deliberately inducing an anti-spoofing launch path.

I wouldn't really recommend that. If there's a add-on or handler that's
interfering here, it would be best to root-cause that as opposed to this
work-around. =\

--
Speaking for myself only.
See [url]http://zachd.com/pss/pss.html[/url] for some helpful WMP info.
This posting is provided "AS IS" with no warranties, and confers no rights.
--
"Shark007" <thom007********.com> wrote in message
news:Shark007.2ouqjz@no-mx.tabletquestions.com...[color=blue]
>
> We are on the same page.
>
> Only problem is, the poster already has the original values you posted,
> but what ever is the cause of his issue, the values i posted, will get
> the poster functioning again. I really doubt the values I posted will
> have any detrimental effects on the systems overall functionality.
>
> You are also correct, there is the pontential for exploitation, however
> that is quite remote in my opinion.
>
>
> --
> Shark007[/color]

Well i think we about covered every angle on that topic.

While I have your attention I had a quick look at the link in your sig. I'm curious as to why you suggest changing the registry values while swapping the systems default player to use WMP x64 as default in Vista. In my experience and testing all that is needed is the command unregmp2.exe /SwapTo:64 to acheive this without touching the registry whatsoever.
What is the purpose of the registry edits?

I'm heading to bed now but I hope you're not trying to trigger some kind of security deception to swing open a backdoor to spoof a deliberate induction of a launch path to Vista's predecessor. (hehe) goodnite.

You're talking about the "Path" value? The SwapTo code I wrote (it's a
test/deployment feature of negligible value - but since it's being picked up
by 64bit fans, is doing exactly what it was written for) didn't set that.
Without that, there are cases where the "old" 32bit player would be
used/picked up. So when you update via SwapTo:32 or SwapTo:64, you need to
explicitly set the path to. Otherwise when executing wmplayer.exe against
execution start path %programfiles% or %programfiles(x86)%... =)

-Zach
--
Speaking for myself only.
See [url]http://zachd.com/pss/pss.html[/url] for some helpful WMP info.
This posting is provided "AS IS" with no warranties, and confers no rights.
--

"Shark007" <thom007********.com> wrote in message
news:Shark007.2outbz@no-mx.tabletquestions.com...[color=blue]
>
> Well i think we about covered every angle on that topic.
>
> While I have your attention I had a quick look at the link in your sig.
> I'm curious as to why you suggest changing the registry values while
> swapping the systems default player to use WMP x64 as default in Vista.
> In my experience and testing all that is needed is the command
> unregmp2.exe /SwapTo:64 to acheive this without touching the registry
> whatsoever.
> What is the purpose of the registry edits?
>
>
> --
> Shark007[/color]

Again, in my experience, the swapto code functions fine without the registry edit. I think the reasons users report it didnt work is that they dont realize the big picture. Its only changing the default player (DVD play etc), not the file associations the user created before the swap. example: mkv file is set to open with WMP under the 32bit default. The user then swaps to the 64bit player expecting everything that used to open the 32bit player to now open the 64bit player but double clicking an mkv file still opens the 32bit player.

back to the original topic. I now have knowledge of the cause and the resolve and also need to take fault for the cause. Its some left over code from when the codec pack was designed for XP. The following is set by my current release but will be changed for future releases to cleanup the mess I created and eventually removed completely because its purpose was only to set a default icon.

redundant setting:
[HKEY_CLASSES_ROOT\.mpg]
"Default"="mpg_auto_file"

in Vista this should be:
[HKEY_CLASSES_ROOT\.mpg]
"Default"="WMP11.AssocFile.MPEG"

I'm at a point now that i wish i could edit out my suggestion above to temporarily fix the issue so its not 'out there', but this board doesnt allow the edit.

Its been nice chatting with you Zach. Have a a nice day.

"Shark007" <thom007********.com> wrote in message
news:Shark007.2ovj10@no-mx.tabletquestions.com...[color=blue]
> Again, in my experience, the swapto code functions fine without the
> registry edit.[/color]

It doesn't, though - I believe the specific scenario you would notice is
clicking in on an HREF to a media file - you really do need to set the Path
here. It's fine if people don't want to do that, but it won't work
cohesively without that, end of story. =)
[color=blue]
> I think the reasons users report it didnt work is that
> they dont realize the big picture. Its only changing the default player
> (DVD play etc), not the file associations the user created before the
> swap. example: mkv file is set to open with WMP under the 32bit
> default. The user then swaps to the 64bit player expecting everything
> that used to open the 32bit player to now open the 64bit player but
> double clicking an mkv file still opens the 32bit player.[/color]

That sounds like MKV wasn't registered in the player registration scheme
that's been around since Win98 days. HKEY_LOCAL_MACHINE,
Software\Microsoft\Multimedia\WMPlayer allows for extensibility of
registration. Should be pretty straight-forward.
[color=blue]
> back to the original topic. I now have knowledge of the cause and the
> resolve and also need to take fault for the cause. Its some left over
> code from when the codec pack was designed for XP. The following is set
> by my current release but will be changed for future releases to cleanup
> the mess I created and eventually removed completely because its purpose
> was only to set a default icon.[/color]
[color=blue]
> redundant setting:
> [HKEY_CLASSES_ROOT\.mpg]
> "Default"="mpg_auto_file"[/color]

Why would you set that ever? mpg_auto_file specifically means that no
association was found so the user clicked on it and the shell automatically
regenerated the association based upon that explicit interaction. None of
the media types should ever need an Auto association here... =)
[color=blue]
> in Vista this should be:
> [HKEY_CLASSES_ROOT\.mpg]
> "Default"="WMP11.AssocFile.MPEG"[/color]

Since that controls the association, it's best to not set that without being
really certain what the user associativity state is - if they're using some
3rd party for MPEG playback, for example, it's best to keep them happily
using that. =) I would only set that if it's unset that if I were you, and
even then the SystemFileAssociations should probably already have a back-up
association there.
[color=blue]
> I'm at a point now that i wish i could edit out my suggestion above to
> temporarily fix the issue so its not 'out there', but this board doesnt
> allow the edit.[/color]

No worries - anybody interested should be able to see the subsequent
follow-ups and corrections.

Best,
-Zach
--
Speaking for myself only.
See [url]http://zachd.com/pss/pss.html[/url] for some helpful WMP info.
This posting is provided "AS IS" with no warranties, and confers no rights.