http://learn.iis.net/page.aspx/246/using-fastcgi-to-host-php-applications-on-iis-7/

Table of Contents

• Overview
• Enabling FastCGI support in IIS 7
  • Windows Server 2008
  • Windows Vista SP1
  • Update for the FastCGI module
  • Administration Pack for IIS 7
• Install and Configure PHP
• Configure IIS to handle PHP requests
  • Using IIS Manager
  • Using command line
• Best practices for configuring FastCGI and PHP
  • Security Isolation
  • Process recycling
  • PHP versioning
  • Security recommendations
• Per-site PHP configuration
• URL rewriting for PHP applications
• Related Resources

本文链接：http://www.cfresh.net/pc-tech/662

友情链接：通过SSH利用Tunnelier+Privoxy实现任意浏览器翻墙

  臣本屁民，蜗居于天朝，苟全性命于网络，不求闻达于四海。
        敢封哥的网，先从哥的尸体上跨过去！ 

       扯淡完毕，切入正题。
       翻墙术大概分这么几种：
       修改hosts文件，https（SSL）安全浏览，在线代理，VPN，SSH等。
       这里秋天选择一种：SSH来讲解，此方法以FireFox配合为例，采用SSH+Tunnlier+firefox+AutoProxy实现完全无障碍翻墙，其他应用举一反三。 

       第一步，SSH账号的获得
       首先，要拥有一个SSH账号，方法有很多种：网上搜索可得，购买空间可得，免费注册可得 etc.
       购买很多国外的空间都会赠送SSH账号；当然也有免费的午餐。

       ======================2010.8.4更新======================

       根据众多网友的反映，由于本文原本提及的cjb.net网站免费ssh服务后来出现不稳定的情况，秋天不再做推荐。在此可以使用另一高速且无需注册的SSH账号服务：Shellmix，根据秋天的试用，试用此SSH通过直接SSH转socks代理后在firefox下观看电影几乎不需缓冲。如果发现Shellmix服务不可用，请自行在Google上搜索”free ssh account”寻找新的免费SSH服务。

       Shellmix提供了两个免费SSH账号，对应不同的服务器，服务器端口均为30，详情如下：

       SSH账号1主机地址：shellmix.com
       登录账号：newusershell
       登录密码：newusershell

       SSH账号2主机地址：fgfg.pl
       登录账号：newuser
       登录密码：newuser

       至此，你已经又有了一个长期有效且免费的SSH账号了，接下来看如何配合FireFox使用。 

       PS，有人会问：你不是Opera的忠实粉丝吗？
       答：为了在方便调试博客(www.cfresh.net)和一些其他临时用途，秋天装了一个绿色版FF备用。 

       ======================2010.5.15更新======================

       由于MyEnTunnel使用Plink核心，存在连接不稳定和转化效率低的情况，现推荐使用Tunnlier替代MyEnTunnel作为SSH客户端，其余步骤配置仍同本文。如果你的网络浏览器/软件不支持Socks代理，请移步另一篇文章：通过SSH利用Tunnelier+Privoxy实现任意浏览器翻墙。

       第二步，使用客户端软件Tunnlier连接SSH
       软件下载地址：
        安装版：http://dl.bitvise.com/Tunnelier-Inst.exe
        绿色版：http://tp.vbap.com.au/download       

        安装版安装完成后，启动软件，来到如图所示界面，依次输入SSH服务器地址、用户名、端口（shellmix使用30端口，一般空间提供的SSH为22端口）、密码，并勾选”Password”下的”Store encrypted password in profile”，如图：

         接下来切换到”Options”选项卡，进入选项配置
        因为Tunnelier默认在连接SSH服务器时开启SFTP和命令行SSH终端，如果你并不需要可以在”On Login”下框选取消”Open Terminal”和”Open SFTP”。

        继续切换到”Services”选项卡，进入服务配置
        勾选”SOCKS/HTTP Proxy Forwarding”下的”Enabled”选项框，第一行监听地址输入127.0.0.1，第二行监听端口输入socks转发端口，如1080，第三行保持0.0.0.0不变。再点左侧的”Save Profile As”按钮，将当前的配置保存为文件方便以后软件启动时调用。 

        至此SSH客户端Tunnelier设置完成，接下来开始安装Firefox插件。

       第三步，配置FireFox
       给FireFox添加插件：”AutoProxy”，此插件专门为应对GFW而生，在此大力表扬一下软件作者！
       添加完毕后重启FF，然后你会看到一个对话框，选择gfwlist (P.R.China)后，点击”确定”。 

       接着你会看到Firefox主界面右下角出现有一个“福”字图案，点击“福”，然后点击菜单”代理服务器”–”编辑代理服务器”      

        这时会看到它提供了很多种代理方式，如Tor、GappProxy、Puff等，需要注意的是将”ssh -D”代理端口设置与My Encrypted Tunnel端口（非SSH端口）保持一致（7070）。

       点击”确定”回到插件设置主界面，点击”代理服务器”–”选择代理服务器”，在”主代理”下拉菜单中选择”ssh -D”，返回插件主界面，接着”确定”。       

       这时再打开你的FF，空气是不是清新多了？ 

       顺便提一下秋天利用GAE搭建的两个代理类API：
       1，支持https安全访问的在线代理服务器：https://flow-proxy.appspot.com（注：该程序不支持cookies）；
       2，一个twitter代理API：http://x-flow.appspot.com/ 

http://hi.baidu.com/zangchunlai/blog/item/3007f419bcb26670dbb4bd6f.html

showDialog里好像不能用href,只能用onclick

最近在项目中经常用到模态窗口(showModalDialog)，客户需要在一个模态窗口中有"生成Excel报表"并"导出"的功能。接到任务后，直接就开始按常规操作实现。
    在按钮的Click事件中，根据模板生成Excel报表，填充数据，保存到临时文件夹，然后用Response.WriteFile函数输出文件，一切看上去都很顺利。代码如下：

            //根据数据集创建Excel报表并返回Excel报表路径
            string fileName = CreateExcel(ds);
            Response.Clear();
            Response.Charset = "utf-8";
            Response.Buffer = true;
            this.EnableViewState = false;
            Response.ContentEncoding = System.Text.Encoding.UTF8;
            Response.AppendHeader("Content-Disposition", "attachment;filename=" + HttpUtility.UrlEncode(fileName, System.Text.Encoding.UTF8));
            //设置输出文件类型为excel文件。
            Response.ContentType = "application/ms-excel";
            Response.WriteFile(fileName);
            Response.Flush();
            Response.Close();
            Response.End();

    但是当完成了代码，开始测试的时候，却发现点击"导出"按钮没有反应。开始的时候以为是创建Excel报表的代码有问题，但经过调试后，证实创建Excel代码没有问题，也成功的在临时文件夹下生成了Excel报表，但是却没有"导出"报表(没弹出下载文件对话框)。再看输出文件的代码，应该也没有问题，之前一直这样输出都没有问题的。
    在百思不得其解的时候，发现了一个关键点。就是之前输出文件成功的面页都是一般的网页窗口，而这次的操作却是在模态窗口中。问题会不会出在这里呢？赶紧试验了一下。把模态窗口改成了一般的网页窗口，果然可以输出文件没问题，也成功下载了报表。
    虽然问题有点怪异，但找到了切入点和问题的关键所在，解决应该就不难了。google一下，发现模态窗口定义了<base target="_self">，这应该是问题所在。然后在页面中重新定义了这个标签，改成了<base target="_blank">，问题成功解决，文件可以正常下载了。但这时候又来了新的问题，下载是可以了，但是却会弹出一个新页面，在模态窗口中下载再弹出页面肯定影响了用户体验。有没有方法在模态窗口中直接下载而不弹出新的页面呢？既然target=_self的时候有问题，target=_blank的时候又会弹出新的页面，这让我想到了在框架中打开新窗口的做法。在页面中加一个看不到的框架，然后把target设为框架名应该可以解决。随后在页面中再加了一个大小为0的iframe

<iframe id="download" name="download" height="0px" width="0px"></iframe><!--用iframe模拟文件下载-->
然后重新修改<base>标签target为框架名：

<base target="download">
重新生成，浏览，测试。问题成功解决。

http://hi.baidu.com/longx5/blog/item/508357112f2fe18b6538db96.html

Per User; Enterprise License; 4954438; 300

http://ts2blogs.com/blogs/rwagg/archive/2009/09/04/aero-glass-on-remote-desktop-services.aspx

As you’ve already read, we’ve renamed Terminal Services to Remote Desktop Services (RDS) in Windows Server 2008 R2. RDS also gives us the ability to leverage Aero Glass from a Remote Desktop Connection.  This is a multi-step process, but there are really two phases.  Phase I is enabling the Desktop Experience functionality on a Server 2008 R2.  Phase II is enabling the Remote Desktop Services functionality on the server.  While an Administrator is able to have one RDP connection to a server, Aero functionality is not enabled until the Remote Desktop Host role is enabled.  I’ve provided a lot of screen shots and narrative as I walk through the process of enabling RDS and the Aero Glass functionality.

Phase I

Install the desktop experience by adding the Desktop Experience feature.

As you go through this wizard, when you choose the Desktop Experience it will ask you to confirm the installation of the Ink and Handwriting Services as well.  This is required, just choose Add Required Features and move on.

