large log file

[maklouf]

Harold,

Ok I have tested it and it worked, the log file is not growing anymore, 
and I got this message at the end.

winShadowUpdateDDNL - IDirectDrawSurface4_Blt failure message maximum 
(10) reached.  No more failure messages will be printed.
Thank you.

Maklouf


Harold L Hunt II wrote:
> Maklouf,
> 
> The XFree86-xserv-4.3.0-6 release was made just for you.  It turns off 
> your error message after 10 instances of it.  Please download it and try 
> it with your screen saver on... I would like to know that the message 
> disabling works.  I don't have a test environment, so your testing is 
> all I can go on.
> 
> Thanks for testing,
> 
> Harold
> 
> maklouf wrote:
> 
>> Indeed my screen saver was on, now it's off hopefully this will fix 
>> the problem.
>> Thanks to all of you for your help.
>> Maklouf
>>
>> Harold L Hunt II wrote:
>>
>>> Cary,
>>>
>>> Hmm... sounds like I should add a max message count to this error 
>>> message.  It could, say, print the message 10 times then print 
>>> "Message reached max, not it printing anymore".
>>>
>>> Harold
>>>
>>> Cary Jamison wrote:
>>>
>>>> "maklouf" <maklouf@hotmail.com> wrote in message
>>>> news:<bj30vr$kq4$1@sea.gmane.org>...
>>>>
>>>>> Hi all,
>>>>> I installed xserv ver 4.3.0-5 on a windows 2000 sp4 system with
>>>>
>>>>
>>>>
>>>>
>>>> directx
>>>>
>>>>> 9 and i ahve a large log file (5 gigs) with this line
>>>>> winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 88760096
>>>>>
>>>>> does any one has any idea what this could be?
>>>>>
>>>>> Thanks
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Turn off your X screen saver.  You don't need an X screen saver going
>>>> when your Windows screen saver is doing its job.
>>>>
>>>> I've found that when the Windows screen saver is on, or I lock my 
>>>> screen
>>>> using win-L, and I have an X application running that is drawing to the
>>>> screen that my log will get filled with these messages.  The X
>>>> screensaver is typically the culprit as it is very busy drawing stuff.
>>>>
>>>> I have reported this problem here before, but it still persists (and I
>>>> haven't done anything to fix it myself, shame on me :-)
>>>>
>>>> Cary
>>>
>>>
>>>
>>>
>>>
>>
>>
> 
>