Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.os.linux.advocacy > #689026 > unrolled thread

Microsoft warns of blue screen crashes caused by April updates

Back to article view | Back to comp.os.linux.advocacy

Contents

  Microsoft warns of blue screen crashes caused by April updates CrudeSausage <crude@sausa.ge> - 2025-04-16 08:55 -0400
    Re: Microsoft warns of blue screen crashes caused by April updates Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-04-17 03:06 +0000
      Re: Microsoft warns of blue screen crashes caused by April updates CrudeSausage <crude@sausa.ge> - 2025-04-17 08:48 -0400
        Re: Microsoft warns of blue screen crashes caused by April updates Borax Man <rotflol2@hotmail.com> - 2025-04-17 14:04 +0000
          Re: Microsoft warns of blue screen crashes caused by April updates CrudeSausage <crude@sausa.ge> - 2025-04-17 10:14 -0400
            Re: Microsoft warns of blue screen crashes caused by April updates Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-04-18 05:36 +0000
              Re: Microsoft warns of blue screen crashes caused by April updates Borax Man <rotflol2@hotmail.com> - 2025-04-18 09:23 +0000
                Re: Microsoft warns of blue screen crashes caused by April updates vallor <vallor@cultnix.org> - 2025-04-18 09:35 +0000
                  Wayland (was: Re: Microsoft warns of blue screen crashes caused by April updates) vallor <vallor@cultnix.org> - 2025-04-18 09:57 +0000
                    Re: Wayland % <pursent100@gmail.com> - 2025-04-18 06:21 -0700
                      Re: Wayland Chris Ahlstrom <OFeem1987@teleworm.us> - 2025-04-18 12:10 -0400
                  Re: Microsoft warns of blue screen crashes caused by April updates Farley Flud <fsquared@fsquared.linux> - 2025-04-18 10:51 +0000
                    Re: Microsoft warns of blue screen crashes caused by April updates Chris Ahlstrom <OFeem1987@teleworm.us> - 2025-04-18 12:08 -0400
                      Re: Microsoft warns of blue screen crashes caused by April updates Farley Flud <ff@linux.rocks> - 2025-04-19 10:24 +0000
                  Re: Microsoft warns of blue screen crashes caused by April updates % <pursent100@gmail.com> - 2025-04-18 06:20 -0700
                    Re: Microsoft warns of blue screen crashes caused by April updates CrudeSausage <crude@sausa.ge> - 2025-04-18 10:11 -0400
                      Re: Microsoft warns of blue screen crashes caused by April updates RonB <ronb02NOSPAM@gmail.com> - 2025-04-18 20:57 +0000
                      Re: Microsoft warns of blue screen crashes caused by April updates Farley Flud <ff@linux.rocks> - 2025-04-19 10:01 +0000
                Re: Microsoft warns of blue screen crashes caused by April updates CrudeSausage <crude@sausa.ge> - 2025-04-18 07:24 -0400
                  Re: Microsoft warns of blue screen crashes caused by April updates RonB <ronb02NOSPAM@gmail.com> - 2025-04-18 20:51 +0000
                    Re: Microsoft warns of blue screen crashes caused by April updates CrudeSausage <crude@sausa.ge> - 2025-04-19 07:46 -0400
                      Re: Microsoft warns of blue screen crashes caused by April updates RonB <ronb02NOSPAM@gmail.com> - 2025-04-21 05:01 +0000
                        Re: Microsoft warns of blue screen crashes caused by April updates CrudeSausage <crude@sausa.ge> - 2025-04-21 08:00 -0400
                          Re: Microsoft warns of blue screen crashes caused by April updates RonB <ronb02NOSPAM@gmail.com> - 2025-04-21 22:10 +0000
                      Re: Microsoft warns of blue screen crashes caused by April updates Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-04-21 05:48 +0000
                Re: Microsoft warns of blue screen crashes caused by April updates RonB <ronb02NOSPAM@gmail.com> - 2025-04-18 20:48 +0000
                  Re: Microsoft warns of blue screen crashes caused by April updates CrudeSausage <crude@sausa.ge> - 2025-04-19 07:45 -0400
                    Re: Microsoft warns of blue screen crashes caused by April updates RonB <ronb02NOSPAM@gmail.com> - 2025-04-21 05:00 +0000
                      Re: Microsoft warns of blue screen crashes caused by April updates CrudeSausage <crude@sausa.ge> - 2025-04-21 07:59 -0400
                        Re: Microsoft warns of blue screen crashes caused by April updates rbowman <bowman@montana.com> - 2025-04-21 20:12 +0000
                          Re: Microsoft warns of blue screen crashes caused by April updates CrudeSausage <crude@sausa.ge> - 2025-04-21 21:00 -0400
                        Re: Microsoft warns of blue screen crashes caused by April updates RonB <ronb02NOSPAM@gmail.com> - 2025-04-21 22:08 +0000
                          Re: Microsoft warns of blue screen crashes caused by April updates rbowman <bowman@montana.com> - 2025-04-22 00:58 +0000
                            Re: Microsoft warns of blue screen crashes caused by April updates vallor <vallor@cultnix.org> - 2025-04-22 01:05 +0000
                            Re: Microsoft warns of blue screen crashes caused by April updates CrudeSausage <crude@sausa.ge> - 2025-04-21 21:16 -0400
                              Re: Microsoft warns of blue screen crashes caused by April updates RonB <ronb02NOSPAM@gmail.com> - 2025-04-22 06:11 +0000
                              Re: Microsoft warns of blue screen crashes caused by April updates rbowman <bowman@montana.com> - 2025-04-22 07:51 +0000
                                Re: Microsoft warns of blue screen crashes caused by April updates CrudeSausage <crude@sausa.ge> - 2025-04-22 08:58 -0400
                                  Re: Microsoft warns of blue screen crashes caused by April updates rbowman <bowman@montana.com> - 2025-04-22 18:23 +0000
                                    Re: Microsoft warns of blue screen crashes caused by April updates CrudeSausage <crude@sausa.ge> - 2025-04-22 15:03 -0400
                                      Re: Microsoft warns of blue screen crashes caused by April updates rbowman <bowman@montana.com> - 2025-04-23 03:45 +0000
                                    Re: Microsoft warns of blue screen crashes caused by April updates RonB <ronb02NOSPAM@gmail.com> - 2025-04-23 05:15 +0000
                            Re: Microsoft warns of blue screen crashes caused by April updates RonB <ronb02NOSPAM@gmail.com> - 2025-04-22 06:09 +0000
                              Re: Microsoft warns of blue screen crashes caused by April updates CrudeSausage <crude@sausa.ge> - 2025-04-22 08:53 -0400
                                Re: Microsoft warns of blue screen crashes caused by April updates rbowman <bowman@montana.com> - 2025-04-22 18:40 +0000
                                Re: Microsoft warns of blue screen crashes caused by April updates RonB <ronb02NOSPAM@gmail.com> - 2025-04-23 05:20 +0000
                                  Re: Microsoft warns of blue screen crashes caused by April updates CrudeSausage <crude@sausa.ge> - 2025-04-23 09:09 -0400
                                    Re: Microsoft warns of blue screen crashes caused by April updates RonB <ronb02NOSPAM@gmail.com> - 2025-04-24 12:45 +0000
                          Re: Microsoft warns of blue screen crashes caused by April updates CrudeSausage <crude@sausa.ge> - 2025-04-21 21:06 -0400
                            Re: Microsoft warns of blue screen crashes caused by April updates RonB <ronb02NOSPAM@gmail.com> - 2025-04-22 06:13 +0000
                              Re: Microsoft warns of blue screen crashes caused by April updates CrudeSausage <crude@sausa.ge> - 2025-04-22 08:54 -0400
                Re: Microsoft warns of blue screen crashes caused by April updates Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-04-21 05:46 +0000
                  Re: Microsoft warns of blue screen crashes caused by April updates Farley Flud <fsquared@fsquared.linux> - 2025-04-21 10:46 +0000
                  Re: Microsoft warns of blue screen crashes caused by April updates vallor <vallor@cultnix.org> - 2025-04-21 12:35 +0000
                  Re: Microsoft warns of blue screen crashes caused by April updates rbowman <bowman@montana.com> - 2025-04-21 20:54 +0000
              Re: Microsoft warns of blue screen crashes caused by April updates % <pursent100@gmail.com> - 2025-04-18 06:19 -0700
            Re: Microsoft warns of blue screen crashes caused by April updates Borax Man <rotflol2@hotmail.com> - 2025-04-18 09:21 +0000
              Re: Microsoft warns of blue screen crashes caused by April updates RonB <ronb02NOSPAM@gmail.com> - 2025-04-18 20:46 +0000
                Re: Microsoft warns of blue screen crashes caused by April updates CrudeSausage <crude@sausa.ge> - 2025-04-19 07:43 -0400
                  Re: Microsoft warns of blue screen crashes caused by April updates RonB <ronb02NOSPAM@gmail.com> - 2025-04-21 04:47 +0000
                    Re: Microsoft warns of blue screen crashes caused by April updates pothead <pothead@snakebite.com> - 2025-04-23 02:33 +0000
                      Re: Microsoft warns of blue screen crashes caused by April updates rbowman <bowman@montana.com> - 2025-04-23 03:48 +0000
                        Re: Microsoft warns of blue screen crashes caused by April updates pothead <pothead@snakebite.com> - 2025-04-23 04:07 +0000
                          Re: Microsoft warns of blue screen crashes caused by April updates % <pursent100@gmail.com> - 2025-04-23 07:02 -0700
                      Re: Microsoft warns of blue screen crashes caused by April updates RonB <ronb02NOSPAM@gmail.com> - 2025-04-23 05:22 +0000
                        Re: Microsoft warns of blue screen crashes caused by April updates vallor <vallor@cultnix.org> - 2025-04-23 07:21 +0000
                          Re: Microsoft warns of blue screen crashes caused by April updates % <pursent100@gmail.com> - 2025-04-23 07:03 -0700
                      Re: Microsoft warns of blue screen crashes caused by April updates % <pursent100@gmail.com> - 2025-04-23 07:01 -0700
                        Re: Microsoft warns of blue screen crashes caused by April updates Chris Ahlstrom <OFeem1987@teleworm.us> - 2025-04-24 08:42 -0400
        Re: Microsoft warns of blue screen crashes caused by April updates wasbit <wasbit@REMOVEhotmail.com> - 2025-04-18 09:36 +0100
          Re: Microsoft warns of blue screen crashes caused by April updates rbowman <bowman@montana.com> - 2025-04-18 18:07 +0000
            Re: Microsoft warns of blue screen crashes caused by April updates Daniel70 <daniel47@eternal-september.org> - 2025-04-19 21:56 +1000
              Re: Microsoft warns of blue screen crashes caused by April updates Chris Ahlstrom <OFeem1987@teleworm.us> - 2025-04-19 09:15 -0400
                Re: Microsoft warns of blue screen crashes caused by April updates pothead <pothead@snakebite.com> - 2025-04-21 01:46 +0000
                  Re: Microsoft warns of blue screen crashes caused by April updates rbowman <bowman@montana.com> - 2025-04-21 02:22 +0000
                    Re: Microsoft warns of blue screen crashes caused by April updates pothead <pothead@snakebite.com> - 2025-04-23 02:29 +0000
                      Re: Microsoft warns of blue screen crashes caused by April updates rbowman <bowman@montana.com> - 2025-04-23 03:58 +0000
                        Re: Microsoft warns of blue screen crashes caused by April updates pothead <pothead@snakebite.com> - 2025-04-23 04:11 +0000
                          Re: Microsoft warns of blue screen crashes caused by April updates rbowman <bowman@montana.com> - 2025-04-23 07:36 +0000
                    Re: Microsoft warns of blue screen crashes caused by April updates chrisv <chrisv@nospam.invalid> - 2025-04-23 18:16 -0500
                      Re: Microsoft warns of blue screen crashes caused by April updates rbowman <bowman@montana.com> - 2025-04-24 00:14 +0000
                Re: Microsoft warns of blue screen crashes caused by April updates Daniel70 <daniel47@eternal-september.org> - 2025-04-21 19:40 +1000
                  Re: Microsoft warns of blue screen crashes caused by April updates Farley Flud <fsquared@fsquared.linux> - 2025-04-21 10:41 +0000
                  Re: Microsoft warns of blue screen crashes caused by April updates Mark Lloyd <not.email@all.invalid> - 2025-04-21 16:09 +0000
                    Re: Microsoft warns of blue screen crashes caused by April updates % <pursent100@gmail.com> - 2025-04-21 12:22 -0700
                    Re: Microsoft warns of blue screen crashes caused by April updates rbowman <bowman@montana.com> - 2025-04-21 19:38 +0000
                    Re: Microsoft warns of blue screen crashes caused by April updates Char Jackson <none@none.invalid> - 2025-04-22 14:47 -0500
                      Re: Microsoft warns of blue screen crashes caused by April updates rbowman <bowman@montana.com> - 2025-04-23 04:02 +0000
                        Re: Microsoft warns of blue screen crashes caused by April updates CrudeSausage <crude@sausa.ge> - 2025-04-23 08:38 -0400
                  Re: Microsoft warns of blue screen crashes caused by April updates rbowman <bowman@montana.com> - 2025-04-21 19:32 +0000
                    Re: Microsoft warns of blue screen crashes caused by April updates Daniel70 <daniel47@eternal-september.org> - 2025-04-22 19:58 +1000
          Re: Microsoft warns of blue screen crashes caused by April updates Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-04-21 05:43 +0000
            Re: Microsoft warns of blue screen crashes caused by April updates rbowman <bowman@montana.com> - 2025-04-21 19:25 +0000
              Re: Microsoft warns of blue screen crashes caused by April updates % <pursent100@gmail.com> - 2025-04-21 12:33 -0700
    Re: Microsoft warns of blue screen crashes caused by April updates Paul <nospam@needed.invalid> - 2025-04-17 05:02 -0400