During the installation of the Desktop Experience feature, the server will require a reboot.  Once the server is rebooted and you log back in, you’ll be presented with the Installation Results screen.

Now that you’ve installed the Desktop Experience feature, you need to enable the Themes service.  Go into your services and now this Themes service shows up, but it’s disabled.  Set it to Automatic and then go ahead and start the service.

At this stage, you’ll have the Windows Desktop experience installed on the server.  To take advantage of it from a Remote Desktop Connection, you need to ensure that you’ve enabled 32 bit colors and the Desktop Experience functionality in your RDP connection, as shown below.

Under Colors, choose Highest Quality (32 bit)

Take note that Aero over RDP is bandwidth intensive, so I’d suggest that you not try to use this functionality over a WAN. 

Phase II – Enabling Remote Desktop Service Role (RDS).

You have to enable RDS on your server anyway if your providing Remote Desktop Services to your users.  You also need RDS to be installed if you want to use Aero Glass.

Install the Remote Desktop Services Role

Now you get to choose the detailed functionality in RDS that you want to leverage.

You need to enable Remote Desktop Session Host if you want Aero Glass, and then we will configure the additional services to be delivered, including the Client Experience.  This is where we get to define the detail of the client experience. 

Once everything is configured you can confirm that Aero Glass is now enabled on your server in a few different ways.  The first is the obvious, check out the transparent windows in your Remote Desktop connection.  The second way is that the Windows Color screen on the Personalization menu is now “different” than it was prior to the installation of the client experience. 

Here’s a shot of the new Windows Color screen that now includes the Enable transparency check box.

Below is a shot of the old screen, before Aero Glass is enabled.  Take note: this “old screen” is still available after the Aero installation, it’s accessed by choosing Advanced appearance settings… from the Windows Color and Appearance window (above).

Now that we have everything enabled, let me show you a screen shot of the Windows Server 2008 R2 desktop with Aero Glass enabled.

Here’s a shot of Aero Peek on the same Server 2008 R2 server.

I hope this helps you setup your remote desktop connections with the same desktop experience as a Windows 7 Desktop.  Remember that with Aero over a Remote Desktop connection, bandwidth is critical.  A LAN connection will provide a much better experience than a WAN connection.

Until next time,

Rob

Step 1

On your VMware Windows host, open a command prompt window by clicking Start --> Programs or All Programs --> Accessories --> Command Prompt or choosing Start --> Run --> type 'cmd' --> press Enter or click 'OK'.

Next, change directories to where your VMware server or workstation application files are installed. In this example we will use VMware Workstation. At the command prompt type: cd c:\program files\vmware\vmware workstation and press 'Enter'

Step 3

Run VMware vdiskmanager by typing the following:
C:\program files\vmware\vmware workstation\vmware-vdiskmanager -x 50Gb c:\my virtual machines\windows xp\windows.vmdk, press Enter. This will expand the VMDK file windows.vmdk located in the directory c:\my virtual machines\windows xp\ to 50 gigabytes.

