The S'87 application is installed on the server and all the databases are
located on the server.  The users run the application from the server
directory.  The application is comprised of several EXEs that are run
from one EXE file using a function called Overlay.  Its also possible
that the Overlay calls are nested, in as some of the child processes may
call Overlay to launch another child.  I'm not the developer of this
application; this is the explanation I got from the developers of the
application.

What happens is as the day goes on the application gets slower and slower
at loading and running the EXEs.  To the point where it can take as long
as 3 min to load an EXE.   In some instances rebooting the server and all
the workstations corrects the problem temporarily; but not always. The
application is running at several other locations, using the same network
configuration without this problem.

Does anyone have an idea of what could be causing this to happen?  Our
hardware guy thinks it may be a problem in the cabling; but I would
suspect that it would happen all the time if this were so.

Any help or suggestions are appreciated.

Thanks
--
Jim Fitzgerald
email replies: chemmast at penn dot com

I never run my exe's from the server.

I have been  told that they need to be marked as read-only if you run them
on the server.

Overlay is a lib that can swap out a program to disk and execute another
program.  Your problem could be creating the temp files.  No problem here if
the program is on the C:

Mike

GOOD LOCK
FRANCISCO

   -**** Posted from remarQ, Discussions Start Here(tm) ****-
http://www.remarq.com/ - Host to the the World's Discussions & Usenet

I'll look into the readonly option.

Thanks;
--
Jim Fitzgerald - ENVIROGENICS? Software Company
www.envirogenics.com
email replies: chemmast at penn dot com

Support the anti-Spam amendment - Join at http://www.cauce.org/

I wish there was a 'Run Once at a Time' property for Windows.

Mike M

This cuts down on network traffic and any multiple copies trying to use the
same file.
I don't know if the other linkers will let you do this.  If this works
please email me.  

--
Scott Burke

Mike

There is a replication engine on The Oasis, under the name
DIRSYNC.ZIP. configure this and put it in the login script. It will
make a local directory that is identical to the master directory.

Put it in the login script, and put a button to it on the desktop.

Here is the help screen:

  DIRSYNC 1.5 will synchronize the files in two directories.

  Any file in the source directory that is not in the destination
  directory will be copied there, and any file in the destination
  directory that is not in the source directory can be removed.

  Changed files will be replaced with originals based on time and date
  stamps.

  USAGE:"
    DIRSYNC <SourceDir> <DestDir> [/NOVERBOSE] [/NOWARNING] ...
                              ... [/NODELETE]  [/NCOPY]"

    Where:"
       <SourceDir> is the Master File Directory
       <DestDir> will contain whatever is in <SourceDir>

       [/NOVERBOSE] will suppress most of the screen output

       [/NOWARNING] will delete extra files in <DestDir> without
                    warning
       [/NODELETE] will suppress automatic deletion

       [/NCOPY] will use NCOPY.EXE instead of DOS copy

  EXAMPLE:
     DIRSYNC X:\NETWORK\EXEPOOL\ C:\LOCAL\EXEPOOL\ /NOWARNING

The nice thing about this is that:

1. The executable maintenance happens on a single master directory on
the network.

2. The executables always run from the local drive

3. Every login updates the local pool with minimum impact. If nothing
has changed, no files are moved. The icon on the desktop performs an
update without needing to log out/in.

4. If your executable crashes and leaves those ugly file fragments
like AHDFEADO, these swap turds will be created on the same drive the
executable ran from, by default. The next DIRSYNC cleans them out.

5. The software loads and runs faster.

6. Network traffic is reduced.

7. No temp files will be built on the network drive.

8. You can put a new executable in place in the master directory at
any time, even while the users are still running the software. When
you do update the exe, you notify the users to exit the software and
hit the update button.

It's the only way to go.

--

        Oasis WWW   http://www.*-*-*.com/ ~philb/
         FTP Site  ftp://ftp.iag.net/pub/clipper
      Clipper FAQ   http://www.*-*-*.com/ ~philb/clipper.html

    "If you love wealth more than liberty, the tranquillity of
     servitude better than the animating contest of freedom,
     depart from us in peace. We ask not your counsel or your
     arms. Crouch down and{*filter*} the hand that feeds you. May
     your chains rest lightly upon you and may posterity
     forget that you were our countrymen." - Samuel Adams