more W7 help

Just out of curiosity, what sub-type ?

Wondering what reagent they're using now and what it senses.

When they were giving away detection kits six months ago, the "guy" didn't even know what the detection kits detected. It should say, somewhere, what it is armed to detect. With constant mutation, there's no guarantee a test kit can detect everything.

Despite all the vaccinations, your protection wanes with time. There is a long-term part of your immune system, which this particular vaccine does not train. COVID is not a human disease. Our immune system (with the exception of some "special" humans) is not a good match for the disease. There are a few humans, who unlike yourself, have absolutely no worries in this regard. They could not catch SARS, MERS, or COVID.

Neither is the H5N1, which should strike... any time now. It has recently hopped species, and will be our next candidate. (AKA the old bird flu.) Normally it does bird to bird, and we kill the bird flocks. But this time it did bird to animal. And then animal to human, is getting... kinda close. It's this kind of s*it, is why poultry farms are run like "biohazard sites", where you dip your Wellies in bleach.

Paul

In message snipped-for-privacy@news.individual.net>, Jeff Gaines snipped-for-privacy@outlook.com writes

Ok. Please tell me why Microsoft would assume this tortuous process is understood and used by their average customer?

Ok. Thanks John and Paul for the detailed explanations.

My technical education stopped in 1983 when I took up farming full time. I guess anyone shunting photographs into word files would have learned these processes as technology progressed

Pass. I got the second red line on an *in date* detection kit.

Day one was low temperature! Moderate balance issues, runny nose with occasional sneezing. Annoyingly overnight bladder control has meant piddling every hour or so:-(

Basically there are too many humans on the planet leading to intensive food production for our survival and further expansion.

I went out over Easter weekend, and have had some kind of lurgy since the week after, cough leading to sore throat, ultra snotty nose, unclearable throat, nothing worse than that.

Don't feel any compulsion to go out a buy a test kit though, I'll just stay at home as much as possible anyway ...

From memory it has been part of the OS since the year dot, if you copy and paste things in Word, Excel etc. etc. you use it (perhaps without realising you are using it) and the "PrtSc" button is reasonably self explanatory - it's a useful extension of the Clipboard.

The clipboard didn't always exist, or didn't always work. You have avoided a lot of aggravation.

Paul

Cough. CTRL + C (copy) and CTRL + V (paste) has been enabled for many years.

You might find it easier to left click and hold to select an area, followed by right click and just select cuT, Copy, Paste or Delete from the menu.

I had it twice last december. The first one started on Nov 30th and the next day was just like nasty shivery flu which lasted 3 days, and gave a strong positive LF test, then gave me the most awful sore throat that I have had for decades. After 8 days an LF test was still positive then it fizzled out by mid December.

ON Xmas eve I picked up a really nasty cold, the sort that did the rounds back in the 1970's, and again had a positive LF test, but this time I had no flu-like shivery, aching muscle symptoms.

Yes - introduced in 1974 at Xerox PARC, apparently, but then became mainstream when Apple's Lisa and Macs were introduced some 40 years ago. Copied by MS for Windows using the CTRL key as a modifier. Macs use the CMD key to this day, instead.

Nope, DEC OSs had it long before that.

Wrong again, it was in DOS long before that.

ISTM much of the conceptual difficulty with the Print Screen key is the fact that it is still called that!

There was a time (when DOS ruled), you pushed it[1], and a snapshot of the (text mode) screen popped out of the printer. It pretty much did what it says on the tin.

In windows world, it has never really done that, but by that time all the key caps were printed and standardised...

A "Copy Screen" key might be more aptly named. You push it, it makes a copy "somewhere", which you can later paste into something (including something that could print it out)

x86 CPUs (like pretty all the others), support an interrupt handling capability - a way for an external device to signal to the CPU that it needs attention. When this happens, the CPU will stop whatever it was doing, jump off to some code (aka an an "Interrupt Handler" or "Interrupt Service Routine" (ISR)) to deal with the needs of whatever was signalling it, and then resume normal execution from where it left off.

To achieve this voodoo there is typically a jump table of interrupt vectors that point the CPU toward those interrupt handlers - so different sources of interrupt can be linked to the required handlers.

Now normally interrupts are a "hardware thing" - some electronic device is wired to an interrupt line into the CPU, so that it can signal when it wants to interrupt.

The x86 range also has a software interrupt capability that uses the same trick for handling some "exceptions" that can be generated in the CPU itself. In the 8088 used in the original IBM PC, the CPU could generate 5 such exceptions - numbered 0 to 4 (for things like a divide by zero event or an overflow, but also single step debugging).

The idea being that you could have an ISR that could "handle" some kinds of software event if wanted. Intel in their published data books for the CPU highlighted that although the 8088/8086 only used 5 of these exceptions, they reserved more of them for extra facilities that may be added to later CPUs. They told developers not to used any of those reserved ones.

So what did IBM do? They implemented the print screen routine as if it was an ISR. Now having the print screen code implemented as an ISR is quite nifty - you can call it anywhere at any time, and it will make a note of what it was doing, go off and print the screen, and then carry on where it left off. So even in the body of the code that handles key presses (also done in an ISR that handles the key up/down events that interrupt the CPU), it could generate a software interrupt to call the print screen code. So far so good. However they also decided to make this handler the sixth one - one of the reserved ones that Intel said "don't use".

All was fine and dandy until the 80286 came out and found it way into the IBM PC-AT. That had a new "bounds" exception internally wired to the sixth interrupt (and another couple of exceptions using the next two reserved ones). The bound exception could be used to automatically validate that data the CPU was processing fell within certain limits or "bounds". Not often used, but it did have the nice side effect that if your code generated a bounds exception unexpectedly, and had not bothered to install its own ISR to handle it, the PC would respond by printing the screen!

(and if you were using bounds processing, and your implemented your own ISR to handle the exception, it now also had to deal with the problem of your code getting called at random times by the PC BIOS whenever the user pressed Print Screen key!).

Windows doesn't get mentioned *at all* in that article. Not a good sign.

which makes sense, because only with a graphics environment, do you get interested in stealing PARC ideas.

So it's PARC, Apple, Windows.

Paul

And they got it wrong about who pioneered it too, it was in the DEC OSs well before that and it DOS too.

Though ctrl-ins and shift-ins were used by some programs.

Feel free to cite evidence of your claims. I know you can't.

ISR 21h was used by DOS. And I recall there was a timer ISR too. In the days of shared PCs I wrote a TSR program that looked for directory names and if a perpetual offender used the machine (who shouldn't be using it) and the active directory included his name, characters would fall down the screen, Matrix style!

I thought there were legacy CP/M commands accessible in DOS too?

On DEC VMS using something like a VT220 or VT320 it was common to use Shift Del and Shift Ins to cut and paste. (If you wanted a "copy" option you got in the habit of rolling over Del and Insert while holding shift to copy to delete the text into the clipboard, and then restore it before moving to the final insert position and inserting it again).

Read the DEC manuals.

In the case of DOS, run it and see.

Even you should be able to manage that if someone was actually stupid enough to lend you a seeing eye dog and a white cane.