EPON、ADSL、BroadBand、IP、ATM 相关

ADSL局端设备DSLAM和用户端设备ATU-R间基于ATM信元传输
PON和DSLAM、BAS组网时，BAS下带OLT，ONU下带DSLAM，或者ONU兼有DSLAM功能
ONU可以兼有NGN体系中MG功能
IP-DSLAM和上面的BAS之间，没有走ATM信元，而是IP包，而IP-DSLAM是今后的趋势
周长林老师说仅仅是在猫和ONU之间走的是ATM。后来了解到，其实ATU-R和DSLAM间走的是ATM协议，而PON系统中ONU兼有DSLAM功能，所以仅仅是猫和ONU之间走ATM协议。DSLAM和BAS间，传统走ATM，现在流行走IP

ONU带数据业务和语音业务的几种情况：
1. 纯数据业务，两种情况
ONU插以太网板卡，直接接RJ-45口出来（9806的ETCA-16路板，F822），整个通道就是数据通道，从电脑到ONU，到OLT，到BAS；
ONU插ADSL板，POTS口出来（9806的AST**-24路板（右边丝印为USER的24个POTS口）），其中任一对线做成RJ-11口，接到猫上，再接到电脑上
2. 纯语音业务
如果是纯语音用户，POTS口出来（9806的ATLC语音板的LEFT(24用户)和RIGHT(24用户)，F822（24路或24+24=48路POTS）），里面一对线接RJ-11口，信令和媒体流从话机到ONU，到OLT，到IP网，到NGN
3. 数据和语音混合业务
ONU，例如9806上，同时插ATLC语音用户板和AST**数据用户板，两板之间对接。对接时，ATLC的POTS口中，LEFT和RIGHT均可，拉出一对线到配线架，AST板左边丝印为PSTN的POTS口中拉出一对到配线架，两对跳通，当然也可以直接把两边的24对POTS口对接，但工程上的做法是先把两边的24对POTS都跳到配线架上，哪个用户想开，就跳通哪一对。AST板右边丝印为USER的24对POTS口跳到配线架，哪个用户想开通，就从配线架引线到用户侧，用户侧装一个分线器，一头分到电话，另一头分到猫。分线器起滤波的作用，当然不用分线器也可以使用，只不过在一个时间点，要么把这个RJ-11的接头接到电话上打电话，要么接到猫上以供上网使用，不能同时打电话和上网。
具体的数据流向，对于语音来说，电话到分线器，到AST的USER口，进入后到了AST板内，有一个分离器之类的东西，把语音信号分离出来，通过AST的PSTN口送入ATLC的LEFT或RIGHT口，再通过ATLC板走到ONU的上联板，往上再进入OLT，再进入IP网，再到NGN系统；对于数据来说，电脑RJ-45口，流出，进入猫，再通过RJ-11口进入分离器，再走到AST板的USER口，再通过AST内部的滤波之后，被AST送入上联板，再走到OLT，在进入上联IP网络。
ONU可以直接上联到PSTN网络。AST板上丝印为PSTN的POTS口，也可以直接上联交换设备，工程中的做法是把PSTN的24对线打到配线架上，然后再和打到配线架上的语音线路对接。

快速信道、交织信道区别在于：交织信道在传送数据时加入了冗余信息，增强数据准确性的同时，降低了传输速度，即以速度换取准确性。

