| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Low level info |
PF> PM> I can find no API call that gets me such low level information as bus
PF> PM> type, serial port address, Irq assignment, etc. How can I get this
PF> PM> information under OS/2?
PF>
PF> Answer: As an application writer, this is none of your
PF> business . When we left DOS, we left such mundane
PF> details behind us.
Think of it as my kinky side . The reason I want to know what
these things are is that: -it is not uncommon for the owner of a system
to not know this information but require it; -I am writing a
program that requires access to serial ports, if I can
determine the bus type is MCA or EISA, I then know that I can reasonably
expect no Irq conflict, if, on the other hand, it is just a regular
AT bus and I can determine what Irqs have been assigned to which
serial ports, I can at least warn the user that a conflict will
occur if he insists on continuing. -it would make a great impression
at parties.
PF> Answer: As a device driver writer, you SET these things, not
PF> query them.
PF>
Oi, write a device driver?!
PF>
PF> DosDevConfig() might tell you a few things that you want to know.
PF>
DosDevConfig seems to give only the number of devices. I can ask for
submodel or model, but I have no info on how to decode the information
I am given.
___
X KWQ/2 1.2e X "640K ought to be enough for anybody." - Bill Gates, 1981
--- Maximus/2 2.01
* Origin: Sol 3 * Toronto * V.32 * (905)858-8488 (1:259/414)SEEN-BY: 12/2442 54/54 620/243 624/50 632/348 640/820 690/660 711/409 410 413 SEEN-BY: 711/430 807 808 809 934 942 712/353 623 713/888 800/1 @PATH: 259/414 400 99 98 3615/50 229/2 12/2442 711/409 54/54 711/808 809 934 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.