PCMCIA ports can be programmed to apper at a range of IO and IRQs=20
This is determined by a combination of the CIS information in the card, =
and the configuration of the
driver.
Dos drivers are usually split into socket services, which are specific to=
 the PCMCIA controller, and
card services, which provide all the higher-level funcitons. The latter =
use a lot of memory, and
require a correctly formatted CIS (structure in ROM in the PCMCIA card) .

=46or your application, you probably only need the socket services =
module, and I'm fairly sure you can
get away without a ROM in the card if you drive it this way, and you can =
simply tell socket services
where you want the socket mapped in I/O space and it will do it. You can =
then talk to the card
direct.

Due the the bloatedness of typical DOS card services, some devices like =
modems used to come with
'point enabler' utilities which talk to socket services direct to map the=
  device into IO space.=20

The downside is you need to know which socket you want to use, and =
handling of card removal can be
less pretty - often not an issue.=20

I have some Turbo Pascal source for IO enablers using both card services =
and socket services which
you can have if you want, but you also really need the parts of the =
PCMCIA spec that deal with this.

=20

On Thu, 19 Dec 2002 14:34:35 +0100, you wrote:

>Hi to all PIC'ers.
>I have got the following problem. I have got an old laptop (486) which I=
 would
>like to use as a peripherial I/O controller.  The only place I can =
connect
>to the PC hardware is via PCMCIA slot. What low level I/O  resources are
>allocated to PCMCIA? (I/O addresses, interrupts etc) Are those resources
>identical on all machines (like LPT and COM ports are)?. Are there any
>ROM BIOS routines available? My software is based on a customised DOS.
>I write all software and drivers myself.

--
http://www.piclist.com hint: The list server can filter out subtopics
(like ads or off topics) for you. See http://www.piclist.com/#topics