Re: NT and ISR
U have right mami_hacky !!!
may be doing this can have negative effects on the operation of the entire system...
Using this trick is a severe violation of NT system IO space security.
For example to use "outportb" function, you dont need a port "handle" (obtained normaly via an CreateFile API invokation), so it's posible for 2 or more aplication to use the paralel port in the same time!!
Imagine what a nightmare can result if someone want to print a file in same time U are testing your board using the same paralel port!!!
In fact the handle for a port can be viewed like a MUTEX object (mutual-exclusive) to acces an shared resource.
If U own the mutex, U can work with the port. When the job is done U release the mutex (via CloseFile) so other users are able to claim the mutex to make their own work.
The only way to comunicate directly to hardware in NT is via a device driver.
Writing a device driver for serial port is far beyond my knowledges.
I prefer to use allready writen device drivers to comunicate with them via API functions, but i dont know if they can answer nada's problem.
Those functions are documented in DDK (not in Win32 API).