|
ok so how can i get its parent disk
|
|
|
|
|
Sorry, I'm not sure, but maybe one of these functions[^] will help.
One of these days I'm going to think of a really clever signature.
|
|
|
|
|
thanks for you help its done...
|
|
|
|
|
Maybe you could give the details here, so it will be available for others facing similar issues.
One of these days I'm going to think of a really clever signature.
|
|
|
|
|
using this to get hard disk num of selected drive
CString drive_is;
int ret_disk_num=-1;
drive_is.Remove('\\');
drive_is.Trim();
CString szDrive=_T("\\\\.\\");
szDrive+= drive_is;
int rt;
HANDLE h = CreateFile(szDrive, GENERIC_READ, FILE_SHARE_READ|FILE_SHARE_WRITE,NULL,OPEN_EXISTING,FILE_ATTRIBUTE_NORMAL | FILE_FLAG_OVERLAPPED,NULL);
if(INVALID_HANDLE_VALUE != h)
{
VOLUME_DISK_EXTENTS vdExtents;
ZeroMemory(&vdExtents, sizeof(vdExtents));
DWORD d =32;
DWORD dwRet;
rt = DeviceIoControl(h, IOCTL_VOLUME_GET_VOLUME_DISK_EXTENTS, NULL, 0, &vdExtents, d, &dwRet, NULL);
CloseHandle(h);
h=NULL;
if(rt != 0)
{
for (DWORD n = 0; n < vdExtents.NumberOfDiskExtents; ++n)
{
PDISK_EXTENT pDiskExtent = &vdExtents.Extents[n];
ret_disk_num =pDiskExtent->DiskNumber;
}
}
else
{
DWORD d;
d = GetLastError();
}
if(h!=NULL)
CloseHandle(h);
}
else
{
return ret_disk_num;
}
return ret_disk_num;
}
after getting disk drive num chek the media type of drive using Win32_DiskDrive.
|
|
|
|
|
In the code for part of a project I am working on is the following use of a thread:
if(txt == "Start" && UpdateData(true))
{
if(!m_inst->StartOperation())
{
MessageBox("The Instrument is Currently in use by another function");
return;
}
if(! CreateData(m_MaxFreq, m_Resolution))
return;
EnableItems(false);
m_Continue = true;
m_datacount = 0;
GetDlgItem(IDC_SPECTRUM_START)->SetWindowText("Stop");
m_Thread = AfxBeginThread(Acq_Data,this,THREAD_PRIORITY_HIGHEST);
return;
}
My goal is to make the data acquired and then displayed continuously. I tried to just loop the thread, but this did not work. I realize I may have to modify the member function the thread calls (Acq_Data), but I am not sure. If someone has a good suggestion (or general thread advice) it would be great help. I can also provide more info if needed (as there is little additional code provided in this initial post relating to the other member functions).
Thanks!
|
|
|
|
|
Neither the code, nor the explanation about the goal of your program is enough. Looking at the code I'm almost sure your threading isn't correct.
|
|
|
|
|
AndrewG1231 wrote:
My goal is to make the data acquired and then displayed continuously.
Remember that you cannot update the UI from the secondary thread. Have the worker thread "post" a message to the primary thread (the one that owns the UI).
"One man's wage rise is another man's price increase." - Harold Wilson
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons
"Show me a community that obeys the Ten Commandments and I'll show you a less crowded prison system." - Anonymous
|
|
|
|
|
Ok, so the thread is merely obtaining the information and being passed elsewhere for updating the UI? This would explain why the for loop attempt failed. So, I must look for the area of the code where the data is drawn is your suggestion?
|
|
|
|
|
The less hassle free solution is sending a message from the worker thread to the ui thread by using SendMessage() or PostMessage() with one of your windows.
|
|
|
|
|
Thank you for the suggestion, but I am unfamiliar with SendMessage() and PostMessage(). Would you be able to give me an example of how to do this or direct me to a good tutorial/article?
|
|
|
|
|
Its easy. Inside your program every window belongs to a thread - the thread that created the window (note that in a normal program every window is created by a single thread). That thread has a message queue. Every time you do something to the window - click on it with the mouse, request redrawing part of its client area - a message for that window is put in the message queue of the thread that handles that window. The gui thread should remove messages and process them in a loop (this is called the main message loop: GetMessage/DispatchMessage funcionts). In your case MFC does this for you, in pure win32 you do that for yourself. The window messages (WM_LBUTTONDOWN, WM_CLOSE, WM_PAINT, etc...) are also messages that come from that message queue, and when the gui thread encounters such a window message it dispatches that to the windowproc of the right window. OK, how is this related to worker threads? Actually message queues are one of the best things to use as inter-thread communication and fortunately this thread-message queue is thread safe, you can put a message to it from any other thread. For example you can put a window message into the message queue of the gui thread by calling PostMessage() or SendMessage() form your worker thread. Both of these functions put a message to the message queue of the gui thread but PostMessage() returns immediately while SendMessage() blocks the execution of the caller thread and returns only after the gui thread has processed the message. OK, but where to send the message, and what message??? You should define your own window messages by starting from the WM_APP constant. You define for example WM_APP+0 and WM_APP+1 and so on as your thread messages. With PostMessage() and SendMessage() you can send these custom messages to your main window and you can also specify 2 integer parameters: wParam and lParam (lParam is somtimes used as a pointer). For example when you are copying a big file on the worker thread and the percentage counter changes you can use PostMessage() to send a WM_APP+0 message with a wParam=percentage parameter. In your main window you handle the WM_APP+0 message (on your gui thread) and update your progressbar accordingly. Note that we used PostMessage() that put the message to the queue of the gui thread for later processing and PostMessage() returned immediately without unnecessarily waiting for the actual processing of the message on the gui thread (and the progressbur update) so as to prevent slowing down the worker thread. No need to wait for that progressbar update on the gui thread! A codeproject article that demonstrates the use of these thingies with MFC: Synchronization in Multithreaded Applications with MFC[^]
modified 4-Sep-12 20:30pm.
|
|
|
|
|
Good comment, but you may win an award for the most poorly formatted comment this year. 
|
|
|
|
|
Well, formatting has never been a strength of mine...
|
|
|
|
|
Yeah that was pretty painful
|
|
|
|
|
Try some better spacing, and use paragraphs; this is very hard on the eyes.
One of these days I'm going to think of a really clever signature.
|
|
|
|
|
pasztorpisti wrote: The less hassle free solution is sending a message from the worker thread to the ui thread by using SendMessage()...
What happens when the primary (UI) thread is blocked and the worker thread sends it a message via SendMessage()?
"One man's wage rise is another man's price increase." - Harold Wilson
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons
"Show me a community that obeys the Ten Commandments and I'll show you a less crowded prison system." - Anonymous
|
|
|
|
|
Then the worker thread is waiting until the message is processed on the gui thread. Exploiting this you can for example pop up a messagebox from the worker thread by sending a WM_APP+X message to the gui thread that processes WM_APP+X and "blocks" until the message box is closed. The worker thread continues running only after the message box is closed and the processing of WM_APP+X is finished on the gui thread. I quoted "blocks" because a MessageBox call doesn't really block the gui thread, it just blocks the processing of a single message an it runs an inner messageloop of its own so processing other messages from the queue of the gui thread goes on. For example your windows are still drawn (by WM_PAINT messages) while a messagebox is active.
PS: The ui thread should never be blocked, that causes unresponsive UI. Often thats the reason for multithreading and not gaining performance. If your UI thread is blocked then your program is either buggy or poorly designed.
|
|
|
|
|
pasztorpisti wrote: Then the worker thread is waiting until the message is processed on the gui thread.
I'm not talking about the primary thread being busy for a few nanoseconds. I'm talking about deadlock. For example, the secondary thread sends a "add item to the control" message (e.g., LB_ADDSTRING) to the primary thread, which is blocked waiting on the secondary thread to complete. Now the secondary thread cannot complete because it is no longer running (waiting on SendMessage() to return). This is the primary reason why SendMessage() should rarely, if ever, be used to communicate between primary and secondary threads.
"One man's wage rise is another man's price increase." - Harold Wilson
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons
"Show me a community that obeys the Ten Commandments and I'll show you a less crowded prison system." - Anonymous
|
|
|
|
|
The gui thread should never block, as a consequence it should never wait for the worker thread to complete. When the worker thread completes it can send/post a message to the gui thread to signal. Why would you want a blocking-wait on the gui thread???
|
|
|
|
|
SendMessage() is a blocking call... that's what he was pointing out.
|
|
|
|
|
DavidCrow wrote: For example, the secondary thread sends a "add item to the control" message
(e.g., LB_ADDSTRING) to the primary thread
This is the scenario that's confused me from time to time. It is really legal for a thread to do a SendMessage() to a control (the target of the LB_ADDSTRING) that is owned by another thread? I thought that Windows checked "thread ownership" of the control and returned an error on the SendMessage(). If the "primary thread" is, as is implied in your reply, the UI thread, then the "secondary thread" should not be allowed access to the control.
I've always used "PostMessage()" and used "user defined messages" to have secondary threads pass messages / commands to the primary thread for action. Since "PostMessage()" is just a queueing action, there is no deadlock (although you might not get the immediate feedback of a screen update).
Does anyone have the definitive answer on "SendMessage and Control Owner Thread" question?
|
|
|
|
|
That's a good question... I do believe the framework allows you to do it though... although now that you're questioning it, you're making me question whether I remember that correctly.
|
|
|
|
|
You know, some days I don't remember where my head is. Of course you can do it and, in fact, I do it all the time in certain apps. For example, if I have a "DO IT!" button, that usually creates a worker thread that does some stuff and updates a "log view" edit control in the main dialog. The GUI thread continues on and watches for the user clicking on "STOP DOING IT!".
Meanwhile, the worker thread does a
TheDialog->m_editcontrol.SetText(logbuffer); or something equivalent to update the subclassed edit window. Works just fine. I guess I forget this because the "SendMessage()" is buried in the SetText() function and not something I explicitly do but it is still "SendMessage()" from a thread that did not "own" or "create" the control.
Oh well, must be getting old.
|
|
|
|
|
Chuck O'Toole wrote:
Oh well, must be getting old.
Happens...
Yeah, as a rule of thumb though, I like to tell people to PostMessage() when doing things between threads (since they're supposed to be independent anyway). As you probably know, the synchronicity of SendMessage() has the potential for deadlocks so it should only be used when you truly need it.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
