Dot Net Framework snafoo

[Lester Stiefel]

I installed DotNet Framework 2.0 yesterday, but when I
install PrintMaster 16 from broderbund, I received installer
trying to install DNF 1.1. I tracked this situation down to
a module incorrectly entered (not entered in SharedDLLs).
The module was identified as 'msvcr80.dll' .
I then entered a DWord value in Shared dll area of registry
for the msvcr80.dll, which I copied into the System32
folder. Currently the path cannot read complex folder names
such as com_Microsoft ...
After doing so, I had both versions running, and even the
rich media streams were working properly. Make a note of
this. The msvcr file is under winsxs\vba folder.

 

[Timothy Daniels]

I installed DotNet Framework 2.0 yesterday, but when I
install PrintMaster 16 from broderbund, I received installer
trying to install DNF 1.1. I tracked this situation down to
a module incorrectly entered (not entered in SharedDLLs).
The module was identified as 'msvcr80.dll' .
I then entered a DWord value in Shared dll area of registry
for the msvcr80.dll, which I copied into the System32
folder. Currently the path cannot read complex folder names
such as com_Microsoft ...
After doing so, I had both versions running, and even the
rich media streams were working properly. Make a note of
this. The msvcr file is under winsxs\vba folder.

When you installed .NET Framework 2.0, did you leave
..NET Framework 1.1 installed? Or did you uninstall
..NET Framework 1.1? The software written for v.1.1
sometimes cannot work with v.2.0, but the runtime environment
should be able to find v.1.1 and run the software using
v.1.1 .

*TimDaniels*
can find .NET Framework.