From: "Lewis G Rosenthal" Received: from [192.168.100.201] (account lgrosenthal HELO [192.168.200.10]) by 2rosenthals.com (CommuniGate Pro SMTP 5.1.16) with ESMTPSA id 2240229 for os2-wireless_users@2rosenthals.com; Mon, 22 Feb 2010 16:59:54 -0500 Message-ID: <4B82FE59.70507@2rosenthals.com> Date: Mon, 22 Feb 2010 16:59:53 -0500 Organization: Rosenthal & Rosenthal, LLC User-Agent: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.8.1.23) Gecko/20090827 MultiZilla/1.8.3.5g SeaMonkey/1.1.18 (PmW) MIME-Version: 1.0 To: OS/2 Wireless Users Mailing List Subject: Re: [OS2Wireless] GenMac driver References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sorry for the delay; turning out to be a busy day... On 02/22/10 12:47 pm, Thomas Dennis thus wrote : > Lewis G Rosenthal wrote: >> Hi, Thomas... >> >> Thomas Dennis wrote: >>> Lewis G Rosenthal wrote: >>>> >>>> >>>> On 02/21/10 03:32 am, Thomas Dennis thus wrote : >>>>> Hi All: >>>>> I must have done something right because I now get the >>>>> GenMac Sign-on message. But there is a small detail that >>>>> I haven't been able to correct. >>>>> And that's a green blinking notice that: >>>>> "No valid hardware found for (WRND32$)" >>> What is this section in the PROTOCOL.ini [W8086x4224_NIF] >>> designed for. It looks like it would be something for an Intel chip. >>> I have no such entry in my PROTOCOL.ini. >> Nor should you. Indeed, that is the entry for *my* Intel chip. Yours >> will be something like [W168Cx001C_NIF] for an Atheros AR5008, for >> example. >>> Is that due to the fact that the Chip Set in the D-Link >>> card is from Atheros? >> Yes. The 168C is the manufacturer code, and the 001C is the model >> code. Put them together (168C:001C) and you have a PCI ID string. >> Each PCI device has a (hopefully) unique ID string. >> Because our cards are different. These refer to the filenames of the >> Windows driver files located in the wrapper directory. >>> From where do these two entries originate? >>> If my understanding is correct than these two files should >>> be in x:\IBMCOM\MACS but these files aren't there. >> No. Only the GenMAC nif and GENM32W.OS2 driver will be there. The >> wrapper files stay under the GenMAC tree. >> >> Your wrapper nif is also incorrect. Under the FILE section, it should >> read: >> >> [FILE] >> Name = GENM32W.OS2 >> Path = IBMCOM\MACS >> >>> Or are these two from Windows? >> Yes. You need to put them in your wrapper directory. > > The Windows drivers for the D-Link/AR5008 card are > "ar5416.sys" and "net5416.inf". So I see. You still have an error in your PROTOCOL.INI file: [W168CX001C] DriverName = WRND32$ VENDOR = 0x168C DEVICE = 0x001C NDIS_SYS = "ar5416.sys" NDIS_INF = "net5416.nif" SSID = "ANY" DEBUGLEVEL = "NONE" OPTIONS = "UNSUPPORTED" The section name should correspond to what's up at the top, so it should be: [W168CX001C_NIF] This is why you should probably have put the files in place and let MPTS edit the file for you. No matter; it should be right when you make this change (unless someone else on the list has picked up on something I missed?)... The nif looks fine. > Question. > Where should I put these files so the program can > find them? > I thought I covered this in my presentation, but perhaps I didn't create a slide for it... Anyway, follow along: To answer your previous question (and then this one, by extension), somewhere on your drive, you have a "genmac" directory. This is either under the root of your boot drive or under \ecs\system. Starting from there, you should have a directory tree (what I referred to earlier as the "GenMAC tree") which looks like this: genmac\ bin\ driver\ WRAPPER_168C_001C\ <- you need to create this (obviously without the trailing "\"!); this is the wrapper directory inf\ nif\ Copy the Win32 driver & inf to the newly created genmac\driver\WRAPPER_168C_001C directory. Copy the nif you edited into the nif directory (and your \IBMCOM\PROTOCOL\MACS directory, if you like). Your CONFIG.SYS should be ready to go, as GENM32W.OS2 will pick up the Win32 driver it is supposed to load from the entries in PROTOCOL.INI. Remember that there is NO GUARANTY that this will work. I do not know of anyone who has tried the AR5008 chipset, so we're all anxiously awaiting news. GL -- Lewis ------------------------------------------------------------- Lewis G Rosenthal, CNA, CLP, CLE Rosenthal & Rosenthal, LLC www.2rosenthals.com Need a managed Wi-Fi hotspot? www.hautspot.com visit my IT blog www.2rosenthals.net/wordpress -------------------------------------------------------------