This content has been marked as final. Show 11 replies
I've also seen that sort of issue on virtualised NT 4 boxes - solution in that case is to revert to CMA 3.5.5 (McAfee re-released this a few months back on their support portal).
Yes I m working with some test virtual pcs, but I have to install it in some pcs afterwards.
Do you know if CMA 126.96.36.1993 give me problems in standard pcs with NT 4.0 SP6a?
Does anyone have experience with this?
We have CMA 188.8.131.523 on 4000 systems with NT4.0 SP6a and it runs without problems.
I will try install it in some test production pc, no in virtual pc.
Finally I could install framework in a test production machine. Problem was vmware and virtual pc machines. :)
Thank you all!
Out of curiosity - anyone know if it would have been possible to configure the VM PC clients to show SSE2 support ?
NT4 and SSE2 don't work together, supposedly.
You could in theory use CPU masking to mask out SSE2 to the VMs.
But, as NT4 went out of support on December 31st, 2004, it would seem more pertinent to ask why the heck anyone is STILL using NT4.
Simple answer is "Because some of us have to" for legacy support constraints - I'm pretty certain that anyone who's ever wored on MOD contracts is well aware of this sort of constraint/scenarion and there's lot's of systems older than NT4 out there still in critical production use.......... scary but true ;)