T
Ted Rodrick
Some necessary background info first: I'm running Windows 98,
Internet Explorer v6.0, and Windows Media Player v7.1. My
preference viz WMP is to run in the "Compact Mode," controlling
player size by clicking-and-dragging the "window size adjuster"
in the right-bottom corner of the player.
My normal settings for IE6 are:
- ActiveX: disabled
- Javascript: disabled, and
- Software Security: HIGH
My wife, frustrated over being unable to access/use some features
of a particular site, mucked with the IE6 settings. Specifically,
she *enabled* Javascript, and changed the Security setting to LOW.
Now (finally) to the WMP problem. When I attempted to use it these
evening, I found it opened in FULL mode (and max size); I can change
the size of the overall window but have little control over the size
of the "playing screen" (which is my major gripe). When I attempt to
change it to the COMPACT mode (from the View Menu) I get the following
ERROR message:
XML Parse Error
Line 1 Column 1
Failed to find token
<M2
leaving the player stuck in FULL mode. FWIW, the keyboard combo
Cntrl+2 (which normally will toggle back to COMPACT mode) does
not work. Clicking on the small "toggle" icon in the lower right
corner of the player produces the same result (including the
error message) as clicking on COMPACT mode from the View menu.
My surmise, is that with the security settings "highly vulnerable,"
a malicious site stealthily downloaded a script which changed the
WMP settings. I uninstalled WMP v7.1, and then downloaded the
player and did a fresh install; I fully expected that to solve
the problem, but ... no such luck. I checked the "Startup" items
(Start/Run/MSCONFIG) looking for some suspicious new applet that
was re-introducing the change at a reboot, but found nothing new.
One thing I may try ... if I can find a previous version of WMP
(e.g. v 5.X or 6.X) ... is uninstally this xy!!!yy*** version of
the player and regress to an earlier version. It would be cleaner
and nicer, of course, if the explanation was a script which could
be modified or eliminated (or anything like that localized to an
accessory file).
Other than that, at the moment, I'm out of ideas. Can anyone help?
TIA
Ted Rodrick
Internet Explorer v6.0, and Windows Media Player v7.1. My
preference viz WMP is to run in the "Compact Mode," controlling
player size by clicking-and-dragging the "window size adjuster"
in the right-bottom corner of the player.
My normal settings for IE6 are:
- ActiveX: disabled
- Javascript: disabled, and
- Software Security: HIGH
My wife, frustrated over being unable to access/use some features
of a particular site, mucked with the IE6 settings. Specifically,
she *enabled* Javascript, and changed the Security setting to LOW.
Now (finally) to the WMP problem. When I attempted to use it these
evening, I found it opened in FULL mode (and max size); I can change
the size of the overall window but have little control over the size
of the "playing screen" (which is my major gripe). When I attempt to
change it to the COMPACT mode (from the View Menu) I get the following
ERROR message:
XML Parse Error
Line 1 Column 1
Failed to find token
<M2
leaving the player stuck in FULL mode. FWIW, the keyboard combo
Cntrl+2 (which normally will toggle back to COMPACT mode) does
not work. Clicking on the small "toggle" icon in the lower right
corner of the player produces the same result (including the
error message) as clicking on COMPACT mode from the View menu.
My surmise, is that with the security settings "highly vulnerable,"
a malicious site stealthily downloaded a script which changed the
WMP settings. I uninstalled WMP v7.1, and then downloaded the
player and did a fresh install; I fully expected that to solve
the problem, but ... no such luck. I checked the "Startup" items
(Start/Run/MSCONFIG) looking for some suspicious new applet that
was re-introducing the change at a reboot, but found nothing new.
One thing I may try ... if I can find a previous version of WMP
(e.g. v 5.X or 6.X) ... is uninstally this xy!!!yy*** version of
the player and regress to an earlier version. It would be cleaner
and nicer, of course, if the explanation was a script which could
be modified or eliminated (or anything like that localized to an
accessory file).
Other than that, at the moment, I'm out of ideas. Can anyone help?
TIA
Ted Rodrick