You are here

Microsoft

NVIDIA drivers and multi-monitor setups

nvidiaSince July 2015, my GeForce Experience has become somewhat of a nightmare.

I'm among a few dozen people who are suffering from several issues with their multi-monitor setup with the latest NVIDIA drivers and the only solution so far seems to be to stick to driver version 353.62 which was released way back on the 29th of July 2015.

No matter which driver version I tried, every version any newer than the previously mentioned version 353.62 would break my monitor setup in Windows 10 in one way or another on a NVIDIA GeForce GTX TITAN X.

These problems include:

  • window positions resetting to the primary monitor when waking up from standby mode
  • monitor IDs swapping between primary and secondary monitor on each boot
  • Windows crashing with blue screen of death

TYPO3 Multi-Domain-Hosting on IIS with wildcard subdomains

TYPO3Ever wanted to use wildcard subdomains with Microsoft Internet Information Services? You might have realized by now that this is actually not possible using only IIS as neither IIS 6 nor IIS 7 support the *.example.com notation.

The key to success is ISAPI_Rewrite, a third party ISAPI extension that brings mod_rewrite functionality to IIS. The latest version ISAPI_Rewrite 3 is compatible with Apache's mod_rewrite URL rewriting module which means that you can use the same rules you would use when hosting on Apache 2.

ISAPI_Rewrite Lite is available for free, but usually requires a more complex configuration as it does not support parsing of .htaccess files as the full version does. In this case, it doesn't matter since the following directions can either be placed inside the global configuration or inside an .htaccess file in your IIS default web.

RewriteCond %{HTTP_HOST} ^(.+)\.example\.com$ [NC]
RewriteRule (.*) http://www.example.com/$1 [P,NC,QSA]

This uses the built-in ISAPI_Rewrite proxy to redirect all subdomains of example.com transparently to www.example.com. Your visitor will still see subdomain.example.com in his browser's address bar, just as if the subdomain was configured in the web that hosts www.example.com.

Now, for serving different contents from TYPO3, you need to tweak your configuration to make TYPO3 handle the HTTP_FORWARDED_HOST header sent by ISAPI_Rewrite.

To do this, you have to add the following lines to localconf.php:

$TYPO3_CONF_VARS['SYS']['reverseProxyIP'] = 'YOUR_SERVER_IP';
$TYPO3_CONF_VARS['SYS']['reverseProxyHeaderMultiValue'] = 'last';

This allows TYPO3 to handle proxy requests by ISAPI_Rewrite correctly.

You have to replace "YOUR_SERVER_IP" in the example above with the IP address of the server that is running ISAPI_Rewrite. This should normally be the IP address of the server that hosts example.com.

Once you did that, you can set up domains in TYPO3 as usual and ISAPI_Rewrite will take care of all the rest. No additional configuration is required.

Related Link: ISAPI_Rewrite 3

Games for Windows LIVE "Code: 80048823" solved

Games for Windows LIVEIf you are in the same situation like I was for a few months now and you get a "Code: 80048823" error when trying to sign in to Games for Windows LIVE on your Windows PC with your correct username and password, this article might contain the solution you are looking for.

If you were wise enough to choose a long (> 10 characters) and cryptic password so script kiddies can't just take over your LIVE account, Microsoft's Games for Windows LIVE client simply can't handle your password and will give you meaningless error messages.

Login to your LIVE account through https://login.live.com and change your password to something that is no longer than 10 characters.

There you go. That's it. You should be able to login again.

Asking for credit card information while not supporting secure passwords. Way to go Microsoft.

Subscribe to RSS - Microsoft