(Note: on linux, normally it's /usr/bin/vmware-vdiskmanager)

Step 4

You must now wait for the expansion to complete. A progress indicator will be displayed. When the process is complete, type 'exit' to close the command prompt window.

Step 5

Insert a Windows PE or BartPE CDROM into your CD/DVD drive or edit the virtual machine settings, select CD/DVD and attach an .ISO image file of one of the above cd's.

Step 6

Boot your virtual machine and quickly press F2 to enter the BIOS. Once in the BIOS make sure the CD/DVD is set ahead of the local hard disk in the Boot Order screen. Save your changes and exit the BIOS.

Step 7

Once the Windows PE or BartPE CD starts, open a command prompt and type the following:

c:\>DISKPART --> press Enter
DISKPART> type 'list disk' --> press Enter
DISKPART> type 'list volume' --> press Enter
DISKPART> type 'select volume=#' (where # is the number of the volume you wish to extend) --> press Enter
DISKPART> type 'extend' --> press Enter to extend the disk file.
DISKPART> type 'exit' --> press Enter to exit diskpart.

Step 8

Shutdown and reboot the virtual computer for the changes to take effect

http://www.thewindowsclub.com/get-the-show-desktop-icon-back-in-windows-7-taskbar#ixzz0qEKTQtMc 

While you have Show desktop transparent vertical bar at the right side end of the taskbar which also adds the functionality of Desktop Peek, it appears that there are some who miss the old Show desktop icon which appeared on the left side of the taskbar.

To get it back, simply follow these steps in the order mentioned:

1. Copy-paste the following in a Notepad and save it as Show desktop.scf on your desktop.

[Shell]
Command=2
IconFile=explorer.exe,3
[Taskbar]
Command=ToggleDesktop

2. Assuming that your Windows 7 is installed on C Drive, cut-paste this Show desktop.scf file in folder:
C:\Users\%Username%\AppData\Roaming\Microsoft\Internet Explorer\Quick Launch\User Pinned\Taskbar. To open this folder, simply copy paste this address in the explorer address bar and hit Enter.

3. Now create any temporary shortcut of  anyone of your other (.exe) applications on your desktop. Rename it to Show Desktop.

Next, right click on it and select Change icon.
Select the Show Desktop icon from the following folder :
C:\Windows\System32\imageres.dll
Click Apply > OK.
NOW right click and Pin to Taskbar. Then you can remove this icon.

4. Now right click on this shortcut icon pinned in C:\Users\%Username%\AppData\Roaming\Microsoft\Internet Explorer\Quick Launch\User Pinned\Taskbar directory and select its Properties.

5. In the Shortcut tab, change its Target to:

C:\Users\%Username%\AppData\Roaming\Microsoft\Internet Explorer\Quick Launch\User Pinned\TaskBar\Show desktop.scf

You will now get the Show desktop icon in the Windows 7 in the location it should be and it will look & behave the way it should look & behave! Drag and drop it to the desired position.

Alternatively, you may also want to check out these freeware

1. press win+r key and Type Regedit at run prompt

2. Locate following registry key

HKLM\Software\Microsoft\Windows\CurrentVersion\Authentication\LogonUI\Background

3. Now in right-side pane, change value of OEMBackground to 1.

4. Now place your custom image in %windir%\system32\oobe

5. Create a new folder info and background within newly created info folder

Folder path should look like this %windir%\System32\oobe\info\backgrounds

6. Now place your desired logon wallpaper within this background folder with file name as backgroundDefault.jpg

Images Name with resolutions

backgroundDefault.jpg

background768×1280.jpg (0.6)

background900×1440.jpg (0.625)

background960×1280.jpg (0.75)

background1024×1280.jpg (0.8)

background1280×1024.jpg (1.25)

background1024×768.jpg (1.33-)

background1280×960.jpg (1.33-)

background1600×1200.jpg (1.33-)

background1440×900.jpg (1.6)

background1920×1200.jpg (1.6)

background1280×768.jpg (1.66-)

background1360×768.jpg (1.770833-)

Please NOTE: Images must be less than 256kb in size

The backgroundDefault.jpg image is loaded and stretched-to-fit when a resolution/ratio specific background cannot be found.

Tuning Physical Standby part I

IT职场求生法则
http://www.cnblogs.com/umlonline/archive/2010/05/10/1731741.html

http://www.cnblogs.com/saul/archive/2010/04/20/1715793.html

纵览,国内比较大的软件公司(以下统一简称"国软"),清一色都是做政府项目的(他们能做大的原因我就不用说了吧),真正能做大的国软又有几家呢?这是为什么呢?
今天风吹就给大家简单分析下:

1."作坊"式管理
  "作坊"往往是效率最高的,国软几乎都是从作坊走过来的,
   但把作坊式的管理模式套用到一个不断壮大的公司中显然是不行的.
   组织架构到达一定程度后就必然要进行分工的细化,依靠作坊式的"暴力开发"是行不通的.

2."法制社会"
   上班必须打卡,迟到要扣钱,还一次比一次多,加班没有加班费,反正算下来就是,只有扣钱的项目,没有加钱的项目.
   比起外企,人家上班不打卡,迟到不扣钱,加班有加班费,这样宽松点的环境不好吗?
 
3.自身自灭
   国软一般没有师徒制,有的话也只是形式上的,公司基本没人管你,你也不用去管别人,
   新进的员工,不管会不会,先丢个东西给你做,自己研究,不懂的google去.
   这也是为什么国软喜欢招有经验的人,因为没经验的人熬不住,跑了几个以后,国软就不招了.

4.销售-开发-维护脱节
   这点是非常严重的,会直接导致项目流产的.国软的典型的做法是,销售为了业绩,在没有调研的情况下就签了合同(这里主要是指项目型的,产品型的一般可以控制),而且合同的范围也非常模糊,可大可小,接下来就是调研人员上场,调研后发现,10w块钱的合同,调研出来了100w的需求,接下来就是和客户扯皮,最后直接导致项目流产,甚至打上官司.项目或产品上线后,维护人员对系统不了解(一方面是没有文档,另外一方面维护人员一般没有参与到开发中),接下来往往就会发生两种情况:

   a.维护人员在不了解系统的情况下擅自修改,结果导致系统越改问题越多.

   b.维护人员一不做二不休,所有客户反馈的问题全部打回给开发人员,于是开发人员就生不如死,在做别的项目的同时还要维护以前的项目,结果就是导致几个项目都失败.

5.缺乏规划
   今天要用这个,明天想用那个(笔者就经历了公司在半年的时间内对框架进行了两次大的变动,导致开发人员都必须重新学习框架)
   产品也接,项目也接,大的也接,小的也接.

   今天领导说往左走,明天说往右走,也不能怪领导,他也没经验,我们就是他的DEMO.
   公司没有一个明确的目标,要做成什么样,只是一味的提出做大做强,但是没有规划出如何做大做强.(和我的标题一样哦)

6.三无-无需求,无设计,无测试.
   a.没有文档是国软的通病,曾几何时,产品经理丢过来的那一句话:"喂,**,给我做一个**模块来",然后开发人员就开始埋头苦写了.
   b.当然如果你天资聪慧,可以轻易理解出产品经理的意思,那有没有设计都无所谓了,但是,当有一天别人要维护你的程序的时候问题就出现了,
   没有文档,代码又那么天马行空,怎么维护?改了这个地方,又影响了那个地方...
   c.其实程序员都懂得测试的意义,可以工时安排的那么紧,哪来的时间测试?测试又没有算工时.所以几乎所有的程序员的做法就是,直接丢给用户测试
   这时候有人肯定要问:那项目经理呢?他不是可以测试吗?请记住这是国软,刚才写代码的那个人就是项目经理,还是售前,还是设计人员,还是维护,还是...
   归结还是成本问题,在外资软件公司中,做文档的工时是比做开发的工时更多的,国软为了节省成本,这块当然要CUT掉了.不必去追去文档有多么详细多么美观,需要做的就是找到一个平衡点,一份适合自己的文档.

7.员工都是"十项全能"
  在国软里面的员工各个都是十项全能(笔者就是一个鲜明的例子,从系统调研分析设计,到进度管理,开发,测试,验收,实施,维护,甚至拉给客户拉网线都需要我去.)
  直接导致的结果就是这些员工每过多久就直接出来自己开公司了...嘿嘿又一家作坊诞生了...
  这样做对员工个人其实是有好处的,但是对于企业本上来说是没有好处的,并不是说员工成立了作坊,成为了你的竞争对手,而是让员工各个都是十项全能的结果就是
  a.员工都是"十项全不能".
  b.员工一旦离职,他手头的项目必定流产.
  c.对公司的发展是不利的(细化分工).

8.莫不关心
  老板并不知道员工在做什么,员工也不知道老板在做什么.
  上级很少去关心下级的工作,更别说去关心下级的生活,一个东西丢给你,一个月后交差,中间不管你任何事情,交不了差就唯你是问.
  下级也不知道能为上级分担什么,只有等着上级分配任务.
  甚至还有些老板都不不知道员工的名字,在这样的国软的,每个人都是孤立的,又怎么能做大做强呢?

9.企业文化
  所谓十年树木,百年树人.
  国软的企业文化表面功夫算是做的很好的了,什么"为客户创造价值","做最好的行业解决方案","软件公司的最大资源就是人才"等等,要多华丽有多华丽,
  重复体现了"口号文化".真正做到企业文化又有多少呢?有多少仅仅是为了做给客户看的呢?

10.盲目跟风
  很多国软看到人家外企软件公司最近在搞什么推进活动,就跟风,效仿外企做,可是无法领悟精髓,纯粹只是在模仿.
  (外企集体笑:"一直被模仿,从未被超越")
  做完了也不知道这么做的意义,劳民伤财.

11.缺乏"执行力"
  国软的通病,就是"执行力",国软的学习劲头很足,今天提出要完善测试标准,明天提出要每周写工作报告,可是又有哪些东西能真正的去执行呢?
  导致这个问题的主要原因有两个:

  a.提出来的东西到底有没必要做,还是只是应付领导走个过场.
  b.谁来跟踪这些东西?员工写了工作报告,领导没有去查看,去反馈,员工觉得写的也没意义,自然不会继续执行下去.

12.管理混乱
    没有划分清楚员工的归属组织,员工并不明确他的上级领导是谁,导致有的员工处于游离状态,有的是员工又是多个领导,不懂要听谁的,有些人忙的要死,有些人又闲的要命,最后搞的最痛苦的就是员工,导致员工离职.

13.缺乏团队精神
   为什么会缺乏团队精神呢?并不是国软没有这方面的概念,国软也很希望培养员工的团队观念和精神,
   无奈因为国软,一般都是一个人负责一个或者多个项目,连团队都没有,何来的团队精神?

14.无法做到补足
   一个项目一旦中途有人辞职,这个项目就会流产.
   一个员工一旦辞职,会有N个项目没人维护.
   A组的员工无法胜任B组的工作,归根结底就是组织上根本没有考虑过组织变动对项目的影响,没有提前培养人员.

15.一成不变和随心所欲
   有两类人一种是把前辈的东西COPY过来,不作任何修改,因为他深信,前辈的一定是对的,
   还有一类是不管前人怎么做的,一律不要,全凭自己的"经验",随心所欲,天马行空的进行自主研发,

   造成的结果就是错的还是错的,乱的更乱了.

16.人才育成
   成本,还是成本,培养一个人要多少成本?
   这就是国软做不大的原因,永远只能停留在"作坊"的原因.

17.向心力.
     老板做的是事业,员工做的是事情,这是国软员工的一致观点.

18.恶性循环
     a.人员力量不足 -> 接不了项目 -> 收入少 -> 人员流失.
     b.人员力量不足 -> 强行接项目 -> 亏本    -> 破产.

Ultimate Key from internet: YCFHQ9DWCYDKV88T2TMHG7BHP
hxxp://download.microsoft.com/download/2/4/7/24733615-AA11-42E9-8883-E28CDCA88ED5/X16-42552VS2010UltimTrial1.iso

http://www.google.com/prc/report.html#hl=en

http://jhdba.wordpress.com/2008/03/04/ora-27054-when-using-rman-to-nasnfs-disks/

http://weblogs.asp.net/scottgu/archive/2010/03/11/asp-net-mvc-2-released.aspx

I’m happy to announce that the final release of ASP.NET MVC 2 is now available for VS 2008/Visual Web Developer 2008 Express with ASP.NET 3.5.  You can download and install it from the following locations:

• Download ASP.NET MVC 2 using the Microsoft Web Platform Installer
• Download ASP.NET MVC 2 from the Download Center

The final release of VS 2010 and Visual Web Developer 2010 will have ASP.NET MVC 2 built-in – so you won’t need an additional install in order to use ASP.NET MVC 2 with them. 

ASP.NET MVC 2

We shipped ASP.NET MVC 1 a little less than a year ago.  Since then, almost 1 million developers have downloaded and used the final release, and its popularity has steadily grown month over month.

ASP.NET MVC 2 is the next significant update of ASP.NET MVC. It is a compatible update to ASP.NET MVC 1 – so all the knowledge, skills, code, and extensions you already have with ASP.NET MVC continue to work and apply going forward. Like the first release, we are also shipping the source code for ASP.NET MVC 2 under an OSI-compliant open-source license.

ASP.NET MVC 2 can be installed side-by-side with ASP.NET MVC 1 (meaning you can have some apps built with V1 and others built with V2 on the same machine).  We have instructions on how to update your existing ASP.NET MVC 1 apps to use ASP.NET MVC 2 using VS 2008 here.  Note that VS 2010 has an automated upgrade wizard that can automatically migrate your existing ASP.NET MVC 1 applications to ASP.NET MVC 2 for you.

ASP.NET MVC 2 Features

ASP.NET MVC 2 adds a bunch of new capabilities and features.  I’ve started a blog series about some of the new features, and will be covering them in more depth in the weeks ahead.  Some of the new features and capabilities include:

• New Strongly Typed HTML Helpers
• Enhanced Model Validation support across both server and client
• Auto-Scaffold UI Helpers with Template Customization
• Support for splitting up large applications into “Areas”
• Asynchronous Controllers support that enables long running tasks in parallel
• Support for rendering sub-sections of a page/site using Html.RenderAction
• Lots of new helper functions, utilities, and API enhancements
• Improved Visual Studio tooling support

You can learn more about these features in the “What’s New in ASP.NET MVC 2” document on the www.asp.net/mvc web-site. 

We are going to be posting a lot of new tutorials and videos shortly on www.asp.net/mvc that cover all the features in ASP.NET MVC 2 release.  We will also post an updated end-to-end tutorial built entirely with ASP.NET MVC 2 (much like the NerdDinner tutorial that I wrote that covers ASP.NET MVC 1). 

Summary

The ASP.NET MVC team delivered regular V2 preview releases over the last year to get feedback on the feature set.  I’d like to say a big thank you to everyone who tried out the previews and sent us suggestions/feedback/bug reports. 

We hope you like the final release!

Scott

http://www.cnblogs.com/sumtec/archive/2009/07/10/1520216.html

你的站点有被客户投诉很慢吗？是不是查了很多遍还是没有完全解决？是不是数据库没有发现异常，CPU也没有异常，内存占用量没有异常，GC计数没有异常，硬盘IO也没有异常，带宽没有异常，线路没有异常，没有丢包，但就是被投诉？而且还是阵发性的，有某个用户投诉慢的时候，你访问却很快，本地又复现不出来？今天你访问了博客园真是太幸运了，也许这里就有你想要的一个答案——假如你的站点动态处理了图片或者其他原本不会动态处理的非网页资源的话。没想到吧，这是Session惹的祸！

我们公司某个站点访问量一直很大，几年前就已经发现客户经常投诉说很慢，而这个问题我们一直都在排查和解决。从线路问题，到数据库连接泄露，到数据库死锁、索引，以及程序的优化问题，我们都查找过，并且解决过。然而，这个问题总还是存在。比如说，在IIS日志中，就会经常看到time-taken大于10秒钟的访问。而最近我们的KPI要求解决这个问题，不得已，再次踏上这趟艰难的排查之旅。

之所以说艰难，是因为这个现象在本地几乎无法复现，一个是这个现象是阵发性的，第二个是本地访问量或者数据量不够大。我们也尝试过在本地加载线上服务器的数据库，然后拿服务器的IIS的Log文件重播，结果确实是偶尔发现IIS日志中的time-taken也会比较长，但是本地服务器性能不如线上服务器的，比如说IO就差很远，于是总说不清楚到底是什么问题。而线上服务器也不方便用做Dump的形式查找：第一是因为线上一做Dump，站点就会在几分钟内失去响应，这样我们客服的电话就会被打爆；另一个原因还是阵发性的问题，我们不可能一直盯着性能看，然后在发生问题的瞬间做Dump。再说了，看性能也看不出来，因为那些响应时间很长的访问，其前后附近的响应都特别的快。不可避免的，我们只能够在代码里面塞入一些调试和日志的代码，以期望能够得到一些有用的信息。

最开始的时候，我们认为最可能的原因是数据库阻塞，比如正好某一个访问锁住某个数据库对象（比如一张表或者某几行），如果这个时候访问特定的页面，可能就会比较慢。于是在数据库层塞入了一堆代码，这些代码会在数据库连接数量多，或者某个数据库连接时间特别长的时候，将所有数据库连接的当前访问语句、连接持续总时间，以及这些连接当前的堆栈情况都输出到文件中。与此同时，我们还打开Sql profiler对这个数据库进行监视，将持续时间超过1秒钟的都记录下来。然而跑了一天之后，却发现什么都没有被记录下来，但IIS日志中仍然在这段时间内出现许多10秒以上的访问。这个时候，我们就意识到，可能方向错了。

接着，我们就开始塞另外一段代码：一个IHttpModule。这个模块就只是截获每一个页面访问的完整生命周期中的所有事件，比如BeginRequest、PreAuthenticateRequest等。同时在BeginRequest开始的时候设置一个定时器，每隔一秒钟就会出发一个事件，来记录本次访问过程中，本模块收集到的所有线程中当前的堆栈情况。最后，在EndRequest的时候，如果访问时间超过5秒，就将之前截获的所有信息输出到文件中。这一下子问题就变得非常的清晰了，比如说，下面这种输出（片断）就是非常典型的一个情况：

#Steps:
#Fields: date time threadId stepName
#---------------------------------------------------
2009-07-09 16:48:01.752 0024 BeginRequest
2009-07-09 16:48:01.752 0024 AuthenticateRequest
2009-07-09 16:48:01.752 0024 PostAuthenticateRequest
2009-07-09 16:48:01.752 0024 AuthorizeRequest
2009-07-09 16:48:01.752 0024 PostAuthorizeRequest
2009-07-09 16:48:01.752 0024 ResolveRequestCache
2009-07-09 16:48:01.752 0024 PostResolveRequestCache
2009-07-09 16:48:01.752 0024 PostMapRequestHandler
2009-07-09 16:48:06.284 0007 AcquireRequestState
2009-07-09 16:48:06.284 0007 PostAcquireRequestState
2009-07-09 16:48:06.284 0007 PreRequestHandlerExecute
2009-07-09 16:48:06.284 0007 EndRequest
#---------------------------------------------------
#End of steps.

也就是说，在PostMapRequestHandler之后，AcquireRequestState之前，有一大段的等待时间。而这个报告后面的堆栈情况，则显得很奇怪：线程7从第一次截快照的时候开始，一直到结束都是空白的！甚至在其他的一些报告中甚至会发现这个线程已经被分派处理其他页面的工作了（堆栈中的调用很明显指出是另一个aspx页面的代码）。结果一Google“PostMapRequestHandler”和“AcquireRequestState”这两个关键字，就找到了国外另一个有类似遭遇的受害者：

http://forums.iis.net/t/1147300.aspx

这个楼主是一个aspx页面里面有好几个iframe，并且每一个iframe里面都是访问同一个Web应用下的Aspx页面。现象就是iframe内的页面会一个个蹦出来，尤其是这些页面都比较慢的时候。和我这里截获到的情况一样，也是PostMapRequestHandler事件到AcquireRequestState之间有很长的空白时间。顺藤摸瓜，又找到了这么一个帖子：

http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.dotnet.framework.aspnet&mid=7f56033f-caac-47c2-bd9c-95512aa14b47

原来，在AcquireRequestState之前，需要等待上一个同SessionId的页面处理完毕之后，才会继续处理当前页面。其根本原因是：同一个SessionId下面的Session对象不应该被同时写入，否则就会全乱套了，原理和多线程竞争是一样的。因此在设计上，同一个SessionId的页面（或者IHttpHandler）就会顺序执行。

好了，到这里真相又一次大白了！（指不定还有别的问题，还会有下一次大白的时候）在我们的系统中，由于特殊的原因，对图片的输出我们会通过Asp.Net来处理，比如说加上一些合适的缓存标记，甚至会动态生成图片输出（令人惊讶的是，这个动态输出的总时间消耗甚至不到100毫秒，所以不要说动态生成是一种不好的实施方式）。但是，由于没有经过特殊处理，Asp.Net底层认为这些访问时需要对Session进行写操作的，于是就在AcquireRequestState之前挂起，等待上一次同SessionId访问结束。可想而知，图片多了就会导致排队，甚至排很长的队。如果在排队结束之前访问下一个页面，正好系统又没有丢掉之前的队列，则这次访问就会变得比较漫长了。那么怎么做呢？ 在一次顺藤摸瓜，找到了确切的说法：

http://msdn.microsoft.com/en-us/library/ms178581.aspx

注意下面的这段话：

Concurrent Requests and Session State

Access to ASP.NET session state is exclusive per session, which means that if two different users make concurrent requests, access to each separate session is granted concurrently. However, if two concurrent requests are made for the same session (by using the same SessionID value), the first request gets exclusive access to the session information. The second request executes only after the first request is finished. (The second session can also get access if the exclusive lock on the information is freed because the first request exceeds the lock time-out.) If theEnableSessionState value in the @ Page directive is set to ReadOnly, a request for the read-only session information does not result in an exclusive lock on the session data. However, read-only requests for session data might still have to wait for a lock set by a read-write request for session data to clear.

上述参考文献中，并没有说明如何对不是Page的IHttpHandler如何设置，这里我特别说明一下。对于自定义的一个实现了IHttpHandler接口的类，只要同时实现IReadOnlySessionState，即可达到EnableSessionState="ReadOnly"的效果。同时，如果没有实现IRequiresSessionState，则等价于EnableSessionState=”false”的效果。

注意：本文所说的，不是说你在代码里面有没有用到Session，Asp.Net不会扫描你的代码看看有没有访问Session，或者在你第一次访问Session的时候才会加锁。Asp.Net是在AcquireRequestState事件之前就首先申请这个锁——只要你的页面没有设置EnableSessionState=”false”或EnableSessionState=”ReadOnly”，或者你的IHttpHandler实现了IRequiresSessionState却没有实现IReadOnlySessionState接口就会这样。回复中有很多同学说“只要我不用Session不就行了吗？”或者“我从来不用Session”，这么想完全是错误的，只能说你没有理解这背后的机制，甚至可能连Asp.net生命周期都不太清楚。Asp.Net之所以在你的页面代码开始执行之前就锁定，是要保证整个环境的完整性，避免部分执行的情况。当然，也正如上面的一些引用中所提到的，你可以自己写一个SessionProvider而不做任何的锁工作，但这样做肯定有不确定性的风险，到时候只能你自己承担，并且更难复现和调试。

后记：

可能有不少人都知道Session是什么，也有很多人知道Asp.net的生命周期都包含哪些，比如一搜索"PostMapRequestHandler AcquireRequestState"，就会出来很多中文的页面介绍HttpApplication类都有哪些事件，以及生命周期等等。而说到Session会造成特殊情况下站点性能问题的，似乎中文界我这还真是第一篇。当然了，这个问题可能比较偏，因为一般大家都只会处理Aspx页面而不会处理图片，甚至用Aspx页面来动态输出图片的机会都比较少，英文的似乎也只有文中提到的唯一一个同志提出来了。

不过，有一个很常见的场景会受这个问题的影响，那就是“验证码”。如果验证码生成速度很慢，同时客户端浏览器选择长连接而服务器也接受长连接，则可能会影响在输出验证码完毕之前访问下一个页面的速度。反过来，我们也经常可以体验到，验证码出来的速度总是特别慢，总是“蹦”出来的，尤其是当前页面特别复杂的时候，似乎页面没有加载完就总不会出现验证码。估计我说的问题就是原因之一。

不过验证码的问题还不是特别好解决，因为为了避免信息泄露的问题，验证码的答案通常是存在在Session里面的，而通常的设计也是一访问验证码图片，就会将验证码答案写到Session里面。所以，很不幸，文中提到的那个解决办法是行不通的，至少不是能够直接行得通的。这个问题有没有救药？有，当然有了。怎么救？哈，那就有劳你自己开动脑筋了，我这里算是点到即止了。

http://www.mydigitallife.info/2008/02/26/unable-to-disable-integrity-checks-cause-drivers-not-found-in-64-bit-vista-x64/

Many Windows Vista users install non-certified or non-signed drivers on 64bit (x64) edition of Vista, which features Kernel Patch Protection that prevents unauthorized patch or change to the key resources used by the kernel or kernel code itself and its data structures from been modified. The workaround to run unsigned and uncertified drivers in 64-bit Vista is by using the following command:

bcdedit /set loadoptions DDISABLE_INTEGRITY_CHECKS
bcdedit -set loadoptions \”DDISABLE_INTEGRITY_CHECK”
bcdedit -set loadoptions \DDISABLE_INTEGRITY_CHECKS”
bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
Bcdedit.exe /set nointegritychecks ON

However, when user attempts to run the above command to disable integrity checks on the loading drivers, the following error message appears:

An error occurred while attempting to reference the specified entry.
The system cannot find the file specified.

And if you manage to apply setting above previously on load options, but suddenly, there are errors and problems related to rejected or unacceptable drivers or services. Vista simply does not accept any unsigned drivers or processes, causing old drivers or software processes that haven’t been updated cannot be found and installed in Vista x64. The issue is known to affect PeerGuardian, TV tuner cards, Gigabit Ethernet adapters, CD/DVD-ROM/RW drives, and many other devices. Although the devices are listed and shown in Device Manager in System Properties, but they’re not working due to the unsigned driver issue. It also affects and fails any modified system files such as patched tcpip.sys to unlock network speed potential.

In System Event Log, there may be also log message saying something like: “Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.”

The problem occurs because Microsoft has decided to disable DDISABLE_INTEGRITY_CHECKS support in updated x64 Vista, which mean users cannot disable the integrity checks anymore. Microsoft is reportedly rolled out the change various updates including KB932596, KB938979, KB938194 and KB941649 hotfixes, and probably Windows Vista Service Pack 1.

The updates also remove the effectiveness of ignoring code signing for drivers in Group Policy. Previously, users can run “gpedit.msc” and navigate to User Configuration -> Administrative Templates -> System -> Driver Installation, and then enable the “Code signing for drivers” and set the option to “Ignore”. This option also no longer works.

There are a few possible resolution or workaround to re-enable the ability to disable integrity checks and have DDISABLE_INTEGRITY_CHECKS option enabled so that it’s possible to load uncertified drivers or executables, such as suggestions below.

1. Uninstall KB932596, KB938979, KB938194 and KB941649 updates from “Installed Updates” in “Programs and Features”, and never install them again. Best still, hide the updates from viewing and accidental install in Windows Update. After uninstalling and rebooting the computer, add the DDISABLE_INTEGRITY_CHECKS option and restart to disable integrity checks again. This method probably won’t work with the release of SP1, which incorporated all these changes.
2. Press F8 key upon initial system boot up, and then choose to disable forced driver signing enforcement for that boot session. However, users have to apply this option every shutdown and restart. An easy solution to the hassle is put computer into sleep or hibernate mode instead of shutting down everytime.
3. Use ReadyDriver Plus to permanently disable and turn off disable driver signing enforcement automatically on every system startup.
4. Sign the driver with test certificate, which is supplied with Software Development Kit (SDK) for Windows Vista and .NET Framework 3.0 Runtime Components, and then turn of test signing mode in Vista x64 by suing “bcdedit.exe /set TESTSIGNING ON” command. This trick will need computer running consistently in testing mode, which meant for developers to try out drivers signed with self-signed or test certificate. Risk for running computer in test signing mode is unknown, and there will be “Test Mode” watermarks been labeled on four corner of desktop, although the 64-bit watermark can also be removed.

http://www.ngohq.com/home.php?page=dseo

It seems that Microsoft has forgotten end users when it introduced a very restricted module of driver signature enforcement in Windows Vista and Windows 7. All drivers and system files must be digitally verified or they cannot run when using both 32-bit and 64-bit versions of Windows Vista and Windows 7. In the past, it was possible to turn that feature off in Vista, but due to new kernel security updates, it is impossible to turn it off without degrading security and stability of your operating system or putting your master boot records in risk by using other software alternatives.

So what is the problem with digital certificates? Well, the problem is… developers have to pay Microsoft to receive verified certificates, and that makes many applications inaccessible under Windows Vista and Windows 7. However, it is still possible to turn it off by pressing the F8 function key during system boot up, but pressing F8 every time on boot up can be a serious pain in the butt. Others have found workarounds, but most of them are too risky and may trash your master boot records, at least until now thanks to our latest tool.

How does it work?
Microsoft is aware that developers cannot submit every beta build they are testing. Microsoft has provided a mode inside Windows Vista and Windows 7 that will allow developers to test their software before they submit it to Microsoft’s labs. Unfortunately, even in that test mode drivers and system files must have a test certificate before installation.

The good thing is that it does not have to be digitally verified. That means we can load drivers by creating our own unverified certificates. Do not worry! You do not have to do anything; our Driver Signature Enforcement Overrider will do everything for you.

False Positive Alert
It has come to our attention that several Antivirus suites have listed our Driver Signature Enforcement Overrider (DSEO) as a dangerous file. That's nonsense! DSEO is safe. These Antivirus suites are being used as a tool to remove software that Microsoft deems contrary to its outlook, instead of protecting the customer from dangerous files. Read more about it here.

Supported OSes
* Windows Vista 32-bit
* Windows Vista 64-bit
* Windows Server 2008 32-bit
* Windows Server 2008 64-bit
* Windows 7 32-bit
* Windows 7 64-bit

Changes
* Watermarks Removal Option
* Support for Windows 7
* Several Bug-fixes

So how do I use it?
First and foremost; you are using this software at your own risk, we do not take responsibility for any damages to your system, but we do not believe it can harm anyone anyway. Secondly, User Account Control (UAC) must be disabled in-order to use this tool as well.

1. Go ahead download and launch the application from the link below. Inside its main menu, press on the “Enable Test Mode” button and follow the instructions on the screen. This will enable TESTSIGNING mode, which allows unverified system files to be loaded.

2. Now all you have to do is to add the unverified signature to the required system files. To do so press on the “Sign a System File” button from the main menu, and enter specific filename including full path. For example: if ATITool64.sys from C:\Windows\System32\drivers refuses to load due to driver signature enforcement, you should type: “C:\Windows\System32\drivers\ATITool64.sys”, and if you would like to sign more than a single file, just repeat this procedure until you’re done, and finally reboot.

After you enabled Test Mode and added signatures to the required system files, they should bypass Windows’s driver signature enforcement and load without any issues. However, if for some reason you are interested to revert it, you can re-launch the application, choose “Disable Test Mode” from the main menu, and reboot. If you encounter issues or having questions, feel free to post it on our forums.

Note: User Account Control (UAC) must be disabled in-order to use this tool.
Download

Outlook Express 6 (OE6) for Win7

    加号(+)是BASE64编码的一部分，而加号在QueryString中被当成是空格。
    因此，当一个含有BASE64编码的字符串直接作为URL的一部分时，如果其中含有加号，则使用QueryString读取时，再使用BASE64解码就会发生错误。

    解决的办法有两个：
一是使用BASE64的字符串作为URL的一部分是，使用UrlEncode一类的函数进行编码；
二是在接收BASE64字符串后，使用Replace将字符串中的空格替换成加号，然后再解码。

http://blog.zhuzhaoyuan.com/2009/03/a-word-on-time_wait-and-close_wait/

I’m surprised by the fact that so many network programmers don’t know TIME_WAIT and CLOSE_WAIT well, particularly those who use Java, C#, Python and etc.

It is true, however, TIME_WAIT and CLOSE_WAIT are the most confusing two among TCP’s 11 states (CLOSED, LISTEN, SYN_SENT, SYN_RECV, ESTABLISHED, CLOSE_WAIT, LAST_ACK, FIN_WAIT1, FIN_WAIT2, CLOSING, and TIME_WAIT), which are displayed by netstat(1).

Before going into detail, let me explain the terms first:
Active Open: An end sends a SYN segment to the other end by calling connect(2). This end is usually called a client.
Passive Open: An end issues a passive open by calling socket(2), bind(2), and listen(2) so that it can accept(2) the clients’ connections. This end is usually called a server.
Active Close: An end performs active close when it calls close(2) first. It results a FIN segment being sent.
Passive Close: The other end receives the FIN segment performs the passive close.
MSL: Maximum Segment Lifetime, the maximum time a segment can live in the network before being discarded.

Now take a look at the TCP state transition diagram.

TCP State Transition Diagram 1

TCP State Transition Diagram 2

In the diagrams above, I denote the active open/close transitions with a green line and the passive open/close transitions with a blue line (Normal transitions are in bold). The end that performs the active close goes through the TIME_WAIT state; while the end performs the passive close enters the CLOSE_WAIT state. Note that either end (the server or the client) can perform the active close!

What’s the TIME_WAIT state for?
1) When the final ACK being sent by the end that performed the active close was lost, the other end would resend a FIN. TCP maintains the information of the connection, hence it would resend the lost ACK rather than respond with an RST (interpreted as error).
2) To allow wandering duplicates to expire in the network, so that the duplicate segments would not corrupt later connections.

