🚀 go-pugleaf

Hi,

(Sorry if this post appeared twice in your NR, my system
time was by mistake on 2003 so the post appeared obsolete)

I noticed that OS itself can stop a service if it detects
something 'wrong' with it - for example some non-handled
exception.

Does anyone know what else (in general) could be the
reason for the serivice to be stopped by the OS?

I have a service which I installed on the real server (NT4).
It worked as I expected about 5 minutes, till it was stopped
suddenly by OS. In the 'laboratory' conditions (at my
development PC) the service was stabile.

I'm now reducing the service functionality piece by piece to
find out what is the problematic part of code.

P.S. On the same server I have some 'old' services (BCB5)
which are working a couple of years without problems. When
I tried today to extract new borlndmm.dll to the system dir it
was occupied, which is probably OK because old services
possibly grabbed it.

Should I replace the old memory manager with newor one?



Best regards,
Vladimir Stefanovic




--


Best regards,
Vladimir Stefanovic