Index
> OS Construction > Useful In and out ports. |
| Author |
|
|
LocoDelAssembly 08 Jan 2008, 23:52
On Windows? Note that NT-based kernels (NT, 2000, XP, 2003, Vista), doesn't allow the applications to access I/O space and you need a driver (google GiveIO).
For a list of ports you can download Part D of the Ralf Brown's interrupt list here and check Ports.* files inside the ZIP. Also check OS Construction forum that can have more info around this (or at least useful links with this information). |
|||
08 Jan 2008, 23:52 |
|
|
Pixelator 09 Jan 2008, 03:40
thank you for the link, but im not quite sure what you mean by by the I/O space thing. I just want to get info from the keyboard.
|
|||
|
09 Jan 2008, 03:40 |
|
|
LocoDelAssembly 09 Jan 2008, 04:01
What kind of info? Isn't enough Windows API?
|
|||
|
09 Jan 2008, 04:01 |
|
|
Pixelator 09 Jan 2008, 15:46
like what key is pressed...
|
|||
|
09 Jan 2008, 15:46 |
|
|
f0dder 09 Jan 2008, 15:51
Pixelator, make up your mind - do you want to do this under Windows, or do you want to do it with Port I/O? If it's the former, you have to drop using ports. If it's the latter, this thread was posted in the wrong section.
Please state your intents, then we can move forward to the solution  |
|||
|
09 Jan 2008, 15:51 |
|
|
Pixelator 09 Jan 2008, 15:59
Quote:
I am extremely new and not used to this style of programming (i come from Dark Basic) so i don't know the difference. All i know is i want to use the commands in and out. Please help me. |
|||
|
09 Jan 2008, 15:59 |
|
|
LocoDelAssembly 09 Jan 2008, 18:10
If this Dark Basic creates programs that runs on Windows then beleave me, it doesn't use direct I/O.
Also note that you will not be able to read the keyboard port in time since the keyboard interrupt handler provided by Windows will read it before you and hence you will loose multi-byte keys (and single-byte as well?). Read Keyboard Input tutorial from iczelion and Keyboard Input from MSDN |
|||
|
09 Jan 2008, 18:10 |
|
|
edfed 09 Jan 2008, 19:57
|
|||
|
09 Jan 2008, 19:57 |
|
|
Pixelator 09 Jan 2008, 22:04
i am going to use this (maybe) for an OS, i just want to print text to the screen.
_________________ Do not your will but the Lord's will. |
|||
|
09 Jan 2008, 22:04 |
|
|
DOS386 09 Jan 2008, 22:27
@mods
1. Move to "OS constructin" DONE was in "Windows" @pixelator 2. Avoid "windows", play with ports in DOS, see DOS subforum 3. OS coding is hard  Last edited by DOS386 on 10 Jan 2008, 01:32; edited 1 time in total |
|||
|
09 Jan 2008, 22:27 |
|
|
Pixelator 09 Jan 2008, 23:18
srry, i didn't see the Os Construction board.
i don't have a computer running dos |
|||
|
09 Jan 2008, 23:18 |
|
|
f0dder 09 Jan 2008, 23:37
DOS386 wrote:
Not really - but obtaining device specifications to able to write drivers - that's hard  _________________  - carpe noctem |
|||
|
09 Jan 2008, 23:37 |
|
|
DOS386 10 Jan 2008, 01:31
> obtaining device specifications to able to write drivers - that's hard
YES. 
And coding a useful OS is hard
> i don't have a computer running dos 1. Install DOS http://www.unet.univie.ac.at/~a0503736/php/drdoswiki/index.php?n=Main.PartErase or 2. Use BOCHS or QEMU |
|||
|
10 Jan 2008, 01:31 |
|
< Last Thread | Next Thread > |
Forum Rules:
|