Not being a commandline guy, I would install ndisgtk which gives ndiswrapper a
GUI and it takes care of the background stuff such as chmod and making the
Windows driver start when you boot the computer.

The inf file may or may not refer to your specific chip by name. However, it
should work and if it doesn't you can do it over with the GUI approach. The
commandline approach can be daunting because you need to type precisely, use the
exact syntax and must know paths which many newbies don't. That's why I would
advise people to install ndiswrapper, plus utils and the gtk GUI. Linux purists
would say, to use the commandline, but it isn't realistic for many people and it
often is more work in the end as often need help from others by searching
forums, you must be precise and it usually involves more steps. Besides, I have
a lousy memory, especially for things I use only once in a blue moon. I often
have to go to the net for help with commandline stuff, but with the GUI I can do
it in one step by only reading the onscreen prompts. For me I know what works.

With the GUI, you find the inf file and the rest is done for you.