It is worth repeating that, on each workstation, you must set up a mapped network drive that contains (or will contain) the GECL folder, and use this when specifying the location of the GECL folder during the installation process. You cannot use Network Neighborhood (My Network Places) type references (i.e. Universal Network Addresses), except to find and launch the install programs themselves that you have downloaded from our website. (Map a network drives either using the Tools menu in Windows Explorer or my computer - or better still (if you have the computer literacy) by creating a DOS batch file ("Initialize.bat" say) in your "Startup" folder (i.e. "C:\Documents and Settings\All Users\Start Menu\Programs\Startup" for workstations running XP, 2000, or NT), that will run an appropriate "NET USE" command. With any Windows 98 computers, simply modify the "c:\AutoExec.bat" file.)
You should install the main software first from the primary workstation. This will configure the default network drive and path settings appropriately. Then run the workstation install for each workstation that will be using the software.
The workstation install will set up the Microsoft VFP run-time engine on the local hard disk. It will also create two shortcuts on the local desktop, and a program group in the Start Menu. It will default these shortcuts to the same drive and directory settings as for the main workstation. (If you are not using a standard drive designation for all workstations, you will need to edit the properties of the shortcuts appropriately. The workstation install program will also configure the local Windows Registry appropriately.
Peer-to-Peer Networks
The "Multi-user Installation" instructions above also apply to small peer-to-peer networks. However, it is wise to create a shared directory ("c:\Shared" say) on the main workstation ("server"), for access by other users (rather than sharing your entire Drive C). Set up drive mappings on the other workstations (as per the instructions above), so that they can easily access this shared resource. The "NET USE" technique is highly recommended in a peer-to-peer environment, because a workstation set up using the Explorer / My Computer technique can easily lose a drive mapping if the main workstation (GECL server) is not turned on first at startup.
On the main workstation itself, you will need to set up a mapped
drive letter (preferably the same letter that is used on all other workstations) to
this shared resource ("c:\Shared"). Either do this as a mapped network drive, or
better still, set this up as a substituted drive (using the
"SUBST" command instead of "NET USE" in an "Initialize.bat" file as
described above - or c:\AutoExec.bat for Windows
98 computers). Once you have done this and rebooted your computer to test
and activate it, then (and only then) install the GECL software into this new mapped
drive.
Upgrading Single-User or
Peer-to-Peer to a new dedicated File Server
Shifting GECL data and software from a single-user installation over to a
dedicated file server is fairly straight-forward. Just copy the whole
"\GECL" folder structure to an appropriate resource on the server (including
the "\GECL" folder itself). Keep the "\GECL" folder
structure on the old workstation for a short while as an extra backup, but rename it
(to "\GECLOld" say) to expose any problem where the main (or any
other) workstation has not
yet been remapped correctly (and is still trying to access the old
programs and data).
If upgrading a single-user installation to a dedicated file server, you next
need to establish a mapped network drive letter to the server resource in
which the "\GECL" folder is located. (This may have already been done if
that resource on the server houses data for other applications.) You
then need to change the properties for all GECL shortcuts on your main
workstation (GECL Professional Practice, GECL Demo, and GECL Backup), so that
they point instead to the new data and programs on the mapped network drive.
Test that this has been done correctly, by running them. "Re-index all
files" (from the "File" menu) is a good test, because it opens all modules and
data files. You can then install new workstations, by running the GECL
Workstation
In a peer-to-peer environment, change the drive letter mapping on respective
workstations so that they point to the new server resource instead of the
shared resource on the old main workstation. (If you have decided to
change the drive letter for some reason, then you will need to edit the
properties of all GECL shortcuts on all workstations accordingly. Note
that it is OK to have two or more mapped drive letters pointing to the same
server resource - and if done systematically, this can give greater
flexibility for increased security in the future as your network grows.)
Migrating everything across to a new file server
It is usually extremely simple to shift the Adminsoft/GECL data and programs across
from one server to
another. Ideally you want to retain the same logical drive
mappings on all the workstations. The simplest way to achieve this is by giving the
new server the same "server name" as the old server that is being retired,
and creating the same "shared resources" as were on the old server (that all
the workstations will find using their existing settings - without any need
to change these). You may have your own reasons
for not doing this (e.g. if the old server will be retained in service and
only some items are being transferred to the new server). If that is
the case, you will obviously need to re-map the network drive letter used by
the Adminsoft/GECL software, so that they point to the new shared resource.
(You will need to do this on each workstation - or edit a common script (or
DOS batch file) that they all run at boot-up.)
If you really do need to change the mapped network drive letter itself, you will need
to alter the appropriate short-cuts on each workstation ("Adminsoft / GECL
Professional Practice" which runs the software, and the "Extra GECL Backup"
if this is present on the respective workstation). You will also need
to edit the "GECL.ini" file in the "c:\Windows"
folder (on each workstation), so that it uses the new mapped drive letter.
Note that the shared resource (that the mapped network drive letter points to)
should be the parent folder in which the GECL / Adminsoft directory
structure is located - not the "\GECL" folder itself. (If the "\GECL"
folder is the only item in this parent folder - then so be it.
However it is usually sensible to create a Download folder in this parent,
and an "Adminsoft" sub-folder hanging off this as a convenient place to store the "WebWkSt.exe" file that you will run when
installing new workstations.)
Refer to the general instructions
in the preceding sections for additional background understanding.
Shifting a single-user installation to a new computer
At a single-user site, you will probably upgrade your computer hardware from
time to time. This is similar to upgrading to a dedicated file
server (see above) in terms of copying the whole "C:\GECL" folder structure
over to the new computer. But you will also need to install the
Microsoft Visual FoxPro run-time library, and appropriate shortcuts on the new
computer, so that you can actually run the GECL software on it. (A files
server doesn't actually need to run the GECL software itself - it just serves
up its files to the workstations that are running the actual programs.)
The additional installation can be done simply by running the GECL Workstation
Install file (3.4MB) that you can download from our website.
Alternatively, you can download and run the "Main software in one file" or
"Core Components and Address Book". These will automatically
detect that you have existing data, and will not overwrite it with any empty
initial data files.
Problems with Windows NT, 2000, and XP
We haven't encountered any problems at all with installations in Windows 95, 98, Me,
and most XP
environments. Unfortunately however, we can't say the same about Windows NT,
2000, and some XP sites. (Can anyone?)
(Click here for assistance with Windows NT,
2000 and XP)
Adminsoft Directory Conventions
GECL software is very flexible with regard to the directory structure that it
can accommodate. Paths for respective data files can be specified during
installation, and altered subsequently in the
configuration settings (see Tools, Options, System Settings menu). Unless
you have over-riding reasons to do otherwise, we recommend that you accept the
default settings "as they come out of the box", as this will require
minimal subsequent "tweaking" on your part (to shortcuts, path
settings etc.).
By default the software and data will be installed together into a "c:\GECL" directory
(i.e. off the root directory in Drive C). When installing in a network environment,
you need to over-ride this of course, so that the "\GECL" directory is located on
the server. You should use mapped network drives rather than
"Universal Network Address" (i.e. you need to map a drive first using
My Computer or Explorer, and specify this directly. Do not use Network
Neighborhood - except to map a drive!!!). It is preferable to place the \GECL directory in the
root directory for the mapped network drive (e.g. "T:\GECL"),
but the install program and software will handle being pushed down one or more
levels of subdirectory (e.g. "F:\Apps\GECL").
When installing the software on a stand-alone computer, we still recommend
placing \GECL in the root directory, rather than under "Program
Files" because we philosophically don't particularly like the idea of having
significant volumes of important data tucked away in the "Programs"
directory. Also, with most of our users, the GECL software is the principle activity of
the computer/workstation concerned. Hanging it off the Root directory makes it
easier for users to find for backup purposes, and whenever they eventually need
to shift it over to a server (if upgrading to multi-user) or new replacement
stand-alone computer. (It also means that novices are less likely to be confused
by all the other sub-directories in the "Program files" directory, and
accidentally damage some of these if they are poking behind the scenes in GECL
programs and data for some reason.) You are fully entitled to disagree with our philosophy if you like, but at
least you can understand our rationale.
If you elect to go for a non-standard directory structure, you will need to
alter all "Demo" shortcuts appropriately, in order to get the Demo
running properly - start by editing the
directories specified in the shortcut, you may also need to change the path
settings (see Tools, Options, System Settings menu).
For user convenience (with updates in particular), we keep just one
master set of program files (GECL.exe and *.app) on the server, rather than installing them
on every workstation. It seems sensible to keep all GECL stuff together
(both programs & data) in the \GECL directory structure. However, it
is easy to separate the program and data files - e.g. if this is a more
convenient way to backup only the data files on a daily basis, say. (However,
this is usually not necessary. GECL's basic backup facility (GEBackup.bat)
only backs up data and configuration files. If you are using a backup tool
like MS Backup, you are able to simply exclude the program files from your daily
backups.) It is also possible to store copies of the program files on the
local hard drive for each workstation and run them from there, if you need to
reduce your network traffic slightly. Contact the GECL HelpDesk if you
want to split the location of your program and data files.
The Microsoft
Run-time engine (VFP*.* files) is installed according to Microsoft conventions,
in the "\Windows\System" directory on respective workstations.
The install process raises appropriate entries in the system Registry for each
workstation. This is why you need to run the "Workstation
Install", rather than merely setting up a shortcut that points to the
programs and data.
If you need further assistance or have feedback you would like to give us,
please contact our Help-Desk:
E-Mail now to: Support@Adminsoft.com
Phone: (09) 262 2020, Fax: 262 2021,
(From overseas +64 9 262 2020, etc.)
Click here for the main Help page
If upgrading a single-user installation to a dedicated file server, you next
need to establish a mapped network drive letter to the server resource in
which the "\GECL" folder is located. (This may have already been done if
that resource on the server houses data for other applications.) You
then need to change the properties for all GECL shortcuts on your main
workstation (GECL Professional Practice, GECL Demo, and GECL Backup), so that
they point instead to the new data and programs on the mapped network drive.
Test that this has been done correctly, by running them. "Re-index all
files" (from the "File" menu) is a good test, because it opens all modules and
data files. You can then install new workstations, by running the GECL
Workstation
In a peer-to-peer environment, change the drive letter mapping on respective
workstations so that they point to the new server resource instead of the
shared resource on the old main workstation. (If you have decided to
change the drive letter for some reason, then you will need to edit the
properties of all GECL shortcuts on all workstations accordingly. Note
that it is OK to have two or more mapped drive letters pointing to the same
server resource - and if done systematically, this can give greater
flexibility for increased security in the future as your network grows.)
Migrating everything across to a new file server
It is usually extremely simple to shift the Adminsoft/GECL data and programs across
from one server to
another. Ideally you want to retain the same logical drive
mappings on all the workstations. The simplest way to achieve this is by giving the
new server the same "server name" as the old server that is being retired,
and creating the same "shared resources" as were on the old server (that all
the workstations will find using their existing settings - without any need
to change these). You may have your own reasons
for not doing this (e.g. if the old server will be retained in service and
only some items are being transferred to the new server). If that is
the case, you will obviously need to re-map the network drive letter used by
the Adminsoft/GECL software, so that they point to the new shared resource.
(You will need to do this on each workstation - or edit a common script (or
DOS batch file) that they all run at boot-up.)
If you really do need to change the mapped network drive letter itself, you will need
to alter the appropriate short-cuts on each workstation ("Adminsoft / GECL
Professional Practice" which runs the software, and the "Extra GECL Backup"
if this is present on the respective workstation). You will also need
to edit the "GECL.ini" file in the "c:\Windows"
folder (on each workstation), so that it uses the new mapped drive letter.
Note that the shared resource (that the mapped network drive letter points to)
should be the parent folder in which the GECL / Adminsoft directory
structure is located - not the "\GECL" folder itself. (If the "\GECL"
folder is the only item in this parent folder - then so be it.
However it is usually sensible to create a Download folder in this parent,
and an "Adminsoft" sub-folder hanging off this as a convenient place to store the "WebWkSt.exe" file that you will run when
installing new workstations.)
Refer to the general instructions
in the preceding sections for additional background understanding.
Shifting a single-user installation to a new computer
At a single-user site, you will probably upgrade your computer hardware from
time to time. This is similar to upgrading to a dedicated file
server (see above) in terms of copying the whole "C:\GECL" folder structure
over to the new computer. But you will also need to install the
Microsoft Visual FoxPro run-time library, and appropriate shortcuts on the new
computer, so that you can actually run the GECL software on it. (A files
server doesn't actually need to run the GECL software itself - it just serves
up its files to the workstations that are running the actual programs.)
The additional installation can be done simply by running the GECL Workstation
Install file (3.4MB) that you can download from our website.
Alternatively, you can download and run the "Main software in one file" or
"Core Components and Address Book". These will automatically
detect that you have existing data, and will not overwrite it with any empty
initial data files.
Problems with Windows NT, 2000, and XP
We haven't encountered any problems at all with installations in Windows 95, 98, Me,
and most XP
environments. Unfortunately however, we can't say the same about Windows NT,
2000, and some XP sites. (Can anyone?)
(Click here for assistance with Windows NT,
2000 and XP)
Adminsoft Directory Conventions
GECL software is very flexible with regard to the directory structure that it
can accommodate. Paths for respective data files can be specified during
installation, and altered subsequently in the
configuration settings (see Tools, Options, System Settings menu). Unless
you have over-riding reasons to do otherwise, we recommend that you accept the
default settings "as they come out of the box", as this will require
minimal subsequent "tweaking" on your part (to shortcuts, path
settings etc.).
By default the software and data will be installed together into a "c:\GECL" directory
(i.e. off the root directory in Drive C). When installing in a network environment,
you need to over-ride this of course, so that the "\GECL" directory is located on
the server. You should use mapped network drives rather than
"Universal Network Address" (i.e. you need to map a drive first using
My Computer or Explorer, and specify this directly. Do not use Network
Neighborhood - except to map a drive!!!). It is preferable to place the \GECL directory in the
root directory for the mapped network drive (e.g. "T:\GECL"),
but the install program and software will handle being pushed down one or more
levels of subdirectory (e.g. "F:\Apps\GECL").
When installing the software on a stand-alone computer, we still recommend
placing \GECL in the root directory, rather than under "Program
Files" because we philosophically don't particularly like the idea of having
significant volumes of important data tucked away in the "Programs"
directory. Also, with most of our users, the GECL software is the principle activity of
the computer/workstation concerned. Hanging it off the Root directory makes it
easier for users to find for backup purposes, and whenever they eventually need
to shift it over to a server (if upgrading to multi-user) or new replacement
stand-alone computer. (It also means that novices are less likely to be confused
by all the other sub-directories in the "Program files" directory, and
accidentally damage some of these if they are poking behind the scenes in GECL
programs and data for some reason.) You are fully entitled to disagree with our philosophy if you like, but at
least you can understand our rationale.
If you elect to go for a non-standard directory structure, you will need to
alter all "Demo" shortcuts appropriately, in order to get the Demo
running properly - start by editing the
directories specified in the shortcut, you may also need to change the path
settings (see Tools, Options, System Settings menu).
For user convenience (with updates in particular), we keep just one
master set of program files (GECL.exe and *.app) on the server, rather than installing them
on every workstation. It seems sensible to keep all GECL stuff together
(both programs & data) in the \GECL directory structure. However, it
is easy to separate the program and data files - e.g. if this is a more
convenient way to backup only the data files on a daily basis, say. (However,
this is usually not necessary. GECL's basic backup facility (GEBackup.bat)
only backs up data and configuration files. If you are using a backup tool
like MS Backup, you are able to simply exclude the program files from your daily
backups.) It is also possible to store copies of the program files on the
local hard drive for each workstation and run them from there, if you need to
reduce your network traffic slightly. Contact the GECL HelpDesk if you
want to split the location of your program and data files.
The Microsoft
Run-time engine (VFP*.* files) is installed according to Microsoft conventions,
in the "\Windows\System" directory on respective workstations.
The install process raises appropriate entries in the system Registry for each
workstation. This is why you need to run the "Workstation
Install", rather than merely setting up a shortcut that points to the
programs and data.
If you need further assistance or have feedback you would like to give us,
please contact our Help-Desk:
E-Mail now to: Support@Adminsoft.com
Phone: (09) 262 2020, Fax: 262 2021,
(From overseas +64 9 262 2020, etc.)
Click here for the main Help page
Migrating everything across to a new file server
It is usually extremely simple to shift the Adminsoft/GECL data and programs across from one server to another. Ideally you want to retain the same logical drive mappings on all the workstations. The simplest way to achieve this is by giving the new server the same "server name" as the old server that is being retired, and creating the same "shared resources" as were on the old server (that all the workstations will find using their existing settings - without any need to change these). You may have your own reasons for not doing this (e.g. if the old server will be retained in service and only some items are being transferred to the new server). If that is the case, you will obviously need to re-map the network drive letter used by the Adminsoft/GECL software, so that they point to the new shared resource. (You will need to do this on each workstation - or edit a common script (or DOS batch file) that they all run at boot-up.)
If you really do need to change the mapped network drive letter itself, you will need
to alter the appropriate short-cuts on each workstation ("Adminsoft / GECL
Professional Practice" which runs the software, and the "Extra GECL Backup"
if this is present on the respective workstation). You will also need
to edit the "GECL.ini" file in the "c:\Windows"
folder (on each workstation), so that it uses the new mapped drive letter.
Note that the shared resource (that the mapped network drive letter points to)
should be the parent folder in which the GECL / Adminsoft directory
structure is located - not the "\GECL" folder itself. (If the "\GECL"
folder is the only item in this parent folder - then so be it.
However it is usually sensible to create a Download folder in this parent,
and an "Adminsoft" sub-folder hanging off this as a convenient place to store the "WebWkSt.exe" file that you will run when
installing new workstations.)
Refer to the general instructions
in the preceding sections for additional background understanding.
Shifting a single-user installation to a new computer
At a single-user site, you will probably upgrade your computer hardware from
time to time. This is similar to upgrading to a dedicated file
server (see above) in terms of copying the whole "C:\GECL" folder structure
over to the new computer. But you will also need to install the
Microsoft Visual FoxPro run-time library, and appropriate shortcuts on the new
computer, so that you can actually run the GECL software on it. (A files
server doesn't actually need to run the GECL software itself - it just serves
up its files to the workstations that are running the actual programs.)
The additional installation can be done simply by running the GECL Workstation
Install file (3.4MB) that you can download from our website.
Alternatively, you can download and run the "Main software in one file" or
"Core Components and Address Book". These will automatically
detect that you have existing data, and will not overwrite it with any empty
initial data files.
Problems with Windows NT, 2000, and XP
We haven't encountered any problems at all with installations in Windows 95, 98, Me,
and most XP
environments. Unfortunately however, we can't say the same about Windows NT,
2000, and some XP sites. (Can anyone?)
(Click here for assistance with Windows NT,
2000 and XP)
Adminsoft Directory Conventions
GECL software is very flexible with regard to the directory structure that it
can accommodate. Paths for respective data files can be specified during
installation, and altered subsequently in the
configuration settings (see Tools, Options, System Settings menu). Unless
you have over-riding reasons to do otherwise, we recommend that you accept the
default settings "as they come out of the box", as this will require
minimal subsequent "tweaking" on your part (to shortcuts, path
settings etc.).
By default the software and data will be installed together into a "c:\GECL" directory
(i.e. off the root directory in Drive C). When installing in a network environment,
you need to over-ride this of course, so that the "\GECL" directory is located on
the server. You should use mapped network drives rather than
"Universal Network Address" (i.e. you need to map a drive first using
My Computer or Explorer, and specify this directly. Do not use Network
Neighborhood - except to map a drive!!!). It is preferable to place the \GECL directory in the
root directory for the mapped network drive (e.g. "T:\GECL"),
but the install program and software will handle being pushed down one or more
levels of subdirectory (e.g. "F:\Apps\GECL").
When installing the software on a stand-alone computer, we still recommend
placing \GECL in the root directory, rather than under "Program
Files" because we philosophically don't particularly like the idea of having
significant volumes of important data tucked away in the "Programs"
directory. Also, with most of our users, the GECL software is the principle activity of
the computer/workstation concerned. Hanging it off the Root directory makes it
easier for users to find for backup purposes, and whenever they eventually need
to shift it over to a server (if upgrading to multi-user) or new replacement
stand-alone computer. (It also means that novices are less likely to be confused
by all the other sub-directories in the "Program files" directory, and
accidentally damage some of these if they are poking behind the scenes in GECL
programs and data for some reason.) You are fully entitled to disagree with our philosophy if you like, but at
least you can understand our rationale.
If you elect to go for a non-standard directory structure, you will need to
alter all "Demo" shortcuts appropriately, in order to get the Demo
running properly - start by editing the
directories specified in the shortcut, you may also need to change the path
settings (see Tools, Options, System Settings menu).
For user convenience (with updates in particular), we keep just one
master set of program files (GECL.exe and *.app) on the server, rather than installing them
on every workstation. It seems sensible to keep all GECL stuff together
(both programs & data) in the \GECL directory structure. However, it
is easy to separate the program and data files - e.g. if this is a more
convenient way to backup only the data files on a daily basis, say. (However,
this is usually not necessary. GECL's basic backup facility (GEBackup.bat)
only backs up data and configuration files. If you are using a backup tool
like MS Backup, you are able to simply exclude the program files from your daily
backups.) It is also possible to store copies of the program files on the
local hard drive for each workstation and run them from there, if you need to
reduce your network traffic slightly. Contact the GECL HelpDesk if you
want to split the location of your program and data files.
The Microsoft
Run-time engine (VFP*.* files) is installed according to Microsoft conventions,
in the "\Windows\System" directory on respective workstations.
The install process raises appropriate entries in the system Registry for each
workstation. This is why you need to run the "Workstation
Install", rather than merely setting up a shortcut that points to the
programs and data.
If you need further assistance or have feedback you would like to give us,
please contact our Help-Desk:
E-Mail now to: Support@Adminsoft.com
Phone: (09) 262 2020, Fax: 262 2021,
(From overseas +64 9 262 2020, etc.)
Click here for the main Help page
Refer to the general instructions
in the preceding sections for additional background understanding.
Shifting a single-user installation to a new computer
At a single-user site, you will probably upgrade your computer hardware from
time to time. This is similar to upgrading to a dedicated file
server (see above) in terms of copying the whole "C:\GECL" folder structure
over to the new computer. But you will also need to install the
Microsoft Visual FoxPro run-time library, and appropriate shortcuts on the new
computer, so that you can actually run the GECL software on it. (A files
server doesn't actually need to run the GECL software itself - it just serves
up its files to the workstations that are running the actual programs.)
The additional installation can be done simply by running the GECL Workstation
Install file (3.4MB) that you can download from our website.
Alternatively, you can download and run the "Main software in one file" or
"Core Components and Address Book". These will automatically
detect that you have existing data, and will not overwrite it with any empty
initial data files.
Problems with Windows NT, 2000, and XP
We haven't encountered any problems at all with installations in Windows 95, 98, Me,
and most XP
environments. Unfortunately however, we can't say the same about Windows NT,
2000, and some XP sites. (Can anyone?)
(Click here for assistance with Windows NT,
2000 and XP)
Adminsoft Directory Conventions
GECL software is very flexible with regard to the directory structure that it
can accommodate. Paths for respective data files can be specified during
installation, and altered subsequently in the
configuration settings (see Tools, Options, System Settings menu). Unless
you have over-riding reasons to do otherwise, we recommend that you accept the
default settings "as they come out of the box", as this will require
minimal subsequent "tweaking" on your part (to shortcuts, path
settings etc.).
By default the software and data will be installed together into a "c:\GECL" directory
(i.e. off the root directory in Drive C). When installing in a network environment,
you need to over-ride this of course, so that the "\GECL" directory is located on
the server. You should use mapped network drives rather than
"Universal Network Address" (i.e. you need to map a drive first using
My Computer or Explorer, and specify this directly. Do not use Network
Neighborhood - except to map a drive!!!). It is preferable to place the \GECL directory in the
root directory for the mapped network drive (e.g. "T:\GECL"),
but the install program and software will handle being pushed down one or more
levels of subdirectory (e.g. "F:\Apps\GECL").
When installing the software on a stand-alone computer, we still recommend
placing \GECL in the root directory, rather than under "Program
Files" because we philosophically don't particularly like the idea of having
significant volumes of important data tucked away in the "Programs"
directory. Also, with most of our users, the GECL software is the principle activity of
the computer/workstation concerned. Hanging it off the Root directory makes it
easier for users to find for backup purposes, and whenever they eventually need
to shift it over to a server (if upgrading to multi-user) or new replacement
stand-alone computer. (It also means that novices are less likely to be confused
by all the other sub-directories in the "Program files" directory, and
accidentally damage some of these if they are poking behind the scenes in GECL
programs and data for some reason.) You are fully entitled to disagree with our philosophy if you like, but at
least you can understand our rationale.
If you elect to go for a non-standard directory structure, you will need to
alter all "Demo" shortcuts appropriately, in order to get the Demo
running properly - start by editing the
directories specified in the shortcut, you may also need to change the path
settings (see Tools, Options, System Settings menu).
For user convenience (with updates in particular), we keep just one
master set of program files (GECL.exe and *.app) on the server, rather than installing them
on every workstation. It seems sensible to keep all GECL stuff together
(both programs & data) in the \GECL directory structure. However, it
is easy to separate the program and data files - e.g. if this is a more
convenient way to backup only the data files on a daily basis, say. (However,
this is usually not necessary. GECL's basic backup facility (GEBackup.bat)
only backs up data and configuration files. If you are using a backup tool
like MS Backup, you are able to simply exclude the program files from your daily
backups.) It is also possible to store copies of the program files on the
local hard drive for each workstation and run them from there, if you need to
reduce your network traffic slightly. Contact the GECL HelpDesk if you
want to split the location of your program and data files.
The Microsoft
Run-time engine (VFP*.* files) is installed according to Microsoft conventions,
in the "\Windows\System" directory on respective workstations.
The install process raises appropriate entries in the system Registry for each
workstation. This is why you need to run the "Workstation
Install", rather than merely setting up a shortcut that points to the
programs and data.
If you need further assistance or have feedback you would like to give us,
please contact our Help-Desk:
E-Mail now to: Support@Adminsoft.com
Phone: (09) 262 2020, Fax: 262 2021,
(From overseas +64 9 262 2020, etc.)
Click here for the main Help page
Problems with Windows NT, 2000, and XP
We haven't encountered any problems at all with installations in Windows 95, 98, Me,
and most XP
environments. Unfortunately however, we can't say the same about Windows NT,
2000, and some XP sites. (Can anyone?)
(Click here for assistance with Windows NT,
2000 and XP)
Adminsoft Directory Conventions
GECL software is very flexible with regard to the directory structure that it
can accommodate. Paths for respective data files can be specified during
installation, and altered subsequently in the
configuration settings (see Tools, Options, System Settings menu). Unless
you have over-riding reasons to do otherwise, we recommend that you accept the
default settings "as they come out of the box", as this will require
minimal subsequent "tweaking" on your part (to shortcuts, path
settings etc.).
By default the software and data will be installed together into a "c:\GECL" directory
(i.e. off the root directory in Drive C). When installing in a network environment,
you need to over-ride this of course, so that the "\GECL" directory is located on
the server. You should use mapped network drives rather than
"Universal Network Address" (i.e. you need to map a drive first using
My Computer or Explorer, and specify this directly. Do not use Network
Neighborhood - except to map a drive!!!). It is preferable to place the \GECL directory in the
root directory for the mapped network drive (e.g. "T:\GECL"),
but the install program and software will handle being pushed down one or more
levels of subdirectory (e.g. "F:\Apps\GECL").
When installing the software on a stand-alone computer, we still recommend
placing \GECL in the root directory, rather than under "Program
Files" because we philosophically don't particularly like the idea of having
significant volumes of important data tucked away in the "Programs"
directory. Also, with most of our users, the GECL software is the principle activity of
the computer/workstation concerned. Hanging it off the Root directory makes it
easier for users to find for backup purposes, and whenever they eventually need
to shift it over to a server (if upgrading to multi-user) or new replacement
stand-alone computer. (It also means that novices are less likely to be confused
by all the other sub-directories in the "Program files" directory, and
accidentally damage some of these if they are poking behind the scenes in GECL
programs and data for some reason.) You are fully entitled to disagree with our philosophy if you like, but at
least you can understand our rationale.
If you elect to go for a non-standard directory structure, you will need to
alter all "Demo" shortcuts appropriately, in order to get the Demo
running properly - start by editing the
directories specified in the shortcut, you may also need to change the path
settings (see Tools, Options, System Settings menu).
For user convenience (with updates in particular), we keep just one
master set of program files (GECL.exe and *.app) on the server, rather than installing them
on every workstation. It seems sensible to keep all GECL stuff together
(both programs & data) in the \GECL directory structure. However, it
is easy to separate the program and data files - e.g. if this is a more
convenient way to backup only the data files on a daily basis, say. (However,
this is usually not necessary. GECL's basic backup facility (GEBackup.bat)
only backs up data and configuration files. If you are using a backup tool
like MS Backup, you are able to simply exclude the program files from your daily
backups.) It is also possible to store copies of the program files on the
local hard drive for each workstation and run them from there, if you need to
reduce your network traffic slightly. Contact the GECL HelpDesk if you
want to split the location of your program and data files.
The Microsoft
Run-time engine (VFP*.* files) is installed according to Microsoft conventions,
in the "\Windows\System" directory on respective workstations.
The install process raises appropriate entries in the system Registry for each
workstation. This is why you need to run the "Workstation
Install", rather than merely setting up a shortcut that points to the
programs and data.
If you need further assistance or have feedback you would like to give us,
please contact our Help-Desk:
E-Mail now to: Support@Adminsoft.com
Phone: (09) 262 2020, Fax: 262 2021,
(From overseas +64 9 262 2020, etc.)
Click here for the main Help page
If you need further assistance or have feedback you would like to give us, please contact our Help-Desk:
E-Mail now to: Support@Adminsoft.com
Phone: (09) 262 2020, Fax: 262 2021,
(From overseas +64 9 262 2020, etc.)
Click here for the main Help page