February 2021 (version 1.54)

软件开发 专栏收录该内容
122 篇文章 0 订阅

Update 1.54.1: The update addresses an issue with an extension dependency.

Downloads: Windows: User System ARM | Mac: Universal 64 bit Arm64 | Linux: snap deb rpm tarball ARM


Welcome to the February 2021 release of Visual Studio Code. There are a number of updates in this version that we hope you will like, some of the key highlights include:

If you'd like to read these release notes online, go to Updates on code.visualstudio.com.

Join us live at the VS Code team's livestream on Thursday, March 11 at 8am Pacific (4pm London) to see a demo of what's new in this release, and ask us questions live.

Insiders: Want to try new features as soon as possible? You can download the nightly Insiders build and try the latest updates as soon as they are available.

Apple Silicon#

We are happy to announce our first release of stable Apple Silicon builds this iteration. Users on Macs with M1 chips can now use VS Code without emulation with Rosetta, and will notice better performance and longer battery life when running VS Code. Thanks to the community for self-hosting with the Insiders build and reporting issues early in the iteration.

The default download of VS Code for macOS is now a Universal build that runs natively on all Macs. On the Downloads page, you can find more links to architecture-specific builds for Intel or Apple Silicon, which are smaller downloads compared to the Universal package.

Website showing the new downloads view for Apple Silicon builds

Website showing the default download for macOS

Accessibility#

Toolbars and tabs occupy one tab stop#

All toolbars in the workbench now follow the standard navigation behavior, so the toolbar occupies only a single position in the tab order, and is navigable with the arrow keys. Once the focus is on the toolbar, arrow keys should be used to move focus to a specific item in the toolbar. As a result of this change, the workbench has far fewer tab stops, making it easier to navigate across all the parts.

For consistency, the same change was applied to the tabs area. Thus the whole tab area is only one tab stop, and keyboard navigation between tabs should be done with the left and right arrow keys.

Word navigation on Windows#

We have improved how word navigation is done on Windows to align with what Screen Readers on Windows expect from an Electron-based application. Now, when using word navigation, each word will be properly read out by the Screen Reader.

Due to this change, we are deprecating the following commands. They will still work, but we might remove them in the future.

  • cursorWordAccessibilityLeft
  • cursorWordAccessibilityLeftSelect
  • cursorWordAccessibilityRight
  • cursorWordAccessibilityRightSelect

Non-Windows platforms already worked as expected, so we made no changes there.

Improved roles for views and buttons#

Based on user feedback, we have improved the roles of multiple views and buttons across the workbench. Activity BarSide Bar, and Panel now have role:none, which will make the screen reader less chatty. Manage and Accounts buttons inside the Activity Bar now properly announce they have a popup.

Integrated Terminal#

Retain terminal processes on window reload#

Local terminal processes are now restored on window reload, such as when an extension install requires a reload. The terminal will be reconnected and the UI state of the terminals will be restored, including the active tab and split terminal relative dimensions.

 

This feature can be disabled by setting terminal.integrated.enablePersistentSessions to false.

Windows performance improvements#

Thanks to the new terminal process layout, frequent pty data events from terminal processes should now process more quickly. This is expected to affect Windows more than other platforms due to the smaller events provided by conpty on Windows.

Automatically relaunch terminal requiring environment changes#

Recently a new feature was rolled out that enabled extensions to influence the terminal's environment. This is used by various language extensions and the built-in git extension to enable VS Code as a git auth provided to negate the need to sign in. Previously the UX for this was to present a subtle ⚠️ icon in the top-right corner to indicate that a terminal's environment was stale. The indicator was subtle, since environment changes may or not be important.

We've tweaked this to automatically relaunch terminals that have stale environments when they have not yet been interacted with. This may result in some flickering, but extension terminal integration is much more seamless now. For example, the first terminal in a Remote - WSL window should no longer show a Git auth error, provided the relaunch happened before typing in the terminal.

Workbench#

Emmet#

The Wrap with Abbreviation and Wrap Individual Lines with Abbreviation commands have been merged into a single Wrap with Abbreviation command to reduce any confusion over which wrap command to use. Additionally, the Wrap with Abbreviation command now shows the preview whitespace properly.

The emmet.extensionsPath setting can now also take in an array of paths, rather than just a string. Therefore, when combined with Settings Sync, one can point to different snippet files depending on the machine they are on, without having to update the setting per machine.

Product Icon Themes#

The first Product Icon Themes have become available in the Extension Marketplace. Thanks to the theme authors for the great work!

To select or find a theme, use the Preference: Product Icon Theme command from the command prompt or the Settings gear.

Product icon themes in the Extension Marketplace

IntelliSense for context keys#

VS Code uses when-clauses to enable and disable keybindings. Extensions also use when-clauses to control menu- and view-contributions. Authoring these when-clauses is now much simpler because the editor offers completions for them.

Theme: GitHub Light Theme, Font: FiraCode

Open Editors New Untitled File action#

There is now a New Untitled File action in the Open Editors view title area.

New untitled file in Open Editors view

Updated application menu settings#