为什么要有DSLAM？
传统的窄带接入方式，是电脑通过电话线接到猫，猫上联到PSTN交换机接入PSTN网络，速率低，而且上网、打电话相互影响；这种方式现在已经被淘汰，现在的PSTN网络中，例如CC08中，基本都是ASL32的语音板卡，少量ASL板卡，还有极少的数据用户的DSL板卡。
DSL这种板卡现在已经极少了，仅用于话务台，也就是一根电话线接到一个装有话务台对应板卡的电脑上，电脑上装上话务台软件，可以进行转接等一系列话务台操作；同时这个话务台下带的其它号码，每一个号码都是实实在在的，通过机房跳线接进来的普通电话。需要注意的是，这种话务台软件只是一个客户端，真正话务台的内部实现，包括内存资源都在交换机上面。在电脑的客户端上做一个操作后，指令通过接到电脑话务台板卡上的电话线被传送到交换机（CC08或者NGN局），交换机接受指令后，做出相应的操作，下发指令到话务台下带的其它号码。
这种DSL板卡也能接数字话机，也就是话机到DSL板之间走的是数字信号，在交换机内部处理的时候，不管通过ASL板接入还是DSL板接入，都是一样的。需要说明的一点是，传统PSTN话机是在PSTN网络里面传送模拟信号，现如今逐步萎缩；后来的数字话机，是在PSTN网络中传送数字信号，现在几乎绝迹；现在的NGN话机，完全是在Internet中传送IP包。
后来出了ADSL，虽然和传统窄带接入方式，在接入侧的用户线路是一样的，但它可以在一根电话线中同时传送语音和数据信号，二者互不影响，而且速率更高，关键的地方是上联设备不一样。
传统窄带是电脑通过电话线往上走到PSTN，通过PSTN走到IP网络，而PSTN网络的带宽可想而知，极大限制了网速；而ADSL不同，它在猫往上走的时候，就直接把语音和数据信号分离，直接把二者送入PSTN和Internet这两个不同的网络，那这个把二者分离的设备就是DSLAM！在ATU-R接入到DSLAM后，准确的说是接到DSLAM里面的ATU-C后（DSLAM包括ATU-C、CORE和WAN三个部分），ATU-C分离出两个信号，语音信号通过配线架，继续上联接入PSTN网络，而剩下的数据信号通过CORE的处理后，通过WAN板卡进入数据网络，如果是WANA，则还是以ATM信元方式往上接入ATM网络，如果是WANE板卡出来，则以IP包的形式出来，上联接入IP网。ATU-R一般指的是modem，有的电脑自带ATU-R。ATU-R和ATU-C之间走的是ATM信元流，往上的话，IP包和ATM信元包都可以。ATM本身是一个很好的技术，但是成本太高，现在IP-DSLAM（也就是往上传送IP包）比较流行。（DSLAM本身包含主控板、分离器板、ADSL单板、上行板，其中的分离器板相当于ATU-C，ADSL单板相当于CORE，上行板相当于WAN；如果是电视网中的这种结构，即通过电视网接入Internet，类似的技术叫HFC）


ISDN，接到PRI的猫
ISDN(Integrated Services Digital Network)翻译过来是综合服务数据网，是一系列标准，包括BRI(Basic Rate Interface)、PRI(Primary Rate Interface)、B-ISDN(Broadband ISDN)。BRI也叫BRA，PRI也叫PRA。
ISDN有两种信道，一种是B，代表bearer，表示承载信道，另一种D，代表data，是用于传送信令的。
BRI的标准是2B+D，其中的B是64kbit/s的，D是16kbit/s的。
B-ISDN基于ATM信元，用于骨干网
以上两种都很少了，现在用的较多的是PRI
PRI在欧美有两种不同实现，美国和日本用的是23B+1D，速率是T1，即1.544Mbit/s，其中的B和D都是64kbit/s，1.544Mbit/s中除去24个64kbit/s后，还有8kbit/s，我估计是用于同步和告警的，如果不是，那么就是做冗余的。
在欧洲和世界其他国家，用的是30B+1D，速率是E1，即2.048Mbit/s。其中的B和D也是64kbit/s，剩下的一个64kbit/s用于同步和告警，具体的来说是第0个信道用于同步和告警，第16个信道用于传送信令，其余所有信道用于传送数据。
在现网中，CC08经常增加PRI用户，这些用户通过小交机，也就是PBX接入到PSTN交换机，基本都是用于固话业务，也即是传统的PSTN业务。实际上PRI是可以用于传送数据业务的，用户通过ISDN猫接入PBX，再接入PSTN网络，虽然一个信道只有64kbit/s，但可以把多个信道捆绑成一个，也就是物理上的一个电缆，在逻辑上被分成若干个64kbit/s的信道，再通过捆绑，形成一个逻辑上的通路。现网只剩有极少量这种用户，因为这种上网方式太贵了。




