Hi! Try using: __try { } __except(1) { } Mukkie

I have solved my original problem. I will post a solution as a new thread because it has some very interesting implications for direct access to devices. As I suspected, the solution is grotesque but works very well.

I think you are correct and a thread can't be interrupted. I don't see any great technical difficulty in doing it... Yes, it is easy for threads to be suspended. However, to change the path of execution for a thread is unthinkable - I mean, if your program is carrying out a task and half way through writing to a file the control gets shifted to a code handler you've had it. Yes, I did mena the terminating return int statement. -- Andrew.

Thanks Michael!!! Saved me again as usual. I also found the answer in MSDN Q184796 together with an example.

I also would not mind paying for. Its like the MSDN cd but better (and more helpful). -Steven Visit Ltpb.8m.com Surf the web faster than ever: http://www.404Browser.com

It'd be better to post this message in th Suggestions Forum, so Chris can see it ;)

This is where the answer is: http://support.microsoft.com/default.aspx?scid=kb;EN-US;q243953 I found this out after failing to ask for help on this forum. I guess there are more than 1 way to do it. It just happened to me that all the solutions provided by this forum does not work for me at all. Vu http://support.microsoft.com/default.aspx?scid=kb;EN-US;q243953 vucsuf

You are an angel of mercy. It works!!! Thank you. (Lesson for others: Don't be stupid like me. Read the MSDN parameter doco very carefuly.)

Yes. I found all this out the hard way by going into the VS disassembler and looking at the calls and the stack. There are two issues here anyway: the fake union cast and external calls into member functions. After all the good advice from everyone here and checking up in Bjarne Stroustrup's (whew, I hope I spelt it right) book I think I will stick to the straight and narrow from now on. It's safer.

Nice tip, I just about to try it.

A thousand blessings upon you! Works like a charm. (It's all there in the MSDN too. I must be getting old and blind.)