Page 5 of 5 — ← Prev page 1 2 3 4 [5]

#689417

On Wed, 23 Apr 2025 18:16:06 -0500, chrisv wrote:

> For a 'scope, I have an ancient Tek 7834 400 MHz mainframe, with two
> dual-channel vertical amplifier plug-ins to go along with the main and
> delayed time-base plug-ins.  It's from the 80's but still works good. I
> confess that it's mostly decorative, these days.  I've thought about
> selling it but it's so damn cool looking.  All the knobs and buttons and
> switches that you could desire!  8)

I never had a 'scope. I did have a primitive RatShack probe on a serial 
connection.

https://www.linuxtoys.org/pscope/pscope.html

I should dig around. I'm a packrat so it must be around someplace.  
xProbeScope.c is a good example of something that will be obsolete when 
Wayland takes over. When you see functions that start with X and not Xt or 
Xm you know you're down in the XLib weeds and probably doing stuff that 
Wayland isn't going to let you do.

Might be an interesting project for PySide6.

It was an interesting idea, a bit ahead of its time. I've got an HiLrtgp 8 
channel USB logic analyzer that is basically the same idea that is pretty 
handy. It's a Salae clone for about a tenth of the cost. I have the 
PulseView app on Windows but sigrok.org seems to be a 404 currently. I'm 
not sure if the Saleae software will work.

