Actually i kinda go back to win32api because i find Qt apps so damn slow in startup. Having a high perf pc and then those startup time make me think we go backwards. And i hate win32api. but it's probably instant compatible running on linux aswell with WINE emulation.
It is almost comical that when searching for a video about Windows Drivers' Development so far, I was only getting results from 10 years ago that have completely given up on that specific matter so the information on these outdated videos is also minimal, and now, out of nowhere, I bumped into this video on my home page. I'd really love to see more guides concerning drivers' development. That was incredible.
Pavel Yosifovich is another good source. Dont know about his videos, but he's written good low level programming type books, such as device driver dev and theyre current.
I thought "There's no way a sub 8 minute video is going to be enough to be informative for a topic like this." I was completely wrong. This was well paced, straight forward, and better than I could have imagined. This will be the go-to video I send to people who want to start with kernel mode dev but don't understand quite where to get started. Also: What shell replacement are you using, It looks swell!
Thanks! :) I use a port of Suckless dwm for Windows called dwm-win32, it actually sits on top of the shell and does not replace it but rather it works by managing the existing windows and listening to newly created ones
Even though I learned about drivers back in Uni. It was all theory. your 7-minute long video was the missing piece. Like your video style, not asking for [like , share, comment] just straight to the point with no pauses. Appreciate your hard work. p.s: liked , shared, subed ✅
Video starts "Before you start writing a driver" Wait.. You skipped 6 steps. "Hello", "Subscribe", "Like", "Sponsor", "Basic shit you should know before even clicking the video", and "Thank you". Overall. Nice, short, and concise video. More of this please!
It amazes me how someone can be both a CS geek and cute at the same time I've always been interested in drivers development, but despite having both hardware/electronics and kernel knowledge, I had no idea of where to start for drivers, ESPECIALLY on Windows. Thanks!
I love Your work. Very helpful. You proved us that creating a driver is not a rocket science. Now some humorous stuff. When I saw the driver not stopping from executing, I expected that You'll like a true programmer make fun of it by saying: "OMG, how is this thing stopping?"
I've been wanting to know windows driver dev for years and suddenly you make this video! Thank you. Would you be able to do more tutorials on windows drivers? For example, what about a driver for a virtual floppy disc or something? I'd love to see that.
You explain very well....the delivery is rare ....many videos I've watched...it's rare to get explanations that actually explain things if that makes sense... thank you ♌🙌🏽💗
Wow, this was an amazing video! so clear and so informative without skipping any steps (like sadly so many do) that are "obvious" to people who this every day
Nir, thanks, i don't understand anything about MicroSoft Windows, running Linux since 1994 as wel as some UNICES. Your video however is the first interesting instruction on MicroSoft development i have ever seen. Main interesting thing is that you actualy show whats happening iso obfuscating the whole process using an IDE.
Interesting, after 10 years of linux kernel programming, I never knew that windows also has something akin to dmesg, I also love how short and to the point this was. Kol hakavod.
Toda! It's somewhat similar to dmesg but also different since dmesg shows you the kernel log buffer and the program dbgview just connects as a debugger to the user mode programs/kernel and shows you debug prints (although it does have a feature to log boot)
I've been developing kernelmode driver for anti-cheat system, used assembly on x86 and ObRegisterCallbacks on x64. This is one of the examples. Another example is a device driver as you can access everything from kernel, you can for example ask PCI device directly.
Really fantastic how the algorithm shows something I didn’t think I wanted to learn but now I do. Why though you needed the two voided parameters but wasn’t used on call with null unless I missed something. תודה
That is just to follow the entry point signature according to the docs which specifies that the driver entry gets two parameters, I did not used the information passed into these parameters so I just ignored them. בכיף 🙂
are you using a tiling window manager within windows? or do you just have multiple instances of a vm on different linux workspeces? if so, what tiling window manager are you using? I tried komorebi a few years back but it was pretty early in development back then.
that looks like i3 and it's a nice wm for linux. seeing it on windows is kinda cursed but it got me curious too. anyways maybe give i3 a try, it's pretty easy to setup and configure
The couple cringe comments bashing Vim or C is laughable and makes one question if they even know programming. Great video, most have sought profit by means of their 20 minute diatribes, inefficiently transmitting that thing called knowledge. This is a pleasant contrast.
Nice Would love to see a more detail video like how to comunicate with a driver from ur user program Suppose u are making a device driver, so how would u get data in and out of it with ur user program so u could comunicate with a device on the other side of a driver?
It won't show up in the services application since it is technically not a service but a kernel driver (I ran sc with type= kernel), SC supports also creating and loading drivers and calls them also "services" but you can see it is a driver by looking at the type (with sc query for example) and seeing that it says "KERNEL_DRIVER".
If you just want to play around and learn I would suggest using VirtualBox or VMware or something similar. Then you don't have to restart. Also if you brick your computer like infinite boot loop or something then with VM you just restore previous snapshot and you are ready to go again.
years ago when making my first USB device with microchip PIC i started to get into driver development. guess i got in at the wrong time... when windows decided "remember when we popped up a box asking if you want to install unsigned driver? tough luck; now we won't let you at all" requiring an end-user to do that stupid advanced troubleshooting startup option (for every reboot) completely stifled my hope for making any sort of custom product. thanks MS for keeping us "safe".
Nasty, dude. Rock! You make the NirSoft stuff? Just wondering, with the coincidence in names is all. I like those tools a lot myself and use them since forever. Same with Russinovich's stuff.
Very nice. Things I want to know: - Is the "cl" compiler "Clang" or something else ? - What happens when you crash a driver ? Do you know the procedure to handle that safely or is it a guaranteed blue screen ?
- "cl" is the Visual Studio compiler - unless you tell it to compile only, it also calls the linker after it finishes compiling (in the video I passed to cl flags for the compiler and for the linker) - You can handle exceptions in the driver safely - more information here: learn.microsoft.com/en-us/windows-hardware/drivers/kernel/handling-exceptions
C++ isn't supported in kernel driver development as it uses memory in ways kernel mode drivers can't support due to the nature of memory management in the kernel.
@paradoxicalcat7173 literally usermode functions such as readprocessmemory is streamed from kernel... what you said is basically "i cant read this book, because its in French, and translations are impossible"
I don't quite understand what a driver does. What is the difference from a "normal" program? And isn't a driver a specific program that a hardware uses to communivate with the OS? If so, the driver you created doesn't have any hardaware attached to it. If you could explain to me... thanks!
Thanks :) .inf and .sys serve a different purpose, the sys file is the actual binary of the driver while inf files are textual config files that tell Windows how to install software/drivers
How did you get into driver developement ? Do you have a software engineering background or CS education ? Or more like an embedded systems background and a CE educaction ?
Access and manipulate kernel data structures normally not available in userland, implement file system filters, hook system calls, etc. The term "driver" in Windows tends to more generically refer to kernel modules (in Linux terminology), rather than just stuff for "driving" actual hardware. That said, you do also have some "user-mode drivers" that *are* for driving hardware, and don't run in kernel mode ¯\_(ツ)_/¯
Can you make video of getting your driver signed so you could run it normally? It's something that we all have to do at some point anyways. MS official tutorial can be big and scary at the beginning. It's not clear if it costs money or if if it's possible for free also.
Is there any way to install custom certificates or anything so that we can sign our own drivers? Disabling driver signature verification permanently is becoming very difficult on modern Windows versions if I remember correctly. It used to be easier.
Very nice topic and indeed what I'm really interested in kernel mode drivers, many thanks. However, just being curious, at 05:49, why didn't compiler emit an error eventhough you left one space after "binPath=" then typing the path after this a space in final stage?
That command wasn't a compiler - sc.exe (I believe) stands for Service Control (similar in function to `systemctl` on a Linux system with systemd), and it has some pretty funky and nonstandard command line syntax, including the values for named parameters requiring leading whitespace. Under the hood in Windows, drivers are also "services" too, hence why this was used to register the driver as a service and then subsequently start it.
@@dylanh333 ah, yes, I know it was SC command, sure. Just weird that it completed fine with white space after equals sign (and no enclosing quotation marks for the path, maybe because of the path had no any space, that's another thing) which I wanted to know. Same also happens for "type" parameter in the same command call leaving one space again. Thanks friend.
Thank you! I had to modernize a driver for Win11 to use a 12+ year old printer. It's an amazing Canon from before the ink stuff started getting bananas. I spend $20/year on ink. The only problem I have is that Canon didn't want to modernize the driver! I've only developed for private companies. I know how they lock down IP and have heard that camera companies have gotten super greedy as well. Is it legal for me to release what I have for a win11 driver so others can enjoy it? Bound by US law here, so a bit nervous navigating this IP minefield lol I'm not hiring an attorney for my first FOSSy aspirations 😅
I just tried the guide on Windows 2000 with its own WDK, it compiled pretty well. Unafotunately i couldn't try it since i couldn't add the sevice, as there's no sc command on that version :O
Drivers enable you to operate in kernel level and call kernel functions (for example the function I use in the video DbgPrint is implemented in the kernel) and are useful for a variety of reasons for example adding support for new devices, implementing a file system or just for fun and learning :)
@@nirlichtman cool touchscreen drivers, mouse pad drivers, keyboard drivers. Is it true that without drivers the hardware wouldn't be able to interact with humans?
I don't seem to be seeing the "km" folder. I'm wondering if there was something I had to do beforehand to gain access to that folder. I see a "um" folder, presumably "user mode". EDIT: followed the guide for downloading the SDK and the WDK and we're good now. I guess what was already installed in the directory only included the user mode directory "um".
I'm getting error startservice failed 577, "Windows cannot verify the digital signature for this file". I have checked that I have done the step where you disabled the Windows driver signature enforcement; am I missing a step?
I'm genuinely curious, do U have a video in Wich u make a minimally working driver Wich can be unloaded as well? I'm having trouble making my driver unloadable lol
@@nirlichtmanaw... But do you have any idea why could my driver be failing in the unloading? Maybe I'm not using the proper command, or maybe I forgot to include some header that defines an important function? Or maybe I forgot to link with some library?
0 water, 100% short and useful information. Thanks!
Another episode of: Things I will never do but watch anyway because i like them.
at least I'm not the only one who does this :)))
Oh now i understand why this very very specific video has 250k+ views lol.
@@lucianprl Same here
Imagine 250k Linux driver devs
Actually i kinda go back to win32api because i find Qt apps so damn slow in startup. Having a high perf pc and then those startup time make me think we go backwards. And i hate win32api. but it's probably instant compatible running on linux aswell with WINE emulation.
It is almost comical that when searching for a video about Windows Drivers' Development so far, I was only getting results from 10 years ago that have completely given up on that specific matter so the information on these outdated videos is also minimal, and now, out of nowhere, I bumped into this video on my home page. I'd really love to see more guides concerning drivers' development. That was incredible.
Same
I wasn't even looking, it just popped up
Pavel Yosifovich is another good source. Dont know about his videos, but he's written good low level programming type books, such as device driver dev and theyre current.
so there are no new episodes and this video is more HELLO WORLD than really driver development guide
There's great stuff on msdn
I liked it. I haven't written a driver in 25 years, but I see things have changed. Short but sweet.
Everything to get you started with drivers
I thought "There's no way a sub 8 minute video is going to be enough to be informative for a topic like this." I was completely wrong. This was well paced, straight forward, and better than I could have imagined. This will be the go-to video I send to people who want to start with kernel mode dev but don't understand quite where to get started.
Also: What shell replacement are you using, It looks swell!
Thanks! :) I use a port of Suckless dwm for Windows called dwm-win32, it actually sits on top of the shell and does not replace it but rather it works by managing the existing windows and listening to newly created ones
Do not encourage this fellow...
Next time he will do it in 4 minutes and I wont get it at all 😢
@@nirlichtman Much like xoblite or Kera desktop
Damn, at the beginning I couldn't even tell if it was Linux or Windows with that DWM bar, looks amazing!
dwm-win32 :)
extremely good tutorial, coincise, no pauses, everything planned
incredible content, I would love to see more videos that introduce or expend on more low level concepts. thank you!
expand
Please expand
Yes please, taking these to the next level
I wonder how much knowledge and IQ is needed for making all these steps with such easiness. Thanks for the video!
Even though I learned about drivers back in Uni. It was all theory. your 7-minute long video was the missing piece.
Like your video style, not asking for [like , share, comment] just straight to the point with no pauses.
Appreciate your hard work.
p.s: liked , shared, subed ✅
Thanks :)
Video starts "Before you start writing a driver"
Wait.. You skipped 6 steps. "Hello", "Subscribe", "Like", "Sponsor", "Basic shit you should know before even clicking the video", and "Thank you".
Overall. Nice, short, and concise video. More of this please!
It amazes me how someone can be both a CS geek and cute at the same time
I've always been interested in drivers development, but despite having both hardware/electronics and kernel knowledge, I had no idea of where to start for drivers, ESPECIALLY on Windows. Thanks!
Thanks for the compliment :)
lmao bro got rizzed on a fucking driver tutorial
@@runninggames771 could you believe it? Being weird and coding really bring the most unexpected parts of people
eww gay
@@runninggames771lmaoo
I love Your work. Very helpful.
You proved us that creating a driver is not a rocket science.
Now some humorous stuff. When I saw the driver not stopping from executing, I expected that You'll like a true programmer make fun of it by saying: "OMG, how is this thing stopping?"
Thank you so much Nir, that's the kind of video I enjoyed the most. Short and informative. No BS. Thanks again.
That's quality content I want on RUclips. Great video sir.
Please make more Windows low level programming, this is awesome!
suggestion: tutorials on C windows api
How bout Native API Programming :3 ?
@@ufufuawa401 true :3
@@ufufuawa401 aint no way we making our own csrss.exe 💀
@@ufufuawa401 couldn't agree more. We all need to know how things used to be during good old days
You have the best programming tutorials.👌If everyone made their tutorials as concise and terse RUclips could free half of its storage.😂
Thanks! :)
I absolutely love these. Short but informational.
I've been wanting to know windows driver dev for years and suddenly you make this video! Thank you. Would you be able to do more tutorials on windows drivers? For example, what about a driver for a virtual floppy disc or something? I'd love to see that.
Yes, planning on more driver/kernel level videos, it's a very interesting subject :)
@@nirlichtman would love to watch more on this
You explain very well....the delivery is rare ....many videos I've watched...it's rare to get explanations that actually explain things if that makes sense... thank you ♌🙌🏽💗
Thanks! :)
This is an excellent video! To the point, concise and beautifully simple! Thanks a lot
Finally someone decided to put out on a tutorial on writing windows driver instead of linux
Short and straight to the point 👍. Subscribed.
simple, concise and excellent for learning basic concepts!
Wow, this was an amazing video! so clear and so informative without skipping any steps (like sadly so many do) that are "obvious" to people who this every day
i can't get enough of your content, it's that good!
i feel so lucky that i found this content. just wow
Well done - succinct, hits the important points. Thanks for this!
Nir, thanks, i don't understand anything about MicroSoft Windows, running Linux since 1994 as wel as some UNICES. Your video however is the first interesting instruction on MicroSoft development i have ever seen.
Main interesting thing is that you actualy show whats happening iso obfuscating the whole process using an IDE.
Never seen this explained so succinctly, bravo!
Could you do another tutorial for creating a driver to talk to a USB device?
Thanks! Noted, that is a good idea :)
HELL YEAH! I'll check this out this later today. Thanks, broseph!
It was interesting to watch how to create a simple driver!
Thanks for the video!
Fantastic tutorial and well explained, subscribed and looking forward to more
Interesting, after 10 years of linux kernel programming, I never knew that windows also has something akin to dmesg, I also love how short and to the point this was. Kol hakavod.
Toda! It's somewhat similar to dmesg but also different since dmesg shows you the kernel log buffer and the program dbgview just connects as a debugger to the user mode programs/kernel and shows you debug prints (although it does have a feature to log boot)
Not being a full time programmer, I would like to see a 'Real World' example of what a driver is and what it can do, if that's possible?
Yes, I plan on making a more general video about drivers as well :)
I've been developing kernelmode driver for anti-cheat system, used assembly on x86 and ObRegisterCallbacks on x64. This is one of the examples.
Another example is a device driver as you can access everything from kernel, you can for example ask PCI device directly.
Really fantastic how the algorithm shows something I didn’t think I wanted to learn but now I do. Why though you needed the two voided parameters but wasn’t used on call with null unless I missed something. תודה
That is just to follow the entry point signature according to the docs which specifies that the driver entry gets two parameters, I did not used the information passed into these parameters so I just ignored them.
בכיף 🙂
are you using a tiling window manager within windows? or do you just have multiple instances of a vm on different linux workspeces? if so, what tiling window manager are you using? I tried komorebi a few years back but it was pretty early in development back then.
that looks like i3 and it's a nice wm for linux. seeing it on windows is kinda cursed but it got me curious too. anyways maybe give i3 a try, it's pretty easy to setup and configure
@597das I use a port of Suckless dwm for Windows called dwm-win32, more information on the vid about my setup
Very well made and without wasting time!
I was trying to refresh making microsoft drivers. Good video.
This is exactly the kind of stuff I want to see. Thanks!
הופתעתי ושמחתי באותו זמן לגלות שאתה ישראלי כשראיתי ״שבת, 02 דצמבר״ :)
:)
Watched the video.
Added driver development to my cv 😁
It’s better to debug your driver inside a VM to avoid having to restart your PC every time you get a BSOD
The first time I wrote a Windows driver I didn't BSOD the machine once. Driver dev isn't for you if you can't handle memory.
The couple cringe comments bashing Vim or C is laughable and makes one question if they even know programming.
Great video, most have sought profit by means of their 20 minute diatribes, inefficiently transmitting that thing called knowledge. This is a pleasant contrast.
Driver is complex, thank you 👏👏👏👏
Nice video 👍🏼 Ps: now i understand the beauty of the linux kernel.. way more cooler and easier to write a kernel module 🧑💻
Thanks!
Holy Sh**!...Dam it so precise, so concise tutorial..freaking amazing!!!🤩
Man after looking at C-Drive for 20 years, your title just gave me a brain fart 😂.
You are ANGEL!! Thank you buddy, i suscribed )) thanks
Nice video. I certainly won't write any drivers for Windows but the commands' syntax of Windows shell is quite interesting, although similar to Linux
לא יודע איך הגעתי לפה אבל כל הכבוד לך ובהצלחה עם הערוץ
תודה!
Nice
Would love to see a more detail video like how to comunicate with a driver from ur user program
Suppose u are making a device driver, so how would u get data in and out of it with ur user program so u could comunicate with a device on the other side of a driver?
That is a good idea for a future video, thanks :)
This is great thank you. I never knew how to create services like that. Would that service also show up in Windows services?
It won't show up in the services application since it is technically not a service but a kernel driver (I ran sc with type= kernel), SC supports also creating and loading drivers and calls them also "services" but you can see it is a driver by looking at the type (with sc query for example) and seeing that it says "KERNEL_DRIVER".
If you just want to play around and learn I would suggest using VirtualBox or VMware or something similar. Then you don't have to restart. Also if you brick your computer like infinite boot loop or something then with VM you just restore previous snapshot and you are ready to go again.
years ago when making my first USB device with microchip PIC i started to get into driver development.
guess i got in at the wrong time... when windows decided "remember when we popped up a box asking if you want to install unsigned driver? tough luck; now we won't let you at all"
requiring an end-user to do that stupid advanced troubleshooting startup option (for every reboot) completely stifled my hope for making any sort of custom product. thanks MS for keeping us "safe".
This is super awesome channel. Thank you
The cmd prompt to compile this alone make me cry. The extra steps to make it work put me in fetal position.
Nasty, dude. Rock! You make the NirSoft stuff? Just wondering, with the coincidence in names is all. I like those tools a lot myself and use them since forever. Same with Russinovich's stuff.
NirSoft is not me :)
The precise video about drivers development.
Can you continue and create executable file for driver ?
Very nice. Things I want to know:
- Is the "cl" compiler "Clang" or something else ?
- What happens when you crash a driver ? Do you know the procedure to handle that safely or is it a guaranteed blue screen ?
- "cl" is the Visual Studio compiler - unless you tell it to compile only, it also calls the linker after it finishes compiling (in the video I passed to cl flags for the compiler and for the linker)
- You can handle exceptions in the driver safely - more information here: learn.microsoft.com/en-us/windows-hardware/drivers/kernel/handling-exceptions
Great video. I would just add that you should always wear your seatbelt when writing a driver. Safety first.
would be cool to see c++ version of drivers as well as how to sign a driver (:
just write ur code in c++, cl is a c++ compiler
C++ isn't supported in kernel driver development as it uses memory in ways kernel mode drivers can't support due to the nature of memory management in the kernel.
@@paradoxicalcat7173 tf you talking about, it is supported, i have been writing kernel drivers for a decade now in c++ obviously...
@paradoxicalcat7173 literally usermode functions such as readprocessmemory is streamed from kernel... what you said is basically "i cant read this book, because its in French, and translations are impossible"
did this guy just entered PC godmode? yes!
Awesome, nice and simple. 👍
Excellent and straight to the point, thank you very much! 🙂
Nice one 👍 is that working with hive and hardware abstraction layer ?
nice albums on the wall man, starset and breaking benjamin.
Thanks! 🤘
@@nirlichtman i religiously listen to downplay's saturday album on every saturday, starting with it's saturday song.
@@defaultentertainment697 Nice song! has some early Breaking Benjamin vibes :) I like the original Downplay version of Dark on Me
I don't quite understand what a driver does. What is the difference from a "normal" program? And isn't a driver a specific program that a hardware uses to communivate with the OS? If so, the driver you created doesn't have any hardaware attached to it. If you could explain to me... thanks!
Wait can you explain why .sys and not .inf? Do they serve the same purpose or is there a difference? This is so neat by the way it's super cool
Thanks :) .inf and .sys serve a different purpose, the sys file is the actual binary of the driver while inf files are textual config files that tell Windows how to install software/drivers
Ahh I see I see, thanks!! And again, really cool video I'm such a sucker for low level windows, thanks for making such a concise video about it!!
Klasse Video Vielen Dank, kurz und kompakt ... btw Ich benutze u.a. Visual Studio hauptberuflich ✨
How did you get into driver developement ?
Do you have a software engineering background or CS education ? Or more like an embedded systems background and a CE educaction ?
how to get your driver certified by ms? how much money does it take to do that?
What would you do with a driver though. All hardware drivers are supplied by MS or the vendor, right?
Access and manipulate kernel data structures normally not available in userland, implement file system filters, hook system calls, etc.
The term "driver" in Windows tends to more generically refer to kernel modules (in Linux terminology), rather than just stuff for "driving" actual hardware.
That said, you do also have some "user-mode drivers" that *are* for driving hardware, and don't run in kernel mode ¯\_(ツ)_/¯
@@dylanh333 that is a very clear explanation, thank you 🙏
Can you make video of getting your driver signed so you could run it normally? It's something that we all have to do at some point anyways. MS official tutorial can be big and scary at the beginning. It's not clear if it costs money or if if it's possible for free also.
can you do more driver videos ? Like how to write a simple filesystem driver.
Yes, more driver videos are planned :)
Thank you for this example.
Just have a doubt... How to implement this driver onto a device... cuz today most devices are plug & play...
Is there any way to install custom certificates or anything so that we can sign our own drivers? Disabling driver signature verification permanently is becoming very difficult on modern Windows versions if I remember correctly. It used to be easier.
no intro, no curve ball, just straight nerd-ery
Very nice topic and indeed what I'm really interested in kernel mode drivers, many thanks.
However, just being curious, at 05:49, why didn't compiler emit an error eventhough you left one space after "binPath=" then typing the path after this a space in final stage?
That command wasn't a compiler - sc.exe (I believe) stands for Service Control (similar in function to `systemctl` on a Linux system with systemd), and it has some pretty funky and nonstandard command line syntax, including the values for named parameters requiring leading whitespace.
Under the hood in Windows, drivers are also "services" too, hence why this was used to register the driver as a service and then subsequently start it.
sc just handles services as mentioned by dylanh333. Their is a tool called: srvman from SysProgs. This can show you all drivers are also services.
@@dylanh333 ah, yes, I know it was SC command, sure. Just weird that it completed fine with white space after equals sign (and no enclosing quotation marks for the path, maybe because of the path had no any space, that's another thing) which I wanted to know. Same also happens for "type" parameter in the same command call leaving one space again. Thanks friend.
yo nice video
what window manager do you use?
Thanks! I use a port of Suckless dwm for Windows called dwm-win32, more info on the vid about my setup :)
thank you buddy@@nirlichtman
If "sc create driverName binPath= C:\path\to\driver.sys type= kernel" is giving you an error try using sc.exe
Thank you! I had to modernize a driver for Win11 to use a 12+ year old printer. It's an amazing Canon from before the ink stuff started getting bananas. I spend $20/year on ink. The only problem I have is that Canon didn't want to modernize the driver!
I've only developed for private companies. I know how they lock down IP and have heard that camera companies have gotten super greedy as well.
Is it legal for me to release what I have for a win11 driver so others can enjoy it? Bound by US law here, so a bit nervous navigating this IP minefield lol I'm not hiring an attorney for my first FOSSy aspirations 😅
If you reverse-engineered their code, then no.
Nice video! deserve likes and subs
Subscribed. Can you make a Windows Shell Extension next?
Thanks :) Yes, that's a good idea for the next Windows video!
I used to make all kinds of genetic print drivers for hp laser printers to get around the bloat ware they pushed.
I just tried the guide on Windows 2000 with its own WDK, it compiled pretty well. Unafotunately i couldn't try it since i couldn't add the sevice, as there's no sc command on that version :O
Nice! Yah sc is only included with WinXP or higher but maybe you can try loading it with the registry
Good video. Very clear
Brilliant tutorial once again, but what are drivers exacly useful for?
Drivers enable you to operate in kernel level and call kernel functions (for example the function I use in the video DbgPrint is implemented in the kernel) and are useful for a variety of reasons for example adding support for new devices, implementing a file system or just for fun and learning :)
@@nirlichtman thank you :)
@@nirlichtman cool touchscreen drivers, mouse pad drivers, keyboard drivers.
Is it true that without drivers the hardware wouldn't be able to interact with humans?
I like your video!
But what is that bar on the top? It looks like dwm but it looks like your using windows?!
Thanks! I am using a port of Suckless dwm for Windows, more info on the vid about my setup :)
I don't seem to be seeing the "km" folder. I'm wondering if there was something I had to do beforehand to gain access to that folder. I see a "um" folder, presumably "user mode".
EDIT: followed the guide for downloading the SDK and the WDK and we're good now.
I guess what was already installed in the directory only included the user mode directory "um".
Great work brother
Can't you do it in visual studio? That's the whole purpose I prefer lattepanda over raspberry pi.
Show us how to make a agent next!
Custom homemade driver instructions for Radeon 6900XT when?
Im curious if you've heard of Pavel Yosifovich? I think youd find his works interesting
Yes :)
I'm getting error startservice failed 577, "Windows cannot verify the digital signature for this file".
I have checked that I have done the step where you disabled the Windows driver signature enforcement; am I missing a step?
awesome video!
I'm genuinely curious, do U have a video in Wich u make a minimally working driver Wich can be unloaded as well? I'm having trouble making my driver unloadable lol
Not yet :)
@@nirlichtmanaw... But do you have any idea why could my driver be failing in the unloading? Maybe I'm not using the proper command, or maybe I forgot to include some header that defines an important function? Or maybe I forgot to link with some library?