W
wjr
One of our developers is having a problem. We use a very specific
version of file converter for old corel 5.1 files. We have to copy
these versions over the existing converter which is in C:\Program
Files\Common Files\Microsoft Shared\TextConv. What appears to happen is
when a microsoft patch/update comes along, they overwrite the converters
again so that we have to replace them again. The users do not have
administrative rights so this copy fails. Need to come up with a
solution...
It is given that:
1) The corel files are not going away anytime soon so these must exist.
2) User's will not be given administrative rights.
3) The specific converter must be used.
4) MS Updates/Patches must be regularly performed!
What would be nice is to have the converters placed somewhere where the
user's have permissions (like documents/settings) and changing the
registry to point to this location. Or some other solution that doesn't
break the given rules above. Is there a way to prevent an update from
overwritting those 2 converter files?
version of file converter for old corel 5.1 files. We have to copy
these versions over the existing converter which is in C:\Program
Files\Common Files\Microsoft Shared\TextConv. What appears to happen is
when a microsoft patch/update comes along, they overwrite the converters
again so that we have to replace them again. The users do not have
administrative rights so this copy fails. Need to come up with a
solution...
It is given that:
1) The corel files are not going away anytime soon so these must exist.
2) User's will not be given administrative rights.
3) The specific converter must be used.
4) MS Updates/Patches must be regularly performed!
What would be nice is to have the converters placed somewhere where the
user's have permissions (like documents/settings) and changing the
registry to point to this location. Or some other solution that doesn't
break the given rules above. Is there a way to prevent an update from
overwritting those 2 converter files?