Technical Notes |
|
When using Reflection NFS Client on Windows 2000, users are unable to import NFS XML settings files. This technical note describes the cause and provides a solution for this problem.
Reflection NFS Client supports exporting and importing settings using a Reflection NFS XML settings file. To import an NFS XML settings file, you must copy the file to the Reflection folder located in the Windows Common Application Data folder, and then restart the computer.
If the NFS XML settings are not being loaded after copying the file to the proper directory and restarting Windows, and you are installing Reflection to a Windows 2000 machine, you may need to update the version of MSXML installed on your machine.
The Reflection NFS Client's XML settings import/export feature requires MSXML version 3.
Note: MSXML version 3 is included in Reflection NFS Client version 12.0 or higher.
To update the version of MSXML installed on your machine, make one of the following changes:
The feature required by Reflection 10.x is available only in version 3.0 of the Microsoft XML Parser. If you already have version 4.x installed, use one of the other methods listed in this section to obtain the necessary MSXML files.
To obtain version 3.0 of the Microsoft XML Parser, download and install the msxml3*.msi update from Microsoft at
http://www.microsoft.com/downloads
MSXML version 3.0 support is included in Reflection NFS Client version 12.0.
Reflection Windows-based products, version 12.0 or higher, include MSXML version 3.0. If you intend to use other Reflection products on the machine where Reflection NFS Client is installed, installing these Reflection products will update the version of MSXML on the machine. Once updated, Reflection NFS Client will use the updated files.
Microsoft Internet Explorer version 6.0 or higher includes an updated version of MSXML. Upgrading this product will update the version of MXSML on the machine. Once updated, Reflection NFS Client will use the updated files.