1.04.02.007 WHQL Drivers

[Zao]

It's been there since the first drivers =)

[GNEP]

Oh well. Just me then

[Chucky Cheese]

.NET 1.1

so I guess that a clean install and going straight to .NET 1.1 is out of the question...dag nabbitt!!

does anyone know when SP 2 for XP is due out?? I want to slipstream SP 2 into my XP cd and install it from the get go.

I believe that I have SP2 for the .NET framework on my system now...could there be that much of a difference between what I have verses 1.1?

cc

[Peter Aragon]

Hi cc

.NET framework is designed so that multiple versions of the framework (1.0, 1.1, 2.0 in the future) so that applications built with a certain framework version can run with that framework. So installing 1.1 doesn't require you to uninstall 1.0

Good luck.

[Chucky Cheese]

.NET Framework

thanks Peter.

I must admit to being a little confused about how this "multi-version side by side" compatability thing works with this .Net stuff.

Is there some sort of "versioning" that kicks in when an application, such as Power Desk-HF, makes a .Net framework call??

can you install 1.1 first then install an older version and expect to have a .NET application make the right call to the right version???

cc

[Peter Aragon]

Hi cc

Yup, that's exactly how it works. You can specify which framework you want to use in a configuration file. Also applications can use DLL's, and have the same name, but different versions. It's all dealt by a global assembly cache (GAC) system.

Altough I can't see a config file in the powerdesk dir that would be responsible for powerdesk being tied to version 1.0, I guess it has to do something with the way the PowerDesk .NET app and the native driver layer interact with each other. Maybe they bind their native app layer directly with a file from the 1.0 version? just speculating here, as I didn't encounter problems with 1.1 in my applications.

So simply install .NET 1.0 and .NET 1.0 SP2 afterwards.

Good luck,

[mutz]

Regarding the Parhelia drivers, I would still keep in mind what Haig said here.

[Chucky Cheese]

I read that !!!

That is why I asked the question!!!

Haig posted that in April...being that it is June and all, plus the fact that they are WHQL certified.

I guess its' no big deal as long as it can operate correctly with the two versions installed on the same system.

cc

[Maggi]

Originally posted by TdB
do the bios increase the slightly underclocked parhelia clock?

don't think so, but they released a tool for that last year before x-mas:

ftp://ftp.matrox.com/pub/mga/utils/t...28_clocker.zip

[mutz]

I dunno Chuck, I just don't feel like opening that can of worms. I'll just wait 'til Matrox get's its finger out, though it's effing annoying.

[mungu]

I am running Windows Server 2003, which installs .Net 1.1 by default, and I installed 1.0 after 1.1 was installed, and everything works perfectly for me, including powerdesk.

[mutz]

Yeah, it all runs fine, but just wait 'til you want to upgrade the P driver.

[Chucky Cheese]

exactly!!!

...then it's.........oops!!!!!!!

of course you probably could install the 1.0 before removing the driver...I assume???

cc

[mutz]

Apparently some undetermined unreachable file deep in the works gets mangled and you can't uninstall the driver.

Haig mentioned this somewhere in the "here" in the post above.

[TdB]

Originally posted by Maggi
don't think so, but they released a tool for that last year before x-mas:

ftp://ftp.matrox.com/pub/mga/utils/t...28_clocker.zip

thanks!

i can´t find any info about those files, and I don´t want to blindly start programs that alters any bios, do you know where I can find some info/release notes about it?

my guess is that ParUp217.exe changes the clock from 217 to 220(and changes the memory clock accordingly), while ParDw217.exe changes the clock back again, is that correct?