The value of TIME_WAIT delay is 2MSL, which is TCP implementation dependent and is generally about 1-4 minutes.

CLOSE_WAIT happens when an end has received a FIN segment from the other end, to wait for the program to close the socket. Long duration of CLOSE_WAIT suggests that there might be a bug in your program. In fact, a TCP connection can stay in the CLOSE_WAIT state forever unless it is explicitly closed. It is the application’s responsibility to close its socket after use, to release the resource of the connection.

Conclusion:
In most cases, there is no need to worry about TIME_WAIT. It is a safety feature of TCP. But you really should take care of CLOSE_WAIT. Also note, if a connection is in CLOSE_WAIT, it would never end up in the TIME_WAIT state, and vice versa. BTW, if you haven’t read Richard Stevens’ Unix Network Programming, go out and buy one. It is a must-have for all network programmers, even if you do Windows programming.

Download the dot files and msc file here:
http://www.zhuzhaoyuan.com/download/tcp/tcp-state1.dot
http://www.zhuzhaoyuan.com/download/tcp/tcp-state2.dot
http://www.zhuzhaoyuan.com/download/tcp/tcp_close.msc

 

http://www.cnbeta.com/articles/101755.htm

美国MIT Media Lab（麻省理工学院媒体实验室）的天才学生普拉纳夫- (Prarnav Mistry)，发明了一项结合实体世界和虚拟世界的科技，令人又惊又喜；喜的是，对于未來生活，悠游於实体和虚拟之间，将更自由无限，惊的是，对于现今的人们和企业而言，这场演讲是一提醒 ：「讯息上身，才有未来」。

