| ??? 05/05/06 13:50 Read: times |
#115667 - PC COM: Ports Responding to: ???'s previous message |
Rustu Kaya said:
I am very doubtfull about standard C`s port access instructions... What do you mean by this? Standard 'C' doesn't have any port access instructions! Borland (and MS?) used to provide extensions like inp(), inport(), and inportb() for direct-access to x86 IO Ports... ...would work reliably with such high level Builder and particularly with the XP. If you're talking about the inp() etc extensions then you're right that these would be a Really Bad Idea under XP! See http://www.8052.com/forum/read.phtml?id=105099 Has any of you ever used standard C port access instructions with Borland when OS is XP? See above. Note that applications that do direct port IO may work to a certain extent under XP - but the timing will be completely messed up. If you are doing very simple serial IO, with no timing constraints at all, you might get away with it. Again, see http://www.8052.com/forum/read.phtml?id=105099 However, the Windows API provides access to COM ports - it basically treats them as files that you open, read, write, etc. What is the most common method that forum members had preferred to have a serial connection to their 8052 based circuits? See above - you can use the standard Windows API. Or you could get some sort of "wrapper" - like AsyncPro. What do you suggest me to settle this case in the easiest way ? Try MSDN and some googling, and see if you can get by with the Windows API. If not, go for something like AsyncPro http://sourceforge.net/projects/tpapro/ |
| Topic | Author | Date |
| PC comm. port | 01/01/70 00:00 | |
| Async Pro | 01/01/70 00:00 | |
| INPOUT.DLL under XP | 01/01/70 00:00 | |
| PC COM: Ports | 01/01/70 00:00 | |
WCSC | 01/01/70 00:00 |