Hi Ky!
> KM> Boo!
> Boo who?!!
KM> No crying until you spill the milk!
OK, I spilt it into the measuring cup, now what?
> ..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'?
KM> Um. I have no good answer to this. Maybe I'll think up a silly
KM> one instead.
I'm not sure I can tell the difference. <rs!>
> 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".
KM> That's... interesting!!
It became obvious what and almost where the problem was once made a
binary chart:
01000001 A
01000010 B
01000011 C
01000100 D
01000101 E
01000110 F
^
If the 3rd LSB (marked) opens/go low then an "E" displays as an "A" ==>
101 becomes 001.
> 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!
KM> Oh! Clever solution. But when you've got a schematic to work
KM> from....
Came with the kit manuals from Heathit. And not that I can read the
whole thing and understand but knew enough from previous electronics fiddlings.
Actually still have the schematic on the cork board (which I
use as a door to cover some shelves with parts boxes) just because it
looks neat.
> KM> Gravity always wins!
> At least I don't have to go looking for dropped parts on the ceiling too!
KM> This is a very good point.
KM> Well, unless you're on the space station.
The good news is I think they have minimal gravity so anything dropped
just kind of floats so unless accidentally swatted whould be easy to
find. Bad news is if they don't find it could be catastrophic whereas I
just grumble and get a new one.
> > 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
KM> It's supposed to. When there are not rules it makes up its own.
Thought probably based on established rules, though which ones can be
'fun' to figure out.
KM> Someone discovered that the value of Pi used in DOOM was wrong
KM> (but it was a lookup table, so the values were fixed). So he
KM> tried lots of other values. Correct Pi was close enough. Others
KM> went from strange to nonfunctional.
I would suppose there would be some out-of-range occurrences.
KM> https://media.ccc.de/v/mch2022-236-non-euclidean-doom-what-happens
KM> -to-a-game-wh
KM> n-pi-is-not-3-14159-
I only watched part of it (never played Doom); did see the demo of the
pi = 3 and the walls didn't act correctly: expanded then contracted.
Also the e-mail prior to that section where some unhappy user suggested
the person who mis-entered the 10th digit of pi in table be fired. heck
I'm lucky to remember the 3.14 part! ...Don't really need pi for
anything -- let's see, last time I had to figure the circumference of a
circle was in nineteen........ There was also a chart pop-up: I thought
the problem was simply typing a 7 for the 4 (miskey on the NumPad)
rather than memory errror.
> 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!
KM> Ah yes, the old step-through method... usually a Good Idea when
KM> you can.
Probably not the best/most efficient but as I barely know what I'm doing
it worked enough to get me to the problem. And also learned once find
the problem hide the thing that found the problem!
> 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.
KM> I remember it vividly, having installed RedHat 6 which at the
KM> time you had to set up X entirely yourself. Make a good guess and
KM> get a screen. Make a wrong guess and start over.
So back to my "always have a spare system" so have something that works,
and can research why the new system isn't working as expected.
> Now pretty much does it itself, though that occassionally creates a
> problem when using a 4K TV and so viewing from ten feet away! <g>
> ..Even the resolution selectrion GUI is teeny-tiny when standing right
> in front of the TV! <g>
KM> LOL. Some of my failed Virtual Machines have been the size of a
KM> postage stamp....
So far not quite that small here!
KM> Did get Win2K VM installed on Roadkill tho, so now I have a
KM> restful grey workspace when I need it. Win11 lacks this.
Serenity NOW!!!! <g>
> > 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
KM> Yeah, that is usually why a system goes goofy over time -- some
KM> cache or data stack gets full or corrupted or wraps around, but
KM> the effect is the same.
I have some of the computers here configured to reboot weekly to avoid problems.
...A couple of versions of Motion ago on Raspberry Pi's
Bullseye was really 'interesting': definitely had to be rebooted weekly
if not sooner: had Watchdog running but also another script of my own
creation to check for keywords in various error files and either restart
Motion or in a couple of cases do an actual reboot. (The current or
maybe one-off on Bookworm does not have these problems.)
> 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.
KM> That was often the issue with Windows. Not a durn thing wrong
KM> with Windows; it was the crappy "fix something" utility that
KM> broke it.
So the thing to fix the break broke the thing when it wasn't broken!
> (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!])
KM> That's good! Cuz frequent rebooting... not my idea of Quality.
KM> Been ruined by software that runs for months on end. RoughDraft
KM> and WinAmp have been up since... probably last October, when the
KM> system was last rebooted. SeaMonkey needs to be restarted every
KM> few weeks, tho, or it gets sluggish.
Right: improper shutdown is a last resort. With the old Motion/Bullseye
issue above I had tried various repairs/updates, etc., and just didn't
fix. Definitely something with that combination as other RPi/Bullseye
systems would run for weeks.
KM> LibreOffice has been up since March, that being when I started
KM> work on the current going-very-slow paid edit (it's not on a
KM> deadline, and it makes my brain hurt).
Mine hasn't been up nearly that long due to a 'restart needed to finish
updates' on May 11. Right now have seven LibreOffice documents open as working
on a few projects at once and the others are for semi-active
stuff I want to be reminded of. ...In the mean time have revised other
dox (open, update, save and close) and created new.
...Read somewhere LibreOffice isn't designed to be kept up that long --
overnight starts causing a few quirks. I'm thinking might be more of
the change in the OS's date and 'borrowing' of RAM for maintenance
projects so LibreOffice can't find where it left some of its stuff.
Here I have quite a bit of RAM so might be why it takes a while to see
some of those problems.
> 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
KM> Fortunately it caches downloads so you don't have to start over.
Good!
KM> That's one thing Windows Update gets wrong. Anything interrupted
KM> starts over.
Boo!
> 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.
KM> Yeah, good policy.
Over the decades I've had all sorts of quirkies occur so just easier
doing one-at-a-time. Not to say I haven't multi-tasked -- all depends.
> 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.....
KM> KDE has about a hundred people involved.
Seems like a good number: leader, group leaders, workers who can
collaborate (hopefully!) and work off each others' knowledge and
experiences.
> KM> http://www.wholenewmonkey.com/
> Huh: under maintainence -- guess the upgrade and update data is stil lrolling
> in!
KM> Better not be under maintenance, it hasn't been changed in years!
Surgery joke in box, underneath that a line "site maintenance",
underneath that an oval-swirl thing which I have a hard time reading
because of my 'tint blindness' but connects to be able to write an
e-mail. Under that 'too many' monkeys and clicks to the link.
KM> (Yes, I got this domain solely for this joke. Cuz it's always
KM> funny.)
Go for it! :)
> .. A group of flamingos is called a stand.
KM> I thought it was called a lawn ornament!
More stuff to cut around!
("Pull out, dummy!")
(That's what she said!)
» «
» BarryMartin3@MyMetronet.NET «
» «
... My wife told me stop impersonating a flamingo; I had to put my foot down.
--- 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)
|