The window.menuBarVisibility setting for the application menu visibility has been updated to better reflect the options. Two primary changes have been made.

First, the default option for the setting has been renamed to classic.

Second, the Show Menu Bar entry in the application menu bar now toggles between the classic and compact options. To hide it completely, you can update the setting, or use the context menu of the Activity Bar when in compact mode.

Show Menu Bar entry in application menuTheme: GitHub Light Theme

Webview caching improvements#

We've improved caching for a local file inside a webview. If a webview reloads a file from disk, then we now use ETags to avoid reading the file again if it has not changed. This can eliminate data transfer, and improves response time, especially for remote workspaces.

This caching currently only applies when an existing webview reloads a resource. It does not apply to newly created webviews, even if that webview belongs to an extension that previously created a similar webview.

Modifier only keybindings#

It is now possible to define keybindings for duplicate modifiers, for example, shift shiftalt altctrl ctrl or cmd cmd / meta meta / win win. These keybindings can be entered manually in keybindings.json, for example:

{ "key": "shift shift", "command": "workbench.action.quickOpen" }

Updated list/tree UI#

We have updated the list/tree styles to match native focus and selection indicators: focused elements will now be rendered with an outline color.

List/tree UI showing focused element

Breaking change

Theme publishers are advised to adopt this style as well simply by swapping the customization of the list.focusBackground color for the quickInput.list.focusBackground color. To see an example, check out this commit.

Table widget#

We introduced a new table widget, built on top of the existing list widget, so we can render tabular data with the same performance as we can render list elements. For now, it is used in the Ports view for our Remote features.

Table widget view of remote Ports

Getting Started#

We are experimenting with a new editor to show on startup, called the Getting Started editor. This is intended to make some of VS Code's features more approachable to new users. Some Insiders users may have already seen it, and it will be slowly rolled out to more Stable users over the course of this iteration. You can always opt in or out of the new behavior by modifying the workbench.startupEditor setting to or away from gettingStarted.

Getting Started experience walkthrough

Timeline view#

You can now compare changes across Git history timeline entries, using the Select for Compare and Compare with Selected commands—similar to comparing files in the Explorer view. This feature lets you quickly see all the changes between any two commits in your Git file history.

Select for Compare command in context menu

Default sash hover border color#

In the 1.52 release, we introduced the hover border color token for sashes (sash.hoverBorder), but did not set a default. We now show this color by default on all themes.

 

Debugging#

Breakpoints view improvements#

New inline action for removing breakpoints

We have added an inline action X to remove breakpoints in the Breakpoints view. This action should make it easier to remove breakpoints.

Breakpoints view showing X next to selected breakpoint

Help text support for exception filters

Recently we have added support for editing conditions on exception filters in the Breakpoints view.

In order to make these conditions more discoverable and their syntax self-explanatory, VS Code now shows a hover on the exception filter and a placeholder text in the condition text box.

Since the information for both is provided by the underlying debug extension, it can be much more specific (and thus helpful) than some generic message.

Since this new feature is based on additions to the Debug Adapter Protocol (see below), it requires an opt-in of debug extensions. In this release, only VS Code's built-in JavaScript debugger supports the new feature.

Breakpoint placeholder

New settings and other improvements#

Collapse identical lines in the Debug Console

There is a new setting, debug.console.collapseIdenticalLines, that controls if the Debug Console should collapse identical lines and show many occurrences with a badge. The default is to collapse.

Control which editors to save before debugging

There is a new setting, debug.saveBeforeStart, that controls what editors to save before debugging starts. This setting has the following values:

  • allEditorsInActiveGroup: Save all editors in the active group. The default value.
  • nonUntitledEditorsInActiveGroup: Save all editors in the active group except untitled ones.
  • none: Don't save any editors.

This setting is useful for PowerShell debugging since the PowerShell debugger supports debugging unsaved files.

Improved Enablement for Restart Frame action

With a new addition to the Debug Adapter Protocol debug extensions are now able to communicate to the VS Code UI whether the "Restart Frame" action is available on a selected stack frame. VS Code now disables the restart frame inline action in the Call Stack view for stack frames that cannot be restarted.

For example JS-Debug extension has adopted this and now async stack traces disable the restart frame action.

Languages#

TypeScript 4.2#

VS Code now ships with TypeScript 4.2.2. This major update includes many TypeScript language improvements, along with many improvements and bug fixes for JavaScript and TypeScript tooling.

You can read more about TypeScript 4.2 on the TypeScript blog.

Quick Fix to declare missing functions#

The new Add missing function declaration Quick Fix stubs out missing functions. For example, if we have a call to a missing function add:

const x: number = add(1, 2);

Using Add missing function declaration on add results in:

const x: number = add(1, 2);
function add(arg0: number, arg1: number): number {
  throw new Error('Function not implemented.');
}

You can use this Quick Fix while writing code to quickly stub out a function based on a call signature.

To use this Quick Fix in JavaScript, you must enable type checking.

JS Doc templates now generate @returns#

JS Doc templates now automatically include @returns if the function being annotated includes a returnstatement. For example, for the function getViz:

function getViz(el) {
  return el?.viz;
}

