Subj : Re: Remmina RDP To : Barry Martin From : Ky Moffet Date : Thu May 23 2024 17:10:00 BARRY MARTIN wrote: > Hi Ky! > > KM> Boo! > > Boo who?!! No crying until you spill the milk! > ..Thought I figured soming out but now makes less sense. If a 'boo' is > a boyfriend/girfriend/lover ("he/she is my boo") and 'boo' is said by a > ghost or to scare someone, why is it good to be a 'boo'? Um. I have no good answer to this. Maybe I'll think up a silly one instead. > That makes sense. I'm thinking it could also mean a faulty bit which is > causing a bad instruction and so garbage output. That one based on > years ago when I built a Heathkit TV and the overlay display (time, > channel, etc.) was sometimes scrambled. A little analysis and only > certain letters: let's say "C" so "Channel" might display as "Thannel" > and "MAY" as "MAR". That's... interesting!! > Figured out via ASCII Chart the problem was a certain bit level was > being set wrong: let's say 3rd LSB (out of the 8). Figured out where > the problem was on the schematic (between encoder and decoder) but which > was LSB and MSB? (I'm not that good and pre-web access to get the chip > specs.) So ended up making four reair solders: two on each end of the > trace and two since I wasn't sure which was LSB and MSB. Ta-dah! No > more misspellings! Oh! Clever solution. But when you've got a schematic to work from.... > KM> Gravity always wins! > > At least I don't have to go looking for dropped parts on the ceiling too! This is a very good point. Well, unless you're on the space station. > > KM> This isn't absolute but it's a pretty good guideline. > > Good starting points which usually work. > KM> Usually good enough, if it's hardware. If it's software, can be > KM> any damn thing. > > Though even software follows rules. I remember one script I was It's supposed to. When there are not rules it makes up its own. Someone discovered that the value of Pi used in DOOM was wrong (but it was a lookup table, so the values were fixed). So he tried lots of other values. Correct Pi was close enough. Others went from strange to nonfunctional. https://media.ccc.de/v/mch2022-236-non-euclidean-doom-what-happens-to-a-game-when-pi-is-not-3-14159- > creating, and since just self-trained a lot of pluck some code from > here, some other code from there.... Something wasn't working so put in > an echo statement to display the output at a certain level of the > script. That helped figure out the problem, so now getting the correct > result per the echo statement but the next step was always displaying > "0". Used to semi-work before! Ends up the following statement was > taking the output of the echo statement: echo finished its job properly > so outputted a '0' for 'good out'. Comment the test echo and now > worked! Ah yes, the old step-through method... usually a Good Idea when you can. > KM> Modern OSs now understand this stuff, and have done so pretty > KM> reliably for about 25 years. Part of the longstanding problem > KM> with linux was that until about 10 years ago, or a bit longer for > KM> some of the more advanced distros, you had to know your hardware > KM> parameters and sometimes input them manually. It seems to have > KM> finally got this right. When you're doing it for free, as has > KM> mostly been the case, hardware programming is not near as sexy as > KM> cute apps and games, so it gets way less attention. > > Yes, I vaguely recall having to initially configure the video settings. I remember it vividly, having installed RedHat 6 which at the time you had to set up X entirely yourself. Make a good guess and get a screen. Make a wrong guess and start over. > Now pretty much does it itself, though that occassionally creates a > problem when using a 4K TV and so viewing from ten feet away! > ..Even the resolution selectrion GUI is teeny-tiny when standing right > in front of the TV! LOL. Some of my failed Virtual Machines have been the size of a postage stamp.... Did get Win2K VM installed on Roadkill tho, so now I have a restful grey workspace when I need it. Win11 lacks this. > > > 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. > KM> Fedora used to do that, tho the problem seems to have gone away > KM> as of v39. Except it would decide to not speak to the outside > KM> world after about a week, unless regularly rebooted. Meanwhile > KM> PCLOS had been running for several months, and WinXP for about a > KM> year and a half, with no such issues. > > Almost seems like 'something runs out of room'. I have some computers Yeah, that is usually why a system goes goofy over time -- some cache or data stack gets full or corrupted or wraps around, but the effect is the same. > around here rebooting themselves on a weekly basis because of that kind > of issue. Not necessarily an OS issue -- may have been years ago, but > now more like a problem with some utility causing the lockup/overrun. That was often the issue with Windows. Not a durn thing wrong with Windows; it was the crappy "fix something" utility that broke it. > (Thinking of a couple years back when had three RPi4's running a previous > version of Motion and other RPi4 running same OS but Motion not > installed. The Motion ones needed frequent rebooting, the others not > running Motion would run for months. [Important note: Motion has been > corrected since then!]) That's good! Cuz frequent rebooting... not my idea of Quality. Been ruined by software that runs for months on end. RoughDraft and WinAmp have been up since... probably last October, when the system was last rebooted. SeaMonkey needs to be restarted every few weeks, tho, or it gets sluggish. LibreOffice has been up since March, that being when I started work on the current going-very-slow paid edit (it's not on a deadline, and it makes my brain hurt). > KM> As we skeap ?? speak Fedora is sitting there upgrading to v40. > KM> It's been at it since 11pm last night, tho a lot of the time was > KM> 5GB of downloads on a 3Mbps connection. Had to do a full update > KM> first, then run the upgrade (fortunately the commands are still > KM> handy in the console buffer... it started life as v32). It is now > KM> running the final step and will be done in about an hour. You can > KM> see why I find rolling a lot less trouble. > > Better hope that connection maintains!! ...The long time to do an Fortunately it caches downloads so you don't have to start over. That's one thing Windows Update gets wrong. Anything interrupted starts over. > update/upgrade was one reason I only did one machine at a time: besides > multiple connections slowing down the limited bandwidth if something > went wrong like an extended power failure I have only one computer to > recover. Yeah, good policy. > KM> And I get my first look at KDE Plasma v6. Given the newness > KM> thereof (just released) for the next while there will be a lot of > KM> updates, possibly to the point of a Whole New Monkey. But they > KM> are usually pretty good about getting the major bugs out (not > KM> least because unlike say Xfce, which is one guy and change, it's > KM> a team of a hundred-plus folks.) > > More people seems to be better as a couple might be experts in video, > others, audio, etc. Plus if only if one or two doing the whole job and > something happens..... KDE has about a hundred people involved. > KM> http://www.wholenewmonkey.com/ > > Huh: under maintainence -- guess the upgrade and update data is stil > lrolling in! Better not be under maintenance, it hasn't been changed in years! (Yes, I got this domain solely for this joke. Cuz it's always funny.) > .. A group of flamingos is called a stand. I thought it was called a lawn ornament! þ RNET 2.10U: ILink: Techware BBS þ Hollywood, Ca þ www.techware2k.com --- QScan/PCB v1.20a / 01-0462 * Origin: ILink: CFBBS | cfbbs.no-ip.com | 856-933-7096 (454:1/1) .