Yeah, I uninstalled it, because the M'soft page said the two could not exist
simultaneously on the same machine (which is apparently untrue). So I
uninstalled v.2 (and Expressions), reinstalled v.1.1, and MCE ran OK (just in
time to recors a football game I wanted to see - later).
I'll try running the two together. Thanks for the info.
[quoted text, click to view] "The Grim Reaper" wrote:
> From what you said about uninstalling v2 and reinstalling v1.1, it sounds
> like you've already uninstalled v1.1???
> Don't!
> The two can run quite happily together on the same machine. So applications
> like XP Media Center can run along with HMTL Editor.
> HTH
> ___________________________________
> The Grim Reaper
>
> "Pazzo" <Pazzo@discussions.microsoft.com> wrote in message
> news:F3D29621-2A4C-4DF3-9A9A-F946D5F8F0D3@microsoft.com...
> > To evaluate Microsoft's new HTML editor (Expressions), I installed NET v.
> > 2
> > (as required by the program). Now XP Media Center (2005) won't run -
> > ehshell.exe generates a .NET framework intialization error and wants .NET
> > v.1.1.4322.
> >
> > I would think that .NET v. 2 would be downward compatible, but apparently
> > it
> > isn't. Is tere a fix (other than uninstalling .NET 2 and reinstalling the
> > earlier version??
>
>
From what you said about uninstalling v2 and reinstalling v1.1, it sounds
like you've already uninstalled v1.1???
Don't!
The two can run quite happily together on the same machine. So applications
like XP Media Center can run along with HMTL Editor.
HTH
___________________________________
The Grim Reaper
[quoted text, click to view] "Pazzo" <Pazzo@discussions.microsoft.com> wrote in message
news:F3D29621-2A4C-4DF3-9A9A-F946D5F8F0D3@microsoft.com...
> To evaluate Microsoft's new HTML editor (Expressions), I installed NET v.
> 2
> (as required by the program). Now XP Media Center (2005) won't run -
> ehshell.exe generates a .NET framework intialization error and wants .NET
> v.1.1.4322.
>
> I would think that .NET v. 2 would be downward compatible, but apparently
> it
> isn't. Is tere a fix (other than uninstalling .NET 2 and reinstalling the
> earlier version??