The generated JSDoc template is:

/**
 *
 * @param {*} el
 * @returns
 */
function getViz(el) {
  return el?.viz;
}

You can disable @returns in JSDoc comments with javascript.suggest.jsdoc.generateReturns and typescript.suggest.jsdoc.generateReturns.

Deprecated DOM APIs are now marked#

Deprecated DOM methods are now marked as deprecated in suggestions and in code:

document.clear being marked as deprecated in code

You can disable showing deprecated properties and functions in the editor by setting editor.showDeprecated: false.

Notebooks#

Automatically reload notebooks#

Notebooks now automatically reload when their file changes on disk and when they don't have unsaved changes. This should make it much simpler to work with notebooks that are under version control.

Improved focus for large cells#

When a large notebook cell is focused, you can now better tell which cell is focused when the top and bottom of the cells are out of view. We now show a border on the left and right side of the focused cell.

Notebook focus for a large cell

Hovers in CSS/LESS/SCSS and HTML#

You can now fine-tune the content of hovers in HTML and CSS to:

  • Not show the documentation from MDN
  • Not show the link to the MDN page

Use the settings css.hover.documentation and css.hover.references to change the hovers for CSS. Replace css with htmlcssscss or less to change the settings for those languages.

Preview features#

Extensible Markdown renderers for notebooks#

This iteration, we explored making the Markdown renderer for notebook cells extensible. In the screenshot below, for example, we've extended VS Code's Markdown renderer to support showing math formula in notebook cells:

A math formula being rendered in a notebook cell

In order to make our Markdown renderer extensible, we explored using Markdown It to render all notebook Markdown. We also explored moving the rendered Markdown into the backlayer webview of the notebook.

While we aren't yet ready to open up an official API for this, we plan on continuing this exploration in March. You can also try out the new extensible Markdown renderers today with the undocumented notebook.experimental.useMarkdownRenderer: true setting.

Contributions to extensions#

Brackets#

Developers coming from the Brackets source code editor can keep using their same keyboard shortcuts in VS Code with the Brackets Keymap extension. There is also a Brackets Extension Pack, which bundles extensions for working with CSS and creating live previews.

Brackets Extension Pack in the Marketplace

GitHub Pull Requests and Issues#

Work continues on the GitHub Pull Requests and Issues extension, which allows you to work on, create, and manage pull requests and issues.

To learn about all the new features and updates, you can see the full changelog for the 0.24.0 release of the extension.

Remote Development#

Work continues on the Remote Development extensions, which allow you to use a container, remote machine, or the Windows Subsystem for Linux (WSL) as a full-featured development environment.

Feature highlights in 1.54 include:

  • Ports view table layout
  • Remote - SSH: X11 Forwarding
  • Remote - WSL: Improved WSL 2 support

You can learn about new extension features and bug fixes in the Remote Development release notes.

Extension authoring#

Limits for editor title menu and "run" submenu#

The space in the editor toolbar (editor/title) is limited. Therefore, we have

  • implemented an overflow behavior. When the primary group, that is, the group of actions that get rendered with icons, exceeds nine commands then all additional commands overflow into the ...menu.
  • added the editor/title/run submenu. We ask extension authors to contribute run- and debug-commands into this menu, not into the editor/title-menu anymore as we had recommended in a previous release. In addition, it is no longer necessary to use the magic group values 1_run@10 and 1_run@20 in order to make the commands show up in the correct position.

Run drop down menu

Also know that the run submenu is dynamic, will replace itself with its first child when that's the only child.

Authentication Provider API#

You can now register an authentication provider, which can be used by other extensions to perform authentication against a service.

New feedback channel for the Extension Marketplace#

There's a new public repository for issues related to the Extension Marketplace. If you have technical issues, want to give feedback, or have feature requests, please open an issue.

Updated codicons#

We've added the following new icons to our codicon library:

  • debug-rerun
  • gather
  • git-pull-request-create
  • notebook-template
  • run-above
  • run-below
  • type-hierarchy
  • type-hierarchy-sub
  • type-hierarchy-super
  • variable-group

Codicons for tasks

We've also updated the following icons to be consistent:

  • debug-alt-small
  • debug-alt
  • debug-rerun
  • play-circle
  • play
  • run-above
  • run-all
  • run-below

Consistent codicons

Proposed extension APIs#

Every milestone comes with new proposed APIs and extension authors can try them out. As always, we want your feedback. This is what you have to do to try out a proposed API:

  • You must use Insiders because proposed APIs change frequently.
  • You must have this line in the package.json file of your extension: "enableProposedApi": true.
  • Copy the latest version of the vscode.proposed.d.ts file into your project's source location.

You cannot publish an extension that uses a proposed API. There may be breaking changes in the next release and we never want to break existing extensions.

Icon contribution point#

