Precedence Network Computer and NetManager
Errors/Bugs on the NCs

  1. When the NCs boot I get the error, 'The Network Computer cannot display the web page you have selected

    If you've just configured the server, you need to reboot the server after it is configured to start the web server processes.

    Otherwise, this is due to a small bug in Apache. If you type ps ax | egrep httpd you will see that there are no processes called /usr/local/apache/sbin/httpd which are the webserver processes. This is because the Apache startup script thought that Apache was already running. Download and apply hotfix 36 to fix this.

    Contents

  2. Whenever the NC boots it starts up Zap with a configuration file in it.

    The problem

    You have edited a file in !NFSBoot.Tasks from Unix (using joe or kedit) rather than from RISCOS. The editor has saved a backup copy of the file with a ~ at the end of the filename in the same directory (e.g. StaticIP,feb has been backed up to StaticIP,feb~). The presence of the ~ means that the ,feb~ extension is not a valid filetype and so the file appears as text. At bootup every file in !NFSBoot.Tasks is run. Running a text file causes it to be loaded into !Zap.

    The solution

    Preferably, use the NC and Zap to edit any configuration files in the NC boot sequence. If you must use Unix, then make sure that you clean up any backup files. Go into the Tasks directory and tidy up after yourself. You can do this from an NC by editing the boot sequence, going into !NFSBoot.Tasks and then deleting all the files that end in a ~. Alternatively, if you want to fix it from Unix, just type: 
    rm ~ncadmin/boot/\!NFSBoot/Tasks/*~

    Contents

  3. When users log in they get the error ".Choices not found"

    This will only happen if you are using domain logons with LanManFS and you've got the incorrect IP address of your domain controller in the settings for ManMan$NameServer. Please check lines in !NFSBoot.Desktop and also check the line in !NFSBoot.Apps.!Login.Messages that begins with lmnameserver:

    Contents

  4. Insufficient access and locked directories

    Over NFS, the RISC OS concept of a locked file is meaningless. Attempting to lock a file will do nothing. However, if a locked directory is copied onto an NFS mount (or a directory is locked over NFS) this will remove the execute bits in the permissions for non-owner access (which means that files may be viewed within that directory, but not used). However, over NFS from RISC OS, this effectively means that the contents of the directory cannot be accessed at all.

    Contents

  5. I get an error about "Cannot fix pointer"

    This is an error from !Printers. To get round it, you will need to delete the Settings file from inside !Printers which will allow the NC to start up so that you can reconfigure the printer drivers. To do this:

    Contents

Next (Living alongside NT)