kernels do their job and never ask for arrays!

@@savagepro9060 XD Win.

if kernel gets promoted it goes to your local cinema to be transformed into something greater

Unfortunately it has signed a contract that never expires.

it will be promoted to code name popcorn

Apologies, I'm not sober right now. But I do have an important question. Is chrome trying to access the kernel of my pc?

@@BS-vf1nv oh it wants much more than your kernel, it wants to own your PC put a collar on it ;)

Why are you talking about your dawg?

Never mind I finished watching the video

@@RunningtoCatchMyBreath hahaha omg that must have been so confusing without the end of the video context 🤣

The dog doesn't understand languages, you oaf; the dog only understands basic sounds and tones. I prove this to every dog owner by issuing commands in pure gibberish that has the same tone as what they use to issue commands normally, and it completely works. Similarly, I can get a dog to sit via calling it a 'stupid fuck' in the same tone as saying 'sit' (for dogs that were trained to sit via told to 'sit'). If you issued commands in a German tone, the dog would follow that as the 'highest authority.'

Keep in mind though that it doesn't really "reset" your graphics driver. It forces Windows to create allocation from GPU to DWM, effectively discarding surface buffer (that's why it black screens for a split second). If you really want to restart you driver, use something like restart64.exe from ToastyX CRU.

I tried this a couple of times, every single time the issues got worse. Maybe I'm just unlucky

@@olivereisenberger7215maybe it wasnt a drivers issue

that doesnt really works. there's a app that does that but better. i know cause i used it. with my 2ndary display.

In my case I also have to go to task manager and manually kill and start explorer. After that the system works as a charm. Except until the next display crash.

Riley looks like a German, so the joke is twice as funny to me

I'm sure that's a full metal alchemist anime refererence lol. when Mr. Tucker turned her daughter and dog into a talking chimera lol. kinda messed up what he did.

I'm sure that's a full metal alchemist anime refererence lol. when Mr. Tucker turned her daughter and dog into a talking chimera lol. kinda messed up what he did.

how else should they pay salaries?

40 seconds

30 second ads on 5 minute videos is an option ​@@Matt43

@@Matt43 idk they could try selling $70 screwdrivers, and maybe mousepads and water bottles for $30

Hi

thought it was just me

Because most of us are on Macs 😅

Only unusual subjects are discussed here, so Windows going wrong is irrelevant.

It's still broken

​@@Dobby_zuul I highly doubt that

Yeah they clearly didn't do proper research for this video.

I was taught the reverse. That Windows was monolithic and Linux was a microkernel. This way, a bad driver in Linux couldn't bring the entire system down.

@@Lurker-dk8jk No, early on in linux's history people thought linux was going to get replaced by gnu/hurd due to hurd being a micro kernel while linux is monolithic. Windows used to be monothlithic but they moved a hybrid kernel. Most everyone has abondonded the micro kernel due to poor performance. The reason why linux is so stable is due to how many companies and people want linux to be stable, with windows microsoft are the only ones that can work on it, with linux, litterally anyone can work on it. And linux has an unstable kernel space, which means unlike windows kernel space, it can change, windows tries to keep it the same, while linux really doesn't care, it'll change, nothing huge, but it will, while linux has a stable user space, which is where all your software runs.

@@Lurker-dk8jk Further to @mathman0569's comment about the history, the other thing to point out is access control and error handling mechanisms. A bad driver in a microkernel can certainly nuke a system if the microkernel doesn't enforce proper safety, and a monolithic kernel can handle a bad driver if access control is correctly implemented (case in point: the experimental bcachefs driver in Linux had some crashing bugs, but hitting one of those bugs only lost access to the filesystem, not causing a kernel panic). Monolithic vs micro-kernel these days is really more to do with just how the kernel and drivers are packaged up than anything else, and this video conflated so many aspects of kernel, security, OS etc that it's really not helpful at all.

It doesn't hurt to refresh your knowledge. Maybe you'll realize you forgot something or oversimplified it.

AMD?

@@theengineer2017 no? My own driver.

"AmD?" My guy still living in 2010 lmao

bro is still stuck in the Piledriver era

@@BlueEyedVibeChecker ​I always have used Nvidia but decided to give AMD a try and bought a 6700XT, not even a full 2 months later and I had a permanent BSOD and had to bring it to a repair shop, I had used a RTX 3080 for oven year and a half with the only issue being the shitty PCIE 180 adapters

