Cadzow 2000 System Requirements

Executive Summary

• Cadzow 2000 requires a server and a number of workstations. However, one machine could be both a server and a workstation.

• The server needs to be Windows NT 4.0 (or better) running Microsoft SQL Server 7.0 (or better) — or — Windows 2000 (or better) with SQL Server 2005 Express Edition or better and Microsoft .NET Framework 2.0.

• Workstations need to be Windows 95 or better.

• Workstations require the Microsoft Access 97 Runtime (included with Cadzow 2000).

• Modern systems, including 64-bit Windows 7/8 and latest Microsoft SQL Server databases are supported.

• If you have an existing machine, check “Minimum Configuration” below to ensure it is capable of running Cadzow 2000.

• If you plan to buy a new machine, check “Recommended Configuration” below to ensure your machine is suitable for Cadzow 2000 and its successors.

Database Technology

Although Cadzow 2000 supports both Jet (.MDB) and SQL Server databases, we will no longer deploy new Cadzow 2000 databases using Jet. Sites which do not have a licence for Microsoft SQL Server can use SQL Server 2005 Express Edition, SQL Server 2008 R2 Express Edition or Microsoft SQL Server 2012 Express Edition, which are free and vastly superior to Jet .MDB files.

However, although Cadzow 2000 supports older operating systems such as Windows 95, SQL Server requires later operating systems with other components such as .NET Framework. Thus a networked environment will require at least one modern system to host the SQL Server components. Client workstations may continue to operate older versions of Windows.

(NB. There are enhanced versions of SQL Server Express Edition called SQL Server Express Edition with Advanced Services; these versions are not required for Cadzow 2000.)

Note that at least one user will need to be granted dbOwner privileges on the database as data updates (field/table changes) are performed by Cadzow 2000 when updates are loaded. This could be a special user account created for this purpose. Day-to-day operations do not require dbOwner rights.

Workstations

Minimum Configuration

The following is the bare minimum specification. This configuration is only practical for users with a low volume:

• Windows 95 or later or Windows NT 4.0 or later;

• If using 64-bit, only Windows Vista and above are supported.

• Microsoft Access 97 Runtime (included with Cadzow 2000);
  (NB this Runtime edition of Access 97 peacefully coexists with all versions of Office)

• MDAC (Microsoft Data Access Components) 2.1 if using SQL Server;

• An Intel Pentium-based computer with 64Mb RAM;

• 500Mb of available hard disk drive space;

• Display adaptor and monitor capable of 800×600 (SuperVGA) and 256 colours;

• Network interface card (if networked); and

The following could be attached locally or shared over a network:

• A printer capable of A4;

• CD-ROM drive or Internet access to obtain installation files and updates;

• Large capacity removable storage or online storage for backups.

Recommended Configuration

As above except:

• Windows XP/Vista/7/8/8.1/10 or greater with latest service packs and security updates. Windows XP Service Pack 3, Windows Vista Service Pack 1/2, Windows 7 Service Pack 1 are supported.

  Windows XP Home, Windows Vista/7 Home editions, Windows 8 (Base) or Windows 10 Home are not recommended except in standalone environments as they do not support Remote Desktop or domain networking.

• Intel Pentium 4 with Dual Core.

  If using Windows Vista or later:

• 2Gb RAM;

• AGP graphics with 256Mb RAM;

• 17″ TFT Display at 1024×768 or better;

• 20Gb of available local hard disk space.

  If using Windows XP:

• 512Mb RAM;

• AGP graphics with 32Mb RAM;

• 17″ TFT Display at 1024×768 or better;

• 2Gb of available local hard disk space.

Email Requirements

• MAPI-compliant email client (such as Microsoft Outlook 97 or greater);

• Microsoft Outlook Express; or

• Windows Mail (in Windows Vista).

See Cadzow 2000 Email Support for full description of features and email systems supported.

Networking

• TCP/IPv4 or TCP/IPv6 supported.

• NetBEUI not supported.

Servers

Required server capacity varies greatly with usage.

If you are using Cadzow 2000 attached to a Microsoft Access database (.MDB) in a small workgroup LAN of 5 or so users, the server is simply the machine storing the data and typically you would choose the fastest machine with the most RAM, the most recent operating system and the most advanced file system. (For example, you would favour NTFS over FAT, or Windows 2000 over a Windows 98, or Windows 7 over Windows XP.) From this point of view a machine as shown under Recommended Configuration is suitable.

If you are using Cadzow 2000 attached to an .MDB in a larger LAN, with dedicated file and print servers, most likely the capacity you have chosen to suit your other file serving will adequately handle the requests on the .MDB file also.

If you are using Cadzow 2000 attached to SQL Server, the system should start at 512Mb RAM with 1-2 processors. Larger systems will benefit from 1-2Gb RAM and 2-4 processors. Sizing SQL Server systems is quite complex and cannot be described simply.

Cadzow 2000 supports Microsoft SQL Server 7.0 or later. All editions and service pack levels are supported, although using the latest service packs is recommended.

New databases will generally be provisioned on the latest version of SQL Server, so if you have a need to operate Cadzow 2000 on an earlier version of SQL Server, please let us know in advance.

Notes:
• SQL Server 2000 requires at least Service Pack 3 on Windows Server 2003.
• “Named instances” of SQL Server require MDAC 2.6 or greater on the client workstation, but Windows 95 only supports up to MDAC 2.5. Thus Cadzow 2000 data must located be on a “default instance” of SQL Server if using any Windows 95 systems. By default, SQL Server 7.0 and greater install as a “default instance”, but SQL Server 2005 Express Edition installs as a “named instance”.

Remote Support

Cadzow provides remote support services for Cadzow 2000 users. Technologies supported are:

• Windows XP Professional Remote Desktop and Windows 2000/2003 and later Terminal Server;

• TeamViewer;

• Symantec pcAnywhere 9.2 or later; [2013 — pcAnywhere support has now been deprecated.]

• VNC (Virtual Network Computing) implementations such as TightVNC or RealVNC.

Cadzow recommends that only Terminal Services and TeamViewer be exposed over the Internet, and, in the case of Terminal Services, on a non-standard port. pcAnywhere and VNC should not be exposed over the Internet. pcAnywhere is a good dial-in product (requiring a modem and a phone line) and VNC is a reasonable technology for workstations on the LAN behind the firewall. In all cases, these products should be used with the latest service packs and security patches installed, and should only be accessible with authentication.

What Cadzow 2000 Does Not Support

• Compressed or encrypted data files, or certain types of non-Microsoft volumes. See Cadzow 2000 File System Support.

• Microsoft SQL Server 6.5 or earlier.

• Microsoft Data Engine (MSDE).

• Pre-release (beta or release candidate) operating systems, service packs or SQL Server.

  In the event you experience a problem with Cadzow 2000 with a pre-release operating system, service pack or SQL Server, we are interested to hear about it so we can investigate in time for the final release of that product. However, the likelihood is that the problem will be fixed in the final release and there will be little we can do about it in the interim. Most likely we will advise you to uninstall the pre-release code or use released code.

• Wireless LAN connections.

  Wireless connections are highly functional but nowhere near reliable enough for mission-critical database applications (such as Cadzow 2000). Database applications assume constant connections to the data source, and dropouts are not handled elegantly. This is a common trait of all database applications, not just Cadzow 2000. Wireless connections are excellent for email and web browsing.

  However, if you are using a wireless connection to access a Terminal Services/Remote Desktop or other remote session running Cadzow 2000, this is fine, because the database is local to the host and not being transmitted over the wireless connection.