The icon contribution point allows extensions to define a new icon by ID, along with a default icon. That icon ID can then be used by the extension (or any other extensions that depend on the extension) at the places where ThemeIcon can be used: In Markdown strings (for example, "$(distro-ubuntu)" Ubuntu 20.04") and at all places that take a ThemeIcon (for example, new ThemeIcon("distro-ubuntu")).

Product icon themes can redefine the icon (if they know about the icon ID).

For more information, see issue 114942 for details and to provide feedback.

Inline value provider API#

Today the Show Inline Values feature of VS Code's debugger is based on a generic implementation in VS Code core, and doesn't provide customizability through settings or extensibility via extensions. As a consequence, it is not a perfect fit for all languages and sometimes shows incorrect values because it doesn't understand the underlying source language. For this reason, we are working on an extension API that allows to replace the built-in implementation completely or to replace parts of the implementation with custom code.

In this milestone, we've made a first implementation of the proposed API available.

Here is the inline values provider API in a nutshell:

  • an InlineValuesProvider must be registered for a language.
  • for a given document the InlineValuesProvider must locate all language elements for which inline values should be shown.
  • for every element an InlineValue descriptor object must be returned which instructs VS Code what information to show. Currently three types of InlineValue objects are supported:
    • InlineValueText: the complete text to be shown,
    • InlineValueVariableLookup: the name of a variable that VS Code will try to look up in the VARIABLES view to find its value. The name and the value are then shown in the form "name = value",
    • InlineValueEvaluatableExpression: an expression that VS Code will send to the debugger for evaluation. The expression and the result are then shown in the form "expression = result".

The following snippet (from Mock Debug) shows a minimal inline values provider for "markdown" files that uses a regular expression to locate "variables" and then instructs VS Code to find their values via the Variables view:

vscode.languages.registerInlineValuesProvider('markdown', {
  provideInlineValues(
    document: TextDocument,
    viewport: Range,
    context: InlineValueContext
  ): ProviderResult<InlineValue[]> {
    const allValues: InlineValue[] = [];
    for (let l = 0; l <= context.stoppedLocation.end.line; l++) {
      const line = document.lineAt(l);
      var regExp = /local_[ifso]/gi; // match variables of the form local_i, local_f, Local_i, LOCAL_S...
      do {
        var match = regExp.exec(line.text);
        if (match) {
          const varName = match[0];
          const varRange = new Range(l, match.index, l, match.index + varName.length);
          allValues.push(new InlineValueVariableLookup(varRange, varName));
        }
      } while (match);
    }
    return allValues;
  }
});

And now the inline values provider in action:

Debugger shows inline values

If you want to provide feedback for this proposed API, please add comments to this issue.

Testing#

We continued to make progress on testing in VS Code. This month we focused on refining the base experience in VS Code and the extension APIs. We have also published some provisional documentationon testing, which will be fleshed out as the APIs continue to stabilize.

Language Server Protocol#

A first proposal of a diagnostic pull model got implemented for the upcoming 3.17 release. The proposal is available in the next versions of the VS Code LSP libraries.

Debug Adapter Protocol#

More help text properties for ExceptionBreakpointsFilter#

Two optional UI attributes description and conditionDescription have been added to the ExceptionBreakpointsFilter.

With these attributes, clients can display additional information about exception breakpoints. The description property could be displayed in a hover and the conditionDescription could be used as a placeholder text for a text box where the condition can be edited.

Improved description for setExceptionBreakpoints request#

We have improved the description of the setExceptionBreakpoints request by adding guidance for what an adapter should do if the user inputs an invalid exception breakpoint condition.

New canRestart property for stack frames#

A new optional boolean property canRestart has been added to the stack frame. It indicated whether the stack frame can be restarted with the restart request. Based on this information a client can enable or disable a Restart Frame context menu action.

Engineering#

Progress on Electron sandbox#

This milestone we continued to make the VS Code window ready for enabling Electron's sandbox and context isolation features.

Specifically:

  • We were able to move some of the native module requirements we have in the renderer to other processes.
  • The MessagePort communication channel was implemented to work when sandbox is enabled.

New terminal process layout#

Terminal processes are now spawned under a new "pty host" process, instead of the window process. This change is not only part of the Electron sandbox but should also improve stability and performance of the terminal.

Windows installers published to Windows Package Manager#

Windows user and system installers for x86 and x64 are now being published to the Windows Package Manager. You can use the winget tool to search for all Visual Studio Code installers - winget search vscode, and install any of the published installers.

Building VS Code using TypeScript 4.3#

VS Code now is built using a nightly build of TypeScript 4.3. This lets us validate the TypeScript team's latest work and also provide feedback on new changes.

The latest TypeScript version already helped us catch a few cases where we were missing awaits in conditionals.

Prevent yarn.lock changes#

We now have CI that prevents PRs against yarn.lock files, in order to improve supply chain security.

Default branch: main#

We have started renaming the default branch of all our repositories to main, including microsoft/vscode. We are about 60% finished with this effort.

Documentation#

VS Code and Python in the classroom#

Read the case study of a Computer Science professor at Harvey Mudd College, who uses VS Code in his introductory CS classes with Python. Learn about the settings he recommends for his students, as well as helpful extensions and free self-paced Python and Data Science lessons.

Troubleshooting extensions blog post#

Everybody loves installing and using VS Code extensions. However, when you have lots of extensions installed, sometimes the editor can start to act "funny" and it would be great to know if the behavior is caused by a specific extension. If you missed the earlier announcement of the extension bisect utility, you can read this "Resolving extension issues with bisect" blog post, which describes how you can quickly troubleshoot "bad" extensions and even help the extension author(s) with feedback.

Notable fixes#

  • 100151: menu key applied to the wrong item in explorer
  • 112055: Debug opens a new integrated terminal for each Python session
  • 114881: Preserve symlinks when copying folders or files
  • 114933: "Task cannot be tracked" frustration
  • 115922: Cursor keys not working for filtering in File Explorer
  • 116037: No Link hovers shown for output in the Debug Console
  • 116101: I can't find target command in command search because the English description has disappeared
  • 116932: Throwing custom exceptions from contributed command execution shows cryptic error popup

Thank you#

Last but certainly not least, a big Thank You to the following people who contributed this month to VS Code:

Contributions to our issue tracking:

Contributions to vscode:

Contributions to language-server-protocol:

Contributions to vscode-languageserver-node:

Contributions to vscode-emmet-helper:

Contributions to vscode-html-languageservice:

Contributions to vscode-js-debug:

Contributions to vscode-textmate:

Contributions to vscode-vsce:

  • 0
    点赞
  • 0
    评论
  • 0
    收藏
  • 一键三连
    一键三连
  • 扫一扫,分享海报

CPU-Z 自读文件 ------------------ Version 1.56 版本号 1.56 October 2010 2010年10月 Contact : cpuz@cpuid.com 联系我们 :cpuz@cpuid.com Web page: http://www.cpuid.com/cpuz.php 网站:http://www.cpuid.com/cpuz.php Validation page : http://valid.canardpc.com 确认页面 :http://valid.canardpc.com Hall of Fame : http://valid.canardpc.com/records.php 名人堂 :http://valid.canardpc.com/records.php Forum : http://forum.canardpc.com/forumdisplay.php?f=74 社区 :http://forum.canardpc.com/forumdisplay.php? CPUID SDK : http://www.cpuid-pro.com/devkits.php CPUID SDK介绍 :http://www.cpuid-pro.com/devkits.php Configuration file (cpuz.ini) 配置文件 (cpuz.ini) ------------------------------ The configuration file must be named cpuz.ini and be present at the same directory level as cpuz.exe. It contains the following : 配置文件必须存放在cpuz.exe. 同一文件夹下名字为cpuz.ini [CPU-Z] TextFontName=Verdana TextFontSize=13 TextFontColor=000060 LabelFontName=Verdana LabelFontSize=13 PCI=1 MaxPCIBus=256 DMI=1 Sensor=1 SMBus=1 Display=1 ShowDutyCycles=0 UseDisplayAPI=1 - TextFontName : Font used for the information boxes. 信息框字体样式 - TextFontSize : Size of the font used for the information boxes. 信息框字体大小 - TextFontColor : Color of the font used for the information boxes. Value is expressed in hexadecimal, and consists in a classic Red/Green/Blue color code : RRGGBB 信息框使用字体颜色。RBG颜色:RRGGBB/000060 - LabelFontName : Font used for the label boxes. 标签框字体样式 - LabelFontSize : Size of the font used for the label boxes. 标签框字体大小 - Sensor : Set to OFF (or 0) disables sensor chip detection and voltages measurement. 1 to enable.传感器检测设置,1为开启、0为关闭 关闭后将不显示温度及电压 - PCI : Set to OFF (or 0) disables the PCI information. This disables chipset, SPD and, depending on the hardware, sensoring information. 1 to enable.PCI检测设置,1为开启、0为关闭 关闭后将不会显示主板、SPD及硬件传感器信息 - MaxPCIBus : Sets the maximum PCI bus to scan. Default value is 256. - DMI : Set to OFF (or 0) disables the DMI (Desktop Management Interface) information. This concerns BIOS vendor and version, motherboard vendor and revision. 1 to enable. DMI设置,1为开启、0为关闭。管壁厚 - SMBus : Set to OFF (or 0) disables SMBus information : SPD, and, depending on the hardware, sensoring information. 1 to enable.SMBUS设置,1为开启、0为关闭 关闭后将不会显示主板、SPD及硬件传感器信息 - Display : Set to OFF (or 0) disables the video card information reported in the validator. 1 to enable. 显示设备设置,1为启开、0为关闭 关闭后将不会显示显示设备信息 - ShowDutyCycles : Set to 1, switches the alternate clock computation method based on duty cycles. 0 to disable.占空比设置,1为开启、0为关闭 关闭后不会进行占空比计算时钟的方法 - UseDisplayAPI : Set to 1, uses the display driver to read the display adapters information. Parameters 参数 ---------- -txt=filename : Launch CPU-Z in ghost mode (no interface appears) and generates the register dump file (.txt) in the same directory as the exe file. 导出报告为txt文本格式 -html=filename : Same as "-txt" except it generates the html report. 导出报告为html超文本格式 -core=id : Displays clock speed of core #id (id can be set from 0 to Number of cores minus one). Keys ---- F5 : save the current tab in a bmp file F5 :保存当前页面为bmp文件 F6 : save the current tab in the clipboard F6 :保存当前页面在剪贴板中 F7 : save cvf file in the current directory F7 :保存CVF在默认目录 Cache Latency Tool ------------------ The cache latency tool can be downloaded at that address : http://www.cpuid.com/download/latency.zip Cache Latency Tool下载地址 :http://www.cpuid.com/download/latency.zip History 更新历史 ------- -------------------------------------------------------------------------------------------------- 1.56 - October 2010 - Intel Core i3/i5/i7 "2000" serie processors (Sandy Bridge) with new logos. - Intel Core i7 970 "Gulftown". - Intel P67 chipset. - AMD Phenom II, Athlon II and Sempron II "Caspian" processors. -------------------------------------------------------------------------------------------------- 1.55 - July 2010 - VIA VX900/VX900M and VN1000/VN1000M chipsets. - Intel Core i5-760, Core i7-875K and Core i5-655K processors. - Intel Core i7-940XM, 840QM, 740QM mobile processors. - Intel Core i5-450M, 540UM, 430UM, Core i3-370M mobile processors. - Intel Pentium P6000 processor. - New parameter in cpuz.ini : UseDisplayAPI -------------------------------------------------------------------------------------------------- 1.54 - March 2010 - Intel Core i7-880, Core i5-680, Core i3-550 processors. - Intel Xeon 5600 line (32nm) processors. - AMD Phenom II X6, Sempron II, Turion II, Turion II Ultra and Athlon II Mobile "Caspian" processors. - NVIDIA GeForce 320M chipset. - AMD 870/880G890GX + SB800/SB850 chipset. - Introduction of validation rooms. -------------------------------------------------------------------------------------------------- 1.53 - December 2009 - Fix validation issue with AMD Phenom processors (1.53.1). - Preliminary support for Intel Pinetrail platform (1.53.1). - Intel Core i7 930 & 950, Core i7 980X "Gulftown", Xeon W3565. - Intel Mobile Core i7/i5/i3 "Arrendale" (LV and ULV). - Intel "Clarkdale" platform improved support. - AMD Phenom FX-5000, Athlon II X2/X3/X4, Athlon L110. - AMD AM3 socket detection improved. - VIA VX800 and VX855 chipsets support. - ATI Radeon 2100 and Radeon X1250 support. - DirectX 11 detection fix. - Hardware virtualization support now reported as instructions set. - New HTML report with less information. -------------------------------------------------------------------------------------------------- 1.52 - July 2009 - Fix Core i7 clock bug (1.52.2) - New design with "Graphics" tab. - NVIDIA nForce 980a chipset support. - Intel Core i5 and Core i3 processors. - Intel Atom Z530, Pentium DC E6300 (2.8GHz) and Core 2 Solo processors. - Intel P55 and US15W chipsets preliminary support. - AMD Phenom TWKR support. - AMD Phenom X2 "Callisto" and Athlon X2 "Regor" processors. - AMD Opteron 6-core "Istanbul" processor. - Improved support for Windows 7. - New Intel logos. MD5 checksum : please refer to http://www.cpuid.com/cpuz.php#history -------------------------------------------------------------------------------------------------- 1.51 - April 2009 - New version with installer. - NVIDIA ION platform. - Intel "Clarkdale" processor preliminary support. MD5 checksum : please refer to http://www.cpuid.com/cpuz.php#history -------------------------------------------------------------------------------------------------- 1.50 - February 2009 - Improved support for AMD Phenom II processor. - Support for NVIDIA 740i chipset. - Several bug fixes. MD5 cpuz.exe (1.50) : E1C827C54F527404EDDA6D65DA0280D8 -------------------------------------------------------------------------------------------------- 1.49 - December 2008 - AMD Phenom II processor. - New Intel Core 2 models. - Improved loading time. - New online validation process. MD5 cpuz.exe (1.49) : B836E86B40D7AFAF99D9C512E8CC9FEF -------------------------------------------------------------------------------------------------- 1.48 - October 2008 - Improved support for Intel Core i7 (Bloomfield & Gainestown). - Intel Atom dual-core version support. - AMD Athlon "Kuma" processor support. - Alternate clock computation method based on "duty cycles" for Intel Core 2 processors (see ShowDutyCycles in cpuz.ini) MD5 cpuz.exe (1.48) : DB78FBF1F99B7709240B495E59758CCE -------------------------------------------------------------------------------------------------- 1.47 - August 2008 - Intel Core i7 processor. - Intel Core 2 Duo S Mobile processors. - NVIDIA MCP79/7A chipset. - AMD 790GX / SB750 chipset. MD5 cpuz.exe (1.47) : A7484EFA3C32BC968C248CB1237FF493 -------------------------------------------------------------------------------------------------- 1.46 - June 2008 - AMD Puma platform (Turion & Turion Ultra "Griffin"); - AMD Black Edition processors. - Intel Xeon EX "Dunnington". MD5 cpuz.exe (1.46) : C47432C41EC26156128F7B8E09E884CF -------------------------------------------------------------------------------------------------- 1.45 - May 2008 - Intel Atom Z500/Z510/Z520/Z530/Z540 processors. - Intel Core 2 Duo E7x00 processor. - AMD 45 nm Phenom (Dened & Shanghai) processors. - Intel P45 chipset. MD5 cpuz.exe (1.45) : DD4E540C04297CF93DC721166C13446E -------------------------------------------------------------------------------------------------- 1.44.2 - Mars 2008 - NVIDIA 650i, 680i, 750a/780a, 750i, 780i, 790i chipsets (1.44.2) - Intel G35 chipset (1.44.2) - Updated support for VIA chipsets (1.44.2) - Support for the new validator (1.44.1) - Preliminary support for VIA Isaiah processor. - Support for all VIA Model D processors: VIA C7-M, VIA C7-D, VIA Eden, VIA Eden. - Memory timings on Intel 5400A/B MCH (Skulltrail). - Fix AMD Phenom detection issue on Windows Vista 64. MD5 (1.44.2) : 81FB48A6EC7355E8D0DD71ADC2157CF6 -------------------------------------------------------------------------------------------------- 1.43 - January 2008 - Intel Skulltrail platform support (Core 2 Extreme QX9775 + 5400B MCH). - Intel X48 chipset detection. - AMD Athlon 64-LE 1600 and 1620 support. - Fix detection issues on unlocked Phenom (ES/BE). -------------------------------------------------------------------------------------------------- 1.42 - November 2007 - Intel Wolfdale/Yorkfield/Penryn CPUs support. - AMD Phenom and Opteron Barcelona support improved. - Current core selection menu (right click on the CPU page). - Loading progress. -------------------------------------------------------------------------------------------------- 1.41 - September 2007 - New CPU voltage monitoring. - Intel Xeon Tigerton support. - Intel IA64 CPUs support (Itanium / Itanium2)(special thanks to Rami Radi and Ray Hinchliffe). - AMD K10 Phenom preliminary support. - NVIDIA MCP73 support. - Intel XMP profiles support. - Memory modules nominal voltage. -------------------------------------------------------------------------------------------------- 1.40.5 - July 2007 - NVIDIA nForce 560 chipset support. - Intel Dynamic FSB technology support. - Athlon 64 X2 BE & Sempron LE (TDP 45W). - SiS671/FX/DX/MX northbridge support. - SiS968 southbridge support. -------------------------------------------------------------------------------------------------- 1.40 - May 2007 - VIA P4M800CE chipset support. - Preliminary support for Intel Penryn CPUs family (45 nm). - Intel Core 2 Duo E6x20, Pentium E2140/2160 processors recognition. - Intel P35, G33, G31, Q35, Q33, X38 chipsets support. - Intel GL960/GM965/PM965 chipsets support. - AMD Athlon 64 "Lima" processor support. - AMD Geode LX processor support. - NVIDIA nForce 520 chipset support. - New parameter "-console" to generate output in a command prompt (Windows XP only). - New icon. -------------------------------------------------------------------------------------------------- 1.39 - February 2007 - Windows Vista 64 support. - VIA CX700/VX700 chipset. - Added Merom XE (X7900/X7800) - Added "PCI" and "MaxPCIBus" in the ini file to configure PCI scanning. - Added "-core" parameter to display the clock speed of the specified core. - Lot of bug fixes. -------------------------------------------------------------------------------------------------- 1.38 - November 2006 - VIA P4M890 and P4M900 chipsets. - NVIDIA 650i and 680i chipset. - AMD Athlon 64 FX-7x processor. - Core 2 Duo E6850, E6750, E6650 processors. - socket 775 Xeon processor. - New parameters "-txt" and "-html" (see above). - Lot of bug fixes. -------------------------------------------------------------------------------------------------- 1.37 - October 2006 - Intel Core 2 Quad, Celeron 360, Mobile Core 2 Duo T5200 support. - Changed SSE4 to SSSE3 (Supplemental SSE3). - Added VIA VT8237A southbridge. - New HTML report. - Several bug fixes. -------------------------------------------------------------------------------------------------- 1.36 - August 2006 - New processor information display. - Intel 5000X/P/Z/V SPD support. - Intel Pentium D 925 & 945. -------------------------------------------------------------------------------------------------- 1.35 - June 2006 - ATI RS350, RS400, RS480/RX480, RS482, RD580/RX580, RS600/RD600, RS690, RS700 chipsets support. - ATI SB600 southbridge support. - Intel P965 chipset support. - Engineering samples Core based CPUs report. - Windows Vista product line report. -------------------------------------------------------------------------------------------------- 1.34.1 - May 2006 - AMD socket AM2/S1/F (rev F.) CPUs support. - Enhanced Performance Profile (EPP) memory information report. - Added Trc (bank cycle time) in DDR2 SPD report. - Added Trc (bank cycle time) on i925, i945, i955, i975 chipsets. - FB-DIMM DDR2 SPD information report. - Core 2 Duo names and logos added. - Turion 64 X2 logo added. - Several bug fixed. -------------------------------------------------------------------------------------------------- 1.33.1 - April 2006 - Intel i965 chipset support added. - Fix SPD detection problem on SiS 964/965/966 southbridges. - ODC (Odd Divisor Correct) for Athlon64 rev E. -------------------------------------------------------------------------------------------------- 1.33 - April 2006 - Memory Command Rate timing added. - Improved support for Intel Conroe/Merom CPUs. - Celeron M 420/430 Yonah. - Xeon Dual core Dempsey. - VIA C7-M CPU detection added. - VIA PT880, PT880 Pro, K8T900 chipsets support. - nVidia nForce 550/560/570 (MCP55) chipset support. - VIA VT8251 southbridge support. - Fixed HyperTransport information misreports (in dump file). - Added K6-2 and K6-III logos. -------------------------------------------------------------------------------------------------- 1.32.1 - March 2006 - New Intel logos. - Added Pentium D 925, Pentium EE 965. - Several bugs fixed. -------------------------------------------------------------------------------------------------- 1.32 - February 2006 - Athlon FX-60 detection added. - Athlon64 new memory dividers. - Celeron 35x Cedar Mill, Pentium D 805. - Core Solo & Core Duo detection improved. - VIA C7 CPU detection added. - Intel i975X, i945GT chipsets support. - ATI RD580 chipset support. - ULi smbus support improved. - Fix smbus conflict with ClockGen. -------------------------------------------------------------------------------------------------- 1.31 - November 2005 - Improved support for ATI RS480/482 chipsets. - GeForce 6100/6150 (nForce 410/430) chipsets support. - Intel E7520 chipset support. - New CPUs support : AMD Opteron socket 939, Intel Pentium 4 Cedar Mill and Presler, Intel Xeon Paxville, Intel Pentium M Yonah SC & DC. - Several bug fixed. -------------------------------------------------------------------------------------------------- 1.30 - August 2005 - Latest Sempron and Turion support improved. - Intel Xeon Potomac, Pentium M 780 support. - Improved Windows version report. - Support for SMBus on latest SiS bridges (964, 965, 966) and ULi bridges. - Increased clocks refresh rate. - Several bug fixed. -------------------------------------------------------------------------------------------------- 1.29 - June 2005 - New PCI devices report. - Switch for VCore report in .ini file. - VCore report on some uGuru mainboards. - Improved clocks computation. - Improved support for latest AMD CPUs, Celeron D 3x1 (EM64T). - Improved support for SiS 649, 650 and 656 chipsets, Intel 915PM chipset. - Improved stability when several instances of CPU-Z are running in the same time. - Restored html report in ghost mode (see "Parameters" chapter above). -------------------------------------------------------------------------------------------------- 1.28.6 - March 2005 - Support for Athlon 64 X2 CPUs - Support for i955X chipset - Bunch of bugs -------------------------------------------------------------------------------------------------- 1.28 - March 2005 - Support for SiS chipsets improved : 648FX, 649, 655FX, 655TX, 656 - Support for nVidia nForce4 SLI Intel Edition - Support for Intel Pentium D, Pentium XE, AMD Turion, Opteron 252 - New F7 key to simplifiy the creation of the validation file -------------------------------------------------------------------------------------------------- 1.27 - February 2005 - Support for Intel Pentium 4 6xx CPUs. - New validation system. - Hundred of bug fixes. -------------------------------------------------------------------------------------------------- 1.26 - December 2004 - VCore display on Pentium M CPUs. - New CPU clock computation. - Improved support of Transmeta CPUs. - Several bugs fixed. -------------------------------------------------------------------------------------------------- 1.25 - November 2004 - nVidia nForce4 chipset support - Intel Pentium 4J support - New button to refresh memory timings - Several bugs fixed -------------------------------------------------------------------------------------------------- 1.24 - September 2004 - AMD Sempron support - New memory SPD page - PCI-Express graphic interface support - Configuration file - External cache latency tool - Restored html report - Fix several bugs -------------------------------------------------------------------------------------------------- 1.23 - June 2004 - Intel i915P/G, i925X chipsets support - Intel LGA775 CPUs support - Intel's CPU number display - New AMD Athlon 64 steppings - New report in one file -------------------------------------------------------------------------------------------------- 1.22 - April 2004 - New CPUs : Xeon Nocona, Celeron Prescott - DDR2 memory support - Clock mode when iconized -------------------------------------------------------------------------------------------------- 1.21 - January 2004 - one file package 一个文件包 - Windows 64 support 支持Windows64位操作系统 - new chipsets support 新主板支持 - new CPU support : Celeron M, Pentium 4 "Prescott" 新CPU支持:赛扬 M,奔腾4 "Prescott" -------------------------------------------------------------------------------------------------- 1.20a - October 2003 - memory frequency and ratio on nForce2 - KT600 support 增加对威盛KT600芯片组支持 - W83627THF VRM mode - SPD read improvement SPD - Fix some memory leaks (DMI) 修复一些内存DMI信息 - Fix memory size report 修复内存大小报告 - Fix AGP side band status 修复AGP带宽状态 --------------------------------------------------------------------------------------------------
©️2021 CSDN 皮肤主题: 大白 设计师:CSDN官方博客 返回首页
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、C币套餐、付费专栏及课程。

余额充值