Yes. And your programs are the music sheet they need to "run".

Imagine it like a police man. If driver missbehaves, it gets stop and gets ticket. And in extreme cases police man sacrifice himself to get driver killed. If one hardware wants to interact with other, its somewhat different. Because driver can, in some cases, talk to other driver or hardware. Its complicated but imagine you have teacher infront of you and you have friend sitting next to you. If teacher is benevolent enough, he can allow you to talk to your friend directly. Driver is basically just a recept, how to manipulate with memory of hardware and its only a question of implementation, how you teach it to behave. Kernel just checks, if you dont do any ilegal moves, like stealing someones lunchbox.

@@gimlicz3862 The driver can actually do whatever it wants, it has the same access as the kernel. The kernel is just responsible for loading the driver, providing services for it and allowing other drivers or userspace to use it. I think a better analogy is that drivers are people and the kernel is a society or company, allowing them to work together to produce something bigger.

The kernel manages "permission to access", "methods to access", and "scheduling" for the computer's hardware. Basically: "who, how, and when" a program gets to interact with the hardware of the computer. Drivers are the low-level software that a hardware manufacturer (or concerned 3rd party) can write to allow the kernel (and others) access to functionality of the hardware. Nowadays, due to plug-and-play and similar efforts, there are generic drivers that will give you basic access to a piece of hardware. So, if you get a fancy new graphics card you don't have to "install a driver and ONLY after that, install the graphics card". Instead, you can install the new graphics card, use the generic driver to get basic access to the card to be able to use your computer, then download and install the SPECIFIC driver that will allow you to use all the features of your new card. This was the result of monumental efforts by manufacturers, operating system developers, and compiler writers. Most of the time, now, people don't even have to update their drivers as the new versions are automatically downloaded and installed for them. A better analogy would be that a kernel is like an elementary school teacher: she makes sure that all the little hardware bits act the way they should, don't hurt each other, take turns when playing with friends, speak the same language to each other, and don't start cursing. A kernel panic is when three of the kids start barfing at the same time. She runs next door and gets help taking the kids to the nurse, and calls a janitor, and moves all the kids next door until the room is clean. Then, all the not-sick kids come back to the room and the class restarts. Something that blows most people's minds is that your hard drive is a piece of hardware -- so the kernel is stored on something it is supposed to manage access to: how does the kernel ever get read out of the hard drive so that the operating system can start? Just like with generic drivers, there is a generic OS that sets up the first steps to start your computer. It is a boot-loader. It "loads stuff so that we can start up (boot) the OS". Anyway. Most modern operating systems are extremely bloated, so the kernel (the initial purpose of the operating system) is typically a very tiny part of what an OS actually provides.

Huh? This video is super surface level and has some wrong info. Read a book or smthn lmao

@@hwstar9416 I know it's very surface level, but it's also super interesting.

Yeah, the "Disk" part of the DOS acronym is the key part. Dealing with disks is hard. Even if programmers were bit-banging the hardware for performance in other areas (as was the case for most games of the era), they left anything to do with files and disks to DOS. There's little performance reason to implement your own disk handler, and the risk of a bug corrupting the file system is too great. The few programs that did implement their own disk routines were things like backup and recovery programs. The former because they often used custom disk formats to squeeze more capacity out of a floppy, and the latter just due to the nature of what they had to do.

​@@Roxor128​It gets even worse when you have to deal with different kinds of drives, different kinds of file systems, networks.. you're one fancy new doublespace away from having your software that access the disk directly breaking. But DOS does offer some other nice facilities, like handling I/O and even some sort of rudimentar memory management. It don't quite enforce it, but you can ask DOS to "allocate" memory for you, and if your program and TSRs etc behave, it helps.

they have nothing really to do with taskmanager

Yeah, imagine if they came up with a series of short explainers and called it something like Techquickie.

They could make a whole channel of stuff like this

But then it's opera gx at 4:58

Because monolithic software design has nothing to do with performance lol. That part is just wrong.

@@jollyswagman4714 That was my point tbh

@@snek_john_titor i know lol

UwU@@jollyswagman4714

Cheat Engine takes advantage of debuggers: Special programs that can access another processor's data (assuming it has admin privileges) to allow for easy error checking, or in this case, memory peeking. Any game that wants to prevent this behavior can easily block debuggers from accessing them.