以下是一段视频，长达13分52秒。但是，我相信你一定不会错过任何一秒。哪怕是它有关于科技，演讲人有浓重的印度口音，但是它如此贴近我们的生活，如此关怀人性，努力把人从“机器前的机器”里解放出来，以至于你会目不转睛地看完这段实况，而且遐想翩翩，愿意努力活到22世纪。

如果说，Windows系统的图形化界面把人们从Dos系统下解放出来，用更符合直觉和人性的方法让人们对电脑进行操作是一次新技术的跨越的话，那么视频里这套Prarnav Mistry提供的第六感（Sixth Sense)装置，则是另外一次意义更为深远的腾跃。和它相比，目前甚嚣尘上的所谓“物流网”，只是这个新技术的小小注脚，无论在深度还是广度上，都无法与之比拟。 网络和电脑技术，终于使得数字世界和现实世界全面融合，人类升级为真正意义上的数位人！新时代就要开始了！

GB11643-1999 公民身份号码中规定，最后一位校验码是根据前面十七位数字码，按照ISO 7064:1983.MOD 11-2校验码计算出来的检验码。
公式如下：
　　∑(a*W) mod 11 ( i = 2, 3, ..., 18 ) (1)
　　"*" 表示乘号
　　i--------表示身份证号码每一位的序号，从右至左，最左侧为18，最右侧为1。
　　a-----表示身份证号码第 i 位上的号码
　　W-----表示第 i 位上的权值 W = 2^(i-1) mod 11
　　计算公式 (1) 令结果为 R
根据下表找出 R 对应的校验码即为要求身份证号码的校验码C。
　　R 0 1 2 3 4 5 6 7 8 9 10
　　C 1 0 X 9 8 7 6 5 4 3 2
由此看出 X 就是 10，罗马数字中的 10 就是X，所以在新标准的身份证号码中可能含有非数字的字母X。