Trivia: it uses a souped up 8051. Some things never die.

[toc] | [prev] | [next] | [standalone]

#689303

On 19/04/2025 11:15 pm, Chris Ahlstrom wrote:
> Daniel70 wrote this post while blinking in Morse code:
>> On 19/04/2025 4:07 am, rbowman wrote:
>>> On Fri, 18 Apr 2025 09:36:23 +0100, wasbit wrote:
>>>
>>>> Much like car ownership. As long as it works there is no need to know
>>>> how. If/when it goes wrong take it to someone who does know to fix.
>>>
>>> That 'someone' has been me. Since I was a little kid taking stuff apart
>>> I've wanted to know how stuff works.
>>>
>> I can recall (mid-60's, 10 years old or so) pulling apart Mum's Steam
>> Iron which had stopped working. Unfortunately, I wasn't able to get it
>> functioning.
>>
>> About six years later, I joined The Army, and did an Electronics
>> Apprenticeship!!
> 
> When I was a teen I got some Social Security money from my father's SS.
> Not sure why. It was about $230.
> 
> In spite of my parents' dismay, I blew it all on a PAIA synthesizer kit
> and the tools needed to assemble it. Clipping leads, soldering, learning
> resistor color coding, testing without an oscilloscope... I had years of
> fun with that thing.
> 
"resistor color coding"!! Now there's a flash from the past .....

Black,		Black
Boys,		Brown
Rape,		Red
Our,		Orange
Young,		Yellow
Girls,		Green
Blessed,	Blue
Virginity,	Violet
Gone,		Grey
West.		White

The Mnemonic we used back then might not be P.C. today but it worked then!!
-- 
Daniel70

[toc] | [prev] | [next] | [standalone]

#689304

On Mon, 21 Apr 2025 19:40:14 +1000, Daniel70 wrote:

>> 
> "resistor color coding"!! Now there's a flash from the past .....
> 
> Black,		Black
> Boys,		Brown
> Rape,		Red
> Our,		Orange
> Young,		Yellow
> Girls,		Green
> Blessed,	Blue
> Virginity,	Violet
> Gone,		Grey
> West.		White
> 
> The Mnemonic we used back then might not be P.C. today but it worked then!!
>

Then you'll need a mnemonic to remember the mnemonic ...

https://xkcd.com/992/

I use a hand-held carboard device that contains wheels that are
dialed to line up the colors and produce the correct value.

E-parts stores, which are no more, used to give those gadgets
away for free.

A good GNU/Linux scripting challenge would be to code a little Bash/Perl
script to cough up the correct value.


-- 
Hail Linux!  Hail FOSS!  Hail Stallman!

[toc] | [prev] | [next] | [standalone]

#689313

On Mon, 21 Apr 2025 19:40:14 +1000, Daniel70 wrote:

[snip]

> "resistor color coding"!! Now there's a flash from the past .....
> 
> Black, Black
> Boys,	Brown 
> Rape,	Red 
> Our, Orange
> Young, Yellow
> Girls, Green
> Blessed, Blue
> Virginity, Violet
> Gone, Grey
> West, White
> 
> The Mnemonic we used back then might not be P.C. today but it worked
> then!!

The first six are the same I learned, although the last four were "But 
Violet Gives Willingly".

BTW, I once saw a clock that used six full-color LEDs (not 7-segment 
displays) to show the time using that color code. At the time I'm writing 
this, its brown-brown:black-violet:orange-white.

-- 
Mark Lloyd
http://notstupid.us/

"We do not want holy books, but true ones; not sacred writings, but
sensible writings." [Lemuel K. Washburn, _Is The Bible Worth Reading And
Other Essays_]

