CPUID Library test

[dedndave]

well - the 3DNow! enhancements are widely used, particularly in multi-media apps
that makes them worth dealing with
if you leave it out - that is probably ok - they can write their own code - lol

when you choose to leave a vendor out, you have to make a lot of qualifier statements
it's like writing a letter of recommendation for an employee
if you say one little bad thing about the employee, the letter is useless to him - lol
if the programmer using the routine wants to incorporate it into an app, they don't want a list of qualifying statements

by the time you are done writing this routine, you will have pulled out all your hair
better PhotoShop yourself to see how that looks - it may not be worth it - lol

[BlackVortex]

Workes fine here on win7 x64, core2duo e8400. Features detected are correct (no sse4.2 for me lol)

P.S.: Who the hell uses 3dnow ?   :bdg

[hutch--]

Thanks Erol, I will have to try and work out what is happening with the manifest, its necessary for late model OS versions and I thought this one was correct.

[sinsi]

For it to work on my XP Home SP3 I needed to add the line "invoke InitCommonControls" after start:

[hutch--]

Sinsi,

Thanks, I have that code for that template, I removed it because it does not use any common controls.  :bg

OK, I just added the full supprt for the common controls. At the risk of imposing on Sinsi and Erol, I need to see if this solves the problems that have been reported on WinXP because of either the manifest or not having initialised the common control library.

[sinsi]

New one works OK now  :U

[hutch--]

Gratsie,

I will have to see if it works on Erol's machines now. It makes sense that the manifest and initialising the common control library are related, just doess not happen on my Xp Pro SP3.

[Vortex]

Hi Hutch,

The new version works perfectly, many thanks :U

[hutch--]

Thanks Erol, you have made me wiser. Looks like including a manifest means initialising the common control library.

[jj2007]

Thanks Erol, you have made me wiser. Looks like including a manifest means initialising the common control library.

Interesting. Does the manifest actually force ml.exe to insert an invoke InitCommonControls?

[hutch--]

JJ,

No, but at least on some Windows versions if you have a manifest and no common control initialisation, the app won't run. All I did with this test piece after Sinsi posted his result was enable the common control initialisation and it worked on Erols XP machines.