Menu

#92 Failed to delete old BG after starting a screensaver

open
nobody
5
2003-07-01
2003-07-01
Anonymous
No

I get the following error when the screen saver kicks in:

Failed to delete old BG after starting a screensaver

I am running Win2k (home machine) and have a dual
head Matrix card with the monitors running at different
resolutions. The screen saver worked fine in the current
config just fine for a while, and had just recently started
displaying this message. I run Zmartix on my work
machine also, another dual head but the monitors are
the same resolution there, and it works just fine. The
bakground feature works just fine on my home machine,
only have a problem with the screen saver.

I would happily try and delete the BG bitmap for it, but I
can't figure out where te bitmap is that it is trying to
delete.

Rebooting doesn't help, haven't tried a reinstall yet.

Love the program though... Looks real cool with the dual
monitors, and my manager is looking to download it for
his system also.

Adam Patt
adampatt@yahoo.com

Discussion

  • Nobody/Anonymous

    Logged In: NO

    I have the same issues on XP Spk2 AMD Opteron.

    If I try the screen saver I get "Failed to delete old BG bitmap
    after starting a screensave". If I try a refresh I get "Failed to
    delete new BG bitmap during a refresh".

    This is the first one that's actually worked across my tri-
    monitor setup (well the background anyway). Every Matrix
    screensaver I've tried fails to work for one reason or another
    on the 3-monitor setup I have. So I'm happy to see the
    background work......but if I try to do pretty much anything in
    the menu I get these "Failed to delete" error pop ups. :-(

     
  • Nobody/Anonymous

    Logged In: NO

    I have an idea this is the same thing I've run into with a few
    3rd party screen savers after a little testing. I have an AMD
    that supports XP's DEP (Data Execution Prevention)...with it
    fully enabled it prevented some screen savers from running or
    even locked my system up. Apparently they are accessing
    memory MS thinks they should not.

    I turned off DEP and the error messages went
    away...perhaps it can access what it needs to delete without
    DEP enabled.

     

Log in to post a comment.

MongoDB Logo MongoDB