Web template
updated by
Christopher Spry

Guide to installing Microsoft's 'FrontPage 98 Server Extensions' for Netscape's 'Communications Server' v 1.12 on IRIX 6.2

This page is a guide to installing  Microsoft's 'FrontPage 98 Server Extensions' on an Indy running IRIX 6.2 with the Netscape 'Communications server' v 1.12.

There is a companion guide on installing Microsoft 'FrontPage 98 server extensions' for Netscape's 'Fasttrack server' v 2.01 on IRIX 6.5.

Obtaining the programs:

Microsoft's 'FrontPage 98 Server Extensions' are used to enable 'clients' running 'Microsoft's FrontPage 98' on PCs elsewhere, to access, read and updated 'webs' running on a Netscape 'Server'. 'FrontPage 98' is one of the best web authoring packages available at present, in my humble opinion. I have found it to be an ideal tool for preparing web pages on my notebook PC. The 'Extensions' on the Indy running IRIX 6.2, enable me to create and administer 'webs' which are 'served' from the Indy, which is available permanently on Internet.

The 'Communications Server' is first installed using the Silicon Graphics CD called "WebForce to Serve 1.12' which was released on 1 November 1995. You have to buy this CD from Silicon Graphics.

The free (and latest) version of the Microsoft 'FrontPage Server Extensions for IRIX' software is called fp30.sgi.tar.Z. Download it from  Microsoft's web site http://www.eu.microsoft.com/frontpage and save it in /tmp. Do not use the IRIX version on Microsoft's 'FrontPage 98' CD, as it is out of date. Then download the 'shell script' fp_install.sh from http://www.eu.microsoft.com/frontpage to /tmp. You will use it to install the software. The version number and date of fp_install.sh is shown in the first few lines of the shell script. Currently, it is version 1.43 of 19 October 1997.

The 'fp_install.sh' script is written in 'perl'. Ensure that you have 'perl' on your system by typing in a shell: 'where perl'. This should show you that perl is in '/usr/bin/perl' and possibly other directories. If it is not there, then you have to get it from one of the IRIX free software ftp sites, before you can start to install the Extensions.


Installing Netscape's 'Communications Server' v 1.12

Use software manager 'swmgr' to install 'ns_httpd' and 'ns_admin' v 1.12 from the CD you obtained from Silicon Graphics. It sets up a web server on port 80 (http://my.web.server:80) and an 'administration Server' is also setup on port 81 (http://my.web.server:81). It places the 'web server' files and the 'administration server' files in the '/usr/ns-home' directory and below. The 'document root' for the server is /var/www/htdocs'. This is where the 'root' web's HTML files will go. The users' 'web' HTML documents will be in ~user/public_html.

I recommend that you become competent at administering the 'Communication Server' before you install the FrontPage Server Extensions. To do this, start the 'Administration Server' using the script '/usr/ns-home/start-admin', as superuser. Then use a web browser to access the administration server (http://my.web.server:81). Use the options boxes to set up the 'Communications Server' in the way that you want. There is lots of information available to you, while using this 'Administration Server' setup resource. 

Note that the 'root' web is set to be owned by owner 'nobody' with group '60001' but the 'user' is my login name 'cspry'. This is because I will be administering the root web. My personal web is in  ~cspry/public_html. I (cspry) belong to user group 'mygroup'. I am also the administrator of the Indy as 'root', of course, and I have set up the Communications Server so that I have personal web pages in ~'myhomedirectory/public_html' and my URLs are served out as 'http://myserver/~cspry/URLs'. I repeat all that so there is no doubt about these complexities :)

Installing Microsoft's 'FrontPage Server Extensions' for IRIX 6.2

Ensure that you have 'fp30.sgi.tar.Z' and 'fp_install.sh' in /tmp. Check that there is a 'configuration file' for the 'Communications Server' called '/usr/ns-home/httpd-80/config/magnus.conf', and also a file called d '/usr/ns-home/httpd-80/config/obj.conf'. They are both used by the installation script. Unfortunately, the path to '/usr/ns-home/httpd-80/config/obj.conf' has to be edited manually into  '/usr/ns-home/httpd-80/config/magnus.conf'. If you do not put the path into obj.conf, there will be an error that it 'does not exist'.

The following steps list the places where you type or respond (shown in red).

In a UNIX shell and as 'Superuser':

bann01.gif (2203 bytes)

Return to the 'home page'

Return to the `Computing index page'

Return to the 'Indy administration index'