Since it requires a micro-scope to see a mega-karocyte, do I need a micro-micro-scope to see a micro-megakaryocyte ?

When it's a backup by EaseUS TODO backup. It failed me several times and the backups are in a proprietary format.

If something were draining the battery that fast then some things in the computer would be getting very warm very fast.

Ahhh ... but do you have to keep explaining the same thing again and again?

The closer you look, the worse it gets!

Doesn't the BIG RED 'X' in front of "

Quote:

Special characters except for # & * < > ( ) ' [ ]

mean that you can use THOSE special characters, but none other?

Yup, 4 key rollover is all it will swallow and it handles that with grace. I can barely think or move fast enough to challenge even 2-3 key rollover.

A PS/2 adapter plugged into a USB multiplexer causes rollover problems and phantom keypresses. The adapter needs to be plugged directly into a primary USB port on the computer.

I am using an old IBM KB-7953 keyboard (with a PS-2 -> USB adapter) from 1998 and it still works perfectly -- great keyboard feel. The texture has worn off the most-used keys, but the letting is still sharp. I planned ahead and set a few aside in case this one wears out ... doesn't look like that will happen. IBM really grokked typing back then.

Delta is a different virus in terms of clinical behavior. People get sicker quicker, younger people are dying. "they can't handle it?" -- your lack of empathy for people working flat out month after month to save lives is noted. Many were burned out before Delta.

Yes! Best boat is an "OPB" ... Other Person's Boat.

Medical experts (ACTUAL EXPERTS, not social media hoax promoters) recommending getting the vaccine after having had COVID-19 because the immune response elicited by the virus is different than that induced by the RNA vaccine and there is evidence that immunity acquired by infection may last a shorter time than that induced by the vaccines.

Microsoft and Apple spend fortunes developing consistent user interfaces ... then the web came along and anyone with a keyboard could create their own UI scheme and user chaos ensued, then the UI geeks with a passion for white space design came and forced us to do endless scrolling for simple tasks, then small device compatibility became an issue and we were given UIs that weren't optimal for either small or big screens. This is like living through some man's mid-life crisis in which he dumps his "old" highly capable & compatible brunette wife for a shiny new young blonde who looks pretty but is awkward at many things.

Quote:

You NEED to get the users involved BEFORE you start coding the new system. Give them the idea that they are in control,

They just might have ideas on improving the system -- frequently the decision-makers (a.k.a. their bosses) have no clue about any of the current work flow impediments, or the work-arounds that are just part of what the users "have to do" to get their old system to support their work.

Conway's Law: In any organization there is one person who knows what is going on. That person must be fired.

You need a second set of glasses optimized for coding. A set of Walmart "readers" may work if you don't have astigmatism or left-right asymmetry in your vision.

Overheard at a church food festival: "I'm the chip monk. You need to look for the fish friar!"

In clinical chemistry it is common for the concentration of an analyte to be reported as "< 0.10 mg/dl" when that is the sensitivity of the test. Sensitivity of a test is defined by the random analytical variation of the test in the absence of ANY analyte, i.e. the "noise" in the measurement. cf. Gaussian standard error of estimate. In this example, a "result" of 0.005 mg/dl is analytically indistinguishable from 0.00 mg/dl. The same issues of analytical precision apply to the extremes of floating point calculation.

And if you want to elaborate and analyze the Nuts and Bolts as structures:

domains
itemDOM = item(integer ID, integer Size).

class predicates
matchItems : (itemDOM* Nuts, itemDOM* Bolts, tuple{itemDOM Nut, itemDOM Bolt}*) -> tuple{itemDom Nut, itemDOM BoltID}*.
clauses
matchItems([], [], RevMM) = list::reverse(RevMM) :-
!.
matchItems(NN, BB, CurrItems) = MM :-
item(IdN, SizeN) in NN,
item(IdB, SizeB) in BB,
SizeN = SizeB,
!,
UnmatchedNN = list::remove(NN, item(IdN, SizeN)),
UnmatchedBB = list::remove(BB, item(IdB, SizeB)),
MM = matchItems(UnmatchedNN, UnmatchedBB, [tuple(item(IdN, SizeN), item(IdB, SizeB)) | CurrItems]).
matchItems(_, _, _) = [] :-
exception::raise_error("Input lists contain an unmatched item or list lengths are unequal.").

And invoke the matching like this:

clauses
run() :-
write("\n\n", "Testing", "\n\n"),
IDs = mkList(5, []), % create a list of 5 random integers
NutItems = [ item(ID, ID * 100) || ID in IDS ], % set sizes to be 5 X the ID
BoltItems = [ item(ID + 300, Size) || item(ID, Size) in NutItems ], % set Bolt IDs to 300 greater than Nut IDs
MM = matchItems(NutItems, BoltItems, []),
write(MM),
write("\nPress [Enter] to exit"),
_ = readLine(),
!.

Something like this, using Visual Prolog:

class predicates
match : (integer_list NutSizes, integer_list BoltSizes, integer_list CurrentMatches) -> integer_list SizesMatched.
clauses
match([], [], RevMM) = list::reverse(RevMM) :-
!.
match(NN, BB, CurrMM) = MM :-
N in NN,
B in BB,
N = B,
!,
UnatchedNN = list::remove(NN, N),
UnatchedBB = list::remove(BB, N),
write("\nUnmatched Nuts: ", NN),
write("\nUnmatched Bolts: ", BB),
write("\nCurrent matches: ", [N | CurrMM]),
MM = match(UnatchedNN, UnatchedBB, [N | CurrMM]).
match(_, _, _) = [] :-
exception::raise_error("Input lists contain an unmatched item or list lengths are unequal.").