Applies To:
  • CitectSCADA 

I am currently running Citect on a mix of Windows NT 4.0 and Windows 98 machines, and am thinking about upgrading them to Windows 2000. Will Citect run correctly on Windows 2000, and is there anything special I have to do to it? 

Citect will run on Windows 2000, but there are some issues you need to be aware of. In fact, Citect v5.21 was tested in a Microsoft sponsored Windows 2000 Compatibility Lab in Melbourne, running on both upgraded and fresh installations of Windows 2000 Professional and Windows 2000 Advanced Server. The issues identified relate to the tighter security model in Windows 2000, rather than issues with Citect itself.

The majority of these issues can be solved by simply promoting your Users to be members of the Power User group. This is done as part of the upgrade from Windows NT 4.0 to Windows 2000, though may not be done during the upgrade from Windows 98 or during a fresh install of Windows 2000. Each issue is described below:

  • Citect.ini permissions. Windows 2000 now restricts access to the WINNT directory, where the Citect.ini file usually resides. Users won't be able to make changes to certain Citect settings when needed. To solve this simply give full control permissions to the Users group for the Citect.ini file.
  • Dr Watson log. When a program crashes a utility known as Dr Watson logs information about the crash to a file for debugging purposes. In the past this file was called drwtsn32.log and was located in the WINNT directory, and if Citect crashed it would log some extra debugging information to the same file. In Windows 2000 the file's name and location have been changed, though Citect will still log its extra information to the drwtsn32.log file, providing it has the correct permissions. If the currently logged in user doesn't have permissions then the file isn't created and no error is reported.
  • Syslog.dat. Citect normally keeps a brief log file reporting compilation, communications errors, startup time etc. This log is kept in the file Syslog.dat in the WINNT directory. Windows 2000 restricts access to this file and directory, which causes the log file to not be generated unless the user is logged in with Administrator privileges. To avoid this, create the syslog.dat file yourself, and give full control permissions to the Users group.
  • Example project can get stuck in a startup/restart loop. When the Example project is run for the first time some Cicode installs the Calendar Control and restarts Citect. Citect can't install the Calendar Control unless the current user has Administrator privileges, and if the control isn't installed then the Example project can get in a loop where it endlessly tries to install the control. To avoid this simply run the Example project for the first time while logged in with Administrator privileges.
  • A copy of Regsvr32.exe is stored in the Example project. The ActiveX demonstration Cicode in the example project requires a copy of Regsvr32 to make sure that the Calendar Control is correctly installed. When doing an upgrade from Windows 98 to Windows 2000 the upgrade will report this file as a backed up system file, and warn that it will be deleted. Deletion of the file will not cause any problems for Citect.

NOTE: To make changes to security permissions on files you will need to have Administrator privileges.