1.5w+
社区成员
- 全部
- VC综合技术
- 互联网技术
- MFC AppLauncher
- .NET 技术
- 界面
- 进程
- 算法
- 硬件/系统
- 数据库
- VC++技术资源
怎样编程禁用网卡？我记得有人问过这个问题？谁知道，我很急，万分感谢，UP有分。
怎样编程禁用网卡？我记得有人问过这个问题？谁知道，我很急，万分感谢，UP有分。
...全文
当前发帖距今超过3年，不再开放新的回复
发表回复
jxk 2002-05-11
我认为这只是修改注册表的问题
你可以用一些监视组成表的软件看看注册表在禁用网卡之前和禁用网卡之后注册表有什么变化！
你可以用一些监视组成表的软件看看注册表在禁用网卡之前和禁用网卡之后注册表有什么变化！
no1vcl 2002-05-11
The ObjectName field contains the name (or name prefix) by which the component is identified by the system. This value must be the same as the name in the related CurrentControlSet\Services subkey. Names for adapters are created by the system and override the Bindform setting.
The first Yes|No pair indicates whether the component is to receive binding information directly in its Linkage subkey. The second Yes|No pair indicates whether the device name is supposed to appear in generated binding strings.
The final optional value in this entry indicates how binding device names are constructed. This value is required for software components.
Class REG_MULTI_SZ
Path: HKEY_LOCAL_MACHINE\Software\Microsoft\Drivername
\CurrentVersion\NetRules
- or -
HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsNT\CurrentVersion \NetworkCards\netcard#\NetRules
Range: NewClassName OldClassName|basic [Yes|No]
Allows a component to define a new class. As many new classes as necessary can be defined by any component.
Note: These classes are not related to the COM object data and DDE classes defined under HKEY_LOCAL_MACHINE\Software\Classes.
Class names do not need to be defined within any particular component. The system adds the new definition to its database without regard to origin. The order of Class entries is irrelevant. However, results are indeterminate if classes are referred to that are not defined anywhere in the system.
This entry is optional, because there are a few predefined classes, and class definitions made anywhere in the system apply to all network components. Because any network component can define new classes, be careful that the names used are unique within all possible installable network components. The following list shows the predefined class names in the first release of WindowsNT. This list, of course, cannot be exhaustive.
Predefined class = Adapter card type
ee16Driver; ee16Adapter = Intel EtherExpress 16 LAN adapter
elnkiiAdapter; elinkiiDriver = 3Com Etherlink II adapter
ibmtokDriver; ibmtokAdapter = IBM Token Ring adapter
lanceDriver; dec101Adapter = DEC Lance adapter
lt200Driver; lt200Adapter = Daystar Digital LocalTalk adapter
ne2000Driver; ne2000Adapter = Novell NE2000 adapter
proteonDriver; p1390Adapter = Proteon adapter
ubDriver; ubAdapter = Ungermann-Bass Ethernet NIUpc aapter
wdlanDriver; smcisaAdapter = SMC (WD) adapter
The final optional value indicates whether this class is a "logical endpoint" for the bindings protocol; the default value is NO.
Hidden REG_DWORD
Path: HKEY_LOCAL_MACHINE\Software\Microsoft\Drivername
\CurrentVersion\NetRules
- or -
HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsNT\CurrentVersion \NetworkCards\netcard#\NetRules
Range: 0 or 1
Suppresses the display of the component (adapter or network software) in the Network dialog box accessible through Control Panel.
Usually, all networking components discovered in the Registry are displayed in the two list boxes in the Network dialog box. Setting this value to 1 prevents the item from being displayed, which means the user cannot configure or remove it.
Interface REG_MULTI_SZ
Path: HKEY_LOCAL_MACHINE\Software\Microsoft\Drivername
\CurrentVersion\NetRules
- or -
HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsNT\CurrentVersion \NetworkCards\netcard#\NetRules
Range: InterfaceName UpperClass "objectName" namingMethod
Allows a single component to make available more than one type of capability to other components in the system. This value contains these components:
InterfaceName The tokenized name of the secondary interface.
UpperClass The class to which the interface belongs. (LowerClass refers to the primary interface.)
ObjectName The WindowsNT device name to be created.
NamingMethod A value that determines how the bindings appear.
Review REG_DWORD
Path: HKEY_LOCAL_MACHINE\Software\Microsoft\Drivername
\CurrentVersion\NetRules
- or -
HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsNT\CurrentVersion \NetworkCards\netcard#\NetRules
Range: 0 or 1
Indicates whether a component requests bindings review. If set to 1 (or nonzero), the system reinvokes this component's .inf file after bindings have been changed. Network components can then modify the binding information or request additional information from administrators about the new or altered connections.
Type REG_SZ
Path: HKEY_LOCAL_MACHINE\Software\Microsoft\Drivername
\CurrentVersion\NetRules
- or -
HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsNT\CurrentVersion \NetworkCards\netcard#\NetRules
Range: component className [lowerClass]
Defines the type of the component in terms of abstract network component classes. If the optional lowerClass name is absent, the first (or upper-level) class type name is used for both its upper and lower classes. This value is required for network software and network adapter cards. The component types are the following:
Adapter Hardware component
Driver A software component directly associated with a hardware component.
Transport A software component used by services
Service A software component providing capability directly to user applications
Basic A token used to represent a fundamental class name (that is, a class with no parent)
Use REG_SZ
Path: HKEY_LOCAL_MACHINE\Software\Microsoft\Drivername
\CurrentVersion\NetRules
- or -
HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsNT\CurrentVersion \NetworkCards\netcard#\NetRules
Range: service|driver|transport|adapter [Yes|No] [Yes|No]
Defines the role played by the component. If this entry is absent, the value of Service is assumed. This value entry only appears for software items.
A hardware device is automatically assumed to be an adapter. Each network component can identify itself as a driver, transport, or service to clarify its role. This distinction is as follows:
Driver Exists only to support one or more adapters. If no bindings are generated (or permitted by the user) that include a particular driver, that driver is not loaded. However, no error is generated, since no "denial of service" has occurred.
Service Provides end-user functionality, and every attempt is made to support its operation. An EventLog entry is generated if a service is present in the system for which there is no available transport (that is, the number of possible bindings is zero).
The first Yes|No pair indicates whether the component is to receive binding information directly in its Linkage subkey. The second Yes|No pair indicates whether the device name is supposed to appear in generated binding strings.
The final optional value in this entry indicates how binding device names are constructed. This value is required for software components.
Class REG_MULTI_SZ
Path: HKEY_LOCAL_MACHINE\Software\Microsoft\Drivername
\CurrentVersion\NetRules
- or -
HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsNT\CurrentVersion \NetworkCards\netcard#\NetRules
Range: NewClassName OldClassName|basic [Yes|No]
Allows a component to define a new class. As many new classes as necessary can be defined by any component.
Note: These classes are not related to the COM object data and DDE classes defined under HKEY_LOCAL_MACHINE\Software\Classes.
Class names do not need to be defined within any particular component. The system adds the new definition to its database without regard to origin. The order of Class entries is irrelevant. However, results are indeterminate if classes are referred to that are not defined anywhere in the system.
This entry is optional, because there are a few predefined classes, and class definitions made anywhere in the system apply to all network components. Because any network component can define new classes, be careful that the names used are unique within all possible installable network components. The following list shows the predefined class names in the first release of WindowsNT. This list, of course, cannot be exhaustive.
Predefined class = Adapter card type
ee16Driver; ee16Adapter = Intel EtherExpress 16 LAN adapter
elnkiiAdapter; elinkiiDriver = 3Com Etherlink II adapter
ibmtokDriver; ibmtokAdapter = IBM Token Ring adapter
lanceDriver; dec101Adapter = DEC Lance adapter
lt200Driver; lt200Adapter = Daystar Digital LocalTalk adapter
ne2000Driver; ne2000Adapter = Novell NE2000 adapter
proteonDriver; p1390Adapter = Proteon adapter
ubDriver; ubAdapter = Ungermann-Bass Ethernet NIUpc aapter
wdlanDriver; smcisaAdapter = SMC (WD) adapter
The final optional value indicates whether this class is a "logical endpoint" for the bindings protocol; the default value is NO.
Hidden REG_DWORD
Path: HKEY_LOCAL_MACHINE\Software\Microsoft\Drivername
\CurrentVersion\NetRules
- or -
HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsNT\CurrentVersion \NetworkCards\netcard#\NetRules
Range: 0 or 1
Suppresses the display of the component (adapter or network software) in the Network dialog box accessible through Control Panel.
Usually, all networking components discovered in the Registry are displayed in the two list boxes in the Network dialog box. Setting this value to 1 prevents the item from being displayed, which means the user cannot configure or remove it.
Interface REG_MULTI_SZ
Path: HKEY_LOCAL_MACHINE\Software\Microsoft\Drivername
\CurrentVersion\NetRules
- or -
HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsNT\CurrentVersion \NetworkCards\netcard#\NetRules
Range: InterfaceName UpperClass "objectName" namingMethod
Allows a single component to make available more than one type of capability to other components in the system. This value contains these components:
InterfaceName The tokenized name of the secondary interface.
UpperClass The class to which the interface belongs. (LowerClass refers to the primary interface.)
ObjectName The WindowsNT device name to be created.
NamingMethod A value that determines how the bindings appear.
Review REG_DWORD
Path: HKEY_LOCAL_MACHINE\Software\Microsoft\Drivername
\CurrentVersion\NetRules
- or -
HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsNT\CurrentVersion \NetworkCards\netcard#\NetRules
Range: 0 or 1
Indicates whether a component requests bindings review. If set to 1 (or nonzero), the system reinvokes this component's .inf file after bindings have been changed. Network components can then modify the binding information or request additional information from administrators about the new or altered connections.
Type REG_SZ
Path: HKEY_LOCAL_MACHINE\Software\Microsoft\Drivername
\CurrentVersion\NetRules
- or -
HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsNT\CurrentVersion \NetworkCards\netcard#\NetRules
Range: component className [lowerClass]
Defines the type of the component in terms of abstract network component classes. If the optional lowerClass name is absent, the first (or upper-level) class type name is used for both its upper and lower classes. This value is required for network software and network adapter cards. The component types are the following:
Adapter Hardware component
Driver A software component directly associated with a hardware component.
Transport A software component used by services
Service A software component providing capability directly to user applications
Basic A token used to represent a fundamental class name (that is, a class with no parent)
Use REG_SZ
Path: HKEY_LOCAL_MACHINE\Software\Microsoft\Drivername
\CurrentVersion\NetRules
- or -
HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsNT\CurrentVersion \NetworkCards\netcard#\NetRules
Range: service|driver|transport|adapter [Yes|No] [Yes|No]
Defines the role played by the component. If this entry is absent, the value of Service is assumed. This value entry only appears for software items.
A hardware device is automatically assumed to be an adapter. Each network component can identify itself as a driver, transport, or service to clarify its role. This distinction is as follows:
Driver Exists only to support one or more adapters. If no bindings are generated (or permitted by the user) that include a particular driver, that driver is not loaded. However, no error is generated, since no "denial of service" has occurred.
Service Provides end-user functionality, and every attempt is made to support its operation. An EventLog entry is generated if a service is present in the system for which there is no available transport (that is, the number of possible bindings is zero).
no1vcl 2002-05-11
Chapter 14
Network Interfaces and Protocols
In this chapter we will look at the Registry parameters for network adapter cards. Under each adapter card setting, there will also parameters for the adapter card that relate to exclusive protocols. We examine those options as well as the architecture that Windows NT uses for Network drivers: the Network Driver Interface Specification.
NDIS
The base of Microsoft Windows NT's network architecture begins with the Network Driver Interface Specification. This is a Microsoft specification for writing hardware-independent drivers at the media access layer (subcomponent of the OSI data link layer.)
NDIS Drivers
Any network interface card that is NDIS-compatible can pass data to any protocol that is NDIS-compatible. Other network operating systems require a single protocol at a time bound to a Network Interface Card.
NDIS Wrapper
Replaces PROTMAN, which was used in previous implementations of NDIS. The NDIS Wrapper controls all initial access to the NIC. It stores all adapter settings in the Registry.
Card Parameters
WindowsNT supports network adapter drivers under the Network Device Interface Specification (NDIS) 3.0 specification. The following sections describe entries in the other areas of the Registry that contain configuration information for network adapter cards and their drivers, including:
NetRules: subkeys under HKEY_LOCAL_MACHINE\Software subkeys store data for drivers and adapters.
Linkage: subkey entries under HKEY_LOCAL_MACHINE\System subkeys for drivers and adapters, define information about bindings for the component.
Parameters: subkey entries under HKEY_LOCAL_MACHINE\System subkeys for network card adapters, define specific information such as the IRQ number, I/O base address, and other details.
NetRules
The NetRules subkey is located under the following registry path:
HKEY_LOCAL_MACHINE\Software\Microsoft\Drivername\CurrentVersion\NetRules
For network adapter cards, where the netcard# subkey is a number, beginning with 01 for the first network adapter:
HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsNT\CurrentVersion\NetworkCards\netcard#\NetRules
Bindable REG_MULTI_SZ
Path: HKEY_LOCAL_MACHINE\Software\Microsoft\driverName\
CurrentVersion\NetRules
or -
HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsNT\CurrentVersionNetworkCards\netcard#\NetRules
Range: fromClass toClass Yes|No Yes|No value
Defines a valid binding and its constraints. This value entry is optional, because there are a few predefined binding rules, and binding rules defined anywhere in the system apply to all network component classes. Because this value entry is of type REG_MULTI_SZ, a single value entry is large enough to hold as many criteria for binding as are needed.
The value entry has the following format:
Class1 Class2 Criteria1 Criteria2 …
For example:
Value name: Bindable
Data type: REG_MULTI_SZ
Value: ndisDriver ndisAdapter non exclusive 100
In this example, the components of class "ndisDriver" can be bound to those of class "ndisAdapter." Non indicates that the component of class ndisDriver can accept other bindings. Exclusive indicates that the component of class ndisAdapter cannot accept other bindings. 100 indicates the relative importance (weight) of this binding; that is, in cases of competition, it will be discarded in favor of other bindings whose weight is greater.
Bindform REG_SZ
Path: HKEY_LOCAL_MACHINE\Software\Microsoft\Drivername
\CurrentVersion\NetRules
- or-
HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsNT\CurrentVersion \NetworkCards\netcard#\NetRules
Range: ObjectName Yes|No Yes|No [container|simple|streams]
Network Interfaces and Protocols
In this chapter we will look at the Registry parameters for network adapter cards. Under each adapter card setting, there will also parameters for the adapter card that relate to exclusive protocols. We examine those options as well as the architecture that Windows NT uses for Network drivers: the Network Driver Interface Specification.
NDIS
The base of Microsoft Windows NT's network architecture begins with the Network Driver Interface Specification. This is a Microsoft specification for writing hardware-independent drivers at the media access layer (subcomponent of the OSI data link layer.)
NDIS Drivers
Any network interface card that is NDIS-compatible can pass data to any protocol that is NDIS-compatible. Other network operating systems require a single protocol at a time bound to a Network Interface Card.
NDIS Wrapper
Replaces PROTMAN, which was used in previous implementations of NDIS. The NDIS Wrapper controls all initial access to the NIC. It stores all adapter settings in the Registry.
Card Parameters
WindowsNT supports network adapter drivers under the Network Device Interface Specification (NDIS) 3.0 specification. The following sections describe entries in the other areas of the Registry that contain configuration information for network adapter cards and their drivers, including:
NetRules: subkeys under HKEY_LOCAL_MACHINE\Software subkeys store data for drivers and adapters.
Linkage: subkey entries under HKEY_LOCAL_MACHINE\System subkeys for drivers and adapters, define information about bindings for the component.
Parameters: subkey entries under HKEY_LOCAL_MACHINE\System subkeys for network card adapters, define specific information such as the IRQ number, I/O base address, and other details.
NetRules
The NetRules subkey is located under the following registry path:
HKEY_LOCAL_MACHINE\Software\Microsoft\Drivername\CurrentVersion\NetRules
For network adapter cards, where the netcard# subkey is a number, beginning with 01 for the first network adapter:
HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsNT\CurrentVersion\NetworkCards\netcard#\NetRules
Bindable REG_MULTI_SZ
Path: HKEY_LOCAL_MACHINE\Software\Microsoft\driverName\
CurrentVersion\NetRules
or -
HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsNT\CurrentVersionNetworkCards\netcard#\NetRules
Range: fromClass toClass Yes|No Yes|No value
Defines a valid binding and its constraints. This value entry is optional, because there are a few predefined binding rules, and binding rules defined anywhere in the system apply to all network component classes. Because this value entry is of type REG_MULTI_SZ, a single value entry is large enough to hold as many criteria for binding as are needed.
The value entry has the following format:
Class1 Class2 Criteria1 Criteria2 …
For example:
Value name: Bindable
Data type: REG_MULTI_SZ
Value: ndisDriver ndisAdapter non exclusive 100
In this example, the components of class "ndisDriver" can be bound to those of class "ndisAdapter." Non indicates that the component of class ndisDriver can accept other bindings. Exclusive indicates that the component of class ndisAdapter cannot accept other bindings. 100 indicates the relative importance (weight) of this binding; that is, in cases of competition, it will be discarded in favor of other bindings whose weight is greater.
Bindform REG_SZ
Path: HKEY_LOCAL_MACHINE\Software\Microsoft\Drivername
\CurrentVersion\NetRules
- or-
HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsNT\CurrentVersion \NetworkCards\netcard#\NetRules
Range: ObjectName Yes|No Yes|No [container|simple|streams]
no1vcl 2002-05-11
基本上修改注册表即可；
以下摘自：
http://www.usv.ro/docm/calculatoare/NT/nt4regpro/cover.htm
WINDOWS NT 4.0 REGISTRY:A Professional Reference
以下摘自：
http://www.usv.ro/docm/calculatoare/NT/nt4regpro/cover.htm
WINDOWS NT 4.0 REGISTRY:A Professional Reference
killwd 2002-05-11
多谢，能解决问题更好，急的不是一般。
ciacia 2002-05-11
那我就帮你up，up，再up！
Thinkpad常见问题大全（转载联想工程师博客） 想要收藏本篇文章请下载Word版 Q：我想升级成VISTA，想问一下，升级之后一键恢复是恢复到XP还是VISTA?A：如果从隐含分区恢复出厂设置，那当然是恢复到出厂时预装的系统；如果是用R&
这样的电脑问题 谁遇到过 (100分） 我设置了2个 202.97.224.68 202.97.230.4 （以前根本不用设置的） wins 为禁用 网关没有设置 ip为自动 出现这个情况后 我解决的办法是 1 删除+禁用那个虚拟的网卡 然后 删除我自己的那块网卡 重新安装后 再安装虚拟...
我在CSDN参与的3000个帖子 2：100分急求，随机输出十个小写字母，但是，要求这十个字母不相同 3：求Sn=a+aa+aaa+…+aaa…a（n个a）之值 4：数组题 望高手帮忙！ 5：呵呵，来推荐一下我的网站，本站提供大量当今流行的免费的音乐和免费电影，...
flash常见问题集锦，很适合新手哦[二] 怎样用文本控制链接 我用flashmx做了一个导航菜单，可是在今后修改链接很麻烦，近日听说可以用文本来控制链接，想请问如何用文本文件来控制flash里的链接？在此先谢谢回答问题的各位了！ 这个分2个步骤来:1.新建一...
flash常见问题集锦，很适合新手哦 如何加载一个SWF文件并控制其位置等相应属性……新建一个空地MC，将它放在主场景中，实体名改为OK，写AS： loadMovie("test.swf", "_root.ok"); 控制这个MC的位置，大小等相对属性（Property）就会影响调入SWF的位置...
手把手教你安装黑苹果之openCore-0.6.3 EFI制作全过程，非常详细 这篇文章主要是记录自己动手安装Big Sur在过程，和心理。略显繁琐，请自行跳跃观看。 macOS Big Sur 正式版于 11 月 12 日星期四(北京时间 11 月 13 日)发布，改动还是挺大的。基于M1苹果自研芯片的macbook也发布了...
Kafka性能优化---2 题外话： 上一篇简单说了一下自己对kafka的一些基础理解，以及...这一篇就来研究研究一些另类玩法，跟代码无关，用到的技术也不算新，但是令我感到意外的是，竟然没有人这么使用过，实践过。。。 我挺难受的，这
高负载高并发网站架构分析 由于自己正在做一个高性能大用户量的论坛程序，对高性能高并发服务器架构比较感兴趣，于是在网上收集了不少这方面的资料和大家分享。希望能和大家交流 msn: defender_ios@hotmail.com ————————————...
批处理 bat cmd 命令大全 net use \\ip\ipc$ " " /user:" " 建立IPC空链接 net use \\ip\ipc$ "密码" /user:"用户名" 建立IPC非空链接 net use h: \\ip\c$ "密码" /user:"...
180天Linux小白到大神-Linux网络管理 15 Linux网络管理 15 Linux网络管理 1.网络基本概述 1.1 为何需要网络 1.2 什么是网络 ...4.2 修改网卡名称 4.3 配置网络地址 4.3.1 nmcli查看网络状态 4.3.2 nmcli配置IP地址 4.3.2 nmcli修改IP地址
[转]高负载并发网站架构分析 由于自己正在做一个高性能大用户量的论坛程序，对高性能高并发服务器架构比较感兴趣，于是在网上收集了不少这方面的资料和大家分享。希望能和大家交流 msn: defender_ios@hotmail.com ——————————————...
180天Linux小白到大神-Linux系统优化 15 Linux网络管理 15 Linux网络管理 1.网络基本概述 1.1 为何需要网络 1.2 什么是网络 ...4.2 修改网卡名称 4.3 配置网络地址 4.3.1 nmcli查看网络状态 4.3.2 nmcli配置IP地址 4.3.2 nmcli修改IP地址 4.3.3 nmc
SQL2005疑难解决方案大全 SQL2005疑难解决方案大全 目录 目录....................................................................................................................................无法连接到服务器...................
高并发高负载系统架构 而后在Yahoo3721负载搜索引擎前端平台开发，又在猫扑处理过大型社区猫扑大杂烩的架构升级等工作，同时自己接触和开发过不少大中型网站的模块，因此在大型网站应对高负载和并发的解决方案上有一些积累和经验，可以和...
转：高并发高负载系统架构 而后在Yahoo3721负载搜索引擎前端平台开发，又在猫扑处理过大型社区猫扑大杂烩的架构升级等工作，同时自己接触和开发过不少大中型网站的模块，因此在大型网站应对高负载和并发的解决方案上有一些积累和经验，可以和...
Linux操作系统不完全指南 0 开始 0.1 显示当前用户名 whoami 选项 功能 –help 显示帮助信息 –version 显示版本信息 example: whoami 0.2 显示当前工作目录 pwd example: ...禁用反斜杠转义功能（默认） ...
Redis 进阶笔记 当访问量上万，数据库压力增大，可以采取的方案有： 读写分离，分库分表 当访问量达到 10 万、百万，需要引入缓存。 将已经访问过的内容或数据存储起来，当再次访问时先找缓存，缓存命中返回数据。 不命中再找数据库...
redis学习笔记 1下载安装包 wget ... 把安装包放入opt目录下，linux的软件都安装在opt下 /opt目录下，解压命令:tar -zxvf redis-3.0.4.tar.gz tar -zxvf redis-3.0.4.tar.gz ...进入目录:cd redis-3.0.4...
ORA-39511|静默安装 Oracle 19c RAC 时遇到的头疼事儿 作者 | JiekeXu来源 |JiekeXu DBA之路（ID: JiekeXu_IT）大家好，我是 JiekeXu,很高兴又和大家见面了,今天和大家一起来看看 ORA-39511 问...
MFC上位机与STM32下位机通讯精讲 本课程主要介绍C++类库MFC上位机与STM32单片机的RS232、RS422、RS485、USB、LWIP以太网、CAN等接口进行稳定通信。课程主要从MFC和STM32基础开始，以编写上位机以及下位机为主，非常注重实践。 本课程主要目标是让大家学会MFC上位机的编程、STM32下位机编程。单单的会上位机或者下位机有时候体会不到通讯的乐趣，如果你单单会下位机，你学了本课程，你可以把你的数据以任何方式在windows上呈现出来，如果你只会上位机，你学了本课程你可以通过windows的串口、以太网、USB控制任何硬件设备。本课程的目标就是补偿大家的短处，让大家成为综合性人才，同时让大家体会到通讯中的更多乐趣。
C语言大型软件设计的面向对象 C语言代码一旦达到一定规模，就特别强调良好的架构设计，以保证代码的可读性好、代码简洁以及可复用。此时，软件设计师势必要用C语言来做面向对象的设计。不能克服面向对象这一关，也是很多人无法读懂Linux内核、驱动等架构比较庞大的软件的主要技术壁垒之一，因为这些软件里面充满了对象式的设计。 本课程以案例来详细讲解，用C语言如何设计面向对象的程序。 本课程以案例来详细讲解，用C语言教大家如何设计面向对象的程序。
