VMware vSphere Client & VMware Converter Plugin on Windows 7
I am frustrated with VMware like many others are using the vSphere client on Windows 7 or Windows 2008 R2 due to the fact that the client does not work without a hack. I am not going to go over the fix in this post, the information can be found in KB1011329. I was actually at a client a few weeks ago while working on an ESX 3.0 host and needed my client but was unable to use it on my laptop due to this issue. This forced me to me waste time attempting to install the older client on two of their servers which would not work. I ended up using the web interface after wasting much time with the client.
But I digress, after following the steps in KB1011329 the I received the following error.
Failed to load shared library in C:\Program Files\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\ssleay32.dll:1260
I tried KB1005446 in an attempt to resolve the issue, however after making the changes I was still getting the error. Since having this plug-in is not critical for me I uninstalled it and was able to launch my vSphere client.
I am disappointed in VMware and the fact that they have not released an official fix for this. Windows 7 has been coming for a long time now through the beta, RC, RTM, and now officially out. The fact that they either were unaware of this problem or simply have chose not release an update to resolve the issue is surprising to say the least.
Update: Brian commented that this issue has been fixed in vCenter 4.0 Update 1 so be sure to upgrade for that and all the other fixes/enhancements.
Ext2Fsd BAD_POOL_HEADER BSOD on Windows 7
I have been using Ext2Fsd for a long time, everything was fine while using Vista. I decided to upgrade to Windows 7 after the release candidate was made available. For the most part everything was fine, until I started browsing my ext3 /home partition where I keep all my data. Sometimes I would get lucky and be able to open the file I wanted, however in most cases I was met with a BSOD saying something about a BAD_POOL_HEADER.
I am not a programmer, in fact I am probably one of the worst candidates for a programmer, I don't like it either. Thankfully for me though a gentleman named Bo Brantén developed a version that eliminates this issue. He describes the issue on the Ext2Fsd project page as a response to the posting of version 0.48. Apparently the issue was caused when the driver referenced memory after it was freed.
The updated version can be downloaded from the link below. Replace your ext2fsd.sys in C:\Windows\System32\drivers with the updated version and reboot.