Subj : Remmina RDP
To   : Ky Moffet
From : Barry Martin
Date : Fri May 17 2024 07:22:00


Hi Ky!

 >   > I use Devuan on two machines.  One is a PC that I do use the GUI on. 
ha
 >   > machine has always had a quirk where, every so often, the screen will
us
 >   > disappear and the machine requires a reboot.  Do you remember ever
rying
 >   > to load a GIF or other graphics on an XT and having it not work?  That
s
 >   > what the screen will suddenly look like... a big mess.  ;)
 >   > It does that no matter what distro is running on it so I figure it is
 >   > something wrong with the box itself.
 >   KM> Bad video RAM, probably at the tail end of the addressing space
 >   KM> and marginal rather than failed, so it only occasionally messes
 >   KM> up.
 > Well I'm going to disagree with the bad video RAM statement thought I'll
 > probably be learning a lot by the 'rebuttal'!
 KM> It's the description of the fault that tells me it's most likely
 KM> bad video RAM.
 KM> That's quite distinctive -- you get a solid mass of random ASCII
 KM> characters. We used to see that a lot in the Olden Tymes.
 KM> When the card is loose, or the GPU is failing, you get random
 KM> lines.
 
Ahhh! I don't recall the random characters part.  The make-and-break of 
the data stream would cause the card to try to make sense of it and output
what it thought it was told.


 KM> When the cable is loose, you'll lose some color (and have frex a
 KM> pink screen).
 
Right.


 KM> This isn't absolute but it's a pretty good guideline.

Good starting points which usually work.


 > Doesn't eliminate video addressing statement as a possibility.  I don't
 > recall how to look up; guessing "all f's" in the range end-point would
 > mean it's at the far end.

 KM> Addressing shouldn't cause this kind of visual screw up; it would
 KM> cause a lockup or no video at all due to the conflict. And if
 KM> you're not a modern gamer, or rendering video, you're not gonna
 KM> fill up that video RAM anyway.

Probably so: this is another of my Black Box areas and so stuff in,
something happens, stuff out.  On the -- guess could call it 
'clarification' area know there are maximum resolutions so I would guess
there is some sort of upper limit.  Doesn't seem to be pertinent as the 
video card and monitor seem to always adjust to each other.

So if I remember correctly Mike's problem was after a while his monitor 
would go black and need a reboot to get things going again.  I don't 
recall if he stated a time but seemed he implied weeks or months.  I 
want to get in on the thread because I have a similar problem with one 
essentially headless system which tends to not talk to a monitor after 
some time -- I'm thinking around 1.5 to 2 months.


                     ¯                                 ®
                      ¯  BarryMartin3@MyMetronet.NET  ®
                     ¯                                 ®


.... I have a 10 foot snake.
You can't fool me, snakes don't have feet.
--- MultiMail/Win32 v0.47
 þ wcECHO 4.2 ÷ ILink: The Safe BBS þ Bettendorf, IA

--- QScan/PCB v1.20a / 01-0462
 * Origin: ILink: CFBBS | cfbbs.no-ip.com | 856-933-7096 (454:1/1)

.