From: "R. G. Newbury" Received: from mxout4.mailhop.org ([63.208.196.168] verified) by 2rosenthals.com (CommuniGate Pro SMTP 5.0.9) with ESMTP id 269803 for os2-wireless_users@2rosenthals.com; Fri, 04 Aug 2006 10:41:37 -0400 Received: from mxin2.mailhop.org ([63.208.196.176]) by mxout4.mailhop.org with esmtp (Exim 4.51) id 1G90ri-0001WA-HM for os2-wireless_users@2rosenthals.com; Fri, 04 Aug 2006 10:41:31 -0400 Received: from tomts35.bellnexxia.net ([209.226.175.109] helo=tomts35-srv.bellnexxia.net) by mxin2.mailhop.org with esmtp (Exim 4.51) id 1G90ri-0004Pw-DR for os2-wireless_users@2rosenthals.com; Fri, 04 Aug 2006 10:41:30 -0400 Received: from [192.168.1.97] ([67.70.60.19]) by tomts35-srv.bellnexxia.net (InterMail vM.5.01.06.13 201-253-122-130-113-20050324) with ESMTP id <20060804144129.NRTX14422.tomts35-srv.bellnexxia.net@[192.168.1.97]> for ; Fri, 4 Aug 2006 10:41:29 -0400 Message-ID: <44D35C98.7080400@mandamus.org> Date: Fri, 04 Aug 2006 10:41:28 -0400 Reply-To: newbury@mandamus.org User-Agent: Thunderbird 1.5.0.2 (X11/20060501) MIME-Version: 1.0 To: OS/2 Wireless Users Mailing List Subject: Re: [OS2Wireless]Re: PCMCIA help References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mail-Handler: MailHop by DynDNS X-Spam-Score: -2.6 (--) I've just had a quick look at the os2warp.be site. The PCMCIA chipset page is, inadvertently, quite misleading. There should be a large caveat before the chipset/driver listing pointing out that, at least in the case of Cardbus NIC's, that no driver or socket services are required. The user should go to the NICPAK page FIRST and search for their PC card. For example, the Xircom Realport cards are listed in NICPAK. I first reported this on the os2-warp list, probably 8 years ago! Geoff Lewis G Rosenthal wrote: > On 08/03/06 05:02 pm, R. G. Newbury thus wrote : >> Lewis G Rosenthal wrote: >>> On 08/03/06 11:01 am, R. G. Newbury thus wrote : >>>> John Poltorak wrote: >>>>> I'd like to try and get a PCMCIA card working on a DELL Inspiron 6000 >>>>> laptop. Has anyone tried this? >>>>> >>>>> AIUI it has a RICOH RL5c476 Cardbus controller according to a PCI >>>>> scanner >>>>> I ran. Which Socket services driver will support that? >>>>> >>>>> >>>> This is a Cardbus card You do not need Socket services. An NDIS >>>> driver should do, exactly as if the card were a PCI card. >>>> >>>> I use a Xircom Realport Cardbus card in my Thinkpad 600E and the >>>> required line is 'device=c:\ibmcom\macs\cbendis.os2' >>>> >>>> (Together with the usual other ibmcom stuff, of course). >>>> >>> Geoff, AFAIK, this is indeed *not* a CardBUS card. Of course, if >>> you're using the same chipset along with a CardBUS card, that would >>> make my statement moot... >>> >>> Are you sure that cbendis.os2 is not just a point enabler driver, >>> which would mitigate the need for socket services? >> >> OK i guess there are 3 choices: >> If it is a 16 bit card, then you need socket services; >> If it is a Cardbus card but the controller chipset does not support >> 32bit cardbus, then it probably will work through socket services. >> ISTR that cardbus can gracefully downgrade to 16bit, but that may be >> wrong. > CardBUS is fully backward compatible with 16-bit PCMCIA. >> Finally, if the chipset supports full 32bit cardbus services then it >> appears as a pci bus to the system, and cardbus cards (well, nic's at >> least) appear as pci cards. >> > Yep, this is my understanding, as well. >> As far as I can tell the Realport is a full cardbus services card. >> Socket services does not 'see' anything to do with the card itself. SS >> will report that the slot is in use but nothing else. That implies >> that it is more than just a point enabled card (althouhg it may be that >> too). These cards among others will work with Veit's special programs, >> such as cbenable which I doubt a non-full-cardbus card would do. >> > Yes, this makes sense. Perhaps, then, the information at os2warp.be is > in need of correction. Thanks for following up and clarifying, Geoff. >