http://www.systemsabuse.com/2007/10/18/how-do-you-install-windows-messenger-51-on-vista-with-uac-enabled/ 

Vista - Messenger 5.1 SIP - workaround:

http://www.iamkane.com/article.asp?id=2

序列号：
MRX3F-47B9T-2487J-KWKMF-RPWBY（chs可用 ）

CM3HY-26VYW-6JRYC-X66GX-JVY2D

DP7CM-PD6MC-6BKXT-M8JJ6-RPXGJ

F4297-RCWJP-P482C-YY23Y-XH8W3

HH7VV-6P3G9-82TWK-QKJJ3-MXR96

HCQ9D-TVCWX-X9QRG-J4B2Y-GR2TT

QC986-27D34-6M3TY-JJXP9-TBGMD

MRX3F-47B9T-2487J-KWKMF-RPWBY

M6TF9-8XQ2M-YQK9F-7TBB2-XGG88

换Key的vbs

ON ERROR RESUME NEXT
Dim VOL_PROD_KEY
if Wscript.arguments.count<1 then
VOL_PROD_KEY=InputBox("使用说明(OEM版无效)："&vbCr&vbCr&" 本脚本程序将修改当前 Windows 的序列号。请先使用算号器算出匹配当前 Windows 的序列号，复制并粘贴到下面空格中。"&vbCr&vbCr&"输入序列号(默认为 XP VLK)：","Windows XP/2003 序列号更换工具","请在此处输入正确的Microsoft Windows XP/2003 产品密钥")
if VOL_PROD_KEY="" then
Wscript.quit
end if
else
VOL_PROD_KEY = Wscript.arguments.Item(0)
end if
VOL_PROD_KEY = Replace(VOL_PROD_KEY,"-","") ''remove hyphens if any
for each Obj in GetObject("winmgmts:{impersonationLevel=impersonate}").InstancesOf ("win32_WindowsProductActivation")
result = Obj.SetProductKey (VOL_PROD_KEY)
if err = 0 then
Wscript.echo "您的 Windows CD-KEY 修改成功。请检查系统属性。"
end if
if err <> 0 then
Wscript.echo "修改失败！请检查输入的 CD-KEY 是否与当前 Windows 版本相匹配。"
Err.Clear
end if
Next

http://www.sosdb.com/jdul/dispbbs.asp?boardID=2&ID=248

我们知道,在Oracle数据库中,可以通过kill session的方式来终止一个进程,其基本语法结构为: 

alter system kill session 'sid,serial#' ; 
 

被kill掉的session,状态会被标记为killed,Oracle会在该用户下一次touch时清除该进程. 

我们发现当一个session被kill掉以后，该session的paddr被修改，如果有多个session被kill，那么多个session
的paddr都被更改为相同的进程地址:

SQL> select saddr,sid,serial#,paddr,username,status from v$session where username is not null;

 

 SADDR           SID    SERIAL# PADDR    USERNAME                       STATUS

 -------- ---------- ---------- -------- ------------------------------ --------

 542E0E6C         11        314 542B70E8 EYGLE                          INACTIVE

 542E5044         18        662 542B6D38 SYS                            ACTIVE

 

 

 SQL> alter system kill session '11,314';

 

 System altered.

 

 SQL> select saddr,sid,serial#,paddr,username,status from v$session where username is not null;

 

 SADDR           SID    SERIAL# PADDR    USERNAME                       STATUS

 -------- ---------- ---------- -------- ------------------------------ --------

 542E0E6C         11        314 542D6BD4 EYGLE                          KILLED

 542E5044         18        662 542B6D38 SYS                            ACTIVE

 

 

 SQL> select saddr,sid,serial#,paddr,username,status from v$session where username is not null;

 

 SADDR           SID    SERIAL# PADDR    USERNAME                       STATUS

 -------- ---------- ---------- -------- ------------------------------ --------

 542E0E6C         11        314 542D6BD4 EYGLE                          KILLED

 542E2AA4         14        397 542B7498 EQSP                           INACTIVE

 542E5044         18        662 542B6D38 SYS                            ACTIVE

 

 SQL> alter system kill session '14,397';

 

 System altered.

 

 SQL> select saddr,sid,serial#,paddr,username,status from v$session where username is not null;

 

 SADDR           SID    SERIAL# PADDR    USERNAME                       STATUS

 -------- ---------- ---------- -------- ------------------------------ --------

 542E0E6C         11        314 542D6BD4 EYGLE                          KILLED

 542E2AA4         14        397 542D6BD4 EQSP                           KILLED

 542E5044         18        662 542B6D38 SYS                            ACTIVE

 

 

 

在这种情况下,很多时候，资源是无法释放的,我们需要查询spid，在操作系统级来kill这些进程. 

但是由于此时v$session.paddr已经改变，我们无法通过v$session和v$process关联来获得spid 

