C / C++ / MFC

Albert Holguin wrote:

COM doesn't have the cross-platform popularity or support...

Albert Holguin wrote:

Traditionally, people have used disk serial numbers, or MAC ids, or other
hardware identification number to uniquely identify a PC.

struct CPUInfo 
{ 
        int EAX; 
        int EBX; 
        int ECX; 
        int EDX; 
}; 
void __cpuid(int CPUInfo[4], int InfoType); 
 
//in main function:
  int b[4]; 
        char eax_hex[9]= {0,0,0,0,0,0,0,0}; 
        char edx_hex[9]= {0,0,0,0,0,0,0,0}; 
 
        //initialize the value 
        char cpuid_hex[17] = {0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0}; 
         
        // get the points to appropriate locations within the character arrays 
        char* first = &cpuid_hex[0]; 
        char* second = &cpuid_hex[8]; 
         
         
        // get level 1 data from __cpuid 
        __cpuid(b,1); 
 
         
        // b[0] will have the value of eax register 
        // b[3] will have the value of edx register 
        //when converting to string,  we ened to reverse the order of first and second due to endianness 
 
        sprintf_s(first,9, "%08X",b[3]); 
        sprintf_s(second,9, "%08X",b[0]); 
 
        // print this on command line -- normally this would be a return value of the function so it could be consumed elsewhere 
        fprintf(stdout, "processorid (equal to wmi repoted processor id): %s\n", cpuid_hex); 
 
        // uncomment below if we want to see the real values returned 
        fprintf(stdout,"eax:%d ebx:%d ecx:%d edx:%d\n",b[0],b[1],b[2],b[3]); 

Main Proc
	mov eax, 3
	cpuid
	RET
Main EndP

"Connected to ROOT\\CIMV2 WMI namespace"


"SELECT * FROM win32_processor"


    VARIANT vtProp;

    // Get the value of the Name property
    hr = pclsObj->Get(L"Name", 0, &vtProp, 0, 0);
    wcout << " OS Name : " << vtProp.bstrVal << endl;
    VariantClear(&vtProp);

   hr = pclsObj->Get(L"ProcessorId", 0, &vtProp, 0, 0);
    wcout << " ProcessorId : " << vtProp.bstrVal << endl;
    VariantClear(&vtProp);

    pclsObj->Release();


// Cleanup
// ========

enhzflep wrote:

These aren't the figures traditionally queried.

Le@rner wrote:

means the EAX,EBX,ECX,EDX can be different for same machine?

Pranit Kothari wrote:

I highly appropriate