Re: Ke386SetIoAccessMap and WindowsXP x64
- From: "Calvin Guan" <hguan@xxxxxxxxxxxxxxxxxxx>
- Date: Tue, 12 Jul 2005 11:22:19 -0700
No surprise at all, as its name suggested, it's 386 specific.
You need a kernel mode driver to access the hardware instead of accessing it
from UM directly.
--
Calvin Guan (Windows DDK MVP)
Staff SW Engineer NetXtreme MINIPORT
Broadcom Corp. Irvine, CA
www.broadcom.com
"Slavo Tomascik" <ssutaz@xxxxxxxxx> wrote in message
news:OfnThJvhFHA.1204@xxxxxxxxxxxxxxxxxxxxxxx
> Hello all,
>
> in my driver I use Ke386SetIoAccessMap and Ke386IoSetAccessProcess for
> direct access to LPT ports. I try compile driver for XP x64, and
> surprise - undocumented functions from previous systems versions are not
> available.
> Know anybody some replacement (or another solution) for that functions?
> I need direct access to ports from my application to fulfill timing
> requirements.
>
> With best regards,
> Slavo Tomascik
> ssutaz@xxxxxxxxx
.
- References:
- Ke386SetIoAccessMap and WindowsXP x64
- From: Slavo Tomascik
- Ke386SetIoAccessMap and WindowsXP x64
- Prev by Date: Deciphering FSCTL_GET_VOLUME_BITMAP cluster information
- Next by Date: Access denied for a regular user, how do I change permissions for a service?
- Previous by thread: Re: Ke386SetIoAccessMap and WindowsXP x64
- Next by thread: Help: rename Microsoft NDISPROT driver
- Index(es):
Relevant Pages
|