Home Up Search Site Map 

OmniClient

Up

This section describes how to configure Omniclient for use in a Topcat system.    It applies to Topcat Version 1.4 onwards with Patch 6a (or later patch) applied.  

To invoke Omni on startup instead of !TCfiler

TCFiler provides the default Logon and Server icons in Topcat.     If you wish to use Omniclient instead proceed as follows:

bulletIn the 'Desktop' files:(to be found in Armboot.!Boot.Ro3xxhook.Boot directories), replace the line:

Filer_Run <BootResources$Dir>.!TCfiler

with the line:

Filer_Run <BootResources$Dir>.<Topcat$Filer>.!Run

bulletAdd the following line just before the end of the file:

connect Server computername Server$ Armuser password

where computername is the name of the computer containing the Server$ share,
and password is the Armuser's password (see the file: Armboot.Tcconfig.User).

bullet

Copy the Folder !Omni from Armboot.Omni to Armboot.!Boot.Resources

bullet

Place the following line into your local Settings file (in the Armboot.Tcconfig.Local folder):

Set Topcat$Filer !Omni    (replace any existing line setting this variable)

To set up the necessary variables:

In the file: Armboot.Omni.!Omni.Files.Startup add the following lines:

SetMacro Choices$UserWrite <TCFiler$Userpath>
SetMacro UserChoices$path <TCFiler$Userpath>.

To hide the Armboot icon:

In the file: Armboot.Omni.!Omni.Files.Mounts add the following line:

LanMan,Armboot,H,computername,Armboot$,,,

where computername is the name of the computer containing the Armboot$ share.

Allow !Browse to start after user logs on

Place an obey file called !Armboot in each user's home directory containing the following lines:

| To allow !Omni to work with !Browse and !Marcel
Set TCFiler$Userpath LanMan::<Omni$UserLanMan>.$
Set TCFiler$Username <Omni$UserLanMan>

Implementing the changes

You will then need to delete all the IDxxxxx folders in the Armboot.!Boot.Mchconfig directory and re-boot the client devices in order for the changes to take effect.

Points to Note

After a user logs on and 'Dismounts' their mount, the remaining mount(s) will still be logged on with the last user's privileges.   This is a limitation of Omniclient.    So it is wise to mount a 'dummy' user - eg Armuser with Read-only privileges, after disconnecting an adminstrator's session for example. 

 

Home ] Up ]Back ] Next ]

Send mail to webmaster@microlynx.co.uk with questions or comments about this web site.
Copyright © 1998-2001 Microlynx Software Engineering Limited   E&OE
Last modified: June 03, 2004