R
Robert Hedström
Hello!
I am upgrading a computer in a factory and on it runs software that uses DDE
to connect to two machines (grinding) which seem to be running windows 3.11
or something similar.
The current computer runs windows 2000 and now I try to replace it with
windows XP but the NETDDE.EXE from 2004 and the NDDENB32.DLL from 2004 does
not work.
They seem to be the result of a "fix" described in:
Microsoft Security Bulletin MS04-031
Vulnerability in NetDDE Could Allow Remote Code Execution (841533)
If I replace these two files with the version from 2003 and 1999 from the
old windows 2000 the DDE connection with the grinding machines work properly.
Now on to my problem since the replacement described above could be
considered a fix.
The File Protection system . . . it replaces the files with the not-working
ones unless I do some things I don't feel happy about.
So my question:
Can anyone give me advice or indicate how I do to get the working files to
stay in the system. I expect the computers to run for another 10 years before
next overhaul and I do not want any Microsoft updates to mess with these
during this time. I know about tweaks such as disabling WFP by editing files
with hex editor and kernel debuggers etc. but that just can't be the way to
go.
Ideal solution:
That Microsoft issues a small update that can be downloaded and run if you
want to replace these two files with the working versions.
Less than ideal solution:
That someone informs me how to get the newer versions to work, why this is a
less prefered solution is because I doubt that it is doable and the time I
spend trying out stuff will be considered too expensive.
/Robert Hedström over in Sweden
I am upgrading a computer in a factory and on it runs software that uses DDE
to connect to two machines (grinding) which seem to be running windows 3.11
or something similar.
The current computer runs windows 2000 and now I try to replace it with
windows XP but the NETDDE.EXE from 2004 and the NDDENB32.DLL from 2004 does
not work.
They seem to be the result of a "fix" described in:
Microsoft Security Bulletin MS04-031
Vulnerability in NetDDE Could Allow Remote Code Execution (841533)
If I replace these two files with the version from 2003 and 1999 from the
old windows 2000 the DDE connection with the grinding machines work properly.
Now on to my problem since the replacement described above could be
considered a fix.
The File Protection system . . . it replaces the files with the not-working
ones unless I do some things I don't feel happy about.
So my question:
Can anyone give me advice or indicate how I do to get the working files to
stay in the system. I expect the computers to run for another 10 years before
next overhaul and I do not want any Microsoft updates to mess with these
during this time. I know about tweaks such as disabling WFP by editing files
with hex editor and kernel debuggers etc. but that just can't be the way to
go.
Ideal solution:
That Microsoft issues a small update that can be downloaded and run if you
want to replace these two files with the working versions.
Less than ideal solution:
That someone informs me how to get the newer versions to work, why this is a
less prefered solution is because I doubt that it is doable and the time I
spend trying out stuff will be considered too expensive.
/Robert Hedström over in Sweden