Skip to main content

Windows 7(RC): first impressions

Finally there is a release candidate for Windows 7. I had been waiting for it for last few months.

My stint with it's predecessor, Vista though spread over just 7 months, had not gone smooth. I had to face a lot of issues as others did. The issue that irritated me the most is the access related confirmation message that often popped up when I had to start any software installation or run some applications like Daemon Tools etc. Vista is slow in starting up, often shows up some unwanted permission related messages when one tries to write/modify anything inside the directories like Progam Files/Windows. The Dreamscene component that runs a video as a desktop background often works for few minutes before generating errors. All these facts were forcing me to think for an alternative like a Windows XP installation in my laptop, but as it is a XPS M1530, Dell does not provide the drivers for XP. There are some unofficial articles available on internet regarding XP installation in XPS M1530, but I din't want to take any chance. By that time, there was already beta version of Windows 7, Microsoft's rework on Vista available. So, I started reading articles and user reviews on it. As stated by Microsoft, Windows 7 will issue some problems of Vista and it's totally compatible with Vista based systems. I also came to know that there would be a release candidate available in next few days, so I opted to wait for RC than trying out one of the beta versions available over torrent which may be malicious program infected! So, this month Microsoft has released RC for their latest offering. I downloaded a copy of it from Microsoft TechNet, download was pretty faster, took around 25 mins of time for 2.35GB iso file. They provided me with a product key which will keep the RC active till May 31, 2010. But starting from March 1, 2010 there will be bi-hourly shutdowns and the system will start notifying two weeks before this process begins.

Windows 7 can't be termed as a next generation OS as it's built on Vista and issues some core problems of Vista. It has to work on lesser amount of RAM, boost up the startup time etc. So, with these claimed features and with some of my own expectations, I have started experimenting with Windows 7. To save time, I have upgraded Vista installation to Windows 7. It showed me a confirmation message as there were 3 installed applications which are incompatible with Windows 7. I choose to continue. It was really a hassle free procedure as the installation itself took care of all the file/registry transfer to temporary places and then reinstating them to their actual locations etc. The process was little bit time consuming as I had a huge windows user folder with around 80GB of data. Finally, the installation was over. So far so good, there was not a single hiccup. The startup time is less compared to earlier Vista installation. All the files & folders of my Vista user folder are still in the same locations. All the applications are working properly except antivirus program, Daemon Tools, Dell Support Center. I had to go for a beta version of Mcafee Total Protection. But there were no alternatives for the other two softwares. The user interface remains almost same except the redesigned taskbar. Dreamscene is totally removed. Windows 7 has a new version of Windows Media Player, it's version 12. It has got a claimed native support for playing blue-ray discs. I don't have any blue-way drive, so can't test this feature. The application loading time is also significantly faster, I have witnessed it with Adobe applications mostly.

But the problem of displaying unwanted confirmation messages while installing a software or writing/modifying particular folders remains still the same and annoying. As my account already has the administrator level access, then why is this confirmation required? I wish that Mircosoft will address this problem in the final release. Overall, it's a good experience, just waiting for the independant software vendors to upgrade their offerings to be compitable with Windows 7.

Comments

Anonymous said…
hello... hapi blogging... have a nice day! just visiting here....

Popular posts from this blog

Working in India

The day I started working in SRA India(Indian arm of Japan's Software Research Associates, Inc ), I never thought that I world become an onsite team member in just one and half years. Because, the branch was very small & it was very illogical for a novice like me to think of an onsite tour that time. But the fact was that they would make you do your work in almost Japanese style. The very first day I started coding in SRA India, I was told that the Japanese were simply put - perfectionists. This simple word had a very large inner meaning. The code that you wrote should be totally bug free, robust, modifiable without introducing regression etc. The first project I was assigned to, it took a hell lot days to prepare only the detailed design(Java Doc) for a very tiny function, every molecular level detail was described on that. But somehow I made myself adjusted to such work environment. My performance was good in my batch. And in one day, one of my managers told me of an onsite a...

Java collection series - miscellaneous

Java Vector is a legacy class. And it is significantly faster in comparison to a list obtained through Collections.synchronizedList(). Vector has loads of legacy operations and hence the manipulations in Vector needs to be done through the List interface, otherwise you won't be able to replace the implementation at a later time. Arrays.asList() is better choice if the list is of fixed size and any kind of size mutation of the collection results in UnsupportedOperationException. The underlying array is updated whenever the list is updated (or vice-versa), but the array reference isn't retained. Collections.nCopies() is another convenient mini-implementation which can be useful in two ways - initialize a newly created list with n null values (need not be only null values) -  new ArrayList (Collections.nCopies(1000, (Type)null)  grow an existing list -  lovablePets.addAll(Collections.nCopies(69, "fruit bat")) Collections.singleton()/Collectio...

DB transaction ACID properties

DB transaction is a combination of different operations. If not performed in a proper manner, different transactions working on the same data at the same time may leave the data in corrupted state, effecting the application. In this article, I am going to illustrate DB transaction ACID properties through an example of money transfer application between two different accounts A and B. To begin with, lets suppose that accounts A and B both have initial balance of $100. ACID stands for Atomicity , Consistency , Isolation and Durability . Let's try to understand these one by one. Atomicity : This is the property that mandates that if a transaction is started, either all the operations which are part of the transaction need to be completed by end of the transaction completion as a single unit of work or none of the operations needs to be completed. It is maintained by transaction management component. If a debit of $10 is made from account A, then the corresponding credit of $10 al...