BEFORE THE INSTALLATION:

1. Users MUST install on a Windows 2000 or 2003 32-bit server machine on a NTFS partitioned drive.

2. Users MUST install with the original “ Administrator ” account.

3. Verify that the POSIX subsystem is present and not disabled.

a. POSIX subsystem can be detected by the presence of the following three files:

i. PSXSS.EXE - the main component of POSIX subsystem.

ii. PSXDLL.DLL - handles communication between applications and PSXSS.EXE .

iii. POSIX.EXE - handles communications between POSIX and Windows NT executive.

b. These files are all located in the System32 directory in Windows 2000, 2003.

4. Before installing Razor, go to Start->Run and type in CMD, then press enter. This will spawn a command line prompt. In the prompt enter: ipconfig and press enter. If you get the message “cable disconnected,” connect your cable, so that when you run ipconfig again, you get your ip address in the output.

INSTALL:

5. AGAIN , install as the original Administrator, NOT as someone with administrative rights.

6. After installing, restart the machine.

7. Input License Keys in the Razor Admin License Key window

YOUR KEYS WILL BE DIFFERENT

8. After Razor verifies the keys, try to start the License Manager.

VERIFY POSIX AND INTERIX AFTER THE INSTALL :

9. Go to Start->Programs->Razor->Razor csh, and type in “razor id”. This should give you the name of your machine, the OS, the processor type and the 8-digit razor id .

If you were not able to get the prompt in the csh window, then check your POSIX or the Interix Installation. To verify that the POSIX subsystem is functional, type “posix” at the CMD prompt. You should receive the following output: “ Posix: Command missing .” This means POSIX is functioning.

10. If, when performing the “razor id” command, the output is all zeros, it means that the network card is not configured properly or it has to be connected to the network.

11. If POSIX works, we must check the Interix path: Go into the Control Panel and double click the System icon.

After entering the System folder, click on the “Environment” tab and find the environment variable called INTERIX_ROOT . Verify its path, which should be: //<drive>/TowerConcepts/Interix .

12. We must also try to execute a command using Interix in order to test it. Go into a CMD prompt and cd to your TowerConcepts directory, then to Interix, and then bin. In the bin directory you will find various UNIX commands that can be executed via Interix and POSIX. To test Interix , just enter a command such as “ ls ” (this is the equivalent of “DIR” in dos/cmd).

Common LM problems:

1. If, after the install process is complete, the license manager does not start from the GUI, attempt to start it from the csh prompt by going to Start->Programs->Razor -> Razor csh. Wait for the prompt and cd to the TowerConcepts/Razor/bin directory. Then type: “ ./razor_lm up. ” Razor should either start up or give you a specific reason for not starting.

2. In the event that the License Manager starts from the csh prompt but does not from the GUI, check the following things:

a. Run “ipconfig” in the CMD prompt, if not connected, connect.

b. Go to the services menu and find a service called Razor License Manager.

You should get a window where you can specify the “Logon As” option.

The “Startup Type” option can be Automatic or Manual. The “Log On As” option is the one that should be changed. First Click on the This Account checkbox, then click on the small browse button to the right of the This Account check box.

Change the name to Administrator and input the password twice. Now attempt to start the service manually.

You can also attempt to start the service from the CMD prompts by typing: net start “Razor License Manager” (exactly as it appears).

Also, check the permissions on the TowerConcepts directory from the csh prompt.

You can change the permissions for this directory by doing “ chmod -R 775 TowerConcepts ”, this should give it the proper permissions to run the License Manager.

Common Database problems.

1. The database will not start . This usually happens when the DB is not created using the Administrator account, causing it to have wrong permissions, or Razor was not installed as the original Administrator. Create your databases and install Razor as Administrator to avoid this problem .

2. In the event that a properly created DB does not start through the GUI, attempt to start it through the csh prompt. Get the prompt -> cd to the TowerConcepts directory, start the LM if not already running, cd to the database you would like to start, type in: source rz_prep, then type: razor up, this should start the DB or provide a specific reason for not starting.

3. Often times, users are unable to connect to the database using one of the clients. The two biggest causes of this are (1) not providing the correct ip address and (2) the path to the DB is incorrect. For example, if the path to your database appears in the License Manager as: D:\TowerConcepts\razor_db\<your_db>\RAZOR_UNIVERSE , then in your client you would specify it as: //D/TowerConcepts/razor_db/<your_db>/RAZOR_UNIVERSE . Notice the forward slashes instead of the backslashes; also notice the two forward slashes in front of the D (unix notation).

The screen shot contains the License Manager and the Versions client. The license manager has the path for the DB in Windows notation; the Versions client has the Unix notation for the DB path.