help me in port programming

[CdiVer]

how do we programme other ports outthere than THe printer port and how
do we know the CONTROL PINS READING PINS AND OUTPUT PINS and also I
there a way to programme the USB PORTS

 

[mmquan]

Good question!

 

[mmquan]

Good question!

 

[David Resnick]

how do we programme other ports outthere than THe printer port and how
do we know the CONTROL PINS READING PINS AND OUTPUT PINS and also I
there a way to programme the USB PORTS

You go and find a newsgroup where this is on topic. Not
even close to comp.lang.c. That you think the above is a good
question here shows a real lack of clue -- even if we discussed
such in this group, not mentioning the hardware means you seem
to think that such things are done the same way on all platforms.

I'd guess comp.os.ms-windows.programmer.win32 is the right place
for your question. Unless you are using a mac or linux or unix or
....

-David

 

[CdiVer]

ThanX Lawrence
i would like to know how to get all the REGISITRY ADD. the one's we use
in functions like int86(.......)
all the interrupts like for mouse ITS is 0x33 and for Video its 0x10
and the Variables to be passed in the REGS
if u could help me out
like how to enable the "modem" usin C????

 

[Lawrence Kirby]

how do we programme other ports outthere than THe printer port and how
do we know the CONTROL PINS READING PINS AND OUTPUT PINS and also I
there a way to programme the USB PORTS

This is highly system specific. On most systems this is handled by the
operating system and you would access devices through system calls
provided. So you'll need to ask on a newsgroup relating to the particular
OS you are interested in, you have to go beyond standard C to do this.

Lawrence

 

[CBFalconer]

Good question!

Bad answer.

 

[Walter Roberson]

:i would like to know how to get all the REGISITRY ADD. the one's we use
:in functions like int86(.......)

Standard C does not know anything about registries.

:all the interrupts like for mouse ITS is 0x33 and for Video its 0x10

Standard C does not know anything about interrupts, only about
"signals", and the only signals that Standard C knows about are
ones that would normally interrupt or terminate your program
(e.g., because you attempted to access an address that did not exist.)

Standard C does not know anything about mice or video.

:and the Variables to be passed in the REGS

The closest that standard C has to "REGS" is that there is a storage-
class qualifier "register", which is mostly an optimization hint and
does not give *any* control over which internal register is used.

:if u could help me out
:like how to enable the "modem" usin C????

Standard C does not know anything about modems.

If you were working in Unix and you wanted to enable a modem, you
would just open its device file (specifying that you do not want
to wait for carrier) and then you would use termios functions
or POSIX tcgetattr() and tcsetattr() to set the line to the proper
state, and then you would [often] write commands out the port to tell
the modem to initialize itself. But in many cases in Unix, it is easier
to leave all of the work up to uugetty as that is well parameterized
to be able to deal with different kinds of modems.

If you are working in Windows (as suggested by "REGISTRY") then
I would suggest that you grab the source for any of the many open-source
terminal programs, as they have already dealt with all the issues.

 

[Neil Kurzman]

ThanX Lawrence
i would like to know how to get all the REGISITRY ADD. the one's we use
in functions like int86(.......)
all the interrupts like for mouse ITS is 0x33 and for Video its 0x10
and the Variables to be passed in the REGS
if u could help me out
like how to enable the "modem" usin C????

You are so lost it is not funny.
Int86 and the int33 int ect are DOS. the registry is windows.
You talk to the Modem by opening its comm port and sending AT commands.
USB requires you learn several Libraries. You can write the code in C.
But you questions have to do with the not standard C libraries. You have
asked some very complicated questions and seem to expect very simple
answers.