搜索资源列表
Serial_Communications_Sample
- MicroSoft C#编写的 .net串口通信程序-MicroSoft C# prepared. Net Serial Communication Program
mscommbcb
- 众所周知，C++Builder本身并不提供串行通讯控件MSComm，但我们却可以通过注册后直接使用它。启动C++Builder5.0后，然后选择C++Builder主菜单中的Component菜单项，单击Import Active Control命令，弹出Import Active窗口，选择Microsoft Comm Control6.0，再选择Install按钮执行安装命令,系统将自动进行编译,编译完成后即完成MSComm控件在C++Builder中的注册,系统默认安装在控件板的Active
CHAPT03
- CHAPT03\\CHAPT03.CPP 16-Bit test program for class PC8250 CHAPT03\\CHAPT03.EXE 16-Bit executable of the test program CHAPT03\\CHAPT03.MAK A makefile for Borland or Microsoft C
CHAPT04
- CHAPT04\\CHAPT04.CPP 16-Bit test program for the Digi Classic board CHAPT04\\CHAPT04.EXE 16-Bit executable of the test program CHAPT04\\CHAPT04.MAK A makefile for Borland or Microsoft C++ CHAPT04\\CLASSIC.CPP Implementation of the ClassicHandle
CHAPT05
- CHAPT05\\CHAPT05.CPP 16-Bit test program for the initelligent Digi board. CHAPT05\\CHAPT05.EXE 16-Bit executable of the test program CHAPT05\\CHAPT05.MAK A makefile for Borland or Microsoft C++ CHAPT05\\DIGI.CPP Implementation of the Digiboard
CHAPT06
- CHAPT06\\CHAPT06.CPP 16-Bit test program for the BiosPort class CHAPT06\\CHAPT06.EXE 16-Bit executable of the test program CHAPT06\\CHAPT06.MAK A makefile for Borland or Microsoft C++ CHAPT06\\BIOSPORT.CPP Implementation of the BiosPort class
CHAPT07
- CHAPT07\\CHAPT07.CPP 16-Bit test program for the Fossil class CHAPT07\\CHAPT07.EXE 16-Bit executable of the test program. CHAPT07\\CHAPT07.MAK A makefile for Borland or Microsoft C++ CHAPT07\\BIOSPORT.CPP A copy of the file from Chapter 6 CHA
CHAPT08
- CHAPT08\\TESTTERM.CPP 16-Bit test program for the terminal emulation classes CHAPT08\\TESTTERM.EXE 16-Bit executable of the test program. CHAPT08\\TESTTERM.MAK A makefile for Borland or Microsoft C++.
CHAPT09
- CHAPT09\\TERMW16.CPP 16-Bit test program for the Win16Port class. CHAPT09\\TERMW16.DEF A file needed by the linker for this program. CHAPT09\\TERMW16.EXE 16-Bit exeuctable of the test program. CHAPT09\\TERMW16B.MAK A makefile for Borland C++.
CHAPT14
- CHAPT14\\MODEM.CPP Implementation of the Modem class CHAPT14\\MODEM.H Declarations of the Modem class CHAPT14\\TSTMODEM.CPP 16-bit test program for the Modem class CHAPT14\\TSTMODEM.EXE 16-bit executable of the test program CHAPT14\\TSTMODEM.
VC-PortProgamming
- 用Visual C++6.0编程工具，使用Microsoft Communications Control控件（MSComm控件）进行串行通信程序的开发。
电表645
- // dianbiao645.h : main header file for the DIANBIAO645 application // #if !defined(AFX_DIANBIAO645_H__EF43A0BD_87CA_4963_B57A_57851872D28C__INCLUDED_) #define AFX_DIANBIAO645_H__EF43A0BD_87CA_4963_B57A_57851872D28C__INCLUDED_ #if _MSC_VER &g
MSComUseInVC++
- Visual C++提供了一种好用的ActiveX控件Microsoft Communications Control(即MSComm)来支持应用程序对串口的访问。本文介绍MSComm在VC++的添加使用实例及给出了mscomm.h头文件主要代码关键部分的注释。-Visual C++ Provides an easy-to-use ActiveX control Microsoft Communications Control (ie MSComm) to support the applica
ComPort
- C# 小工具：替代微软的超级终端，将com口接收的数据转化成Unicode明文；-Gadgets: Microsoft' s HyperTerminal alternative, I will com to receive the data into Unicode explicitly
NetSerialComm
- 微软C#读写类，针对串口数据的读写等操作的类-Microsoft C# to read and write class for reading and writing serial data operation
VC_MSComm
- 利用Visual C++ MFC和微软的MSComm（Microsoft Communications Control）串口通信控件写的串口通信程序-Using Visual C++ MFC and Microsoft MSComm (Microsoft Communications Control) serial communication control program written in serial communication ... ...
FileTransComm
- 利用Visual C++ MFC和微软MSComm（Microsoft Communications Control）串口通信控件，借助于串口来传输文件。由于串口的缓冲区限制，需要将文件先分割成多个部分分别打包发送，接收方只有在接收到说有的文件包后才进行解包、校验和拼接，最后提取文件名，提示用户保存。这个资源还包含了一些其它的有用文件和信息…… 对于刚开始利用VC++开发的程序员也是会有较大的帮助，可以下载看看，我相信您会觉得值的-Using Visual C++ MFC and Micro
mscomm
- vc++串口编程，串口精灵源代码mscomm.c- Machine generated IDispatch wrapper class(es) created by Microsoft Visual C++
VCPPsci
- 用Microsoft Visual C++ 6.0编写的串口调试软件，串口设置可调，有发送接收、自动发送功能。-Using Microsoft Visual C++ 6.0 prepared by the serial debug software, serial port settings adjustable, with sending and receiving, automatic transmission function.
ComPort
- simple c++ com port classes as discribed in the microsoft library dokumentation