设备的网管
带内、带外
业务通道、管理通道
带内网管就是走业务通道，主控板通过上联板往上，业务数据怎么走，它就怎么走；而带外网管是直接在主控板上接一根网线，直接操控设备
在华为MD5500这种很老的设备中，也有类似的东西，例如，ping的时候有-b参数，这个参数的解释是这样的：Set the channel of echo requests to be management channel, default is service channel（设置发送PING请求报文的通道为管理通道, 默认为业务通道）。也就是说，默认ping IP走的是业务通道，也就是带内，如果加了-b参数，走的就是管理通道，也就是带外。
默认情况下，设备都有console口的，外表和RJ-45的网口无差别，可以直接接电脑（注意，中兴设备的console口需要用特制的串口线接，否则虽然接上了，但电脑上的超级终端怎么都连不上），在施工时一般都要先用串口连上去把设备的带内或带外网管地址先配上，然后再通过带内或带外网管连上去网管。
对于PON系统，有些配置也可以通过OLT直接下发数据到ONU，不用通过console或带内外登录到设备上配置。



DSLAM、BAS、Radius、PPPoE
BAS是Broadband Remote Access Server (BRAS, B-RAS or BBRAS，或者RAS、UAS)的俗称，主要用于聚合电路，提供QoS，并对流量进行路由，BAS也是认证、授权、计费的系统中的一部分，即radius客户端(radius代表Remote Authentication Dial In User Service, 用于3A管理：Authentication, Authorization, and Accounting)，用于和radius服务器交互。BAS作为radius客户端向radius服务器发出请求，radius服务器再根据用户信息分配IP、指定服务等。
PPP是Point-to-Point Protocol的缩写，主要作用是为连接提供认证、加密、压缩。在IP/ATM网络中，用的更多的是PPP被封装后的形式：PPPoE(over Ethernet)和PPPoA(over ATM)。
用户拨号上网的时候，电脑上的PPPoE客户端，发起的PPP连接，被封装在以太网帧中发送出去，有两种情况：
1. 电脑通过猫上网，以太网帧遇到猫后，被封装到ATM信元（AAL5帧）中，往上到DSLAM，DSLAM拆开ATM信元，把里面的以太网帧通过DSLAM和BAS之间的PVC（永久虚电路）送到BAS，由BAS处理里面的PPP信息；下行时数据包到BAS被加上PPPoE的头后送到DSLAM被封装为ATM信元，到猫后从ATM信元中解出PPPoE包，电脑客户端从中解出IP包。
2. 电脑接以太网交换机时，以太网帧直接通过以太网交换机上传到BAS
到了BAS后，PPPoE就终止了，以太网帧之上的PPPoE以及在PPPoE之上的PPP只存在于PC和BAS之间，对于中间的部分来说是透明的。
PPPoE实质上是在BAS和用户端之间建立起一个管道，以太网帧在这个管道里传送，由于猫和BAS间是基于ATM的，所以他们之间的以太网帧又是建立在ATM之上的，这样就增加了开销，有一种替代方法就是PPPoE to PPPoA，也就是在猫那里做一个转换，连接PC的一头是PPPoE，连接BAS的一头是PPPoA，这样猫和BAS之间就减少了一层以太网层，增加效率。
猫上面有IP地址池，用于访问网络，所以连到猫上的电脑不用配置IP，不管怎么配，都是不起作用的。

.NET Framework 的相关问题

2011-08-11 03:42

某软件依赖.NET Framework 1.1，不小心装上了2.0版本后该软件不可用

卸载2.0版本后1.1装不上，通过微软在线帮助，卸载了1.1，重新安装后恢复。

过程比较复杂，相关操作都需要手动完成，涉及到删除注册表项、删目录、删dll等等

相关资料如下：

How to manually remove and then reinstall the.NET Framework 2.0：