那还可以怎么办呢? 

  SQL> SELECT s.username,s.status,

   2  x.ADDR,x.KSLLAPSC,x.KSLLAPSN,x.KSLLASPO,x.KSLLID1R,x.KSLLRTYP,

   3  decode(bitand (x.ksuprflg,2),0,null,1)

   4  FROM x$ksupr x,v$session s

   5  WHERE s.paddr(+)=x.addr

   6  and bitand(ksspaflg,1)!=0;

 

 

 USERNAME                       STATUS   ADDR       KSLLAPSC   KSLLAPSN KSLLASPO       KSLLID1R KS D

 ------------------------------ -------- -------- ---------- ---------- ------------ ---------- -- -

                                         542B44A8          0          0                       0

                                ACTIVE   542B4858          1         14 24069                 0    1

                                ACTIVE   542B4C08         26         16 15901                 0    1

                                ACTIVE   542B4FB8          7         46 24083                 0    1

                                ACTIVE   542B5368         12         15 24081                 0    1

                                ACTIVE   542B5718         15         46 24083                 0    1

                                ACTIVE   542B5AC8         79          4 15923                 0    1

                                ACTIVE   542B5E78         50         16 24085                 0    1

                                ACTIVE   542B6228        754         15 24081                 0    1

                                ACTIVE   542B65D8          1         14 24069                 0    1

                                ACTIVE   542B6988          2         30 14571                 0    1

 

 USERNAME                       STATUS   ADDR       KSLLAPSC   KSLLAPSN KSLLASPO       KSLLID1R KS D

 ------------------------------ -------- -------- ---------- ---------- ------------ ---------- -- -

 SYS                            ACTIVE   542B6D38          2          8 24071                 0

                                         542B70E8          1         15 24081               195 EV

                                         542B7498          1         15 24081               195 EV

 SYS                            INACTIVE 542B7848          0          0                       0

 SYS                            INACTIVE 542B7BF8          1         15 24081               195 EV

 

 16 rows selected.

           

我们注意,红字标出的部分就是被Kill掉的进程的进程地址. 

SQL> select p.addr from v$process p where pid <> 1
  2  minus
  3  select s.paddr from v$session s;

Ok，现在我们获得了进程地址，就可以在v$process中找到spid，然后可以使用Kill或者orakill在系统级来杀掉这些进程.

实际上,我猜测:

当在Oracle中kill session以后, Oracle只是简单的把相关session的paddr 指向同一个虚拟地址.

此时v$process和v$session失去关联,进程就此中断.

然后Oracle就等待PMON去清除这些Session.所以通常等待一个被标记为Killed的Session退出需要花费很长的时间.

如果此时被Kill的process，重新尝试执行任务，那么马上会收到进程中断的提示，process退出，此时Oracle会立即启动PMON
来清除该session.这被作为一次异常中断处理.

http://sunya.org.cn/article.asp?id=1259

今天，试了下用foxmail收取gmail 跟msn邮件
能成功收下！

在6.5 beta 3版本已经全面支持hotmail了，只是目前没有随安装包一起发放出来

自己琢磨了一下，就缺一个文件msidcrl40.dll，找了半天都是4.0的都不能用

后来直接在live mail里面挖出来一个5.0的

将其放到Foxmail安装路径3rdParty目录下

然后在到注册表HKEY_CURRENT_USER\Software\Aerofox\Foxmail\General下，新建“字符串值”SupportHotmail，值为1。

重新启动foxmail就可以了，新增hotmail帐号时候就会有个http服务器

还会有个路径
http://mail.services.live.com/DeltaSync_v2.0.0/Sync.aspx

填上用户名、密码就可以使用了。

PS:由于是HTTP登录，那么在客户端上Foxmail删除邮件，会同步删除hotmail上的邮件。所以要特别注意下，以免重要邮件被删除。

PS2:附上msidcrl40.dll版本是5的，从live mail客户端里扒出的，还有注册表信息，直接导入就可以了
点击下载

http://msdn.microsoft.com/en-us/library/dd638062.aspx

You can upgrade any installed SQL Server 2008 component with a SQL Server 2008 servicing update. If the version level of an existing SQL Server 2008 component is later than the update version level, the Setup program will exclude it from the update.

The following considerations apply when you install SQL Server 2008 updates:

• All features that belong to an instance of SQL Server must be updated at the same time. For example, when you update the Database Engine, you must also update Analysis Services and Reporting Services components if they are installed as part of the same instance of SQL Server. Shared features, such as Management Tools, Business Intelligence Development Studio, and SQL Server Integration Services, must always be updated to the most recent update. If a component or instance in the feature tree is not selected, the component or instance will not be updated.
  
• By default, SQL Server 2008 update log files are saved to %Program Files%\Microsoft SQL Server\100\Setup Bootstrap\LOG\.
  
• Starting with Service Pack 1 (SP1), you can now slipstream an update with the original media to run the original media and the update at the same time. For more information, see Slipstream a SQL Server Update.
  
• Before you apply a SQL Server 2008 servicing update, we recommend that you consider backing up your data.
  
• SQL Server updates are available through Microsoft Update. We recommend that you scan for updates regularly to keep your instance of SQL Server updated and secure.
  

For more information, see How to apply a SQL Server 2008 update to a failover cluster instance in the Microsoft Knowledge Base.

 Disk Space Requirements

The recommended disk space requirements are approximately 2.5 times the size of the package to install, download, and extract the package.

The size of SP1 packages are listed here:

• X86: 270 MB
  
• X64: 331 MB
  
• Ia64: 320 MB
  

After installing SP1, you can remove the downloaded package. Any temporary files are removed automatically.

 Installation Overview

This section discusses the SQL Server 2008 update installation, including how to do the following:

• Prepare for a SQL Server 2008 update installation
  
• Install SQL Server 2008 updates
  
• Restart services and applications
  

Prepare for a SQL Server 2008 Update Installation

You must do the following before you install SQL Server 2008 updates:

• Back up your SQL Server 2008 system databases — Before you install SQL Server 2008 updates, back up the master, msdb, and model databases. Installing a SQL Server 2008 update changes these databases, making them incompatible with earlier versions of SQL Server 2008. Backups of these databases are required if you decide to reinstall SQL Server 2008 without these updates.
  It is also prudent to back up your user databases.
  

Important:
When you apply updates to instances of SQL Server that participate in a replication topology, you must back up your replicated databases together with your system databases before you apply the update.

• Back up your Analysis Services databases, configuration file, and repository — Before you update an instance of Analysis Services, you should back up the following:
  
  • Analysis Services databases. By default, these are installed to C:\Program Files\Microsoft SQL Server\MSAS10\<InstanceID>\OLAP\Data\.
    
  • Analysis Services configuration setting in the msmdsrv.ini configuration file. By default, this is located in the C:\Program Files\Microsoft SQL Server\MSAS10\<InstanceID>\OLAP\Config\ directory.
    
  • (Optional) The database that contains the Analysis Services repository. This step is required only if Analysis Services was configured to work with the Decision Support Objects (DSO) library.
    

Note:
Failure to back up your Analysis Services databases, configuration file, and repository will prevent you from reverting an updated instance of Analysis Services to the earlier version.

• Verify that the system databases have sufficient free space — If the autogrow option is not selected for the master and msdb system databases, these databases each must have at least 500 KB of free space. To verify that the databases have sufficient space, run the sp_spaceused system stored procedure on the master and msdb databases. If the unallocated space in either database is less than 500 KB, increase the size of the database. For more information, see "Expanding a Database" in SQL Server Books Online.
  
• Stop Services and Applications — To avoid a possible restart of the system, stop all applications and services that make connections to the instances of SQL Server that are being upgraded, before installing SQL Server 2008 updates. These include SQL Server Management Studio, Business Intelligence Development Studio, Control Panel, and Add or Remove Programs.
  

Note:
You cannot stop services in a failover cluster environment. For more information, see the failover cluster installation section later in this topic.

• To eliminate the requirement to restart your computer after update installation, Setup will show a list of processes that are locking files. If the update Setup program must end a service during installation, it will restart the service after the installation finishes.
  
• If Setup determines that files are locked during installation, you might have to restart your computer after the installation finishes. If it is required, Setup prompts you to restart your computer.
  

 

Install SQL Server 2008 Updates

This section describes the installation process.

Important:
SQL Server 2008 updates must be installed under an account that has administrative privileges on the computer where they will be installed.

Starting a SQL Server 2008 Update

To install a SQL Server 2008 update, run the self-extracting package file SQLServer2008-KBxxxxxx-PPP.exe, where PPP indicates the specific platform.

Note:
To apply updates to SQL Server 2008 components that are part of a failover cluster, see the section for failover cluster installation. For more information about how to run an update installation in unattended mode, see How to: Install SQL Server 2008 (Setup).

Slipstream a SQL Server Update

Overview:

Slipstreaming is integrating a SQL Server 2008 update and the original installation media so that the original media and the update are installed at the same time. When you run the original release version of SQL Server 2008 Setup, the Setup program copies itself on the local computer, and then re-runs from the local copy. Therefore, if there is a later version of Setup on the computer, the Setup program runs the updated Setup.

Slipstreaming is supported in the following scenarios:

• Original media and service pack
  
• Original media, service pack, and cumulative update
  

  Note:
  Slipstreaming an update with the original media but without the service pack is not supported.

  Important:
  For SQL Server Express, you must download the version with the service pack and slipstream cumulative updates as needed.

There are several ways that you can slipstream an update:

Option 1: Install the latest update with the original release version of SQL Server 2008 Setup directly:

We recommend that you use this option if you are running the upgrade on a few computers.

