呵呵，利用空閒時間來發怖一些最新Windows 7 及未來Windows 8~9消息！
以下資料國外流出。
windows 8, midori, singularity, redhawk, minsafe
CodenameWindowsWindows 7, Windows 8, Windows 9, Singularity, Midori - Alpha, Beta, Release Candidate (RC), Release to Manufacturing (RTM)
« Windows 7 Software Logo - Download Alpha Toolkit
Windows 7 Features Support for Suite B Cryptographic Algorithms via IPsec »
Starting Soon, Windows 8 Major Improvements to Revolutionize File Access in Branch OfficesPublished by Mire_Bat April 15, 2009 in Windows 7
Windows 8 improvements and innovative features designed to reinvent the file access wheel for branch offices are planned to debut soon, according to Microsoft. Planning for Windows 8, the successor of Windows 7, is already well under way, but there’s no way to tell yet if Microsoft will start the actual work on the DFSR (Distributed File System Replication ) file replication engine in Windows 8, or if the features will debut into the planning stage. Windows 7 and Windows Server 2008 R2, already offer companies with branch offices BranchCache which streamlines access to content. Cached content is available either in Distributed Cache mode (peer-2-peer clients) or in Hosted Cache mode (hosted on a Windows 7 Server).
“For the upcoming version of Windows, new critical features are being worked on including cluster support and support for one way replication. The core engine is also being reworked to provide dramatic performance improvements. We will also soon be starting major improvements for Windows 8 where we will be including innovative features which will revolutionize file access in branch offices,” reads an excerpt from a Microsoft job posting for the position of Lead Software Development Engineer in Test - Date Posted: 04/14/2009
The full job details from Microsoft:
Are you a talented SDE/T Lead looking for the next technical challenge on a key operating system component? Are you passionate about distributed systems, networking, file systems and want to be the leader of a cutting edge project? Are you looking for a team with abundant opportunities to grow? If so, we have the position for you!
DFSR is Microsoft’s premier file replication engine and is an integral part of our branch office strategy and File Server role. It can scale to thousands of servers and replicate hundreds of terabytes of data. We have shipped the technology that powers file sharing in Windows Live Messenger, Windows Meeting Spaces (Vista) and Branch Office replication in Windows Server 2008 which has strong customer deployment. DFSR technology saves MS-IT and our customers more than 80% WAN bandwidth by using advanced On-The-Wire differential compression.
For the upcoming version of Windows, new critical features are being worked on including cluster support and support for one way replication. The core engine is also being reworked to provide dramatic performance improvements. We will also soon be starting major improvements for Windows 8 where we will be including innovative features which will revolutionize file access in branch offices.
We are looking for a strong lead who has the right blend of technical passion, leadership skills and testing experience. From a technical standpoint, we are looking for a candidate having an understanding of and a passion for large scale distributed systems. From a leadership point of view, you will need to be able to build the vision for the team, work with your development and PM counterparts on engineering excellence and effectively drive the quality of the component. In terms of testing experience, the ability to define and deliver test solutions affecting all release criteria (functionality, scalability, performance, stress, longhaul, security, etc.) is a must.
This is a great opportunity to work in a fun and fast paced group where we value innovation, creativity, technical excellence and career growth in the test discipline.
Our ideal candidate would have completed at least one product cycles or have a related industry experience. Experience in managing projects and teams is required. Excellent knowledge of testing techniques and methodologies, good communication skills, and a proven track record of growing people are a must. A MS or BS in Computer Science with 5+ years of technical experience is required. Experience in kernel mode device drivers development and distributed systems is a plus.
ShareThis
9 Responses to “Starting Soon, Windows 8 Major Improvements to Revolutionize File Access in Branch Offices”Feed for this Entry Trackback Address
Windows 7 Pre-RTM官方命名規則：
X86的ISO文件名中含有GRMCULFRER字樣！X64的則爲GRMCULXFRER！
何謂散裝版？解釋如下：
即所發布的ISO鏡像裏的文件均爲官方文件，由于MC提供的原版鏡像含有水印，不能夠泄露，所以ISO是由非MS官方人員重新打包發布！只要散裝版ISO中的install.win和官方原版的一樣（MD5）即可！安裝效果與官方原版鏡像無任何區別！可放心使用！
最新進展：（2009年6月12日）
Windows 7 Build RTM Final will leak after June 19, 2009…
Windows 7 Build7229/7231後應該不會再Leak其他版本（直至RTM Final）…
大家可以直接等Windows 7 Build RTM Final…
來自國外ZDNet部落格的消息，微軟正在籌備一款「Midori」作業系統，用來取代目前的Windows。目前Midori還在初期發展的階段，也就是說，Winodws Vista之後還會推出下一版Windows 7、甚至Windows 8，再來才有可能讓Midori接手。這至少也是2010年以後的事了。
「Midori」是「綠色」的日文發音，還有一款作業系統剛好也叫「Midori Linux」。當然這跟微軟的Midori無關，目前官方也不表示任何意見，最多也只能找到一些引用ZDNet報導的小道消息而已。
ZDNet號稱，Midori是從「Microsoft Research」研究中心的「Singularity」計畫所衍生的分支，關於Singularity的細節就明確多了，這是一套全新作業系統的研究計畫，非但不是「不能說的祕密」，連原始碼都是公開的。因為Singularity不是以發佈商用作業系統為終極目標，而是提出一套系統架構，讓學術界、產業界用來進行更深入的研究。
砍掉重練的作業系統
Singularity計畫在2003年成立，從微軟官方的說明來看，的確很像是在試探Windows之後的全新作業系統。Microsoft Research網站上提到，不管是Windows、Mac OS X、Linux、UNIX等作業系統的開發流程，都是繼承了沿用40年之久的傳統架構，已經不符合目前的硬體功能與需求。所以Singularity要解答一個簡單的問題：「如果現在就要重新開發一套穩定、安全的作業系統，該怎麼做？」
Singularity的做法包括：
1. 大都是以managed code寫成，簡單的解釋，managed code就是讓程式碼在虛擬機器底下執行，比方JAVA和.NET程式都會編譯成managed code，相反的，unmanaged code就會直接交給CPU執行。
2. 幾乎都是以C#語言寫成，C#的發音是C Sharp，是微軟開發的最新程式語言，比傳統的C/C++寫成的作業系統更可靠，能夠避免緩衝區溢位等漏洞。
3. 另外，系統裡的程式會被拆解成獨立的元件，在編譯之前就可以執行檢查，避免單一程式錯誤就讓整個系統當機；安裝軟體之前也會核對程式碼，確保不影響系統穩定性才會「放行」。
目前微軟內部版本為Windows 7_build_7300 已經由俄羅斯某網站洩漏出來最新版本！
比較可能接近RTM正式版本會由build 7300跳過......
Best Buy 備忘錄洩露 Windows 7 升級資訊
以下圖片是我昨天安裝最新Windows 7 _7127版本
下面這張是程式設計軟體 2010版本~(在xp上安裝~還沒有在Windows 7安裝過)
這是安裝好的介面圖
Pre-Milestone 1:(初期演化版 1)
6.1.6410.0.fbl_refactor_dev(jschwart).070409-1035
6.1.6415.0.debuggers(dbg).070404-1234
6.1.6418.0.debuggers(dbg).070404-1255
6.1.6429.?.fbl_multimedia_media.070514-1730
6.1.6459.1.fbl_shell_dex.070826-1730
6.1.6469.1.fbl_find_dev.
6.1.6475.1.fbl_wlk_dtmse_11000.071108-1226
6.1.6480.1.fbl_srv_powershell_ctp(srvbld).071029-1751
6.1.6499.1.fbl_security_bugfix(sepbld-s).071120-0135
6.1.6507.1.winmain_longhorn(wmbla).071113-1716
Milestone 1:(演化版 1)
6.1.6516.1.fbl_dox_dev_ihvs.080109-1848
6.1.6516.1.fbl_dox_dev_ihvs.080109-1928
6.1.6518.1
6.1.6519.1.winmain.071220-1525
6.1.6521.1.fbl_kernel_platarch.080107-1800
6.1.6522.0.winmain.071223-1309 .
6.1.6536.?.fbl_tools_phoenix(corevc).080215-1330-LDDM
6.1.6547.1
6.1.6568.1.winmain.080312-1858
6.1.6568.1.fbl_wdk_build(dasmit).080318-1440
6.1.6574.1.winmain.080???-????
6.1.6585.?.winmain.080407-1714
6.1.6585.1.fbl_srv_powershell_ctp.080411-1634
Milestone 2:(演化版 2)
6.1.6589.1.winmain_win7m2.080420-1634
6.1.6608.?.winmain_win7m2.080511-1400
6.1.6720.1.fbl_dox_dev_ihvs.080603-2145
6.1.6720.1.fbl_dox_dev_ihvs.080603-2149
6.1.6721.1.debuggers(dbg).080908-1333
6.1.6723.1.winmain.080603-1835
6.1.6726.1.fbl_dox_dev_ihvs.080609-2026
6.1.6726.1.fbl_dox_dev_ihvs.080609-2033
6.1.6727.1.fbl_dox_dev_ihvs.080611-0004
6.1.6727.1.fbl_dox_dev_ihvs.080611-0008
6.1.6727.1.fbl_dox_dev_ihvs.080611-0027
6.1.6727.1.fbl_dox_dev_ihvs.080611-0032
6.1.6730.1.fbl_dox_dev_ihvs.080614-0511
6.1.6730.1.fbl_dox_dev_ihvs.080614-0543
6.1.6756.0
6.1.6759.0.FBL_FUN_DIAG_DEV(josesua).080807-0822
6.1.6761.0.fbl_wexpartners_mc(dcohen).080731-1456
6.1.6764.0.fbl_wexpartners_mc(shyams).080805-1551
6.1.6768.0.fbl_security_bugfix(nide).080811-1231
6.1.6768.0.FBL_SECURITY_BUGFIX(nide).080811-1458
6.1.6769.0.fbl_security_bugfix(dlisley).080814-1553
6.1.6769.0.fbl_security_bugfix(dlinsley).080814-1555
6.1.6776.?.fbl_srv.080823-0???
6.1.6780.0.winmain_win7m3.080829-1900
6.1.6801.0.winmain_win7m3.080913-2030
Pre-Beta 1:(初期測試版1)
6.1.6904.0.fbl_dox_dev_ihvs.080908-1556
6.1.6908.0.fbl_fun_global_m1(sunggch).080422-1716
6.1.6912.0.fbl_security_bugfix(dacostan).080918-1720
6.1.6912.0.fbl_security_bugfix(dacostan).080918-1756
6.1.6914.0.fbl_dox_dev_ihvs.081001-1528
6.1.6914.0.fbl_dox_dev_ihvs.081001-2123
6.1.6914.0.fbl_dox_dev_ihvs.081001-2138
6.1.6914.0.fbl_dox_dev_ihvs.081001-2209
6.1.6914.0.fbl_dox_dev_ihvs.081001-2251
6.1.6914.0.fbl_dox_dev_ihvs.081001-2254
6.1.6914.0.fbl_dox_dev_ihvs.081006-0105
6.1.6914.0.fbl_dox_dev_ihvs.081006-1212
6.1.6916.?.winmain.080924-1557
6.1.6917.?.winmain.080925-1915
6.1.6919.?.fbl_fun_diag_dev(gaurava).080118-1456
6.1.6920.0.winmain.081001-1846
6.1.6920.?.fbl_dgt_dev2.081006-1730 deeper2k
6.1.6920.0.fbl_dgt_dev2_sdknovember08(bld4act).081 016-1627
6.1.6922.0.fbl_fun_diag_dev(wedsonaf).080818-1825
6.1.6925.0.fbl_dox_dev_ihvs.081009-1812
6.1.6926.?.winmain.081009-1855 Rhys
6.1.6926.0.fbl_uiplat_dev1(alexlop).081013-1037
6.1.6926.0.fbl_dox_dev_ihvs.081016-1746
6.1.6926.0.fbl_dox_dev_ihvs.081026-2150
6.1.6928.0.fbl_tools_developer(amitrao).081111-1608
6.1.6930.?.fbl_multimedia_media.081016-1750
6.1.6930.0.fbl_multimedia_media(bld4act).081019-0916
6.1.6930.0.fbl_multimedia_media(bld4act).081019-0926
6.1.6931.0.fbl_security_bugfix(jscottm).081020-1655
6.1.6931.0.fbl_security_bugfix(jscottm).081020-1735
6.1.6932.?.winmain.081017-1835
6.1.6932.?.fbl_shell_dex.081020-1755
6.1.6933.0.winmain.081020-1842
6.1.6934.?.winmain.081021-1817
6.1.6935.?.winmain.081022-1857 Rhys
6.1.6935.0.fbl_multimedia_media(bld4act).081026-0917
6.1.6936.0.winmain.081023-1800
6.1.6936.0.fbl_net_rpc.081028-2000
6.1.6937.?.winmain.081027-1805 Staneck
6.1.6937.?.fbl_whenet_devbugfix.081028-1900
6.1.6938.0.fbl_multimedia_media(bld4act).081031-0928
6.1.6940.?.fbl_wexpartners_mc.081102-1800
6.1.6941.0.winmain.081101-1740
6.1.6941.0.fbl_srv.081102-0300
6.1.6944.0.fbl_fun_diag_dev(sanketp).081028-1927
6.1.6944.0.fbl_multimedia(codecna).081104-1358
6.1.6945.0.?.081106-1833 Shipit
6.1.6948.?.winmain.081111-1905 peacho
6.1.6948.?.fbl_shell_dex.081112-1755
6.1.6949.0.(fbl_srv_powershell_ctp(srvbld).081105-1651
6.1.6951.0.winmain.081114-2042
6.1.6953.?.winmain.081118-1923
6.1.6953.0.FBL_SECURITY(nide).081119-1801
6.1.6954.? Freak180
6.1.6956.0.winmain.081122-1150
6.1.6995.0.winmain.081202-1120
Beta 1:(測試版1)
6.1.7000.0.winmain_win7beta.081212-1400
Pre-RC:(初期RC版)
6.1.7003.?.winmain.081201-????
6.1.7004.0.?.081203-1830
6.1.7012.0.winmain.081215-1810
6.1.7015.0.winmain.081218-1724
6.1.7015.?.fbl_multimedia_media.090104-1750
6.1.7015.0.fbl_security_bugfix(sepbld-s).090105-1037
6.1.7016.0.winmain.090105-1500 bb10
6.1.7017.0.fbl_multimedia_media(bld4act).090111-0916
6.1.7022.0.winmain.090115-1850
6.1.7025.0.winmain.090120-1850
6.1.7028.?.fbl_srv_cluster.090125-1930
6.1.7032.0.winmain.090129-1812
6.1.7033.?.winmain.??????-????
6.1.7033.?.fbl_kernel_vm_dev(mikekol).090203-1215
6.1.7034.0.winmain.090202-1920
6.1.7041.?.winmain.090210-1755
6.1.7046.?.winmain.090219-????
6.1.7047.0.winmain.090218-1900
6.1.7047.0.winmain.090219-0255
6.1.7048.0.winmain.090219-1845
6.1.7050.0.winmain.090223-1948
6.1.7050.0.fbl_deployment_bugfix(anfairch).090224-1514
Pre-RC 2:(初期RC版2)
6.1.7051.0.winmain.090224-1840
6.1.7052.0.winmain.090225-1855
6.1.7053.0.winmain.090226-1910
6.1.7054.0.winmain.090302-1902
6.1.7055.0.winmain.090303-2130
6.1.7056.0.winmain.090304-1844
6.1.7057.0.winmain.090305-2000
6.1.7058.0.winmain.090307-1140
6.1.7059.0.winmain.090309-1815
6.1.7060.0.winmain.090310-1910
6.1.7061.0.winmain.090311-1856
6.1.7062.0.winmain.090312-1900
6.1.7063.0.winmain.090313-1842
6.1.7064.0.winmain.090316-1936
6.1.7065.0.winmain.090317-1835
6.1.7066.0.winmain.090318-1812
6.1.7067.0.winmain.090319-1853
6.1.7068.0.winmain.090321-1322
6.1.7069.0.winmain.090323-1630
6.1.7070.0.winmain.090324-1853
6.1.7071.0.winmain.090326-1750
6.1.7072.0.winmain.090327-1845
6.1.7073.0.winmain.090330-1830
6.1.7074.0.winmain.090331-1850
6.1.7075.0.winmain.090401-1840
6.1.7076.0.winmain.090402-1838
RC Branch:(RC 支流版)
6.1.7077.0.winmain_win7rc.090404-1255
6.1.7078.0.winmain_win7rc.090406-1758
6.1.7079.0.winmain_win7rc.090407-1902
6.1.7080.0.winmain_win7rc.090408-1900
6.1.7081.0.winmain_win7rc.090409-1900
6.1.7082.0.winmain_win7rc.090410-1901
6.1.7083.0.winmain_win7rc.090413-1900
6.1.7084.0.winmain_win7rc.090414-1900
6.1.7085.0.winmain_win7rc.090415-1900
6.1.7086.0.winmain_win7rc.090416-1900
6.1.7087.0.winmain_win7rc.090417-1900
6.1.7088.0.winmain_win7rc.090419-1500
RC 1:(RC版1)
6.1.7100.0.winmain_win7rc.090421-1700
Pre-RTM 1:(初期RTM版1)
6.1.7105.0.winmain.090404-1235
6.1.7106.0.winmain.090408-1623
6.1.7107.0.winmain.090409-1840
6.1.7108.0.winmain.090410-1755
6.1.7109.0.winmain.090413-1552
6.1.7110.0.winmain.090414-1906
6.1.7111.0.winmain.090415-1920
6.1.7112.0.winmain.090416-1820
6.1.7113.0.winmain.090417-1710
6.1.7114.0.winmain.090420-1603
6.1.7115.0.winmain.090421-1650
6.1.7115.0.winmain.090421-1650
6.1.7116.0.winmain.090422-1816
6.1.7117.0.winmain.090423-1737
6.1.7118.0.winmain.090424-1710
6.1.7119.0.winmain.090427-1750
6.1.7120.0.winmain.090428-1740
6.1.7121.0.winmain.090429-1835
6.1.7122.0.winmain.090430-1800
6.1.7123.0.winmain.090501-1720
6.1.7124.0.winmain.090504-1715
6.1.7125.0.winmain.090505-1530
6.1.7126.0.winmain.090506-1820
6.1.7127.0.winmain.090507-1820
6.1.7128.0.winmain.090508-xxxx
6.1.7129.0.winmain.090511-xxxx
6.1.7130.0.winmain.090512-1609
6.1.7131.0.winmain.090513-xxxx
6.1.7132.0.winmain.090514-xxxx - actual build in winmain branch
6.1.7133.0.winmain.090515-1635
6.1.7134.0.winmain.090518-1730
6.1.7135.0.winmain.090519-xxxx
6.1.7136.0.winmain.090520-0703
6.1.7137.0.winmain.090521-1745
6.1.7138.0.winmain.090522-xxxx
6.1.7139.0.winmain.090525-xxxx
週六及週日微軟不上班,所以不可能會出現在週六及週日發佈的版本
好啦~就此為止囉~ 有什麼Windows 7~8 消息~我會再找時間PO上的
Engadget披露一封自Best Buy內部外洩的備忘錄，內含一些有關Windows 7的詳細資訊。
其中最令人注目的是，這封備忘錄指出，自6月26日起，民眾就可開始買到日後可免費升級至Windows 7的Vista電腦。根據我所掌握的消息，這個日期是正確無誤的。
備忘錄上說，在6月26日當天，Best Buy將透過自家網站，開始預售升級版Windows 7 Home Premium，預售價49美元，而Windows 7 Professional則售99美元。至於這些是標準定價或促銷價，目前還不是很清楚，備忘錄只說預購活動以16天為限。
微軟資深副總裁Bill Veghte上周接受訪問時的確表示，微軟正考慮應Vista使用者的要求，提供一種低價或甚至免費的Windows 7升級計畫。據此推論，或許預購選擇就是那個計畫。
Best Buy的備忘錄中也附帶Windows 7的文宣：「這個新版作業系統不只是『可用的Vista』計畫 - 它是新的作業系統，提供改良的生產力、功能以及創造力，而且佔用更少的電腦資源。」
上周微軟宣布，Windows 7預定在10月22日正式推出。同時，微軟證實，的確計劃推出這樣的技術升級保證計畫，只是未說明何時啟動。
記者截稿前尚未能取得Best Buy方面的回應，但消息來源向我證實確實有這封備忘錄，是在6月1日發布的。
|
