Selecting an appropriate data directory (Multi user sites)

Due to security concerns there are certain folders that Windows XP will not allow to be shared for write access over a network. These include the following directories.

	Program Files
	Windows
	Documents and Settings

Chreos relies on other computers being able to write to data files in a shared directory on the Server machine. It is important not to put your data in any of the above directories if you will be running Chreos Server on a Windows XP machine.

Please read the following section on Windows 2000 / NT as Windows XP is based on these two operating systems.

 

Multiple users sharing one NT / 2000 workstation

It is possible to install Chreos once and have multiple user accounts use the same install on Windows NT and Windows 2000 machines. Since these operating systems provide enhanced security systems above those of Windows 9x some changes need to be made before an existing install can be shared to multiple users. These changes could cause damage to your system and Wild Software recommends these changes only be made by your systems support engineer.

Chreos uses the following registry Keys and their subkeys

HKEY_LOCAL_MACHINE\Software\Wildsoft
HKEY_LOCAL_MACHINE\Software\Borland\Database Engine

HKEY_LOCAL_MACHINE\Software\Wildsoft stores all chreos settings, and should only be used by Chreos. This key (and its sub keys) must have its permissions set to FULL ACCESS. The best way to acheive this is to set the everbody group to FULL ACCESS (for this Key).

HKEY_LOCAL_MACHINE\Software\Borland\Database Engine provides settings for the Boraland database engine used by chreos to provide database support. This is NOT a Chreos specific key and may be shared by other applications. Chreos users must have FULL ACCESS to this key.

Once these settings are changed, the user only needs to add a short cut to Chreos on each users desktop.

These changes are required on each machine running Chreos Client and multiple user accounts.

Please Note : The above information is for clarification only. You are advised to consult your operating system (os) administrator about this and any other os issues.

 

Problems with NT Service Pack 6 and 6a

Due to the number of operating system related problems reported with NT 4.0 running Service Pack 6 (SP6) and Service Pack 6 (SP6a), Wild Software strongly recommends that you do not upgrade to this service pack. If you are already using SP6 or SP6a we recommend returning to SP4 or SP5. If you are experiencing problems with Chreos and are running Service Packs 6 or 6a please return to an lower Service Pack level and try testing the problem again, *before* contacting support about your problem.

From SP 39, released in April 2004, Windows 95 is no longer officially supported by Chreos. The documentation provided here was provided for versions up to this date. While Windows 95 is no longer officially supported, Chreos may sill run under this operating system.

We highly recommend that you run Windows 95 OSR 2.

Make sure you have the latest release of the Windows common controls as well as the latest release of Ole32.dll ( Version: 4.71.3328.0 or greater ). The easiest way to upgrade the common controls and Ole32.dll is to download and install the latest release of Microsoft's Internet Explorer. This is the preferred method since it will bring your system up-to-date for other system .dlls as well. You can obtain Microsoft's Internet Explorer from: http://www.microsoft.com/windows/ie/

If you do not wish to install Internet Explorer you can download and install the following two files:

1) DCOM95 for Windows 95, version 1.3 which is available from: http://www.microsoft.com/com/dcom/dcom95/dcom1_3.asp
2) The latest version of Comctl32.dll for Windows 95 which is available from: http://www.microsoft.com/downloads/release.asp?ReleaseID=12637

Microsoft has released two updates that you should investigate. The first is the Windows 95 Kernel 32 update. This update to Kernel 32 for Windows 95 resolves a memory leak which occurs when using applications that require continuous opening and closing of a socket over a long period of time. We strongly recommend that you download and apply this update (only for non OSR2 users). The second is Windows Socket 2 update. This update resolves a number of issues in Winsock 2 and includes an update of the TCP/IP stack.

 

TCP/IP and Windows 95