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: [ECS] Win2k and I/O Port Byte
Dario Greggio
Tue, 01 Aug 2000 00:39:55 +0200

Scott Danks wrote:
> 
> I'm just hoping that there is a way to turn off the way that windows 2000 stops the
inp and outp functions from being blocked.  Otherwise we might have to all get together
and find a suitable I/O board that Mark would be willing to write ECS to talk to the
drivers of.

No, I don't think you can. It's part of hardware abstraction proper of
NT/2000. It's consequence of the fact you can run NT on processors other
than Intel or even on multiprocessor boards.
But someone (possibly I) could write a driver to simply do inp/outp and
then using calls to this driver would be the same as performing assembly
instruction.
 
> . . . . Or... I... GUESS... I... could... go... back... to... Windows... 98.

This, for sure, is the best thing! I can't see a good reason to move to
NT or 2000. New hardware or multimedia or video come out first for Win98
and then for NT. OS may be a little less stable, but if your application
works well you won't get too many troubles. And you don't need all that
network security: you need to run a single task app with maybe one or
two Winamps and internet DUNs.
For what concerns system hangs, I think an hardware watchdog will be
enough to make sure the system is always up and running.

-- 
Ciao,
Dario
--
ADPM Synthesis sas - Torino
--
http://www.geocities.com/adpm99



  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
.