http://support.microsoft.com/kb/908077

文中节选：

This step-by-step article describes how to troubleshoot issues that you may experience when you install the .NET Framework 2.0.

When Microsoft Windows Installer is incorrectly registered in the Windows registry, the .NET Framework 2.0 Setup program cannot access some Windows Installer components. This article discusses how to work around this issue by unregistering and then reregistering Windows Installer.

You may not always be able to completely remove the .NET Framework 2.0 by using the Add/Remove Programs tool in Control Panel. This article also discusses how to work around this issue either by repairing the .NET Framework 2.0 or by manually removing the .NET Framework 2.0 from the computer and then reinstalling the .NET Framework 2.0.
Back to the top
Requirements
The following list outlines the recommended hardware, software, network infrastructure, and service packs that you need:
Microsoft Windows Server 2003, Microsoft Windows 2000 Service Pack 3 (SP3), or Microsoft Windows XP Service Pack 2 (SP2)
Microsoft .NET Framework 2.0.
To obtain the Microsoft .NET Framework Version 2.0 Redistributable Package (x86), visit the following Microsoft Web site:
http://www.microsoft.com/downloads/details.aspx?familyid=0856EACB-4362-4B0D-8EDD-AAB15C5E04F5
To obtain the Microsoft .NET Framework Version 2.0 Redistributable Package (IA64), visit the following Microsoft Web site:
http://www.microsoft.com/downloads/details.aspx?familyid=0856EACB-4362-4B0D-8EDD-AAB15C5E04F5
Note To troubleshoot .NET Framework 2.0 installation issues, you must use an account that is in the Local Administrators group on the computer that is running the .NET Framework 2.0.

This article assumes that you are familiar with the following topics:
Microsoft .NET Framework 2.0
Registry Editor
Windows Installer
Back to the top
Unregister and then reregister Windows Installer
This action corrects most situations. Additionally, this action does not affect any currently installed programs that use the Windows Installer.
Unregister Windows Installer. To do this, click Start, click Run, type msiexec /unregister in the Open box, and then click OK.
Reregister Windows Installer. To do this, click click Start, click Run, type msiexec /regserver in the Open box, and then click OK.
Back to the top
Repair the .NET Framework 2.0
The following are three ways to repair the .NET Framework.
Use the Repair command on the Windows Installer cache file
To repair the .NET Framework 2.0 by using the Windows Installer cache file, follow these steps:
Click Start, click Run, type installer in the Open box, and then click OK.
On the View menu in Windows Installer, click Details, right-click the Name column header, and then click Comment.
Right-click the cached Windows Installer file that has the Microsoft .NET Framework 2.0 RTL x86 enu comment, and then click Repair.
After the repair process has completed, quit Windows Installer.
Run the .NET Framework 2.0 Redistributable package at a command prompt
To repair the .NET Framework 2.0 by using the command prompt, follow these steps:
Locate the Dotnetfx.exe file that you used to install the .NET Framework 2.0. To do this, use one of the following methods:
If you installed the .NET Framework 2.0 from a CD or from a DVD, insert the installation disk in the CD drive or DVD drive.
If you installed the .NET Framework 2.0 from the hard disk, download the .NET Framework 2.0 Setup program to the hard disk.
If you installed the .NET Framework 2.0 from a network drive, reconnect to the network drive.
Click Start, click Run, type cmd in the Open box, and then click OK.
At the command prompt, run the following command:
%InstallationPath%\dotnetfx.exe /t:%temp% /c:"msiexec.exe /fvecms %temp%\netfx.msi"
Note %InstallationPath% is a placeholder for the path of the Dotnetfx.exe file that you located in step 1.
Manually remove and then reinstall the .NET Framework 2.0
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows


Important These steps may increase your security risk. These steps may also make your computer or your network more vulnerable to attack by malicious users or by malicious software such as viruses. We recommend the process that this article describes to enable programs to operate as they are designed to, or to implement specific program capabilities. Before you make these changes, we recommend that you evaluate the risks that are associated with implementing this process in your particular environment. If you choose to implement this process, take any appropriate additional steps to help protect your system. We recommend that you use this process only if you really require this process.
Remove the .NET Framework 2.0 from the Windows Installer cache:
Click Start, click Run, type installer in the Open box, and then click OK.
On the View menu in Windows Installer, click Details.
Right-click the Name column header, and then click Comments.
Right-click the cached Windows Installer file that has the Microsoft .NET Framework 2.0 RTL x86 enu comment, and then click Uninstall.
After the uninstall process has completed, quit Windows Installer.
Manually delete the following from the computer. Note Depending on the current condition of the .NET Framework installation, these items may not exist on the computer.
The URTTemp folder
The Mscoree.dll file
The v2.0.50727 folder
To do this, follow these steps:
Click Start, click Run, type system32 in the Open box, and then click OK. The contents of the System32 folder appear in Windows Explorer.
Locate and then delete the URTTemp folder.
Locate and then delete the mscoree.dll file.

Note If the .NET Framework 1.1 or the .NET Framework 1.0 is also installed on the computer, and you do not intend to reinstall the .NET Framework 2.0, you must repair the .NET Framework 1.1 or the .NET Framework 1.0. For more information, see the "Repair the .NET Framework" section of the following Microsoft Knowledge Base article:
824643 How to troubleshoot Microsoft .NET Framework 1.1 installation issues in Windows XP or in Windows 2000
Click Start, click Run, type microsoft.net in the Open box, and then click OK. The contents of the Microsoft.NET folder appear in Windows Explorer.
In the Microsoft.NET folder, double-click the Framework folder.
In the Framework folder, delete the v2.0.50727 folder.
Close the Framework folder.
Manually delete the relevant registry keys:
Click Start, click Run, type regedit in the Open box, and then click OK to start Registry Editor.
In Registry Editor, locate and then delete the following registry keys.

Note Depending on the current condition of the .NET Framework installation, these registry keys may not exist on the computer.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v2.0.50727
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\policy\v2.0
Quit Registry Editor.
Use the Windows Installer CleanUp Utility (Msizap.exe) to remove Windows Installer information from the registry. The components (Msizap.exe) of the Windows Installer Software Development Kit are included in the Microsoft Windows Software Development Kit (SDK).

The following file is available for download from the Microsoft Download Center:
Download the Windows Installer CleanUp Utility (Msicuu2.exe) package now.
For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591 How to obtain Microsoft support files from online services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:
290301 Description of the Windows Installer CleanUp Utility
To remove Windows Installer information from the registry, follow these steps:
Click Start, click Run, type cmd in the Open box, and then click OK.
At the command prompt, locate the directory that contains the Windows Installer CleanUp Utility, and then run the following command:
Msizap TP {7131646D-CD3C-40F4-97B9-CD9E4E6262EF}
Restart the computer.
Disable all antivirus programs and all firewall programs that you have installed on the computer. To do this, use the System Configuration Utility (Msconfig.exe) to perform a clean start of your computer. Then disable any services that you do not need.

When you use the System Configuration Utility in diagnostic mode, reenable the Windows Installer Service on the Services tab.

To start the System Configuration Utility, click Start, click Run, type msconfig in the Open box, and then click OK.
Delete the contents of the Temp folder:
Click Start, click Run, type %Temp% in the Open box, and then click OK. The contents of the Temp folder appear in Windows Explorer.
In the Temp folder, click Select All on the Edit menu.
On the File menu, click Delete.

Note Delete as many files and folders as possible from the Temp folder.
Reinstall the .NET Framework 2.0. To obtain the Microsoft .NET Framework Version 2.0 Redistributable Package (x86), visit the following Microsoft Web site:
http://www.microsoft.com/downloads/details.aspx?familyid=0856EACB-4362-4B0D-8EDD-AAB15C5E04F5
To obtain the Microsoft .NET Framework Version 2.0 Redistributable Package (IA64), visit the following Microsoft Web site:
http://www.microsoft.com/downloads/details.aspx?familyid=0856EACB-4362-4B0D-8EDD-AAB15C5E04F5
Note If you do not want to reinstall the .NET Framework 2.0, and the .NET Framework 1.1 or the .NET Framework 1.0 is installed on the computer, you must repair the .NET Framework 1.1 or the .NET Framework 1.0. You must repair these installations to replace the Mscoree.dll file and the URTTemp folder.



















