** Reply to message from WD Loughman <wdloughman@xxxxxxxxxxxxx> on Mon, 01 May
2006 02:11:30 -0700
>
>I've been running the same, since 4-16-06. I did have problems and
>wrote you with screenshots attached. I re-sent the attachments. Never
>received acknowledgement, etc.
>
>Did you receive the following?
>____________________________________________________
>John -
>
>The attachment contains three screen-shots:
>
>JBSWU_monA.jpg 40777 4-15-06 0:21 ImgWdl 4OS2 problem
>JBSWU_monB.jpg 48281 4-15-06 0:21 ImgWdl 4OS2 problem
>JBSWU_monC.jpg 44849 4-16-06 2:48 ImgWdl CMD.EXE is okay
Yes, I did. But I'm sorry to admit that it got overlooked until I saw this
message.
The new beta I uploaded today should fix "A" & "B". The problem was that 4OS2
apparently displays a message when a file is deleted. CMD.EXE does not.
>IMPORTANTLY, in "C" the blue demonstrates screen areas *not blanked* by
>your WU-monitor -- causing the problem shown in "B".
>
>I had a similar corrupt display (under 4OS2) with an earlier version of
>your WU-monitor. Wrote you about it then; and you fixed it.
>
>Clearly the problem is back: incorrect blanking in the final display.
"C" occurs when the background color is something other than the default
(black). Fixing "C" may take a while. In fact I may not be able to fix it and
therefore I would have to abandon the color for the messages displayed
occasionally at the bottom of the screen.
As a temporary fix (which disables the color), you can do the following:
Lines 834-835 should read:
cfg.ansi = (CheckAnsi() == 1)
if cfg.ansi == 1 then
Insert a line between them so that they are:
cfg.ansi = (CheckAnsi() == 1)
cfg.ansi = 0
if cfg.ansi == 1 then
Let me know how this works for you.
--
John Small
|