[toc] | [prev] | [next] | [standalone]

#689314

Mark Lloyd wrote:
> On Mon, 21 Apr 2025 19:40:14 +1000, Daniel70 wrote:
> 
> [snip]
> 
>> "resistor color coding"!! Now there's a flash from the past .....
>>
>> Black, Black
>> Boys,	Brown
>> Rape,	Red
>> Our, Orange
>> Young, Yellow
>> Girls, Green
>> Blessed, Blue
>> Virginity, Violet
>> Gone, Grey
>> West, White
>>
>> The Mnemonic we used back then might not be P.C. today but it worked
>> then!!
> 
> The first six are the same I learned, although the last four were "But
> Violet Gives Willingly".
> 
> BTW, I once saw a clock that used six full-color LEDs (not 7-segment
> displays) to show the time using that color code. At the time I'm writing
> this, its brown-brown:black-violet:orange-white.
> 
mine is the same but the reverse of that

[toc] | [prev] | [next] | [standalone]

#689318

On 21 Apr 2025 16:09:19 GMT, Mark Lloyd wrote:

> On Mon, 21 Apr 2025 19:40:14 +1000, Daniel70 wrote:
> 
> [snip]
> 
>> "resistor color coding"!! Now there's a flash from the past .....
>> 
>> Black, Black Boys,	Brown Rape,	Red Our, Orange Young, Yellow 
Girls,
>> Green Blessed, Blue Virginity, Violet Gone, Grey West, White
>> 
>> The Mnemonic we used back then might not be P.C. today but it worked
>> then!!
> 
> The first six are the same I learned, although the last four were "But
> Violet Gives Willingly".