How to troubleshoot Microsoft.NET Framework 1.1 installation issues in Windows XP or in Windows 2000：

http://support.microsoft.com/kb/824643

文中节选：

Method 1: Unregister and then reregister Windows Installer
Unregister Windows Installer:
Click Start, click Run, type msiexec /unregister, and then click OK.
Reregister Windows Installer:
Click Start, click Run, type msiexec /regserver, and then click OK.
Back to the top
Method 2: Repair the .NET Framework
There are two options to repair the .NET Framework.
Option A: Repair the .NET Framework 1.1 by using the command prompt
Locate the Dotnetfx.exe file that you used to install the .NET Framework 1.1. To do this, use one of the following methods:
If you installed the .NET Framework 1.1 from a CD or from a DVD, insert the installation disc in your CD drive or DVD drive.
If you installed the .NET Framework 1.1 from your hard disk, download the .NET Framework 1.1 Setup program to your hard disk.
If you installed the .NET Framework 1.1 from a network drive, reconnect to the network drive.
Click Start, click Run, type cmd, and then click OK.
At the command prompt, run the following command:
%InstallationPath%\dotnetfx.exe /t:%temp% /c:"msiexec.exe /fvecms %temp%\netfx.msi"
Note %InstallationPath% is a placeholder for the path of the Dotnetfx.exe file that you located in step 1.
Option B: Repair the .NET Framework 1.1 by using the Windows Installer cache file
Click Start, click Run, type Installer, and then click OK.
On the View menu in Windows Installer, click Details.
Do one of the following, depending on your operating system:
In Windows XP, right-click the Name column header, and then click Comments.
In Windows 2000, right-click the Name column header, and then click Comment.
Right-click the cached Windows Installer file that has the Microsoft .NET Framework 1.1 RTL x86 enu comment, and then click Repair.
After the repair process is complete, exit the Installer.
Back to the top
Method 3: Remove and then reinstall the .NET Framework 1.1
There are two options to remove and then reinstall the .NET Framework 1.1.
Option A: Use the .NET Framework cleanup tool (automatic method)
The .NET Framework cleanup tool will remove and then reinstall the .NET Framework 1.1 for you. For information about how to obtain and to use this tool, visit the following MSDN Web site:
http://blogs.msdn.com/astebner/archive/2005/12/10/502439.aspx
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.
Option B: Modify the registry (manual method)
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows
Remove .NET Framework 1.1 from the Windows Installer cache. To do this, follow these steps:
Click Start, click Run, type Installer, and then click OK.
On the View menu in Windows Installer, click Details.
Do one of the following, depending on your operating system:
In Windows XP, right-click the Name column header, and then click Comments.
In Windows 2000, right-click the Name column header, and then click Comment.
Right-click the cached Windows Installer file that has the Microsoft .NET Framework 1.1 RTL x86 enu comment, and then click Uninstall.
After the uninstall process is complete, exit the Installer.
Manually delete the existing files and folders from your computer. Depending on the present condition of the .NET Framework, this file and folder might not exist .To delete the file and folder, follow these steps:
Click Start, click Run, type system32, and then click OK. The contents of the System32 folder appear in Windows Explorer.
Locate and then delete the URTTemp folder.
Locate and then delete the mscoree.dll file.

