Paths furnish

Here the following cases are to be distinguished:

A single place solution hardly needs settings.

A big number of jobs which is waited centrally needs carefully planned surroundings.

They pursue a job with Moskito.

Moskito can be begun with the help of the program file Moskito.exe in the list Moskito\main.nt directly. Then all paths are booked with defaults. They have with it all data in subdirectories of Moskito and can rename this list also arbitrarily and shift. If you have installed the files in the net, it can make sense to hold the Workfiles, i.e. the fields of work of Moskito, on the local calculator. In this case you begin please Moskito not by the abovementioned file, but by a Batchdatei.

•Put on a copy of the file m.cmd in the same list.

•Write behind the line ”SET GDS$WORKFILE =” the list on which you would like to store the Workfiles. On the suitable record 50 MByte should be free (according to size of the loaded data).

•Begin Moskito by these Batchdatei. It is best to place a reference on the desktop or in the start menu from this file.

They administer a bigger number of jobs with Moskito.

An exact structuralisation of the lists is important here. It is obvious to assign at least 2 lists to every functionality. The first one is same for all users, the second one is held separate for every user. It can be necessary to carry out an other grouping after projects.

It must be distinguished whether all Workfiles are used together, or whether every user own Workfiles used. In the second case the Workfile on the local record can be accommodated, in the first case you must lie centrally.

Action:

•Lay the installation of Moskito on a common network resource.

•Prepare the second installation for a beta version of Moskito.

•Put on for every user the subdirectories like in Moskito\rahmen. These are able (and had to go?) are in the private area of the user.

•Put on for every configuration a Batchdatei and you at first simply use copies from m.cmd. Besides, with configuration every setting which should be carried out for a Workfile automatically by start is meant. This can be, e.g., a capture and information, split itself, however, also further.

• If your jobs are equipped with incompatible hardware, one more list tree Moskito must also exist on the local calculator, so that there the local settings can be accommodated. In this case it makes sense to store the Workfiles there also. Besides, mice with 2 and 3 keys and different trays are incompatible. It is to be seen to the fact that the plans which are loaded in a Workfile cannot be changed any more in other Workfiles.

•Edit now the Batchdateien, so that for every configuration a Batchdatei points at the necessary lists. If several lists are necessary for a function, their names are able to come ";" are connected. The name of the user can be accessed about %USERPROFILE %.

Possible list structure:

C:MoskitoLokal\

BATCH\

Symbols\

Signatur\

Workfile\

\\MOSKITO\

main.nt

rahmen\

batch\

DBB\

150\

200\

symbols\

signatur\

...\Profiles\

Andre\Moskito\

Batch\

Menu\

Horst\Moskito\

Batch\

Menu\

Monika\Moskito\

Batch\

Menu\

Ralf\Moskito\

Batch\

Menu\

With the intimated structure arises the following Batchdatei for the start of Moskito:

set GDS$BATCH=c:\moskitoLokal\batch \; % userprofile %\moskito\batch;.\rahmen\batch

set GDS$DATA =

set GDS$DBB = \\MOSKITO\RAHMEN\DBB

set GDS$TABLES_HEA =

set GDS$TABLES_TEX =

set GDS$WORKFILE = c:\moskitoLokal\workfile

set GDS$MENUE = c:\moskitoLokal\menu; %USERPROFILE %\MOSKITO\MENU;.\rahmen\menu

set GDS$TABLES_DLT =

set GDS$TABLES_CHAR =

set GDS$TABLES_SYM =

set GDS$TABLES_SIG =

set GDS$TABLES_TOOL =

set GDS$RASTER =

set GDS$MESSAGE =

moskito %1

Now the name of the Workfile is given about a call parametre. Then all not sedate lists automatically point at a subdirectory from ".\rahmen".

By the way:

If Moskito is begun like in the above example by a Batchdatei, can be provided Moskito from the Batchdatei also immediately already a row by orders. This functions about the parametre "EXEC / <Befehl1\nBefehl2\nBefehl3...>". The following entry in the Startbatch begins Moskito under the Workfile with the name TEST and brings immediately the announcement "everything OK!":

moskito test "Exec/echo (""Everything OK!"")"