Yes. 

> BTW, I once saw a clock that used six full-color LEDs (not 7-segment
> displays) to show the time using that color code. At the time I'm
> writing this, its brown-brown:black-violet:orange-white.

That would be an interesting project with a neopixel strip. I think i 
could get a credible brown but black would be a problem.

[toc] | [prev] | [next] | [standalone]

#689367

On 21 Apr 2025 16:09:19 GMT, Mark Lloyd <not.email@all.invalid> wrote:

>On Mon, 21 Apr 2025 19:40:14 +1000, Daniel70 wrote:
>
>[snip]
>
>> "resistor color coding"!! Now there's a flash from the past .....
>> 
>> Black, Black
>> Boys,	Brown 
>> Rape,	Red 
>> Our, Orange
>> Young, Yellow
>> Girls, Green
>> Blessed, Blue
>> Virginity, Violet
>> Gone, Grey
>> West, White
>> 
>> The Mnemonic we used back then might not be P.C. today but it worked
>> then!!
>
>The first six are the same I learned, although the last four were "But 
>Violet Gives Willingly".

Also, by the time the 1970s rolled around, Black Boys had become Bad
Boys.

[toc] | [prev] | [next] | [standalone]

#689388

On Tue, 22 Apr 2025 14:47:39 -0500, Char Jackson wrote:

> Also, by the time the 1970s rolled around, Black Boys had become Bad
> Boys.

Yes, they did. Still are. The BLM crew learned a lot from the mostly 
peaceful '60s riots. Politicians can ignore your marches and protest 
rallies until you start burning shit down.

[toc] | [prev] | [next] | [standalone]

#689403

On 2025-04-23 00:02, rbowman wrote:
> On Tue, 22 Apr 2025 14:47:39 -0500, Char Jackson wrote:
> 
>> Also, by the time the 1970s rolled around, Black Boys had become Bad
>> Boys.
> 
> Yes, they did. Still are. The BLM crew learned a lot from the mostly
> peaceful '60s riots. Politicians can ignore your marches and protest
> rallies until you start burning shit down.

A few years from now, one of the four American networks, most likely 
ABC, will make documentaries about how the BLM people struggled, were 
attacked and victimized and became heroes when they burned the whole 
country down. They'll conveniently omit the burning the country down 
part though.

-- 
God be with you,

CrudeSausage
LibreOffice supporter
John 14:6

[toc] | [prev] | [next] | [standalone]

#689316

On Mon, 21 Apr 2025 19:40:14 +1000, Daniel70 wrote:

> "resistor color coding"!! Now there's a flash from the past .....

Maybe it's a flash from your past...  Working with microcontrollers there 
is a need for external circuitry requiring resistors for pullups, biasing, 
and current limiting LEDs. 

My eyes aren't getting any better with age but iirc it was a lot easier to 
read the colors on 1/4 watt resistors than the 1/8 watt metal film types 
where the body is light beige or blue.

[toc] | [prev] | [next] | [standalone]

#689356

On 22/04/2025 5:32 am, rbowman wrote:
> On Mon, 21 Apr 2025 19:40:14 +1000, Daniel70 wrote:
> 
>> "resistor color coding"!! Now there's a flash from the past .....
> 
> Maybe it's a flash from your past...  Working with microcontrollers there
> is a need for external circuitry requiring resistors for pullups, biasing,
> and current limiting LEDs.

