According to MSDN : On Windows 7 and on Windows Server 2008 R2 with the Wireless LAN Service installed, the operating system installs a virtual device if a Hosted Network capable wireless adapter is present on the machine. This virtual device normally shows up in the "Network Connections Folder" as "Wireless Network Connection 2" with a Device Name of "Microsoft Virtual WiFi Miniport adapter" if the computer has a single wireless network adapter. This virtual device is used exclusively for performing software access point (SoftAP) connections. The lifetime of this virtual device is tied to the physical wireless adapter. If the physical wireless adapter is disabled, this virtual device will be removed as well. On Windows 7, there's no UI to start or stop SoftAP....

I learned this the hard way. Apache is set up and running fine. I can open the "It works!" page in a local browser. I added the rules to the Windows Firewall to allow incoming connection from both Private and Public networks. But when I tried to access the default Apache page from another PC, timeout! I removed the rules, added them back again, double checked, still timeout! I then removed the firewall rules and used Windows 7 troubleshooting tool to fix the problem. It correctly identified and "fixed" the problem. But I still get timeout! Finally I got tired of all this and hit the Power button. It worked! Everything worked out after reboot! Lesson learned: Windows 7 is still Windows.

Steps to configure SSL for Apache HTTPD server on Windows: In Apache2.2/conf/httpd.conf , load mod_ssl and include httpd-ssl.conf : LoadModule ssl_module modules/mod_ssl.so ... In Apache2.2/conf/extra/httpd-ssl.conf , make sure the paths for the cert files point to the cert and key you want to use: # Server Certificate: # Point SSLCertificat... Start up Apache. If it fails, use the command line to see what the error is. There won't be any log in error.log if there are errors in the conf files: C:\Program Files (x86)\Apache Software Foundation\... I corrected the previous error by using the alternative line for SSLSessionCache : # Inter-Process Session Cache: # Configure ...

Microsoft provides free downloadable Windows images to support IE browser compatibility testing, just google Internet Explorer Application Compatibility VPC Image . These VMs run on Microsoft's Windows Virtual PC . According to MS: You can technically have a base image which never expires although you will never be able to permanently save any changes on these images for longer than 90 days.

IE9 has pretty good developer tools support - similar to that of Firebug, though not as good (under the Tools icon pick F12 Developer Tools , or hit F12 directly.). It also allows you to test compatibility with older browsers like IE8: Bring up Developer Tools with F12. pick IE8 in Browser Mode and IE8 standards in Document Mode .

1. Install windows resource kit . 2. Install srvany as a service: C:\tools\putty>instsrv ssh_tunnel "C:\Program File... 3. Edit the following registry template to suite your environment: Windows Registry Editor Version 5.00 [H... 4. Import the registry entry. 5. Start the service with "net start ssh_tunnel" or from the services applet. You may choose to use a batch file for srvany (instead of plink.exe ), but you won't be able to shut down the tunnel when you stop the service. Also, if the Windows SYSTEM user cannot see the host key for SSH connection, the tunnel cannot be established.

mysql> show character set; +----------+--------...

Focus on the checkbox. press the Space bar!

Characters \/:*?"<>| are forbidden in Windows file names. For Python, the effect of using a forbidden character in the file name is undetermined. In the following session a file named mytest can be seen from the Windows Explorer, which contains 0 bytes - as confirmed by the read back in the session. But if you open the file with the invalid file name used to create the file (i.e., mytest: 1.txt ), you get the original contents. C:\>python Python 2.7 (r27:82525, Jul 4 2010, ...

There seems to be an upper limit to the heap size that you can allocate to the JVM on 32bit Windows. Although the total addressable memory space is 4G, only 2G is available to applications (the other 2G reserved by the OS). Out of the 2G used for applications, you also need to load any static or dynamic libraries, which further pushes down the actual limit to about 1.5-1.8G. Below are some references: 1. How to get (almost) 3 GB heap on Windows! 2. maximum heap size limitations on Windows 32-bit