[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[ale] MintWifi
- Subject: [ale] MintWifi
- From: jknapka at kneuro.net (JK)
- Date: Wed, 24 Jan 2007 13:51:54 -0700
- In-reply-to: <1169666295.1246.20.camel@pepper>
- References: <[email protected]> <1169664159.1246.12.camel@pepper> <[email protected]> <1169666295.1246.20.camel@pepper>
Michael B. Trausch wrote:
> On Wed, 2007-01-24 at 14:05 -0500, Paul Cartwright wrote:
>
>
>>On Wednesday 24 January 2007 13:42, Michael B. Trausch wrote:
>>
>>>I would try downloading the Windows driver for the card that you have
>>>and see if you can install it using the NDIS-Gtk front-end program,
>>>which you can find in "System?Administration?Windows Wireless Drivers"
>>
>>I saw that menu, but it didn't make sense to me..I did try to add one, but I
>>didn't have the .INF file. I'll try to download that driver.. I probably have
>>it on my XP partition...
>
>
>
> Even if you don't, the INF file is distributed with the driver itself.
> As to why it's necessary, well... ask Microsoft, I guess. :-) I can't
> think of a reason that such a thing should be necessary, since the
> driver metadata should be available within the (theoretically signed)
> driver file itself.
IIRC NDIS is a generic driver; the .INF file tells the
NDIS driver how to talk to a particular card. That
is, there isn't a separate binary driver for each card;
there's a single binary driver, which reads .INF files
in order to understand the particulars of each card.
-- JK