ECS-L Home Automation and Security Archives
  learn more | view messages for this month | NetBloc® | terms of use | search

Google
 


  subject (prev) or (next) | time (prev) or (next) | author (prev) or (next) | view more subjects

Subject:
From:
Date:
RE: RE: [ECS] Win2k and I/O Port Byte
Dan Hoehnen
Mon, 31 Jul 2000 11:32:24 -0400

Scott,

Your guess is right.  Windows 2000 is just like NT in that programs are not
allowed to access hardware directly.  I assume Mark is using the inp and
outp (or similar functions) for this functionality.  If so, then they will
not work on NT or 2000 from ECS (or any other program).  Typically, you
would have ECS talk to a device driver.  The device driver runs at the
kernel level and has access to hardware and so the device driver CAN use the
inp and outp functions.

Dan



> I upgraded my system to windows2000 over the weekend, and
> immediately when I opened ecs with my current ecs.cfg, windows
> said it caused an "Error" and was shutting it down.  I am using
> an I/O Card from Quatech (PCB-721) and it has 72 inputs / outputs
> using a 8255 (PIO) chip.  I talk to it by setting the base to
> 300h (768d) and then consective memory locations are used to set
> the control (input oroutput) and then read the next memory
> location and that is the way to see what inputs are on.   SO, I
> found that If I put in the ecs.cfg an item of type I/O port byte
> and the location is 768, when it initializes I get this windows
> error.  Does Windows protect this area of memory from letting
> programs write to it like NT does?  I really dont think I'm doing
> anything wrong.  Thanks for any help.
>
> Scott Danks.
>
>
>


  subject (prev) or (next) | time (prev) or (next) | author (prev) or (next) | view more subjects




Services provided by [NetBloc]®! NetBloc Solutions Inc.
Terms of use. Indexing software (c) 1999 Lin-De, Inc
.