s
(1) When using Microsoft
R
Windows NTR
Workstation Operating System Version 4.0
and Microsoft
R
WindowsR
2000 Professional Operating System
When using Windows NTR
Workstation 4.0 and WindowsR
2000 Professional,
MX Component may be installed and used only on the administrator's authority.
(2) About Ethernet communication, computer link communication and CPU COM
communication on Microsoft
R
WindowsR
95 Operating System
(a) Making Ethernet communication using TCP/IP and UDP/IP on WindowsR
95
of the version older than OSR2 will cause a memory leak. When performing
continuous operation on WindowsR
95, use WindowR
95 OSR2 or later.
(b) On WindowsR
95, communication using the COM port, e.g. computer link
communication or CPU COM communication, will cause a memory leak.
Therefore, do not perform continuous operation.
(3) About installation
(a) When performing overwrite installation, install the software in the folder
where it had already been installed.
(b) If you install the MELSEC board driver or GX Developer into the personal
computer where MX Component has already been installed, communication
using a specific path (e.g. ASCII packet of the AJ71E71) may result in a
receive, device number or other error.
If any of these phenomena has occurred, perform overwrite installation of MX
Component again.
(4) Precautions for performing installation and uninstallation on a dual boot machine
where two different operating systems are installed in a single IBM-PC/AT
compatible personal computer
On a dual boot machine having Windows NTR
Workstation 4.0 (hereafter referred to
as OS1) and WindowsR
95/98 (hereafter referred to as OS2), note the following points
when MX Component was installed on OS1 first and MX Component was then
installed over the same folder on OS2.
(a) If MX Component is uninstalled first on the OS2 side, uninstallation does not
delete the control DLLs and ACT folders, and they remain within the IBM-