Comprehensive Case Management Software
Installation and Trouble-Shooting
July 2002
If you are using, or planning on using Windows 95/98/NT/ME/2000/XP, you can be confident that Tracker will run fine on these workstation operating systems. However, Windows is a complicated environment. It has many internal settings that effect its performance, and the factory defaults for most of these settings presume that you will be using Windows on a stand-alone PC. Since most installations of Tracker are on networks, these default settings can cause problems. You simply need to tell Windows that you are on a network, and tell it the correct settings for your specific network.
You will find the following sections in this document:
● Installing the Novell Client/Server Engine
● Installing the Windows Client/Server Engine
● Installing a Windows Peer-to-Peer Server
● Additional steps for Windows 95/98/ME workstations
● Additional steps for Windows NT/2000/XP workstations
● Considerations and precautions
● Tracker printer environments
● Assess the Nature and Scope of the Problem
● Specific problems and likely solutions
Tracker can run as a client/server database on the following networks:
1. Novell NetWare versions 3.11, 3.12, 4.x, 5.x and 6.x
2. Microsoft NT Server 4.0
3. Microsoft Windows 2000 Servers
4. Heterogeneous networks mixing both Novell and Microsoft servers
Note: You must purchase the correct server module for your specific network operating system version. Client/server installation on a Novell network utilizes a native 32 bit, Novell Certified NLM as the database engine; installations on a Windows network utilize a native 32 bit Windows Service as the database engine.
We will provide the correct server engine with your new installation; however, if you change network operating systems you will need to purchase the appropriate engine for your new network. If you move to a newer version of the same network operating system you may need to update your current server engine. Please call us before changing your network, to see if you need to update the server engine along with your network operating system.
Tracker can run as a peer-to-peer database on the following networks:
1. Windows 95/98/ME
2. Windows NT4/2000/XP
3. Networks mixing compatible versions of Microsoft Windows
4. Most other peer-to-peer networks
Note: You must use the correct peer-to-peer drivers for your network. Please consult with us to determine your exact needs.
Tracker can run as a stand-alone, single user, PC-based application:
1. Windows 95/98/ME
2. Windows NT/2000/XP
Note: Single-user versions of Tracker may not be installed on a network without a network driver. If two users simultaneously attempt to access a single user version of the software, the files will become corrupted. Therefore, if you plan to install a single-user version of Tracker on a network, you must also install the correct network driver to prevent this corruption.
Installing the Novell Client/Server Engine
Tracker uses database products from Revelation Technologies, Inc. The database engine is a very advanced, post-relational database engine that has been ported to different server platforms. The version that runs on Novell NetWare is a Novell Certified NLM. This section provides information that is intended to supplement the installation instructions that ship with the Revelation NLM.
1. Check your versions: If you are using NetWare version 3.x or 4.x you must use the Revelation NLM version 1.5 or lower. If you are using NetWare version 5.x or higher you must use the Revelation NLM version 5.x.
2. Install relevant Novell Service Packs. It is recommended that you install the latest Service Pack for your specific network operating system version. Occasionally, some service packs do have problems, so we do not recommend that you install service packs immediately upon release (unless you are trying to solve an existing problem). Wait a while after a release before installing that Service Pack to give Novell enough time to repair any problems with the Service Pack. Call us if you have questions about a specific release. We are aware of the following issues:
A. Service Packs 3 and 4 for NetWare 5.0 are problematic. Tracker will not run in this environment. You must install Service Pack 5, NW5SP5.EXE, or higher.
B. NetWare 5.1 requires at least Service Pack 1: D51SP1.EXE-Domestic 128 bit. Tracker will not run on NetWare 5.1 without any service packs. As of this writing, if you are using Novell version 5.0, 5.1 or 6.0 and you are using a post NW51 Support Pack 3 release of filesys.nlm, dated August 22, 2001 or newer, you must install the Turbod2.exe patch from Novell. See the Turbo FAT corruption section below for specific instructions.
3. Install Novell patch for Turbo FAT corruption. There is a bug in all versions of Novell NetWare, except version 3.12, needs to be patched before using Tracker. The patches are not included in Novell’s normal Service Packs. This bug affects random access databases with large data files. Examples in the Novell documentation include Btrieve, Groupwise, and Revelation databases.
The problem has its roots in NetWare’s caching of its file allocation table (FAT). Under normal circumstances NetWare uses the FAT to locate files on the server’s hard disk. When files grow to approximately 6MB in size, NetWare creates a special cache to help speed up access to that file. This special cache is called the “Turbo FAT.” Unfortunately, the Turbo FAT is prone to corruption in all versions of NetWare except version 3.12. The larger your data files, and the longer your server is up, the greater your chances of being bitten by the bug.
Fortunately, there is an easy fix. You must install the correct patch for your version of NetWare to insure that you will not be affected. The patches are:
A. NetWare 3.11: Install Novell’s FATFIX patch. This patch installs in an unusual manner. Please follow the instructions closely. It is available from Novell.
B. NetWare 4, 5 or 6: Download and install Novell’s TURBOD2.EXE file. This self-extracting file contains two versions of the patch and installation instructions. Please refer to Novell’s technical document # 2960009 for more information.
4. Verify protocols. As this is written, the NLM requires the use of the IPX/SPX protocol. Revelation Technologies is working on a TCP/IP version that should be available soon. Therefore, IPX/SPX has to be installed on both the server and any workstations that will use Tracker.
5. Install the database engine. After the NetWare patches have been installed, install the Revelation NLM and the workstation drivers according to the directions that are provided with the product. Normally you would install the files to the SYSTEM directory.
Check the AUTOEXEC.NCF file in the SYSTEM directory on your file server and make sure it has the command LHSTART somewhere near the end of the file. This will insure that the Revelation NLM is loaded each time your server is re-started.
Edit the LHSTART.NCF file in the installation directory (normally SYSTEM) to specify the packet size used by your network topology. Locate the line that contains the command, LHIPXSER and add a switch to that line. The switch should indicate the size of the packets on your network, minus the size of the packet header. For example, a typical ethernet network would be set up as follows:
LHIPXSER /P:1472
We recommend that you leave all other settings in LHSTART.NCF at their default values. If you experience problems, the other settings can be used to tune your installation, but the default settings seem to work well everywhere.
6. Set Directory Options. Next, you need to create parameter files that help the NLM protect your data files. The NLM will use a file called REVPARAM to make sure your workstation is still communicating with the file server. Create a file called REVPARAM in each directory that stores Linear Hash data files on your server. Linear Hash files are the files used by Advanced Revelation and Tracker to store data and they look like REV12345.LK and REV12345.OV.
The REVPARAM file may be created using a ASCII text editor such as Edit from the command line, Notepad, Wordpad, or any suitable text editor. To create the file using Edit, simply change to a directory that holds Linear Hash files and type ‘EDIT REVPARAM’. On the first line type ‘ServerOnly=True’. Leave the text editor saving the REVPARAM file. This file will prevent workstations from accessing linear hash files in local mode (for example, if the NLM is not loaded on the server). Create an identical file in each Tracker sub-directory. If the REVPARAM file already exists in the Tracker directories, make sure it contains ServerOnly=True.
7. Configure routers. If there is a router between the server and a workstation, you need to make sure the router does not filter out SAP broadcasts (Stay Alive Packets) from the server. The NLM currently uses 0X5B8, but you should verify this address against the instructions included with your NLM.
9. Set up security. Set up user groups to allow Tracker users to have access to the database files. Users should have rights as follows:
AREVx directory: Read, Write, Filescan, Create, and Erase
DATAx directory: Read, Write, and Filescan
TRANSFER directory: Typical users should have no rights to this directory.
SSI (and possibly your System Managers) should have full rights
FINANCIAL data: This varies with the modules installed. Please consult with us.
10. Map drives. Drive mappings must be set up to allow users to access Tracker files without using the MAP ROOT command. The behavior of the MAP ROOT command changed with version 2.5 of the Novell Client, and it causes numerous runtime problems as you task switch between applications in Windows. Basically, the Novell Client can keep track of only one MAP ROOT drive at a time. If you task switch between two applications that refer to MAP ROOT drives, even if they are the same drive, the Novell Client loses it way.
Therefore, DO NOT use the MAP ROOT command for any drive letter used by Tracker! There are also certain scenarios with the MAP command that cause problems.
Use the MAP command alone and set up a drive letter that other applications will not use.
For example, your drive mappings must look like:
MAP T:= ServerName/VolumeName:\
...and, your drive mappings must not look like:
MAP ROOT T:= ServerName/VolumeName:\
...or, MAP ROOT T:= ServerName/VolumeName:\TRACKER\
You will also have intermittent problems if you enter a non-root drive mapping that includes subdirectories, such as:
MAP T:= ServerName/VolumeName:\TRACKER\
If your NDS structure requires you to map drive F:, as in:
MAP F:= ServerName/VolumeName:\
...then do not use drive F: to launch TRACKER! An explicit mapping to drive F: will cause drive F: to behave as a MAP ROOT command, even though the ROOT statement was never used!
DO NOT map drives in Windows Explorer. Set drive mappings in the Login Script.
11. Set up workstations. Refer to the sections below that describe how to set up the type of workstations that you use.
Installing the Windows Client/Server Engine
Tracker uses database products from Revelation Technologies, Inc. The database engine is a very advanced, post-relational database engine that has been ported to different server platforms. The version that runs on Microsoft Windows servers requires the use of Windows NT 4.0 or Windows 2000, and it runs as a “Windows Service.” (As this is written, Windows XP Server is not available.) This section provides information that is intended to supplement the installation instructions that ship with the Revelation NT/2000 Service.
1. Install relevant Service Packs. It is recommended that you install the latest Service Pack for your specific network operating system version. As this is written, Window NT has Service Pack 6 and Windows 2000 has Service Pack 2. Microsoft also has hundreds of individual patches available at its web site to address problems that are not addressed in the Service Packs.
Occasionally, some service packs do have problems, so we do not recommend that you install service packs immediately upon release (unless you are trying to solve an existing problem). Wait a while after a release before installing that Service Pack.
2. Verify protocols. As this is written, the Windows Service communicates over any protocol that supports Named Pipes. In a Windows environment this typically means you will be using NetBEUI and/or TCP/IP. Various versions of Windows implement TCP/IP differently. For example, some of the earlier versions wrap TCP/IP packets in NetBEUI packets, so TCP/IP will not work correctly unless you also have NetBEUI installed. So, you could try TCP/IP alone, but if you have trouble getting your machines to talk correctly you may need to add NetBEUI. Windows 2000 was the first Microsoft product that shipped with TCP/IP that was not dependent on NetBEUI. Some later versions of Windows 98/ME, however, may work without NetBEUI. This is an issue with the implementation of TCP/IP on Windows, not an issue with Tracker.
3. Install the database engine. After the Windows patches have been installed, install the Revelation NT/2000 Service and the workstation drivers according to the directions that are provided with the product.
4. Set up Sharing. Make sure that the directories containing Tracker files are shared.
5. Disable file caching. If your server is using Windows 2000, be sure to disable caching of files in each shared folder that contains Tracker files. Open the Sharing window, click the caching button, and make sure caching is not enabled.
6. Enable the SYSTEM user. You need to add the SYSTEM user to a directory that is above the directory containing the Revelation files and grant all rights to the SYSTEM user. Do not add the SYSTEM user directly to the directory that contains the files. For example, if your directory structure looks like this:
\TRACKER
\AREV_RT.312
\Tracker program files
\DATA.312
\Tracker data files
...then add the SYSTEM user to the TRACKER directory.
7. Set up security. You must install NTFS on your server (if it is not installed already) if you want to have any server-level security. Go to My Computer/Manage/Disk Management to see the type of filing system that is installed on your server. Check your server’s Help files to determine how to install NTFS if it is not installed.
Set up user groups to allow Tracker users to have access to the database files. Use the Security tab in the folder’s Properties to set up rights for various groups of users. Users will need Read, Write, Read & Execute, and List Folder Contents rights to the AREV and the DATA directories. Users do not need to have access to the TRANSFER directory. If you use the financial module, you must set up additional groups and modify the security for the financial files. Call us for assistance in setting up security for the financial module.
8. Map drives. If you have a Windows 2000 network (server and workstation) you can set up a login script that maps drive letters for you. Otherwise, you need to map drives at each workstation. Set up a single drive letter that will be used by all Tracker users. Different users cannot use different drive letters to access the same version of Tracker because Tracker will have internal pointers that tell it where the data files are located. You can use any drive letter you wish and any location you wish. You can also re-locate Tracker files as long as you set the internal pointers. Note: Windows will perform better if your directory structure is not too deep. The deeper your structure, the slower the performance.
9. Set directory options. Next, you need to create parameter files that help the Service protect your data files. The Service will use a file called REVPARAM to make sure your workstation is still communicating with the file server. Create a file called REVPARAM in each directory that stores Linear Hash data files on your server. Linear Hash files are the files used by Advanced Revelation and Tracker to store data and they look like REV12345.LK and REV12345.OV.
The REVPARAM file will be created using a ASCII text editor such as Edit from DOS. To create the file simply change to a directory that holds Linear Hash files and type ‘EDIT REVPARAM’. On the first line type ‘ServerOnly = True’. Leave the text editor saving the REVPARAM file. This file will prevent workstations from accessing linear hash files in local mode (the NLM is not active on the workstation). Create an identical file in each Tracker sub-directory. This step will only need to be performed once. If the REVPARAM file already exists in the Tracker directories, make sure it contains ServerOnly=True.
10. Set up workstations. Refer to the sections below that describe how to set up the type of workstations that you use.
Installing a Windows Peer-to-Peer Server
Tracker uses database products from Revelation Technologies, Inc. The database engine is a very advanced, post-relational database engine that has been ported to different server platforms. Normally, we recommend that you use one of the client/server versions of Tracker. Your system will perform better and be less exposed to problems. The client/server version can better isolate your data from network and power problems, and user errors. However, the client/server version may not be practical for small offices, and the peer-to-peer version may be used.
The peer-to-peer version relies on Windows file sharing to create a multi-user environment. This approach requires the use of a product called the Network Performance Pack (NPP) to enable multi-user capabilities and prevent file corruption when multiple users access the same file at the same time. It does not have the same benefits as the client/server implementation, but it is more affordable and a reasonable choice for small offices (approximately 5 users). You may use the NPP product on Windows NT or 2000 machines, just as you can with the client/server version; however, you may also run the NPP on Windows 95/98/ME/XP peer-to-peer servers as well.
This information is meant to supplement the installation instructions that ship with the Revelation NPP:
1. Select a server. In an office with a peer-to-peer network any machine can be designated as the “server.” This is simply the machine that will hold the Tracker files. It should be a machine that can be turned on first, and it should have backup capabilities and a UPS. If you have a choice between a machine that has NTFS installed and one that does not, we recommend that you use the machine with NTFS so you can implement security on the server.
2. Install relevant Service Packs. It is recommended that you install the latest Service Pack for your specific network operating system version. As this is written, Window NT has Service Pack 6 and Windows 2000 has Service Pack 2. Microsoft also has hundreds of individual patches available at its web site to address problems that are not addressed in the Service Packs.
You may also use Windows 95/98/ME/XP machines as a peer-to-peer server. Install any relevant service packs on these operating systems, just as you would for a Windows NT/2000 machine.
Occasionally, some service packs do have problems, so we do not recommend that you install service packs immediately upon release (unless you are trying to solve an existing problem). Wait a while after a release before installing that Service Pack.
3. Activate Sharing and map drives. Set up file and printer sharing on your peer-to-peer server machine and set up drive mappings. Each machine that will use Tracker must use the same drive letter mapping, including the server machine. So, for example, you might want to map drive T: to the shared directory containing the Tracker files, and create this drive mapping on every machine.
If your server is a Windows 2000 or XP machine, make sure you disable file caching from the Share settings for the Tracker folder(s).
4. Disable file caching. If your server is using Windows 2000 or XP, be sure to disable caching of files in each shared folder that contains Tracker files. Open the Sharing window, click the caching button, and make sure caching is not enabled.
5. Set up security. If your server machine is Windows NT/2000/XP you can install NTFS and obtain a higher level of security. After you install NTFS you can use Windows Explorer to Right click on a directory, go to Properties, and use the Security tab to specify which user groups have which rights to the folder. Users will need Read, Write, Read & Execute, and List Folder Contents rights to the AREV and the DATA directories. Users do not need to have access to the TRANSFER directory. If you use the financial module, you must set up additional groups and modify the security for the financial files. Call us for assistance in setting up security for the financial module.
If your server machine does not use NTFS, or it uses Windows 95/98/ME you can only set up share-level access, but you have no control beyond that. Tracker has internal security measures, but your machine is generally vulnerable. Any user with a bootable floppy disk and a little bit of knowledge can circumvent operating system security on a non-NTFS machine. Therefore, we recommend that you use NTFS configured machines as the server for a peer-to-peer network whenever possible.
6. Set up workstations. Refer to the sections below that describe how to set up the type of workstations that you use.
Installing the workstation has several parts. This section will discuss the steps needed on all Windows 95/98/ME/NT/2000/XP PC’s that are used for Tracker, then it will discuss network-specific steps to take depending on the type of network you are using. Begin as follows:
1. Install all available Windows service packs. Each version of Windows has Service Packs available. You should use the latest version available, except that we do not recommend you install a service pack immediately following its release. You should give it a month or two for initial problems to get resolved.
2. Disable Windows Power Management. Windows has a feature that attempts to save power by shutting down the computer (putting it in “sleep” mode). This feature becomes active if the PC has been inactive for a period of time. Unfortunately, this feature will cause dropped connections with the Novell database engine on the server, and under some conditions may contribute to index corruption and locking conflicts on all client/server and peer-to-peer installations. You should disable this feature.
You may disable the power saving features by double-clicking on My Computer, then double-clicking on Control Panel, then double-clicking on Power:
• In Windows 95/98/ME you should click on the “Power” tab, then uncheck the box that says “Allow Windows to manage power use on this computer”, then click Apply.
• In Windows NT/2000/XP you should click on the “Power Schemes” tab and select “Always On.”
You will also see other settings that address other critical components of your machine. For example, you can specify whether your disk drives will shut down after a period of inactivity. You may want to consider changing the settings on your machine to keep disk drives running continuously. It is not required by Tracker, but we believe it may be wise to do so. The reason is that hard disk drives experience the most wear and tear during power-up and power-down. When this power saving feature is enabled, Windows will constantly stop and start your hard drive. Although you may save a slight amount of power, you will experience greater wear and tear on your hard drive, and possibly cause it to fail earlier than it would if it remained on all of the time. There are also delays in the performance of your machine as the hard drive needs time to start up. Some users perceive these delays as workstation problems and will reboot or take some other inappropriate action during the delay. Again, this change is not required by Tracker, but we believe it is something you should consider.
You will need to re-start your computer for the change to take effect. If your machine still “sleeps” after making this change you may also need to make changes in the BIOS of your PC. This is very unlikely, but possible.
3. Disable any power management settings in the workstations’ BIOS. Many new computers ship with built-in settings to shut down the computer or to suspend operation of certain components in the computer after a period of non-use. This will have the same impact as the Windows power management settings discussed earlier and should be disabled.
Windows power settings (in the Control Panel) do not control the BIOS power settings. You must disable these power settings separately. Each PC is different. Check with your manufacturer to see how to change BIOS settings on your computer. Disable any “power management” or “sleep” related features.
4. Decide on an icon strategy. You may place icons in any location that is convenient. You may place them on the desktop, in menus or in folders, or in any combination thereof. You may also create an icon, copy it to your server, then just create a shortcut to that icon on each machine. Do not, however, create a shortcut with one version of Windows and use it with another version. You must create a separate icon for each version that will be using Tracker.
5. Create the icon. Use your mouse to point to the location for the icon and press the right mouse button. You will see a drop down box of options. Move your cursor to ‘New’ and then click on ‘Shortcut’. On the Command line type in the full path to the arev.exe file or click on ‘Browse’ and locate the arev.exe file through the Browse window. Either way the Command line must contain the full path to the Arev.exe file. Once the path and file name are displayed, click on Next. In the ‘Select a name’ line enter ‘Tracker’ and click on ‘Finish’. In a few seconds you will see an icon for Tracker.
Additional Steps for Windows 95/98/ME Workstations
1. All versions of Windows. Complete the steps described in the section entitled “All Versions of Windows” before proceeding with this section.
2. Configure the icon. There are several settings that need to be modified before launching Tracker from the icon just created. Start by pointing your mouse at the icon and pressing the right mouse button. You will receive a drop down box that contains an option for Properties. Single left click on Properties. You will get a tabbed box with multiple tabs across the top. Each tab contains settings for this icon. To review the settings for each tab simply click on the tab name.
We will discuss each tab in detail and the settings for each:
General - This tab contains basic information about the icon.
Read-only Unchecked
Archive Checked
Hidden Unchecked
System Unchecked
Program - This tab contains information used to launch Tracker including the icon.
Title Line Tracker
Cmd line Full path to the Arev.exe, plus switches, as in:
path\arev.exe , /S /X /M2048
If your environment allows you to capture the username in a DOS variable, you may pass the username to Tracker in the icon, as follows:
path\arev.exe %USERNAME% /S /X /M2048
This is easy to do on a Novell network, or from the autoexec.bat file of an individual machine. It cannot, however, be done from a Windows server login script.
If you just want to hardcode the username in the icon, you may do so as well. For example:
path\arev.exe yourname /S /X /M2048
Working Full path to the directory containing the Arev.exe file.
Batch file Leave this blank, unless you are on a Novell network. If you are on Novell, see the Novell instructions below.
Shortcut key None
Run Normal window or Maximized (We recommend maximized)
Close on exit Checked
Change icon Advanced Revelation provides an icon that can be used for Tracker. To change the current icon, click on the Change Icon button and use the Browse option to locate the Advanced Revelation files on your network. Double click on the Arev.ico file to return it to the Change Icon window and click OK.
Font - This tab controls the way Tracker displays on your screen.
Bit map only Unchecked
True type only Unchecked
Both font types Checked
Font size Auto
Memory - This tab controls memory settings for the application.
Conventional Memory Auto
Total Auto
Protected Unchecked
Initial Environment Default
Expanded (EMS) Memory 2048
Extended Memory None
Uses HMA Checked
MSDOS Protected Mode (DPMI) Memory Auto
If the Expanded Memory option is not available on your machine you must try to make it active:
• If you are using Windows 95 or Windows 98, check your CONFIG.SYS file. If it contains a statement like:
DEVICE=C:\WINDOWS\EMM386.EXE NOEMS RAM
Remove the NOEMS portion of the command and replace it with 2048.
If no such line exists in your CONFIG.SYS file, modify the file to contain these two lines at the very top of the file:
DEVICE=C:\WINDOWS\HIMEM.SYS
DEVICE=C:\WINDOWS\EMM386.EXE 2048 RAM
Reboot your machine to activate these settings. Return to the Memory tab on the icon Properties. If Expanded Memory (EMS) is not available you may need to contact your computer manufacturer for information about how to activate it for your specific machine. Call us if you have contacted the computer manufacturer and still need further assistance.
• If you are using Windows ME you must take a different approach to activate Expanded Memory (Refer to Microsoft’s technical article #Q275423):
Click Start/Run and type system.ini and press Enter to edit the system.ini file. Make sure it does not have either of these statements in the [386enh] section:
EmmExclude ...
NoEMSDriver
If it does, just comment out these lines by placing a semi-colon at the front:
;EmmExclude
;NoEMSDriver
Save the file and restart your computer. If this does not resolve the problem, add
ReservePageFrame=yes
To the [386enh] section of the system.ini file.
Microsoft’s technical document Q275423 provides additional steps you can take if these steps do not work.
Screen - This tab controls how the window Tracker runs in will be displayed.
Full Screen Or...
Window RECOMMENDED setting
Initial size Default
Display toolbar Personal preference. If checked the toolbar contains an icon that allows users to cut and paste between Tracker and other applications. Unfortunately, it also allows users to turn off background processing. Background processing must be active for the Tracker application. Either instruct users to leave this setting alone or leave this option unchecked.
Restore settings on startup Checked
Fast ROM Emulation Checked
Dynamic Memory Allocation Checked
Misc - This tab controls foreground and background processing.
Allow screen saver Unchecked
Always suspend Unchecked (Extremely important)
Idle sensitivity Medium to Low
Quick edit Unchecked
Exclusive mode Unchecked
Warn if still active Checked
Fast pasting Checked
Alt+Tab Checked
Alt+Esc Checked
Ctrl+Esc Checked
Prtsc Checked
Alt+Prtsc Checked
Alt+Enter Checked
Alt+Space Checked
After all settings have been set, click on the ‘Apply’ button and then click OK to return to your desktop. If you are on a network, proceed to the instructions below for your type of network.
Additional Steps for Windows NT/2000/XP Workstations
1. All versions of Windows. Complete the steps described in the section entitled “All Versions of Windows” before proceeding with this section.
2. If you are on a Novell network... You need to take these steps. Otherwise, go to step 3:
A. Install the Novell Client. Install the current version of the Novell Client for Windows NT/2000/XP on the workstation. As this is written, the most current Novell Client for Windows NT/2000/XP is version 4.83.
During installation it is essential that you perform the “Custom” install. This approach is the only one that allows you to select the IPX protocol. If you need IP installed, select IP and IPX. DO NOT select “IP with IPX compatibility mode.”
If the Microsoft Client for Novell Networks has been installed, the Novell Client installation process uninstalls the Microsoft Client, but it leaves behind a couple of lines in the %systemroot%\WINNT\system32\autoexec.nt file. These lines should be commented out. You can do this by placing “REM” at the beginning of each of the lines that refer to the nw16.exe and vipxspx.exe. Failure to take this step will create huge performance problems.
B. Install Novell Client patch 236779 on Windows 2000/XP. If you are using Windows 2000 or Windows XP you must install Novell patch 236779.exe, which can be found at Novell’s web site. This patch does not apply to Windows NT. This is a self extracting executable and it will extract it’s files to the directory that contains the executable. So we recommend creating a folder with just this file in it. Once all the files are extracted, locate the 236779.inf file and install the patch by right clicking the icon and selecting install from the menu. This process updates the system’s registry.
C. Modify/verify the Novell Client settings. The default installation settings are not appropriate for use with Tracker. Access the Novell Client settings as follows:
• Windows 2000/XP: Start/Settings/Network and Dial-up Connections/Local Area Connection and clicking on the Properties button.
• Windows NT: Start/Settings/Control Panel/Network. From here you can access the Novell Client and the network protocols.
...and make the following changes:
• Protocol Preferences. Check the Protocol Preferences tab and make sure that IPX, not IP, is the preferred protocol.
• Advanced Settings. Check the Advanced Settings tab and turn off any option that appears to allow any caching to occur on the workstation. The specific terminology varies with each release of the Novell Client. In the past these options have been labeled as “True Commit”, “Opportunistic Locking”, etc. You need to read each item and make sure your workstation is not caching any data.
D. Create the client initialization batch file. You must create a single batch file and locate it in the AREV directory of your network. This file will contain startup commands for the client so that it can talk to the NLM server engine. Each Windows NT/2000/XP machine on your network can then use this file to launch Tracker. Create the batch file as follows:
1.) Switch to the directory that contains the AREV.EXE file.
2.) Create the batch file using the Edit command, or Notepad, Wordpad, or any other text editor. We recommend that you name the file AREV_W2K.BAT or AREV_WXP.BAT or something similar. The batch file should contain the following lines:
@echo off
cls
LHIPXTSR /P
IF "%1"=="" GOTO NOUSERNAME
AREV %1% /S/X/M2048
GOTO END
:NOUSERNAME
AREV , /S/X/M2048
:END
3.) Save the file and exit.
E. Modify the Program tab in the icon. Right click on the Tracker icon, go to the Program tab, and make the following changes:
Icon name: Change the top field on the Program tab to read “Tracker”
Cmd Line: You must modify this line to call the AREV_W2K.BAT or AREV_WXP.BAT file instead of the AREV.EXE file. You should also add either a username or a system variable name after the batch file. For example,
path\arev_rt.312\arev_2K.bat %username%
path\arev_rt.312\arev_XP.bat %username%
Working Full path to the directory containing the Arev.exe file.
Batch File: Leave this blank. It does not work in Windows NT/2000/XP.
Run Normal window or Maximized (We recommend maximized)
Close on exit Checked
F. Go to step 4.
3. If you are not on a Novell network... You need to take these steps:
A. Modify the Program tab in the icon. Right click on the Tracker icon, go to the Program tab, and make the following changes:
Icon name: Change the top field on the Program tab to read “Tracker”
Cmd Line: You must modify this line to use the necessary switches. If you are on a Windows 2000/XP machine you can include the username in the command line:
path\arev_rt.312\arev.exe %username% /s/x/m2048
If you are on Windows NT, or if you want users to enter their username manually during logon, change the command line as follows:
path\arev_rt.312\arev.exe , /s/x/m2048
Working Full path to the directory containing the Arev.exe file.
Batch File: Leave this blank. It does not work in Windows NT/2000/XP.
Run Normal window or Maximized (We recommend maximized)
Close on exit Checked
B. Go to step 4
4. Finish configuring the icon. There are several additional settings that need to be modified before launching Tracker from the icon. Display the icon Properties dialog box. You will get a tabbed box with multiple tabs across the top. Check the settings on each of the following tabs:
General - This tab contains basic information about the icon.
Read-only Unchecked
Hidden Unchecked
Archive Checked
Program - This tab contains information used to launch Tracker including the icon.
These settings are described above, in steps 2 and 3.
Memory - This tab controls memory settings for the application.
Total Auto
Protected Unchecked
Initial Environment Auto
Expanded (EMS) Memory 2048
Extended (XMS) Memory None
Uses HMA Checked
MSDOS Protected Mode (DPMI) Memory Auto
Screen - This tab controls how the window Tracker runs in will be displayed.
Window Checked
Initial size Default
Display toolbar This option does not work on Windows NT/2000/XP, however, you may cut and paste by left clicking on the upper left hand corner of the window while running Tracker. Select Edit to mark, cut and paste.
Restore settings on startup Checked
Fast ROM Emulation Checked
Dynamic Memory Allocation Checked
Misc - This tab controls foreground and background processing.
Allow screen saver Unchecked
Always suspend Unchecked (extremely important)
Idle sensitivity Low to Medium
Quick edit Unchecked
Exclusive mode Unchecked
Warn if still active Checked
Fast pasting Checked
Alt+Tab Checked
Alt+Esc Checked
Ctrl+Esc Checked
Prtsc Checked
Alt+Prtsc Checked
Alt+Enter Checked
Alt+Space Checked
Once all settings have been set, click on the ‘Apply’ button and then click OK to return to your desktop. You can now launch Tracker from the icon.
6. Make final Adjustments. Some changes to the icon may be made only after launching the program. Double click the Tracker icon now to launch Tracker. If it does not launch correctly, refer to the Trouble-shooting steps at the end of this document. If it launches correctly, make these additional adjustments:
A. Adjust the size of the window. Right click on the title bar at the top of the window and select Properties, the Font tab, and change either the font type or size so that the size of your window is comfortable for you. Next click OK, and when the Apply Properties popup appears select “Save properties for future windows with the same title”.
B. Activate the mouse. Right click on the title bar at the top of the window and select Properties, the Options tab, and make sure that QuickEdit Mode and Insert Mode are not checked. This will enable your mouse within Tracker. Next click OK, and when the Apply Properties popup appears select “Save properties for future windows with the same title”.
7. Multi-tasking considerations in Windows 2000/XP. Microsoft changed the behavior of the virtual machines between Windows NT and Windows 2000. As a result, programs like Tracker can consume more CPU cycles than necessary under Windows 2000 or XP. Behavior under Window NT should not be an issue.
If you experience slow or jerky screen response in other applications, like word processing, when Tracker is also running, you should consider purchasing a third party utility to manage the CPU cycles. We have found that Tame (www.tamedos.com) does a much better job at managing the CPU’s utilization than Windows itself. If you choose to use Tame we can provide further assistance in helping you install and configure it.
If you do not see any jerky response in other applications, while Tracker is also running, there is no need for you to pursue a utility like Tame.
Printing from within Tracker is simple, flexible, reliable, and easy to maintain, as long as you pay attention to a few details:
Considerations and Precautions
1. Do not purchase “Windows Only” printers. Tracker prints to the LPT port on your PC, or to an LPT port that has been redirected to a network printer. Many low cost printers cannot print from LPT ports. These printers are typically labeled as “Windows Only” printers, and you should not purchase them for use with Tracker. As thi