A
Alon Bar-Lev
Hello,
I've posted several posts in the last month or so, and got no relevant
reply.
Unfortunately no Microsoft personal bothered to try and help.
A similar problem was officially recognized and should have corrected in
WinXPSP2, ( http://support.microsoft.com/default.aspx?scid=kb;en-us;330909 )
I have WinXPSP2 and get the same message.
I want to help to fix this problem, but I need to know how to produce some
kind of trace that will pin point which process or device are faulty, and
which API is failing!
I want to think that this is possible, and stop the guessing process of
Windows support!
I will be grateful if some one from Microsoft will instruct me how to do so.
Best Regards,
Alon Bar-Lev.
I've posted several posts in the last month or so, and got no relevant
reply.
Unfortunately no Microsoft personal bothered to try and help.
A similar problem was officially recognized and should have corrected in
WinXPSP2, ( http://support.microsoft.com/default.aspx?scid=kb;en-us;330909 )
I have WinXPSP2 and get the same message.
I want to help to fix this problem, but I need to know how to produce some
kind of trace that will pin point which process or device are faulty, and
which API is failing!
I want to think that this is possible, and stop the guessing process of
Windows support!
I will be grateful if some one from Microsoft will instruct me how to do so.
Best Regards,
Alon Bar-Lev.