Note If the .NET Framework 1.0 is also installed on your computer, and you do not intend to reinstall the .NET Framework 1.1, you must repair the .NET Framework 1.0. For more information, see the "More Information" section.
Click Start, click Run, type Microsoft.NET, and then click OK. The contents of the Microsoft.NET folder appear in Windows Explorer.
In the Microsoft.NET folder, double-click the Framework folder.
In the Framework folder, delete the v1.1.4322 folder.
Close the Framework folder.
Manually delete the relevant registry keys. To do this, follow these steps:
Click Start, click Run, type regedit, and then click OK to start Registry Editor.
In Registry Editor, locate and then delete the existing registry keys (all the registry keys may not be present):
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v1.1.4322
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\policy\v1.1
Exit Registry Editor.
Zap Windows Installer information from the registry by using the Msizap.exe utility. The Msizap.exe utility is included with Microsoft Windows Installer Software Development Kit (SDK). To download Windows Installer SDK, visit the following Microsoft Web site:
http://www.microsoft.com/downloads/details.aspx?FamilyId=A55B6B43-E24F-4EA3-A93E-40C0EC4F68E5&displaylang=en
To zap Windows Installer information from the registry, follow these steps:
Click Start, click Run, type cmd, and then click OK.
At the command prompt, locate the directory that contains the Msizap.exe utility, and then run the following command:
Msizap TP {CB2F7EDD-9D1F-43C1-90FC-4F52EAE172A1}
Restart your computer.
Clear the contents of your Temp folder. To do this, follow these steps:
Click Start, click Run, type %Temp%, and then click OK. The contents of the Temp folder appear in Windows Explorer.
In the Temp folder, click Select All on the Edit menu.
On the File menu, click Delete.

Note Delete as many files and folders as possible from the Temp folder.
Disable all antivirus programs and all firewall programs that you have installed on your computer. To do this, use the System Configuration Utility (Msconfig.exe) to perform a clean start of your computer, and then disable any services that you do not need. When you use Msconfig.exe in diagnostic mode, re-enable the Windows Installer Service on the Services tab. Then, start Msconfig. To do this, follow this step:
Click Start, click Run, type MSconfig, and then click OK
Install the .NET Framework 1.1. To download the .NET Framework 1.1, visit the following Microsoft Web site:
http://www.microsoft.com/downloads/details.aspx?FamilyId=262D25E3-F589-4842-8157-034D1E7CF3A3&displaylang=en
Note If the .NET Framework 1.0 is installed on your computer, and you do not intend to reinstall the .NET Framework 1.1, you must repair the .NET Framework 1.0 to replace the Mscoree.dll file and the URTTemp folder. For more information, see the "More Information" section.

关于证书的添加

2011-07-07 00:29

公司新搞了个citrix的xenapp，让大家可以从外网的PC及Apple和ipad访问oa，结果citrix的浏览器插件装上后，由于证书的原因，一直打不开，显示错误61或86

从浏览器中将显示错误的证书导出，再添加，结果还是不行，最后手动将***.p7b证书导入“受信任的根证书颁发机构”后就OK了。

虽然刚开始的时候将该文件下载下来，右键，安装证书，但由于是放到了默认的位置，而不是“受信任的根证书颁发机构”里面，导致错误

网卡物理地址没了

2011-07-03 10:18
把网线插到另一台机子上后，再插回来，无法上网，ping不通网关，偶尔有ping通一个包，ipconfig /all发现物理地址有，在网卡属性的高级里面查看物理地址，居然是空，手动把物理地址填上，就好了

网卡
网卡地址，物理地址，硬件地址
IP地址，逻辑地址，IP

空密码不能访问共享文件夹

2011-07-03 10:29

空密码用户访问共享文件夹时，总出现问题。开始用两台笔记本的wifi将两台机互联，不能访问，后来加一台路由器，两台笔记本通过无线路由器互联，还是不行，加上密码就好了。估计是系统中权限设置的问题

win7下add分区工具的替代epm

2011-06-24 23:54

EPM

EASEUS Partition Master

今天在win7中运行add，总出问题，最后换成EPM就搞定了。而且EPM是免费版本，而且其安装文件要小很多

word2007不能输入中文的解决

2011-06-15 02:23

