That .BIN file sounds like that - yeah... I'm seeing this confusion increasingly as we get more long-time windows users making the switch. Previously I mostly saw geeks (who are used to changing paradigms) and computer novices (unfamiliar with anything OS related).
But maybe I've just been lucky.
To this kind of experienced windows user - when something don't go it means a driver is missing. To get a driver, you go to the website of the computer or HW manufacturer and search it. Maybe you google for the driver.
Trouble is, many third-party driver sites include the word "linux" someplace on their pages ... so you can easily get false-positive hits for "linux driver".
A newbie can be forgiven for getting confused and trying to install the windows binary. I mean - we don't even have .exe files, right? Who would figure, after uing (say) XP or so many years that an OS would actually supply most drivers built-in, or that someone would have written non-intrusive software to manage the rest of the software stuff for you?
This is where getting hold of a local LUG can really pay off for the newcomer. Attend an installfest. Also why we have to keep running them.
And it's another reason to put your location in your profile - there is a good chance someone knows how to contact your local lug
Mostly it's just reassurance - you are not going mad and it does make sence.
I sympathise from the other direction... I've used a windows box so seldom now that I've mostly forgotten how they work. When I do have occasion to rediscover - I am struck by what kinds of things end up being normal.