When I joined the Australian Army (1973), I did a three year trade 
apprenticeship. IF, at the end of the trade apprenticeship, *IF* you had 
pasted all your module exams, you got a two week introduction to these 
new-fangled things called "chips" or "ICs" .... which got you about as 
far as AND/OR/NAND/NOR gates ..... but there were several of them 
with-in the one component!!

> My eyes aren't getting any better with age but iirc it was a lot easier to
> read the colors on 1/4 watt resistors than the 1/8 watt metal film types
> where the body is light beige or blue.
> 
Correct! Correct! Given my failing eyesight (too), give me rings of 
colour ANY day of the week ... any light condition (well, at least with 
some light!! ;-P ).
-- 
Daniel70

[toc] | [prev] | [next] | [standalone]

#689300

On Fri, 18 Apr 2025 09:36:23 +0100, wasbit wrote:

> Much like car ownership. As long as it works there is no need to know
> how. If/when it goes wrong take it to someone who does know to fix.

Would you buy a car with a sealed bonnet? Or would you buy one that can be 
opened and its parts examined?

Even if you’re not a mechanic, you want to be able to take your car to 
your choice of mechanics to have it fixed/maintained. Imagine if the 
vehicle manufacturer had a monopoly on the ability to service your vehicle 
and supply parts for it; would you put up with that?

[toc] | [prev] | [next] | [standalone]

#689315

On Mon, 21 Apr 2025 05:43:28 -0000 (UTC), Lawrence D'Oliveiro wrote:

> On Fri, 18 Apr 2025 09:36:23 +0100, wasbit wrote:
> 
>> Much like car ownership. As long as it works there is no need to know
>> how. If/when it goes wrong take it to someone who does know to fix.
> 
> Would you buy a car with a sealed bonnet? Or would you buy one that can
> be opened and its parts examined?

When I'm looking for a new car I always open the hood to make sure the 
common parts replaced during PM are accessible. With my last three Toyotas 
the plugs and distributor are moot since the plugs are fired by individual 
coils mounted on the plug and are not on the maintenance schedule. 5000 
mile oil changes are, and I can reach down from the top to replace the oil 
filter.  

I've favored straight engines since they're usually easier to work on and 
have had straight 2s, 4s, 6s, and 8s.  I do have V twins on two of the 
bikes. 

[toc] | [prev] | [next] | [standalone]

#689317

rbowman wrote:
> On Mon, 21 Apr 2025 05:43:28 -0000 (UTC), Lawrence D'Oliveiro wrote:
> 
>> On Fri, 18 Apr 2025 09:36:23 +0100, wasbit wrote:
>>
>>> Much like car ownership. As long as it works there is no need to know
>>> how. If/when it goes wrong take it to someone who does know to fix.
>>
>> Would you buy a car with a sealed bonnet? Or would you buy one that can
>> be opened and its parts examined?
> 
> When I'm looking for a new car I always open the hood to make sure the
> common parts replaced during PM are accessible. With my last three Toyotas
> the plugs and distributor are moot since the plugs are fired by individual
> coils mounted on the plug and are not on the maintenance schedule. 5000
> mile oil changes are, and I can reach down from the top to replace the oil
> filter.
> 
> I've favored straight engines since they're usually easier to work on and
> have had straight 2s, 4s, 6s, and 8s.  I do have V twins on two of the
> bikes.
> 
all my bikes are deckers you pop the hood ,
ever since you bought that ford that had no motor in it

[toc] | [prev] | [next] | [standalone]

#689066

