Amendments to possible fixing instructions: 1. C;Close all programs; do a Find Files & Folders, or otherwise locate the tapinini file; 2. Delete it. 3. Restart the computer. 4. Find... or otherwise locate the telephone.ini file. 6. rename telephoni.ini to telephon.old; 7. Restart the computer. 8. Try working again. If luck held, your problem is resolved. ----- Original Message ----- From: Flor Lynch To: vicsireland@xxxxxxxxxxxxx Sent: Tuesday, January 09, 2007 4:37 PM Subject: [vicsireland] Re: Simn prob Maureen, I feel fairly certain that it is MSIMN.exe - note the m! MSIMN.exe is the file that controls all outgoings of Outlook Express, so that sometimes you will have difficulty sending messages. It may probably be due to a corrupted telephon.ini file. . We need to know what OS you are using there? (M.E.?) If ME, then: I am writing from memory of such a problem in the past: You close all programs; possibly do a find files & Folders search for tapi.ini. (Have found this file, you delete it. It will be located in somewhere like C:\Windows\System ... Now, we need to rename the telephon.ini file to telephon.old. that done, we restart the computer. The tapi.ini file is automatically re-created, as also is the telephon.ini file. Sorry I could not be precise enough. In the days when tech support from IOL was a straightforward and relatively hassle-free experience, I got a relevant article sent to me by e-mail from their tech support that explained the procedure the results of which solved the problem. If you're feeling a little adventurous, you could go to http://support.microsoft.com and go down to the *second* edit field and there type in your query. HTH a bit. ----- Original Message ----- From: maureen newell To: vicsireland@xxxxxxxxxxxxx Sent: Tuesday, January 09, 2007 4:06 PM Subject: [vicsireland] Re: Simn prob yes, definitely. __________ NOD32 1966 (20070109) Information __________ This message was checked by NOD32 antivirus system. http://www.eset.com __________ NOD32 1967 (20070109) Information __________ This message was checked by NOD32 antivirus system. http://www.eset.com