My setup for my day job these days is a Surface Pro 4 and either an LG 34UC87M-B or a Dell P2715Q monitor, depending on where I'm working. This is a fantastic setup, but some applications have trouble dealing with the high pixel density and don't scale appropriately.
One case in point is Skype for Business. For some reason it scales correctly as I move between the Surface screen and the external monitor when I use the Dell, but on the LG monitor Skype is either massive on the external monitor, or tiny on the Surface screen.
After a big of digging around I came across a solution that worked for me, which is to change a setting in Skype's manifest file (who knew there was one?). On my machine the file is here:
C:\Program Files\Microsoft Office\Office16\LYNC.EXE.MANIFEST
And the setting in question is this:
<dpiAware>True/PM</dpiAware>
<dpiAware>True/PM</dpiAware>
Which I changed to this:
<dpiAware>False/PM</dpiAware>
Note that you'll probably have to edit the file as administrator in order to be able to save it.
Once I made that change, saved the file, and restarted Skype, it now scales correctly for both the Surface screen and the external LG monitor.
Comments
Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide
Make a new DWORD named PreferExternalManifest and set the value to 1
1. Change the LYNC.EXE.MANIFEST file, set to True (I took out the /PM bit)
2. In regedit, find the lync.exe HIGHDPIAWARE key in HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers and delete it.
3. Change the permissions on HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers so your account doesn't have write access. This way the key won't get rewritten.
4. Restart Skype
Found the solution here: https://www.skypefeedback.com/forums/299913-generally-available/suggestions/9572103-skype-for-business-in-latest-2016-preview-still-no
1. Make the change in the Lync manifest as stated above. (Change to False)
2. Make the change to the registry as stated above.
Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide
Make a new DWORD named PreferExternalManifest and set the value to 1
Thank you both for these steps. It WORKED!
Applying both the solutions worked.
For read more information:
http://www.virusspywaredesinstalacion.com
http://www.comerimuoverevirus.com
http://www.deinstallierenwindowsmalware.com
http://www.freemalware-removal.com
PREPARE FOR THE WORST...
Market change over time. A well designed system starts with trend analysis to stay away from potentially losing trades. There are two problems of how a Forex system recognizes the trend.
PROBLEM: FALSE "STRONG TREND" INDICATION.
The system responds only to immediate price action. An explosive price movement that is usually the result of news release is tempting people to jump in and make a profit. It looks like a "strong trend", but what usually happens next is a hard fall.
To avoid falling into this trap, check for the SOLUTION to find a REAL trend:
SECOND PROBLEM: TREND RELIABILITY
Most systems use various indicators to determine the trend. Actually, there is nothing bad about using indicators. One Simply Moving Average can do the job. The problem comes with the question: "Is the market trending NOW?" Whether the market is trending or not trending is not like black and white. The correct question is: "How well the market is trending?"
And here we have something called TREND RELIABILITY.
Trends exist and they can be traded up and down for a profit. You have to focus only on the most reliable market trends. "Forex Trendy" is a software solution to find the BEST trending currency pairs, time frames and compute the trend reliability for each Forex chart:
After the basic settings and deploying in IIS getting this error. Any help?
HTTP Error 500.0 - Internal Server Error
scriptProcessor could not be found in application configuration
Most likely causes:
IIS received the request; however, an internal error occurred during the processing of the request. The root cause of this error depends on which module handles the request and what was happening in the worker process when this error occurred.
IIS was not able to access the web.config file for the Web site or application. This can occur if the NTFS permissions are set incorrectly.
IIS was not able to process configuration for the Web site or application.
The authenticated user does not have permission to use this DLL.
The request is mapped to a managed handler but the .NET Extensibility Feature is not installed.
Things you can try:
Ensure that the NTFS permissions for the web.config file are correct and allow access to the Web server's machine account.
Check the event logs to see if any additional information was logged.
Verify the permissions for the DLL.
Install the .NET Extensibility feature if the request is mapped to a managed handler.
Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.
Detailed Error Information:
Module FastCgiModule
Notification ExecuteRequestHandler
Handler DictionaryEditor Handler
Error Code 0x80070585
Requested URL http://localhost:8009/
Physical Path C:\a_source\DictionaryEditor\DictionaryEditor
Logon Method Anonymous
Logon User Anonymous
More Information:
This error means that there was a problem while processing the request. The request was received by the Web server, but during processing a fatal error occurred, causing the 500 error.
View more information »
Microsoft Knowledge Base Articles:
294807