From: "Andy Willis" <os2-wireless_users@2rosenthals.com>
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:content-type:content-transfer-encoding;
        b=lgSkEInnHhz8fYXIY0kzOnxARPbpK0OzmiWeydHJu4LM3KEDf6dCMnApBeLtbw2l9C
         UiawzatALMWcEpVq3gKIyN2AKoE5Jg0sZ3oXFc9QtVLInX/9QVPM1NUFYf2i44Yomtfg
         xy3CKL6bWcAwGxiaI82Ics9u05QxegIdMf+Dk=
Message-ID: <4B7415F5.5010408@gmail.com>
Date: Thu, 11 Feb 2010 07:36:37 -0700
User-Agent: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.9.1.4) Gecko/20091028 SeaMonkey/2.0 not(Firefox3.7)
MIME-Version: 1.0
To: OS/2 Wireless Users Mailing List <os2-wireless_users@2rosenthals.com>
Subject: Re: [OS2Wireless] Driver Problem
References: <list-2202710@2rosenthals.com>
In-Reply-To: <list-2202710@2rosenthals.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Thomas Dennis wrote:
> Andy Willis wrote:
>> Lewis G Rosenthal wrote:
>>> Hi, Thomas...
>>>
>>> On 02/10/10 03:42 pm, Thomas Dennis thus wrote :
>>>> Hi:
>>>> I'm trying to get my Laptop to work with eCS 2.0 rc7.
>>>> Since my Laptop is an older model I'm using a PCMCIA
>>>> plug-in card. A D-Link DWA 645. The chipset is suppose
>>>> to an Atheros but I haven't been able to establish it
>>>> as a fact.
>>>> I did download two s/w packages from Netlabs that are
>>>> for the Atheros chipset but I have not been able to
>>>> install them. The problem may be due to one of the files being
>>>> saddled with the DOS name regulation 8:3. I have
>>>> renamed it correctly as it is on the Internet, but
>>>> one of the eCS 2.0 rc7 widgets keeps showing the
>>>> DOS file name.
>>>> Like: GENMAC220_ATHEROS.WPI
>>>> GENMAC~1.WPI
>>>> Where it's getting this data from I don't know.
>>>> WarpIN, which came with eCS 2.0, gives me an error
>>>> message saying that:
>>>> "GenMac could not find any network interface card in
>>>> the system!"
>>>> Can anybody tell me what the problem is?
>>>> Am I doing something wrong or left something out that
>>>> needs to be included?
>>> You need to install Veit's cbenable driver to get GenMAC to see the card
>>> and turn it on. Please see my other post of 2/3 @ 8:25pm EST. Without
>>> cbenable, there's no "glue" to bind the card slots to the PCI bus
>>> (insofar as GenMAC is concerned), so it doesn't see the card.
>>>
>>> Also, in that same message, I asked you to provide the PCI ID string of
>>> the card, so that we could be certain of the chipset. If you need
>>> assistance with this step of the process, please advise.
>>>
>>> You should probably review
>>> http://article.gmane.org/gmane.org.netlabs.genmac.user/1187 , et seq.
>>>
>> One thing to note: cbenable does not work with ACPI.
>> I've had success with the following:
>>
>> REM [PCCARD section
>> DEVICE=D:\UTILS\THINKPAD\VPCMCIA.SYS
>> DEVICE=D:\UTILS\THINKPAD\PCMSSDIF.SYS
>> REM DEVICE=D:\UTILS\THINKPAD\PCM2SRAM.SYS
>> REM DEVICE=D:\UTILS\THINKPAD\FLSH2MTD.SYS
>> REM DEVICE=D:\UTILS\THINKPAD\PCM2FLSH.SYS
>> BASEDEV=PCMCIA.SYS /R:500
>> BASEDEV=IBM2SS14.SYS
>> rem BASEDEV=sspcic.sys /VS:auto /E /AP:on
>> BASEDEV=AUTODRV2.SYS
>> REM BASEDEV=PCM2ATA.ADD /S:2 /!DM /NOBEEP
>> BASEDEV=PCM2ATA.ADD /S:2 /NOBEEP
>> REM BASEDEV=OS2PCARD.DMD
>> BASEDEV=CBENABLE.SYS * * 0 0 PCIIRQ
>> BASEDEV=OEMHLP2.SYS
>> DEVICE=D:\OS2\$ICPMOS2.SYS /G
>>
>> sspcic - Apsoft driver does not work for this configuration either.
>> eCS 2.0 rc7 should have the proper pccard support level, previous
>> releases did not.
>> Until cbenable is in place, the pccard will not show with pci.exe.
>> Not much more involved really other than, if once you have all drivers
>> in place and if it hangs on boot at or around netbind then wait for a
>> short while but if it doesn't continue then you can pull the pccard
>> and the boot will continue but the card will not function.
>> Andy
> Andy:
> If I understand you correctly you are suggesting that I add the REM[PCCARD
> section to my Config.sys file, and double check that the s/w mentioned
> is also
> on my PC somewhere, is that correct?
>
You should have most of that already in place I would suspect.  If not, 
then you will need to make sure that the socket services support was 
installed.  I copied the entire section here so that you could see the 
order for where cbenable was placed in relation to the socket services 
drivers.  Normally I would actually have PCM2ATA.ADD REMed out as well 
but I have been recently playing with a pcmcia - IDE adapter.
The cbenable line itself is pulled from the cbenable.txt file that 
should be in the distribution.  THe second 0 corresponds to the card 
slot.  cbenable enumerates as 0 and 1 while the Card Director calls them 
1 and 2.  On my T42 the 0 is the top slot.
Andy