You would need to access the disk io API directory. Then via that 1. Find the contiguous clusters. 2. Mark them in use 3. Attach them to a file 4. Then write to the file, being careful to not exceed the maximum. Naturally the application must also have permissions to access the API.

You can create a CBT Hook or a Shell Hook to be notified whenever a new dialog box is going to be created. You can then check its caption and text. «_Superman_»

Thanks for the reply Hamid. This articles describes about the development of a Processor Monitoring Application by Implementing a Kernel-mode driver, using the kernel mode driver API PsSetCreateProcessNotifyRoutine(). But I can't use this since I have to implement the Process monitoring in my MFC dialog baesd application.

VCSharp007 wrote: But I have to use CArray varibale not pointer!!!! No then forward declaration won't work, since classes should know their sizes. Pointer is ok since size will be sizeof a pointer. Forward declaration just tells the compiler that the class is ok and definition of that is readily available somewhere. So it searches for the given class when code for the parent class is being generated. Otherwise include "afxtempl.h" in precompiler header file. But then again there will be issues when this header file is being used somewhere else where there is no precompiled header file. Nibu thomas A Developer Code must be written to be read, not by the compiler, but by another human being. http:\\nibuthomas.wordpress.com

Actually no! I have a guess though – incremental compilation will sometimes result in a similar error because it did not know to recompile a particular piece of code, for some reason. Normally you can fix it by recompiling all, which may take a while. The thing that bothers me is the exception code; that is a code you never want to see and is what you normally see on a blue screen. In either case I does not really matter unless you are the one creating the compiler, just recompile all. I understand the reason you want to know, but you will run across many questions like that. If you dwell on them, they will drive you nuts, so just learn to accept them. If you are like me that may not be acceptable, but given time you will learn. INTP "Program testing can be used to show the presence of bugs, but never to show their absence."Edsger Dijkstra

If the MFC dialog is created on the main application thread then the main application thread needs to be an MFC UI thread. That means your application needs to be an MFC app. I think the easiest way to convert a Win32 app to MFC would be to create a new MFC project with the app wizard. MFC provides the WinMain() function so... From the Win32 code, take application-wide initialization code and put it in the new app class' InitInstance() override. Cleanup code goes to an ExitInstance() override. The Win32 app's main window message handling can be moved to MFC window message-map style handlers. MFC provides the message loop. Hope that helps get you started. Mark "Posting a VB.NET question in the C++ forum will end in tears." Chris Maunder

Again, why one need to use MFC classes in WIN32 app, if standard library function do ? Prasad Notifier using ATL | Operator new[],delete[][^]

No, there is only one thread. That's why if you start a lenghty process in one of your function, your appliation will freeze: it won't be able to respond to messages (like WM_PAINT) Cédric Moonen Software developer Charting control [v1.1]

Double-check to see that the handler has the correct signature (return type, calling convention and parameters).    Peace! -=- James If you think it costs a lot to do it right, just wait until you find out how much it costs to do it wrong! Avoid driving a vehicle taller than you and remember that Professional Driver on Closed Course does not mean your Dumb Ass on a Public Road! DeleteFXPFiles & CheckFavorites (Please rate this post!)

In ATL you use the CAdapt class. Or you can use smart pointers that don't overload operator &. Another alternative would be to create or use collections that use similar techniques to Boost's addressof[^] template (or use it). Steve

Nibu babu thomas wrote: COleDateTime::GetCurrentTime() has an issue since it uses the underlying time_t... Actually it uses a DATE, which is a double. CTime has the year 2038 problem. "Approved Workmen Are Not Ashamed" - 2 Timothy 2:15 "Judge not by the eye but by the heart." - Native American Proverb

oop! Thanx Nibu..

yeah. Thanx.

Hello. There are status signals you can test, such as DSR (Data Set Ready) and CTS (Clear To Send) (Provided you did set RTS (Request To Send) high first). If there are a device connectoed to the port, those staus signals should indicate the port is connected to a powered on device. But in my experience, the status signals aren't 100% trustworthy when the serial port is unplugged. What's worse, it seems as their state depends on the hardware. So the best way to find out, is to send some kind of status question to the device, then wait for an answer. If you get an answer, it's definately plugged in. Alcohol. The cause of, and the solution to, all of life's problems - Homer Simpson

DO NOT USE THE IMMEDIATE ABOVE SUGGESTION; it will result in a buffer overrun and is VERY poor coding practice. Two general methods: 1) Cast the void pointer to a char, tchar or wchar_t pointer. 2) Call CString::GetBuffer() with the length of buffer you require. Copy the data in and then call CString::ReleaseBuffer(). You will want to to the latter if your buffer contains multiple zero terminated strings since method one will terminate the copy at the first null. Anyone who thinks he has a better idea of what's good for people than people do is a swine. - P.J. O'Rourke

See here[^] maybe it is some helpful to you _** **_ WhiteSky

At some time in the past, Life was simple, we had telex machines, printing on rolls of paper! In those days, when at the end of a line, the next step was sinple, you send a signal to make the paper advance one line, a \NL symbol, and you followed it by a Carriage Return Symbol, a \CR Symbol! Then the CRT Screen was invented, and everyone took a step back. What shall we bo when we are at the end of a line: Send a NL, Send a CR, or send a totally new magic incantation. There was never any agreement on this issue, and it still seeps through into the WIN32 in unexpected ways. for instance, in opening files. By reason of history, if you open or save a Textfile, e.g. by using FILE f = fopen(!MyFile.txt","a+"), any New Line Char (\n) will actuallly be translated on the fly to a '\r\n' pair. When reading back, every '\r\n' pair will be converted on the fly to be read into memory as a '\n'. You may avoid this translation on the fly by opening your files as "a+b" (b for Binary). The purpose of the above is to explain that Microsoft maintains two text formats, The one used in a Program, and the One stored on File! This is all without good reason, but that's the way it is, anyways. The problem is, that Microsoft is not consistent in how the rule is applied! For some reason, best known to both God and Bill Gates, certain controls expect the '\r\n' pair, or in others the '\n\r' pair to work propperly. Try to replace each '\n' with an '\r\n' or an '\xa','\xd' pair. You may have to copy your strings into a buffer to do so, I've been doing so for a long time, Unfortunately, that's the only way it seems to work! By the way, Your resource NEEDS to be flagged as MULTILINE for any of the above to work! LateNightsInNewry

Well, I'm not sure what happens. My suggestion is to read about ReadFile at MSDN. Or, as I said before... Use a ready-made serial comms class... That way, you won't have to reinvent the wheel. Serial comms ain't easy to handle. I'm leaving for the weekend now.