Well I don't know why JFW32 wasn't triggering this problem, but I'm not complaining either. It turns out that looking over one of Microsoft's technical blurbs about something totally un-related helped me fix the problem. The problem was in the telephon.ini file. Some how it had become either damaged or corrupted. So using a utility called TAPIINI I regenerated me a new file, and now things are all well again. So it wasn't a JFW3.3 issue after all. Brian - Visit the jfw ml web page: http://jfw.cjb.net
