From: "Steven Levine" Received: from mxout4.mailhop.org ([63.208.196.168] verified) by 2rosenthals.com (CommuniGate Pro SMTP 5.0.9) with ESMTP id 271878 for os2-wireless_users@2rosenthals.com; Sat, 05 Aug 2006 14:15:37 -0400 Received: from mxin1.mailhop.org ([63.208.196.175]) by mxout4.mailhop.org with esmtp (Exim 4.51) id 1G9QgK-0006LT-Jo for os2-wireless_users@2rosenthals.com; Sat, 05 Aug 2006 14:15:29 -0400 Received: from pop-canoe.atl.sa.earthlink.net ([207.69.195.66]) by mxin1.mailhop.org with esmtp (Exim 4.51) id 1G9QgF-0008AO-9N for os2-wireless_users@2rosenthals.com; Sat, 05 Aug 2006 14:15:23 -0400 Received: from user-vcaujte.dsl.mindspring.com ([216.175.79.174] helo=slamain) by pop-canoe.atl.sa.earthlink.net with smtp (Exim 3.36 #1) id 1G9Qg9-0001PY-00 for os2-wireless_users@2rosenthals.com; Sat, 05 Aug 2006 14:15:17 -0400 Reply-to: "Steven Levine" Date: Sat, 05 Aug 2006 10:32:24 -0700 To: "OS/2 Wireless Users Mailing List" In-Reply-To: Subject: Re: [OS2Wireless]Re: PCMCIA help X-Mailer: MR/2 Internet Cruiser Edition for OS/2 v2.67/60 Message-Id: X-Mail-Handler: MailHop by DynDNS X-Spam-Score: -2.5 (--) In , on 08/05/06 at 01:33 AM, "John Poltorak" said: Hi John, >Yes, there looks to be quite a lot of useful stuff, but nowhere to ask >questions. You can ask here. >I get the impression that my controller card is supported out of the box >with Warp 4, but it doesn't work. I'd like to know what I'm doing wrong. In the hope of not muddling things worse than they already are. There are two kinds of PCCard interfaces. The older 16-bit PCMCIA interface and the current Cardbus interface, which is usually 32-bit. There are two kinds of PCCard drivers. Socket services compliant and point enabled. Socket services compliant drivers require a socket services driver (i.e. IBM2SS14.SYS etc.). Point enabled drivers do not require a socket services driver. They contain code to power up the PCCard and assign fixed resources. They rarely contain APM support, so typically you can not suspend and resume. Some drivers include code for both Socket Services support and point enabled use. A given point enabled driver written in the days of 16-bit PCMCIA sockets may or may not work in a Cardbus socket. We do not live in a perfect world. First thing you need to do is find a driver for the Token Ring card. Next you need to figure out if the driver requires socket services or if it is point enabled. If it is only point enabled, you may be out of luck. The driver will either work or not. If the driver is point enabled only and the driver does not work, your next task is try Veit's cbenable. If may be able to power up the socket sufficiently for the driver to work. If the driver is Socket Services compliant, you need to track down a Socket Services driver for your Cardbus socket controller (i.e. the Ricoh). It may or may not exist. My sources say you need to use the Socket Services driver for the Lattitude CPX, C600 or C610 models. This is at the Dell site. As I often tell you, you would really help yourself if you provided more specifics without being asked. Exactly which token ring card are you trying to use and which PCCard driver are you using with it? A link to the driver would be good. The NIFs and readmes ofthen provide useful clues. Steven -- ---------------------------------------------------------------------- "Steven Levine" MR2/ICE 2.67 #10183 Warp/eCS/DIY/14.103a_W4 www.scoug.com irc.fyrelizard.com #scoug (Wed 7pm PST) ----------------------------------------------------------------------