----- start of file -----



DualSave v4.208 (2004-03-16)

Copyright 2004, Benjamin Despres



Purpose:

    A "moving windows" style screensaver that runs on a single
    monitor of a multi-headed system. I wrote this because I
    use a dual-headed system, and find that I rarely need to
    interact with my second screen, although I need to see its
    contents. This will keep all windows on the second screen
    visible, while preventing a static image from unevenly ageing
    (aka "burn-in", aka "phosphor etching") a given monitor.



Usage:

    Simply place the executable (or a shortcut thereto) on the screen
    where you want DualSave to run.

    Double-click the shortcut to run DualSave.  The screen will blink
    once, and a new icon will appear in your system tray.

    Moving the mouse off of the screen with DualSave running will
    activate it (after a five second delay).  Moving the mouse onto
    that screen will immediately make DualSave restore the screen
    (but not stop running).

    To stop DualSave from running, just left-click on its tray icon.



Notes:

    Although extensively tested, I cannot guarantee the correct
    operation or safety of using DualSave.  It does not ever touch
    the disk, or close any windows (other than itself), so in the
    worst case scenario, you may need to manually reposition your
    open windows after killing DualSave (Old bug, I believe I fixed
    it, though if you force-kill DualSave via Task Manager rather
    than by clicking its tray icon, this can still occur).

    In some cases, if you move the mouse away from the screen too
    quickly, DualSave will fail to correctly capture the currently
    visible windows (it technically uses the location of the mouse,
    not the location of its shortcut, to pick a screen on which to
    run).  This can cause either a black screen, DualSave to run on
    the wrong screen, or the "moving windows" to flicker like an
    epilepsy-inducing Pokemon episode.  To correct this, just click
    its tray icon to kill it, then restart it, letting the mouse
    linger for a few seconds on the correct screen.

    To uninstall DualSave, just delete it.  It never touches the
    disk, including the registry, so you will only have whatever files
    you manually create (ie, itself, and possible a shortcut to it).

    Some programs seem to handle window repositioning oddly, which
    will result in some flicker.  Some versions of Winamp, for
    example, will cause the playlist and the equalizer to keep
    swapping the foreground.  This does not result from the order
    in which DualSave updates the screen (ie, not a Z-Buffer issue),
    but from how the applications themselves handle a redraw.  With
    Winamp, you can correct this simply by hiding the equalizer.
    With other programs (I have not yet identified any others that
    show this behavior), you may need to either deal with this, or
    choose not to use DualSave.

    Dualsave uses roughly 10% CPU on a 1GHz P3 machine while handling
    five active windows.  Not a lot, but for running CPU intensive
    tasks, you may wish to temporarily disable DualSave.  This also
    depends on the complexity of the windows involved, and poorly
    designed programs with complex window contents may increase the
    CPU usage dramatically.

    DualSave can run on more than one monitor at a time (including
    the primary display, the one with the task bar).  Simply copy
    DualSave (or a shortcut thereto) to each screen you want it
    to use, and start them one at a time.  You can thus have any
    combination of available monitors running or not running
    DualSave simultaneously.

    I have not tested DualSave on Windows XP Service Pack 2, which
    implements protected memory.  Although DualSave works entirely
    by standard Win32 GUI functions, memory protection may cause
    this to not work.

    Dual-headed configurations using older NVidia cards in its
    TwinView/NView clone/span mode may cause DualSave to behave
    incorrectly, as they do not have distinct screens, but only
    a single large screen.  For "clone" mode, I do not believe any
    means of avoiding this exists.  For "span" mode, the newest
    drivers include an option to force the second screen to appear
    as a distinct display device to Windows.  Using that will
    allow DualSave to work correctly.     



License/Disclaimer:

    You may use DualSave for free (as in beer), but I have NOT
    released it into the Public Domain.  Although if it becomes
    popular, I may tidy up the source and release it under the
    GPL, I currently consider it copyrighted by me, and reserve
    all rights to it.  You may distribute DualSave as long as you
    do not charge for it or for the distribution media.

    This program exists purely for self gratification.  By using
    DualSave you agree to assume all responsibility for its use.
    I provide no guaranteed of suitable for any purposes whatsoever,
    including but not limited to any and all primary functionality
    described in this documentation.  Furthermore, by using this
    program you agree to pay for any and all legal fees incurred
    by myself as a result, directly or indirectly, of your actions.



----- end of file -----
