>On each WWC application we have in production, we are using SYS(2335,0) as a protection to suppress any dialog that could come up on the server console. That is a safe and probably used by many developers who do those WWC applications.
>
>This has worked nice so far and we didn't have any problem before.
>
>However, under WIN2K SP3, if I simulate a situation that will make that happen, no dialog will appear on screen (that part is working ok) but this is making the WWC instance in memory to be completely corrupted.
>
>Anyone know an alternative to that SYS() approach I could use?

Well, after a long day of investigation to check every line in order to detect what was happening exactly, I finally found a major breakthrough in that quest.

Under WIN2K SP3, at least, for my setups on several servers, I have found that when SYS(2335,0) is invoked, SET TALK becomes ON. So, that was affecting WWC eval object MergeText() method which evaluate a lot of = values and was returning a blank instead. For areas where a lot of evaluations was taking place, it was a big mess seeing the result that this was given.

I have no SET TALK anywhere in the code. Magically, under that environment, memory has decided to turn it ON. So, in my error event, I have put the following:

* This is needed under Win2K SP3 as,
* after a SYS(2335,0) has been issued,
* the value of SET EXACT is changed.
SET EXACT OFF

For those interested, you may take note of that.

I know a lot of people have unauthorized the installation of WIN2K SP3 on several servers.

Additionnaly to that, we also faced the WAM account desynchronization problems as well from the Components Service.