>>>>The server is win 98 se
>>>>The client is windows NT server 4
>>>
>>>I read in an MS KB article (don't remember which one) that the DCOM server must already be running on a a Win95 machine. I believe the same is true for a Win98 box.
>>>
>>>With NT/Win2K acting as the server, the DCOM server will automatically run when instantiated. This is not the case using the less robust operating systems.
>>>
>>>HTH.
>>
>>That is in
>>http://support.microsoft.com/support/kb/articles/q165/1/01.asp
>
>Did this help you at all when you were having this problem a week or so ago?

Not much, as I am still not sure how to run it exactly on the server. I understand that I have to run the server app manually, so the EXE should have the wait state. For VB sample they suggest to run an empty form, for VFP I assume I should issue READ EVENTS, but if I run it this way I am getting the message "This application is busy..." on the client side when I try to instantiate my COM object.
Not that I have to run it on Windows 98, I was just trying to test it on two Windows 98 machines. I moved my server COM to NT box and never had the problems since then. I am still curious what exact steps one should undertake in order to run the server on Win 98, because none of the documents and articles I have read describes the setting up the COM modules step-by-step without missing something. They usually omit the info about autentication settings, do not talk about protocols options when you register your COMs, etc.