Hi David:
Thanks for acknowledging the hardware
problem.
However, I don't think anyone here really would be too
upset about hardware problems on your end - if it didn't uncover what appears to
be a HUGE software problem? It's the DecludeSOFTWARE that
deactivates/downgrades itself, if we
Hi David,
Would you kindly elaborate on the ramifications of such a failure? I am
interested in when its fixed but more importantly its ramifications.
Are you saying that a hardware/network/software issue on your end can
in anyway disarm/defuse/alter/change the way Declude functions on its
FYI - For the other affected by this I put 3.0.5.22
back on and everything is flying along with no issues. Processing messages
as fast as could be.
FWIW - My issues started on December 24th at
approximatly - 2:10pm EST.
I will follow-up with Declude tomorrow to determine
why my version