On Wed, 4/16/2025 8:55 AM, CrudeSausage wrote:
> At what point do we finally give up?
> 
> <https://www.bleepingcomputer.com/news/microsoft/microsoft-warns-of-blue-screen-crashes-caused-by-april-updates/>
> 
> Microsoft warned customers this week that their systems might crash with a blue screen error caused by a secure kernel fatal error after installing Windows updates released since March.
> 
> According to advisory updates for the KB5055523 April cumulative update and the KB5053656 March preview update, this known issue affects devices running Windows 11, version 24H2. Those affected will see their PCs crash after installing these updates and restarting their devices.
> 
> "After installing this update and restarting your device, you might encounter a blue screen exception with error code 0x18B indicating a SECURE_KERNEL_ERROR," Microsoft said.
> 
> Until a fix is rolled out through Windows Update, Microsoft resolved this issue via Known Issue Rollback (KIR), a feature that reverses buggy non-security updates delivered via Windows Update.
> 
> This fix will propagate automatically to all home, non-managed enterprise devices, and business devices not managed by IT departments over the next 24 hours. To expedite the rollout, Microsoft advises affected users to restart their devices, which ensures the fix is applied faster.
> 
> After installation, you can find the Group Policy under Computer Configuration > Administrative Templates. To deploy it on affected endpoints, you must go to the Local Computer Policy or the Domain policy on the domain controller using the Group Policy Editor to choose the Windows version you want to target.
> 
> "You will need to install and configure the Group Policy for your version of Windows to resolve this issue. You will also need to restart your device(s) to apply the group policy setting," Microsoft added.
> 
> Windows admins can find additional guidance on deploying KIR Group Policies on the Microsoft support website.
> 
> Earlier this week, Microsoft released emergency Windows updates to address an issue affecting local audit logon policies in Active Directory Group Policy and warned admins that Windows Server 2025 domain controllers might become inaccessible after restarts, causing services and apps to fail.
> 
> Today, Redmond also started deploying a fix for an issue causing some Windows devices to be offered Windows 11 upgrades despite Intune policies blocking them.
> 
> 

This article was written by an AI.

It's hard to know what it used as a trigger event, to make all this text up.

https://windowsforum.com/threads/windows-11-24h2-update-failures-how-microsoft-addresses-the-blue-screen-secure_kernel_error-crisi.361032/?amp=1

    "miscellaneous security improvements to internal OS functionality"  <== is it snowing in here or what ?
                                                                            This is what I got on one search string.

And telling an Enterprise IT to enable the KIR policy, why would they
do that ? The Enterprise person would just reimage the machine and
tip it upright that way. Done and done. Enterprise IT have been
to the rodeo, they know what to do. They would hold back updates.
The employee would go back to work.

*******

There is a report of one here, from June 29, 2024 , and against Win11.
This is a driver issue, that seems to have triggered a similar response.
That might even mean it's against an earlier version of W11.

https://answers.microsoft.com/en-us/windows/forum/all/windows-11-blue-screen-securekernelerror-18b/3d8b10ac-b749-4af4-991b-d75894287547

   nt!HvlSkCrashdumpCallbackRoutine and nt!KiProcessNMI.

And that seems to be related to Hypervisor. Windows runs on top of
the inverted hypervisor, but it's hard to say what kernel this is.
It could be the sandbox kernel for example.

Unless we have diagrams of the expanded virtualization ecosystem on
this puppy, we'll never make any progress interpreting these
bullshit articles with sprinkles on top. What good is telling
customers you have a problem you don't want to tell them about ?
The root cause might be traceable to some CVE, but the articles
have no information at all to go on.

I bet the crashes all have certain features that are common. Yet
the information about the crashes does not hint about what that
would be. In the second link, where an fiio driver causes a problem
at kernel level, multiple people reported the problem and could
correlate the problems showed up when they got their USB DAC.
That's the normal activity that goes with problem reports.

If "thousands of yokels" have been tipped over, where are
the hits in Google ? Would they, perhaps, all be Enterprise
customers and suffering from a code of silence (the blanket NDA thing) ?

Sorry, article made up, no signal in evidence.

And this is not the first issue that's been like this.
While the Google search AI is responsible for gating off most
of the signal, some issues are so silent, it's like they
don't even exist. All I can get from Borncity is regurgitated
press release. That's not like Born. There was a time, enthusiast
sites provided color commentary. If they can't find a signal
either, what the hell is going on ??? IDK.

"There's a fire!!! But, there's no smoke and no heat. Um, that is all."

   Paul

[toc] | [prev] | [standalone]

Page 5 of 5 — ← Prev page 1 2 3 4 [5]

Back to top | Article view | comp.os.linux.advocacy

csiph-web