Originally Posted by Kubatko
nothing after typing
I still have to type modprobe ndiswrapper after I start my computer,
It turns out to be pointless to run all three of those commands one after the other (which your post implied). The first two completely overwrite the existing ndiswrapper file in /etc/modprobe.d, and the third one will issue some error messages before appending the traditional alias line to the existing ndiswrapper file (creating a mess there IMO). If you did
do that, then one of them might have worked but you might not know it. See what I mean? The idea, IMO, is to find the one that works and use only it. So, to find that one, I would try running all three of them again but one at a time followed by a reboot after each one. And start with the -m option so it will be overwritten by one of the others if it doesn't work. When one of them works, then stop.
Next, if that still didn't help, try the above again but before rebooting each time, rename the /etc/modprobe.d/ndiswrapper file that gets created to have a .conf ending. That's a relatively new requirement, and I am not sure if ndiswrapper has kept up with things like that. In fact, I doubt that anyone is maintaining ndiswrapper at all now.
Last, if nothing above helped, then enter your modprobe ndiswrapper command in your /etc/rc.local file.
P.S.: A note about those three ndiswrapper options... The -m option is the original one. It creates a file named /etc/modprobe.d/ndiswrapper with a single alias line in it. We used that for years. Then some time later, those other two suddenly appeared with very little fanfare and even less explanation. The ndiswrapper --help command tells basically all that I know about them. I looked for a long time for something about them and found nothing. Not even any developer email banter. So I just experimented with them. When one worked, I quit and promptly put the whole affair out of my mind. Good luck with it.