May 20
Without Hardware Virtualization Sony Vaio Laptops Do Not Perform to Spec!
For the last 8 months I’ve been working almsot exclusively off my Sony Vaio SR140D – the laptop I purchased with the revenue from my book. And until recently I have had nothing but good things to say about it. That was until I needed to run a virtual OS on it. Turns out that for reasons no sane and logical person could ever figure out, Sony has disabled hardware virtualization on all their Vaio laptops – this in spite of full hardware support. Now I’m not a lawyer but since virtualization is supported by the expensive Intel processor and Sony has decided to disable this function in the BIOS without warning about this in the specs for the computer I think it’s a fair claim that the whole line of laptops do not perform to spec. And If this is not fixed very soon I urge all owners of Vaio laptops to return them for a full refund for this very reason!
Hardware Virtualization is Supported on a Sony Vaio…
When I started looking for a laptop back in the fall of 2008 I had a number of requirements: It had to be small (13.3” screen), light and powerful. I’m also a big proponent of future proofing so I did a lot of research on the capabilities of the processor to ensure that when I encountered unusual situations that required above-standard specs I would be able to get this from my laptop as well. As a result I narrowed my search down to laptops with the Intel Core 2 Duo P8400 or above processor. Not only were these processors based on the new 45nm technology making them faster and more energy efficient than their predecessors but they also had full support for 64bit operating systems and hardware virtualization. This last bit was paramount because as a beta tester I knew that somewhere down the line I would need to run virtual operating systems on my computer to do proper testing.
After much pining and tons of research I landed on the Sony Vaio VGN-SR140D – it was small, light, powerful, full featured and had the right processor. Before buying it I read all the specs on both Sony’s own site and in multiple reviews and store listings and saw nothing about hardware virtualization being disabled so I figured like any sane person would that this meant the computer would let me use the processor the way it was designed if and when the time came. To make double sure I ran the Intel Processor Identification Utility on a store model and as expected it stated that Intel Virtualization Technology was supported.
Done deal.
… But Sony Has Disabled Virtualization in the BIOS
Flash forward to May 2009 and I was in for a big and unpleasant surprise. Needing to run some tests on Expression Web 3 for my upcoming book I set up a virtual PC on my laptop to run XP inside my current OS. But when I tried to start the virtualization environment I got an error message saying that hardware virtualization was disabled in the BIOS and asking me to enable it. Sure thing I thought and spent the next hour trying to figure out how to access the BIOS on my laptop in the first place (tip to Vaio owners: To access the BIOS you have to hit F1 or F2 when the VAIO screen flashes).
Once I did get into the BIOS I was flabbergasted. The BIOS on this laptop is so stunted it is really not useful for anything but setting the system time and selecting a booting device. And nowhere was there any virtualization settings.
A quick search on Google told me I should have been more vigilant in my research: Users all over the world have reported for some time that Sony has stunted all their Vaio laptops and turned off hardware virtualization. And in spite of heroic efforts from hacks to full on BIOS rewrites users have had little to no success enabling the feature without risking killing their laptops in the process. But most surprisingly Sony has been beligerent in their refusal to even address the issue of why virtualization has been disabled and have provided zero information on whether this feature will be enabled in the future.
No Virtualization Means the Computer Does Not Perform to Specifications
So it turns out no Vaio laptop allows hardware virtualization in spite of full support for this feature from the processor. This is because Sony has deliberately (or ignorantly) disabled the feature. I can imagine two scenarios that may explain this bizarre situation:
Either the BIOS on the newer Vaios with the new processors that support hardware virtualization is left over from older versions with processors that did not support this technology and they simply forgot or were too lazy to update the BIOS.
Or Sony deliberately disabled the feature in some half-brained effort to force people who want the feature to pay top dollar for a more advanced model.
The problem with the latter is that to my knowledge not even the top-of-the-line Sony laptop allows for virtualization so my money is on the first option.
Regardless, any fair minded, logical and intelligent person will agree that when the hardware supports a feature and there is no explicit information warning that this feature has been disabled, one can assume that the feature will work properly. And since there is no information in the documentation or spec sheets for these computers stating that hardware virtualization has been disabled in spite of the processor supporting it, it is fair to say the computer is not performing to specifications.
Fix it or I’m Sending it Back!
Where does that leave us? The answer should be simple. Just like if you had bought a new 1080p HDTV only to discover that for whatever reason the manufacturer decided to turn off the colour feature leaving you with only black and white images without warning about this, a laptop that has hardware virtualization disabled in the BIOS in spite of hardware support without the customer being warned about this is by definition not performing to specifications and should be returned. That is unless the manufacturer gets its head screwed on straight and fixes the problem immediately.
I know for a fact that Sony is well aware of this problem but so far they have not lifted a finger to do anything about it. So here’s my ultimatum: I need hardware virtualization enabled on my Vaio VGN-SR140D on or before June 1st. If Sony has not coughed up a viable solution to this problem by then, I am taking my computer back to the store and demanding a full refund of the purchase price claiming the computer does not perform to specifications. This is unfortunate because I love my laptop and I’m having a hard time finding a replacement, but I will not stand for this kind of disrespect where customer service is concerned.
Why should you care? Windows 7 is just around the corner!
I’m sure a lot of people are reading this thinking “seriously dude, why do you care. It’s not like normal people need hardware virtualization anyway.” Well, here’s some news for you and for Sony: When Windows 7 rolls out before the end of this year, the support calls from Vaio owners frustrated with not being able to turn on virtualization are going to go through the roof. Why? Because Windows 7 comes packaged with Virtual XP – an application that lets everyone run a fully working version of the old operating system within Windows 7 thus letting them use older applications that don’t run properly in Vista and Windows 7 environments. This is a huge and revolutionary feature in Windows 7 and a big selling point and unless Sony gets their act together there’s going to be a long line of people wanting to return their laptops come December.
The countdown starts NOW!
Feb 02
Windows 7 Beta Report Part 1: Bugs
I had Windows 7 installed on my trusted Vaio SR140D laptop a couple of weekends ago and have been running it on a near constant basis since. Now after 3 weeks or so I have compiled a list of bugs and bonuses that should be helpful to the development team as well as users who are curious about this new operating system.
Overall I have to say Windows 7 has been a revelation (of the good kind that is). People say that Microsoft get things right every second release of something major, and since Windows 7 can be said to be a second coming of Vista the saying rings true. Windows 7 sees vast improvements in everything from usability to functionality to performance and puts a final nail in the coffin of most of the negatives the naysayers and Mac fanatics have been riding so hard on for the last two years.
But I’m getting ahead of myself here. Because I know you came for the trash talk I’m going to start with the bugs, ‘cus there are some nasty ones. My Windows 7 Bonuses article with the many reasons why Windows 7 is the best OS I have ever worked with will be up some time next week.
System Fatal Program Crashes
Yes, you read that right; system fatal program crashes. In the first week alone my computer crashed upwards of 40 times from this error. Bizarrely that number has gone down to almost zero in this last week but still, there is something horribly wrong going on here.
Although I can’t reproduce the problem at will, it is obviously related to files being written to drives, both internal and external: When saving one or multiple files from different applications, one or more of the applications will freeze, display “Not Responding” in the window header and a fade effect is applied. There is no way of turning the program off when this happens; even opening Task Manager, selecting the process and hitting Delete does not kill the application and you are left with a dead program locking up your computer. This problem is cascading so once it has occurred and you attempt to save another file from a different program, that one will also stall and so on.
But the problem doesn’t end there: Because Windows 7 is unable to terminate the application even from Task Manager, it is impossible to shut down or restart the operating system by normal means. When you try to shut it down, the Open Applications window will appear listing the stalled applications with and you are asked if you want to shut them down. But no matter what you try, the applications just won’t shut down and the computer is left in an infinite loop. At the end the only way of resolving the issue is to do a manual restart by holding down the power button for 8 seconds.
And now for the really bizarre part: As I said, this problem appears when you try to save a file. The application stalls almost immediately after the saving process has started so one would think the file was never saved, right? Wrong! For some inexplicable reason, once the computer has been restarted you will find the file that caused all the problems to begin with in the location where you saved it. And it works the way it is supposed to.
At first I thought that the problem was caused by some sort of drive writing conflict but that theory was shelved when I discovered that the files were actually written properly. My new hypotheses is that the problem is a broken communication between Windows 7 and the applications as to the writing process itself; a checksum error or something along those lines. That still wouldn’t explain why the applications stall so completely nor why Windows 7 is incapable of shutting them down, but it is a start.
The system fatal program crash has been triggered by both Windows 7 native and 3rd party applications including these ones: Windows 7 native zip extractor, IE 8, FireFox, Expression Web 2, PhotoShop CS2, Illustrator CS2, Notepad, Notepad ++, Opera and FileZilla. In the case of the zip extractor the crash occurred multiple times when I tried to drag-and-drop files out of an archive and onto my desktop. As for the browsers the crash occurred when I tried to save files from the web.
Caveats
Note that the system fatal program crash only happens during write-to-disk operations. I have managed to crash several programs for other reasons but in all the other cases the program has either shut down properly on its own or been possible to shut down through the Task Manager. Also note that I have been unable to find any similar references to this specific problem anywhere else on the web. However I highly doubt the problem is caused by my computer itself – I installed Windows 7 on an empty hard drive and the computer is only or 5 months old and running perfectly – and there is no possible way I’m the only one experiencing it. And even if I was, there is a good chance someone else will run into it further down the line and since none of the conventional shut down techniques work once it rears its ugly head I foresee true panic unfolding among the Windows 7 using masses.
First Start Program Incompatibilities
The second major problem I’ve run into is a transient one: Upon first installation a lot of programs do not run properly. I’ve installed a huge pile of applications under Windows 7 and for the most part (often surprisingly) they work without a hitch. But in some cases things go badly wrong until I reboot the computer. The most recent example is when I installed Camtasia from TechSmith yesterday. Upon installation the application seems to run fine, but when I stopped my screen recording and tried to start it again, the actual recorder portion of the program stalled. A warning windows opened asking if the application terminated properly and when I said no, the recorder shut down wihtout shutting down Camtasia in the process. I am guessing this is because Camtasia actually runs several different sub-programs and the crash only occurred in the recorder sub-program. Anyway, the recorder shut down and I had to restart it. After experiencing the exact same problem 5 times in a row I restarted the computer and after that everything worked perfectly.
This problem also happened when I installed PhotoShop and Illustrator CS2, FileZilla and some other applications. The problem seems to be rooted in registry rewrites or some other element that runs in the “bottom” of the operating system and needs to be restarted to be reset. Because it is transient and is easily resolved by restarting the computer it is not a major problem like the one listed above but it is still hugely annoying.
A solution?
If I’m right (and I think I am) the problem is caused by a registry rewrite or something similar that unlike Vista, Windows 7 requires a restart to apply. If that’s the case it shouldn’t be too hard to create some form of conditional operation within Windows 7 that tracks such changes and suggests that the user restarts the computer for the newly installed program to run properly.
Compatibility Mode Annoyances
As I mentioned before I am running PhotoShop and Illustrator CS2 on this computer (dont’ ask why – long story). If you’ve played with these programs under Vista you probably know that there are some crazy and annoying compatibility issues (though they are nothing like the ones in Premiere Pro CS2 which pretty much becomes nonfunctional under Vista). Fortunately the wise minds at Microsoft foresaw this problem and created something called Compatibility Mode where you can set applications to run as if they were running under older operating systems like Windows XP SP1, SP2 or even older ones like Windows 98 or 95. And this worked great. In Vista.
In Windows 7 on the other hand things get a bit annoying. Because of the Vista problems with CS2, I set PhotoShop and Illustrator to run in Compatibility Mode for XP. But when I did, Windows 7 started treating the applications as unwanted bastard step children. First off, the otherwise wonderful icons displayed in the Start menu and the new and vastely improved task par are branded with an ugly User Account Control sheild warning you that something is very wrong. Seccondly, when you open the application, a User Account Control warning appears saying that an application from an unknown publisher is trying to run on your computer and asks if you still want it to run. This is totally rediculous because if you run the same program under either Vista Compatibility Mode or without Compatibility Mode, that warning doesn’t appear. Finally, in XP Compatibility Mode the splash screen at startup is totally mangled and ends up looking like some poorly hacked knock off. This of course is purely aesthetic but it still bugs me.
Yes, I know you can turn User Account Control off etc etc but the majority of user won’t do that. And even if you did, it still wouldn’t explain why the application while running under Compatibility Mode all of a sudden becomes a potentially malicious piece of software from an unknown publisher. That’s just plain rubbish and it should be fixed.
Crazy Window Dither Effect
This last bug is one that occurred twice, but I have not been able to reproduce it since then. It is hard to describe but the screen grab above pretty much says it all: The top and bottom bars of the windows are dithered and screwed up by horizontal lines that spill out to the sides. The effect is distracting and makes it hard to work with the windows but had no actual effects on the window functionality. Click here or on the image to see the full screen grab with multiple busted windows.
This dither effect appeared during the installation of Adobe Reader and also appeared after the reboot I did to get rid of it (which is when I took the screengrab). For a while I thought this was some sort of permanent screen driver glitch but after another reboot everything was back to normal. Very weird.
That really is all there is to it. Apart from the bugs listed above, all of which should must be fixed before the final release of the new operating system, Windows 7 is running flawlessly on my laptop and I am so content with it I am considering wiping the Vista partition on the machine to free up more space for fun stuff work.
