ChatterBank8 mins ago
What does this warning mean?
I had this warning on start-up yesterday:
A POTENTIAL CONFLICT WAS DETECTED.
PROCESS 400 IS CURRENTLY RUNNING AND MAY ALSO BE A CLIENT WITH MACH.ID 1. THE PROCESS WILL NOW EXIT. UPON RESTART, THE CHECK WILL NOT BE DONE..... etc.
What's it all about ? Cause for concern ?
Thanks.
D
A POTENTIAL CONFLICT WAS DETECTED.
PROCESS 400 IS CURRENTLY RUNNING AND MAY ALSO BE A CLIENT WITH MACH.ID 1. THE PROCESS WILL NOW EXIT. UPON RESTART, THE CHECK WILL NOT BE DONE..... etc.
What's it all about ? Cause for concern ?
Thanks.
D
Answers
Best Answer
No best answer has yet been selected by derekpara. Once a best answer has been selected, it will be shown here.
For more on marking an answer as the "Best Answer", please visit our FAQ.
-- answer removed --
If it boots up next time ok, then probably not a great worry.
I'm not familiar enough to give a comprehensive answer not I do know that in "Ye Olden Days" when one added boards and suchlike to a PC one had to select certain settings so that one board didn't try using the same resources as another.
Now-a-days the boards and the operating system tends to work out what to assign where, without you needing to know or worry about it.
It's possible something corrupted and was using the wrong settings, and conflicted with a different part of the computer that had already been allocated them. If it boots up ok next time then presumably the PC sorted itself out.
The bit about not performing a check seems a little off though. But my suggestion would be to not worry unless it becomes a regular thing or you notice other problems.
I'm not familiar enough to give a comprehensive answer not I do know that in "Ye Olden Days" when one added boards and suchlike to a PC one had to select certain settings so that one board didn't try using the same resources as another.
Now-a-days the boards and the operating system tends to work out what to assign where, without you needing to know or worry about it.
It's possible something corrupted and was using the wrong settings, and conflicted with a different part of the computer that had already been allocated them. If it boots up ok next time then presumably the PC sorted itself out.
The bit about not performing a check seems a little off though. But my suggestion would be to not worry unless it becomes a regular thing or you notice other problems.