User's Manual

62
function is completely transparent to user and developer alike, and is managed by the dongle's software drivers. There
is therefore no need to carry out periodic dongle access operations to ensure timeout is refreshed.
11.6 Errors
In addition of the errors returned with the Standalone driver, the status entry may assume one of the following
values:
Nome Valore Descrizione
ST_NET_ERROR
-5 Generic error on the Lan communication.
ST_USER_ERROR
-8 Maximum number of user and license reached.
ST_EXEC_ERROR
-16 Maximum number of execution reached.
ST_NET_PWD_ERR
-9
Wrong netpassword specified.
ST_INIT_ERROR
-11 Generic error in the library initialization.
ST_TOO_MANY_OPEN_KEY
-14 Maximum number of open connection reached.
ST_NET_CONF_ERROR
-21 Generic error in the library configuration.
ST_NET_ANP_INIT_ERROR
-22 Generic error in the initialization of the protocol ANP.
ST_NET_TCPIP_INIT_ERROR
-23 Generic error in the initialization of the protocol TCPIP.
ST_NET_NOVELL_INIT_ERROR
-24 Generic error in the initialization of the protocol Novell.
ST_NET_LOCAL_INIT_ERROR
-25 Generic error in the initialization of the protocol Local.
ST_NET_KEY_NOT_MAP
-26 Attempt to open a MAP connection without using a MAP configured
device.
11.7 Standalone or Multilan drivers?
Use of drivers for standalone programs was described in the chapter on manual protection. The Multilan technology
was instead discussed in the current chapter. This technology enables use of drivers for both standalone and networked
environments. Here are a few hints on which of the two types of drivers the following should be used:
Programs which are certainly standalone only
: use a standalone type driver, because the dimension is
smaller (about half of the relevant MultiLan driver, as it does not include support of the network).
Standalone and network programs
: user a MultiLan type driver, because it makes the program independent
of the operating mode (standalone or network).