打开“控制面板→添加或删除程序”，从列表中单击选中“Microsoft Office Professional edition 2007”，单击“更改”。在Office安装窗口中选中“添加或删除功能”选项，单击“下一步”，单击“选择应用程序高级自定义”复选项，再单击下一步，从中间列表中依次展开“Microsoft Office→Office共享功能→中文可选用户输入法→微软拼音输入法 ”，选择“不安装”，单击“更新”按钮。

完成后即可输入中文，重启后系统输入法多了个微软输入法，再次删除之。


后记：
今天发现在win7 64 下的 word 2007 下还是有不能输入中文的问题，后来在 区域和语言->键盘和语言->更改键盘->文本服务和输入语言->语言栏 里面，有一个“非活动时，以透明状态显示语言栏”，勾上后应用，word立马可以使用中文输入了，甚至连word都不用重启！

网上还有一个方法，Word菜单->工具->选项->选择 编辑 的选项卡-不要勾选‘输入法控制处于活动状态’-确定，重启Word，在word 2007中是 word选项->高级 中，去掉“输入法控制处于活动状态”的勾。估计可以，因为这两种方法是相关联的。

mstsc历史记录的删除

2011-06-12 10:39

HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\Default

进去选择要删的项

ff4频繁假死/卡的解决

win7 64 下的 firefox 4.0.1
这个版本界面不错，几乎所有浏览器都朝这个方向发展，包括IE、Chrome、Opera，还有ff
但自从用了firefox 4.0 后，常常卡，频繁假死，等好一会儿，自己又好了，网速慢的时候尤其如此。相对于占用内存来说，内存现在都够用，不去考虑，但这个频繁卡的问题不得不解决。网上查到的和两个有关：一个是ff的flash插件和plugin-container.exe之间的问题，另一个是ff设置中的钓鱼侦测。

1.
firefox 4 把插件放到了plugin-container.exe 中，好处是插件崩溃了，不影响整个浏览器，但碰巧的是flash插件在ff上老是出问题，老是喜欢卡住，过一会儿又好，而且在网速慢的时候越是容易假死，flash老喜欢后台连他自己的那个网站，不知道是不是和这个有关系，可能是连不上就狂耗资源。
既然二者不配合，那么可以考虑两边。最好的解决方法是找到一个比较好的flash插件版本，重装flash插件；
不行的话只能考虑plugin-container这边，解决方法是针对所有插件禁用plugin-container（进about:config中把dom.ipc.plugins.enabled改为false），或者针对flash禁用plugin-container（进about:config中把dom.ipc.plugins.enabled.npswf32.dll改为false）
除了flash player插件外，其他插件也有嫌疑，也可以关注下

2.
ff设置中的钓鱼侦测是有用的，最好不要动，如果确实是这个原因，那么可以用如下方法解决：
首先，进入ff设置，安全，把“Block reported attack sites”和“Block reported web forgeries”这两个的勾去掉，
之后，删除或重命名用于存储钓鱼侦测的 sqlite 文件：进入
Vista/Win7：C:\Users\用户名\AppData\Local\Mozilla\Firefox\Profiles\随机数字.default\urlclassifier3.sqlite
XP：C:\Documents and Settings\用户名\Application Data\Mozilla\Firefox\Profiles\随机数字.default\urlclassifier3.sqlite
删除或者重命名 urlclassifier3.sqlite
启动ff即可



后记：
现在发现，重装flash player插件后，使用ff 64的浏览器还没有出现异常，除了第一次使用时立马崩溃了一次之外，即使在用入门型3G手机连电脑这种网速很慢的情况下也没有出现异常。

本地127.0.0.1的端口可通，IP端口不通的解决

症状：
在本机
telnet 127.0.0.1 端口号，能通
telnet IP 端口号，不通
在其他机，能ping通，但telnet到端口不通
原因：
TCP/IP筛选开启，选择了“只允许”，但里面没内容
解决：
TCP/IP筛选选择“全部允许”

附：
TCP/IP筛选（网卡属性） 和 IP安全策略（控制面板->本地安全策略中的一项） 区别：
前者粗，针对所有应用，同一采用开启或者不开启某项端口或协议
后者细，因为后者是基于策略的