>Ah - I hadn't gotten this message!
>
>No DLL Declares at all. I thought it might be the timers, but removing them doesn't have any effect.
>
>Thanks, though,
>Barbara

I just read your reply to George Lee, and it still -might- well be something fixed by installing DCOM's components; even if DCOM itself isn't a fix, you're dying an an OLE component DLL!

I've gotta start reading these posts better...

>
>>My apologies - I stopped reading at C0000005!
>>
>>I'd still apply at least SP3 to NT; there's a tremendous amount of stuff fixed in it, and even more in SP4 if it doesn't bite you during the installation...
>>
>>If you're using many .DLL DECLARES, I've avoided some problems releasing .DLLs by invoking the ExitProcess() API call rather than using QUIT. Try:
>>
>>DECLARE ExitProcess IN WIN32API INTEGER uExitCode
>>=ExitProcess(0)
>>
>>in place of QUIT. I don't know exactly why this works, but it fixed some problems I had after far too many DECLARE...DLLs and DLL call invocations.