Re: Ke386SetIoAccessMap and WindowsXP x64

Tech-Archive recommends: Fix windows errors by optimizing your registry

Neill Clift [MSFT] wrote:
"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.



None of this user mode access to privileged instructions stuff is available
on the X64 platform. This is stone age stuff to be honest. It just
doesn't make sense to have applications talking to h/w directly in a
modern OS. Too many things you can't control from user mode.
Issue I/O requests to drivers for hardware instead.



I know the rules of the modern OS. The demands of the real life are against rules - stupid device which performance is dependent on the communication speed of LPT port (and which communication protocol doesn't allow to be serialized to increase performance). I have developed device driver, but overhead costs of I/O request (and of course boss' decision) force stone age solution. Anyway, thank you for your time.

Slavo Tomascik
ssutaz@xxxxxxxxx
.

Relevant Pages

  • Re: Ke386SetIoAccessMap and WindowsXP x64
    ... > direct access to LPT ports. ... I try compile driver for XP x64, ... > I need direct access to ports from my application to fulfill timing ... on the X64 platform. ...
    (microsoft.public.development.device.drivers)
  • Re: Virtual Device Driver Basics
    ... and then acts as a generic PCSC driver to any of these devices. ... because they also want direct access to the hardware from user mode.. ...
    (microsoft.public.development.device.drivers)
  • [PATCH] Fix "deprecated" typoes.
    ... Direct access to SA1111 INTPOL is depreciated. ... This is the old driver. ... use the sethdlc utility available in the standard ax25 ...
    (Linux-Kernel)
  • Re: Ke386SetIoAccessMap and WindowsXP x64
    ... 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 ... > surprise - undocumented functions from previous systems versions are not ... > I need direct access to ports from my application to fulfill timing ...
    (microsoft.public.development.device.drivers)
  • Ke386SetIoAccessMap and WindowsXP x64
    ... 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. ... I need direct access to ports from my application to fulfill timing requirements. ...
    (microsoft.public.development.device.drivers)