1. Install the following prerequisites that are required for SQL Server 2008.
   
   • Microsoft Windows Installer 4.5
     
   • Microsoft .NET Framework 3.5 Service Pack 1
     

     Note:
     On the IA-64 platform, the .NET Framework 3.5 is not supported, and the .NET Framework 2.0 SP2 is required. You must install the .NET Framework 2.0 SP2 from the source media because it is not available from the Microsoft Download Center. The .NET Framework 2.0 SP2 is located in the following folder on the source media: Drive_Letter:\ia64\redist\2.0\NetFx20SP2_ia64.exe

2. Download the service package and cumulative update that you want to slipstream. Select the language or architecture package that matches your environment. Service packages must match both language and architecture; cumulative updates are language-neutral.
   
3. Double-click the service pack to install the SQL Server 2008 Setup support files. To confirm that the updated setup is installed, search for the "SQL Server 2008 Setup Support Files" entry by using the Add or Remove Programs item in Control Panel in operating systems that are earlier than Windows Vista. In Windows Vista or later versions of Windows, view the entry by using the Programs and Features item in Control Panel.
   
4. For each package, extract the contents of the package by running the following script at the command prompt:
   <name of the PCU or CU package>.exe /x:<Root of path to extract to>\<PCU | CU>
   

   Note:

   The name of the package is in the form: PCU: SQLServer2008SP1-<KB Article>-<Architecture>-<Language>.exe CU: SQLServer2008SP1-<KB Article>-<Architecture>.exe The architecture placeholder represents the different hardware platforms. For example, it can represent one of the following folders: x86 x64 IA64 For example, run the following commands to extract the contents of the PCU package: SQLServer2008- KB123456-IA64.exe /x:c:\MyUpdate\PCU SQLServer2008- KB123456-x64.exe /x:c:\MyUpdate\PCU SQLServer2008- KB123456-x86.exe /x:c:\MyUpdate\PCU If you want to include a CU based on the PCU, extract out the CU packages to c:\MyUpdate\CU

5. Start the SQL Server 2008 Setup program and specify the path for the service pack and cumulative update files by using the /PCUSource and /CUSource parameters. For example, here is a path based on the extracted location indicated in step 4:
   
   Copy Code

   Setup.exe /PCUSource = c:\MyUpdate\PCU /CUSource= c:\MyUpdate\CU

   Note:
   For SQL Server Express SP1 or later, only the /CUSource parameter is supported. If you are slipstreaming SQL Server in WOW64, you need to do one of the following:

   • To skip the installation center, specify the /Action parameter and the /x86 parameter on the command line.
     
   • Or, on the Options page of the Installation Center, select x86.
     

Option 2: Slipstream Express Core Service Pack with cumulative update:

We recommend that you use this option if you are running the upgrade on a few computers.

1. Install the following prerequisites that are required for SQL Server 2008.
   
   • Microsoft Windows Installer 4.5
     
   • Microsoft .NET Framework 3.5 Service Pack 1
     

   Note:
   SQL Server Express only requires .NET 2.0 SP2, but this version is not publicly available so you need to install .NET 3.5 SP1 instead.

2. Download the SQL Server Express core package and cumulative update that you want to slipstream. Select the language or architecture of SQL Server Express that matches your environment. The cumulative updates are language-neutral.
   
3. Extract the contents of the cumulative update package by running the following script at the command prompt:
   <CU package>.exe /x:<Root of path to extract to>\<CU>
   

   Note:

   The name of the package is in the form: CU: SQLServer2008-<KB Article>-<Architecture>.exe The architecture placeholder represents the different hardware platforms. For example, it can represent one of the following folders: x86 x64 IA64 For example, run the following commands to extract the contents of the cumulative update package: SQLServer2008-KB123456-IA64.exe /x:c:\MyUpdate\CU SQLServer2008-KB123456-x64.exe /x:c:\MyUpdate\CU SQLServer2008-KB123456-x86.exe /x:c:\MyUpdate\CU

4. Start the SQL Server 2008 Setup program and specify the path for the service pack and cumulative update files by using the /CUSource parameters.
   

   Note:
   For SQL Server Express SP1 or later, only the /CUSource parameter is supported.

• Microsoft Windows Installer 4.5
  
• Microsoft .NET Framework 3.5 Service Pack 1
  

Option 3: Update the original media files:

We recommend that you use this option for running a patched setup on many computers or large deployments, or for when an administrator wants to make this patched setup available to users. We also recommend that you test fully before you make this option available to other users. This option is supported in the following scenarios:

• Original media and service pack
  
• Original media, service pack, and cumulative update
  

1. Download the service pack and the optional cumulative update based on the service pack that you want to use to update the original media files. You must download the service pack and updates for all platforms (x86, x64, and IA-64) because the original media contains the files for each platform. For example, you must either download three packages for merging the original media and just the service pack or six packages for merging the original media, service pack, and cumulative update.
   
2. For each package, extract the contents of the package by running the following script at the command prompt:
   <name of the PCU or CU package>.exe /x:<Root of path to extract to>\<PCU | CU>
   

   Note:

   The name of the package is in the form: PCU: SQLServer2008SP1-<KB Article>-<Architecture>-<Language>.exe CU: SQLServer2008SP1-<KB Article>-<Architecture>.exe The architecture placeholder represents the different hardware platforms. For example, it can represent one of the following folders: x86 x64 IA64 For example, run the following commands to extract the contents of the PCU package: SQLServer2008- KB123456-IA64.exe /x:c:\MyUpdate\PCU SQLServer2008- KB123456-x64.exe /x:c:\MyUpdate\PCU SQLServer2008- KB123456-x86.exe /x:c:\MyUpdate\PCU The previous command merges the three architectures into a single folder. If you want to include a CU based on the PCU, extract the cumulative update packages out to c:\MyUpdate\CU

3. Copy the contents of the SQL Server 2008 DVD to a local folder, for example SQLServer2008RTM.
   
4. To update the files in the original installation media, copy the SQLSupport.msi file from the C:\MyUpdate\PCU\<Architecture>\setup\<Language LCID>\sqlsupport.msi to C:\SQLServer2008RTM\<Architecture>\Setup\sqlsupport.msi. Ensure that you copy Sqlsupport.msi for each architecture.
   

   Note:
   If you are using slipstreaming to integrate a cumulative update package also, use the files in the extracted cumulative update folder instead

5. Copy the Setup.exe and Setup.rll files from the C:\MyUpdate\PCU\ folder to the root folder that contains the source media from the DVD.
   

   Note:
   If you are using slipstream to integrate a cumulative update package also, use the files in the extracted cumulative update folder instead.

6. To update the files in the original installation media, copy all files without the folders, except the Microsoft.SQL.Chainer.PackageData.dll, in c:\MyUpdate\PCU\<architecture> to C:\SQLServer2008RTM\<architecture>
   

   Note:
   If you are using slipstream to integrate a cumulative update package also, use the files in the extracted cumulative update folder instead

7. Start the Setup.exe program that is located at C:\SQLServer2008RTM and specify the values for /PCUSource and /CUSource parameters. For example, C:\SQLServer2008RTM\Setup.exe /PCUSource=c:\MyUpdate\PCU /CUSource= c:\MyUpdate\CU.
   

   Note:
   If you place the folder on a share for user installs, set the /PCUSource and /CUSource parameters to a UNC path.

Applying a SQL Server 2008 Update to a Failover Cluster Instance

For more information about how to install updates to a SQL Server 2008 failover cluster, see How to apply a SQL Server 2008 update to a failover cluster instance in the Microsoft Knowledge Base.

Rebuilding a SQL Server 2008 Failover Cluster Node

If you must rebuild a node in the failover cluster after updates were applied, follow these steps:

1. Rebuild the node in the failover cluster. For more information about rebuilding a node, see "How to: Recover from Failover Cluster Failure in Scenario 1" in SQL Server Books Online.
   
2. Run the original SQL Server 2008 Setup program to install SQL Server 2008 on the failover cluster node.
   
3. Run SQL Server 2008 updates Setup on the node that you have added.
   

Restart Services and Applications

When the Setup program is finished, it might prompt you to restart the computer. After the system restarts, or after the Setup program finishes without requesting a restart, use the Services node in Control Panel to restart the services that you stopped before you applied the SQL Server 2008 updates. This includes services such as Distributed Transaction Coordinator and the Microsoft Search services, or instance-specific equivalents.

Restart the applications that you closed before you ran SQL Server 2008 update Setup. You might also want to make another backup of the upgraded master, msdb, and model databases immediately after successful installation.

Uninstalling updates to SQL Server 2008

You can uninstall SQL Server 2008 cumulative updates or service packs from Programs and Features in Control Panel. Each cumulative update is listed separately. However, when a service pack is installed that is higher than the cumulative updates, the cumulative update entries are hidden and become available only if you uninstall the service pack.

To uninstall any service packs and updates, you must start with the latest update or service pack applied to the instance of SQL Server and work backward. In each of the following examples, SQL Server ends up with Cumulative Update 1 after uninstall has been completed for the other service packs or updates:

• For an instance of SQL Server 2008 with Cumulative Update 1 and SP1 installed, uninstall SP1.
  
• For an instance of SQL Server 2008 with Cumulative Update 1, SP1, and Cumulative Update 2 installed, uninstall Cumulative Update 2 first and then uninstall SP1.
  

 See Also

Concepts

Installing Updates from the Command Prompt

Help and Information

Getting SQL Server 2008 Assistance