Mutex 2

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

When I restart my computer I get a error Mutex 2 Could not reopen? Could
someone help me with this?
 
A mutex object is a synchronization object whose state is set to signaled when it is not owned by any thread, and nonsignaled when it is owned. Only one thread at a time can own a mutex object, whose name comes from the fact that it is useful in coordinating mutually exclusive access to a shared resource. For example, to prevent two threads from writing to shared memory at the same time, each thread waits for ownership of a mutex object before executing the code that accesses the memory. After writing to the shared memory, the thread releases the mutex object.

So it's a standard thingy in multi threaded applications (how an application multitasks within itself - ie one thread prints and the other allows you to still click and type).

You need to find what is saying this. Look in event viewer for hints or errors arond the same time you recieved the message.
 
I've often wondered how applications in a multi-threaded environment figure
out 'who goes first'. I'm sure it's a complex process, but I thank you for
that information.

Modem Ani

"David Candy" <.> wrote in message
A mutex object is a synchronization object whose state is set to signaled
when it is not owned by any thread, and nonsignaled when it is owned. Only
one thread at a time can own a mutex object, whose name comes from the fact
that it is useful in coordinating mutually exclusive access to a shared
resource. For example, to prevent two threads from writing to shared memory
at the same time, each thread waits for ownership of a mutex object before
executing the code that accesses the memory. After writing to the shared
memory, the thread releases the mutex object.

So it's a standard thingy in multi threaded applications (how an application
multitasks within itself - ie one thread prints and the other allows you to
still click and type).

You need to find what is saying this. Look in event viewer for hints or
errors arond the same time you recieved the message.
 
David Candy said:
A mutex object is a synchronization object whose state is set to signaled when it is not owned by any thread, and nonsignaled when it is owned. Only one thread at a time can own a mutex object, whose name comes from the fact that it is useful in coordinating mutually exclusive access to a shared resource. For example, to prevent two threads from writing to shared memory at the same time, each thread waits for ownership of a mutex object before executing the code that accesses the memory. After writing to the shared memory, the thread releases the mutex object.

So it's a standard thingy in multi threaded applications (how an application multitasks within itself - ie one thread prints and the other allows you to still click and type).

You need to find what is saying this. Look in event viewer for hints or errors arond the same time you recieved the message.
Click to expand...
OK, from my event viewer: Error 1:the Windows Firewall/ICS service
terminated with the following error. An address incompatible with the
requested protocol was used.
I haven't been able to turn my firewall on for a while now.

Error 2: The folloing Bootstart driver(s) failed to load: i8042prt

Error 3: The computer browser service terminated with the following error.
This operation returned because the timeout period expired.

Error 4: Is the same as Error 1.

Error 5: Is the same as error 2.

Error 6: Is the same as error 3.

I have a warning that happined 2 hours after I posted. But it sounds more
related than the errors:
The time service has not been able to syncronize the system time for 49152
seconds because none of the time providers has been able to provide a usable
time stamp. The system clock is unsyncronized.
 
This is one of a few ways.


Platform SDK: DLLs, Processes, and Threads

Synchronization Objects
A synchronization object is an object whose handle can be specified in one of the wait functions to coordinate the execution of multiple threads. More than one process can have a handle to the same synchronization object, making interprocess synchronization possible.

The following object types are provided exclusively for synchronization.

Type Description
Event Notifies one or more waiting threads that an event has occurred. For more information, see Event Objects.
Mutex Can be owned by only one thread at a time, enabling threads to coordinate mutually exclusive access to a shared resource. For more information, see Mutex Objects.
Semaphore Maintains a count between zero and some maximum value, limiting the number of threads that are simultaneously accessing a shared resource. For more information, see Semaphore Objects.
Waitable timer Notifies one or more waiting threads that a specified time has arrived. For more information, see Waitable Timer Objects.


Though available for other uses, the following objects can also be used for synchronization.

Object Description
Change notification Created by the FindFirstChangeNotification function, its state is set to signaled when a specified type of change occurs within a specified directory or directory tree. For more information, see File I/O.
Console input Created when a console is created. The handle to console input is returned by the CreateFile function when CONIN$ is specified, or by the GetStdHandle function. Its state is set to signaled when there is unread input in the console's input buffer, and set to nonsignaled when the input buffer is empty. For more information about consoles, see Character-Mode Applications
Job Created by calling the CreateJobObject function. The state of a job object is set to signaled when all its processes are terminated because the specified end-of-job time limit has been exceeded. For more information about job objects, see Job Objects.
Process Created by calling the CreateProcess function. Its state is set to nonsignaled while the process is running, and set to signaled when the process terminates. For more information about processes, see Processes and Threads.
Thread Created when a new thread is created by calling the CreateProcess, CreateThread, or CreateRemoteThread function. Its state is set to nonsignaled while the thread is running, and set to signaled when the thread terminates. For more information about threads, see Processes and Threads.


In some circumstances, you can also use a file, named pipe, or communications device as a synchronization object; however, their use for this purpose is discouraged. Instead, use asynchronous I/O and wait on the event object set in the OVERLAPPED structure. It is safer to use the event object because of the confusion that can occur when multiple simultaneous overlapped operations are performed on the same file, named pipe, or communications device. In this situation, there is no way to know which operation caused the object's state to be signaled.

For additional information about I/O operations on files, named pipes, or communications, see Synchronization and Overlapped Input and Output.


Platform SDK Release: August 2001 What did you think of this topic?
Let us know. Order a Platform SDK CD Online
(U.S/Canada) (International)
 
i am trying to delete icsviewer6.0 but it want let me .i cant even find it
on my computer. i need some help i used to have it to where i could download
a application and fill it out but when i try now it says i need to download
the pure edge viewer then when i try to load this it says i already have a
version that i have to uninstall it but i cant find it to do so please help
if you can .
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

AbandonedMutexException doesn't make sense. 1
ThreadPool and WaitHandle 1
Is Mutex Owned? 13
Mutex access denied 2
Problem with mutex in release mode 11
How to find Mutex - nobody can answer! 2
Cannot find Mutex created in win service from win application 6
Easy mutex problem... 4

Back
Top