Skip to main content

Development of Windows 7 - Middleware News

Development

Development of Windows 7

Originally, a version of Windows codenamed Blackcomb was planned as the successor to Windows XP and Windows Server 2003. Major features were planned for Blackcomb, including an emphasis on searching and querying data and an advanced storage system named WinFS to enable such scenarios. However, an interim, minor release, codenamed "Longhorn" was announced for 2003, delaying the development of Blackcomb.[10] By the middle of 2003, however, Longhorn had acquired some of the features originally intended for Blackcomb. After three major viruses exploited flaws in Windows operating systems within a short time period in 2003, Microsoft changed its development priorities, putting some of Longhorn's major development work on hold while developing new service packs for Windows XP and Windows Server 2003. Development of Longhorn (Windows Vista) was also "reset," or delayed, in August 2004. A number of features were cut from Longhorn.[11]

Blackcomb was renamed Vienna in early 2006,[12] and again to Windows 7 in 2007.[13] In 2008, it was announced that Windows 7 would also be the official name of the operating system.[14][15]

The first external release to select Microsoft partners came in January 2008 with Milestone 1, build 6519.[16] At PDC 2008, Microsoft demonstrated Windows 7 with its reworked taskbar. Copies of Windows 7 build 6801 were distributed out at the end of the conference, but the demonstrated taskbar was disabled in this build.

On December 27, 2008, Windows 7 Beta was leaked onto the Internet via BitTorrent.[17] According to a performance test by ZDNet,[18] Windows 7 Beta beat both Windows XP and Vista in several key areas, including boot and shut down time, working with files such as loading documents; other areas did not beat XP, including PC Pro benchmarks for typical office activities and video-editing, remain identical to Vista and slower than XP.[19] On January 7, 2009, the 64-bit version of the Windows 7 Beta (build 7000) was leaked onto the web, with some torrents being infected with a trojan.[20][21] At CES 2009, Microsoft CEO Steve Ballmer announced the Windows 7 Beta, build 7000, had been made available for download to MSDN and TechNet subscribers in the format of an ISO image.[22] The Beta was to be publicly released January 9, 2009. Initially, Microsoft planned for the download to be made available to 2.5 million people on January 9. However, access to the downloads was delayed due to high traffic.[23] The download limit was also extended, initially until January 24, then again to February 10. People who did not complete downloading the beta had two extra days to complete the download. After February 12, unfinished downloads became unable to complete. Users can still obtain product keys from Microsoft to activate their copy of Windows 7 Beta. Users can still download Windows 7 via the Microsoft Connect program. The beta will expire on August 1, 2009, with shutdowns every two hours starting July 1, 2009. The release candidate, build 7100, has been available for MSDN and TechNet subscribers and Connect Program participants since April 30 and became available to the general public on May 5, 2009. It has also been leaked onto the Internet via BitTorrent.[24] The release candidate is available in five languages and will expire on June 1, 2010, with shutdowns every two hours starting March 1, 2010.[25] Microsoft has stated that Windows 7 will be released to the general public on October 22, 2009 and to Technet subscribers on August 6, 2009.[26] Microsoft announced that Windows 7, along with Windows Server 2008 R2 were released to manufacturing on July 22, 2009. Windows 7 RTM is build 7600.16385 which was compiled on July 13, 2009, and was declared the final RTM build after passing all Microsoft's tests internally.[3]

Goals

Bill Gates, in an interview with Newsweek, suggested that the next version of Windows would "be more user-centric".[27] Gates later said that Windows 7 will also focus on performance improvements.[28] Steven Sinofsky later expanded on this point, explaining in the Engineering Windows 7 blog that the company was using a variety of new tracing tools to measure the performance of many areas of the operating system on an ongoing basis, to help locate inefficient code paths and to help prevent performance regressions.[29]

Senior Vice President Bill Veghte stated that Windows Vista users migrating to Windows 7 would not find the kind of device compatibility issues they encountered migrating from Windows XP.[30] Speaking about Windows 7 on October 16, 2008, Microsoft CEO Steve Ballmer confirmed compatibility between Vista and Windows 7,[31] indicating that Windows 7 will be a refined version of Windows Vista.[31]

Comments

adsrerrapop

Popular posts from this blog

Troubleshooting Java/JMS SSL Configurations - Middleware News

 This document is intended to help diagnose WebSphere MQ V7 Java™ or JMS SSL setup errors. It lists most of the common configuration errors that can cause an SSL connection from a Java/JMS client to a queue manager to fail, and gives the course of action to resolve the problem. In each case the error can be diagnosed by a combination of the error seen in the client log - either a console output, trace file or SystemOut.log file - and the queue manager's error logs. The document is quite long, so the easiest way to find the potential error is to search for one of the errors seen in this list, then filter this list using the error from the opposite end of the channel. All cases here assume that 2-way authentication is being attempted (SSLCAUTH set to REQUIRED on the queue manager's SVRCONN channel). This is the default, and the errors are very similar for 1-way authentication (SSLCAUTH set to OPTIONAL). Symptom Instructions on collecting documentation...

Using telnet to test connectivity between IBM Websphere MQ Client and MQ server - Middleware News

You are having trouble connecting a WebSphere MQ client to a MQ server, receiving errors that you can not connect to the MQ queue manager. One of the first things to determine is if the two machines can communicate, and using the telnet tool is one way to accomplish it. Symptom Receiving errors which state that a queue manager is not found or not available. Connection errors. For example: AMQ9213, AMQ9524, AMQ9202 or AMQ9508 or MQRC =2059 0x0000080b MQRC_Q_MGR_NOT_AVAILABLE. Please note, this is by no means an exclusive list of errors related to this type a problem but just a sample of some of the more common error messages and codes that might occur. Cause One possible cause is that the two machines can not communicate. May be the IP address or hostname was not properly specified by the MQ client. The port number might be incorrect. A queue manager is not running at the desired host. The queue manager could be running, but the corresponding listener is not runnin...

IBM Websphere MQ interview Questions Part 5

MQ Series: - It is an IBM web sphere product which is evolved in 1990’s. MQ series does transportation from one point to other. It is an EAI tool (Middle ware) VERSIONS:-5.0, 5.1, 5.3, 6.0, 7.0(new version). The currently using version is 6.2 Note: – MQ series supports more than 35+ operating systems. It is platform Independent. For every OS we have different MQ series software’s. But the functionality of MQ series Default path for installing MQ series is:- C: programfiles\BM\clipse\SDK30 C: programfiles\IBM\WebsphereMQ After installation it will create a group and user. Some middleware technologies are Tibco, SAP XI. MQ series deals with two things, they are OBJECTS, SERVICES. In OBJECTS we have • QUEUES • CHANNELS • PROCESS • AUTHENTICATION • QUERY MANAGER. In SERVICES we have LISTENERS. Objects: – objects are used to handle the transactions with the help of services. QUEUE MANAGER maintains all the objects and services. QUEUE: – it is a database structure ...