Strange :omg:, I always thought that "C" stands for MFC (Microsoft Foundation Class) so if you call your classes like "CMyClass" you say that your class is only for MFC. So I won't put any "C" before my class name ;P but anyway: My class isn't a real stream class, so I thought that "Stream" is not the right name for it: neither CMyVeryCoolAbsoluteUnbelivableWorkingBuglessSpiritRichMasterlyWorkOf ArtStream will do... I thought about packing names because it is packing data to one big block. Also DataCollector, BufferPacker, DataPatcher, DataConnector, DataWeld, DataSoupPot or DataMashCollectingTank...:wtf::laugh::omg::eek::laugh:;P So I am not sure what it really is... may be I have to expand it a littlebit more so it would be really a stream class: i have to overload the << and >> operators etc. in that way that you can use it as follows: network_in<>MyStream>>MyClass; but I don't think that it is possible to create such an intelligent class :| but any way: I will use this class to prepare Data to be send over network and also to be reconverted back to its old structure after receiving it on the second pc. datastructure -> Stream -> sending -> receiving -> Stream -> datastructure Thank you :rose: Sendel PS: I will release this code here for free anyway: if you want or if you don't!;P The only place for millions of bugs is the Rainforest

Actually, putting the macro before the function may work, I'm not sure. :) Either way, putting a statement at the start of each function seems like a lot of work to me, but I can't think of a better way.

Thank you ! Long time ago when I asked this question, I thought I never get an answer, but I failed: Thank you, I will try that Link out. But I already looked into MSDN Help, so I think it would not help to solve my problem. May be I have to buy a good book in WMI-Programming because I need example sources to understand really how it works (its a little habit). Thank you :rose: Sendel The only place for millions of bugs is the Rainforest

Use WMI to get what you're looking for. DMI is in a protected low-memory area of the bios and Windows won't let you get at it without writing a device driver to the best of my knowledge.

thanks Sendel there is no spoon

This is my solution: i don't know where I found this source, but its quite good: and with comments ;-P #include #pragma comment(lib, "winmm.lib") DWORD GetCPUSpeed() { LARGE_INTEGER ulFreq, ulTicks, ulValue, ulStartCounter, ulEAX_EDX; // Query for high-resolution counter frequency (this is not the CPU frequency): if (QueryPerformanceFrequency(&ulFreq)) { // Query current value: QueryPerformanceCounter(&ulTicks); // Calculate end value (one second interval); this is (current + frequency) ulValue.QuadPart = ulTicks.QuadPart + ulFreq.QuadPart; // Read CPU time-stamp counter: __asm RDTSC // And save in ulEAX_EDX: __asm mov ulEAX_EDX.LowPart, EAX __asm mov ulEAX_EDX.HighPart, EDX // Store starting counter value: ulStartCounter.QuadPart = ulEAX_EDX.QuadPart; // Loop for one second (measured with the high-resolution counter): do { QueryPerformanceCounter(&ulTicks); } while (ulTicks.QuadPart <= ulValue.QuadPart); // Now again read CPU time-stamp counter: __asm RDTSC // And save: __asm mov ulEAX_EDX.LowPart, EAX __asm mov ulEAX_EDX.HighPart, EDX DWORD tmp = (DWORD) ((ulEAX_EDX.QuadPart - ulStartCounter.QuadPart) / 1000000); timediff = tmp/10000000.0*0.001; // Calculate number of cycles done in interval; 1000000 Hz = 1 MHz return tmp; } else { // No high-resolution counter present: return 0; } } Thanks for all information, =Sendel=