Contents - Index

6.4 Compatibility

We keep getting errors on a laptop computer
Some laptops do not maintain a constant processor speed. It may vary slightly and this could cause a problem for Sheriff when it is locked to the processor speed (which is the case if the Licence Key has been generated for a Standalone installation). Also, there is a problem with some laptops using the Intel mobile Pentium III chip; this is a dual speed processor that uses "SpeedStep" technology. The problem is that when Sheriff is using a "Standalone" licence it locks to the processor speed, so the solution will be to issue a new Licence Key for the laptop but do not check the "Standalone" box. However, the key should be defined for just one concurrent user if it is to be used on a standalone machine - the fact that a key is not defined as Standalone does not prevent it from being used in a standalone configuration.

NB. With Sheriff 2.41 and above this problem should not occur with any kind of licence key.

The documentation says that in a network environment, the licence file must be in a location where all users can access it. In a Novell environment, we cannot put the licence file on the server because Novell does not recognise long file names. What options do we have?
You could put the licence file on a workstation instead. As long as the users have write access to it there shouldn't be a problem. Also, I think I'm correct in saying that you can implement long file names by following the procedure set out in Novell Technical Information Document 2929574 (search for 2929574 at

Regarding Novell & Linux file systems. We have our application running at some clients on Novell & Linux file systems (8+3 filename). Sheriff stores the required licence files under the Product ID directory (E.g. 1234-5678-1914-9999-6666). What can we do?
Make sure your file system recognises long file names:

  • For Linux you need to mount your FAT partition as vfat rather than msdos
  • For Novell 3 you need to:
    1. Load os2.nam
    2. At the console prompt ADD NAME SPACE OS2 TO VOLUME
    3. Reboot workstation
    4. Place "Load OS2" in the startup.ncf file.