I'm running Windows 11 for Arm under Parallels for M1 on my M1 Mac computer. I'm having a text scaling issue with a program. Their tech support suggests adjusting the text scaling in Windows setting. System > Display > Custom scaling includes a warning about this setting and offers a way to turn it off. However, after a restart it persists. Changing the scale to 100 (from the 200 default) doesn't stick after a restart. Searching the internet hasn't provide solution as yet.
Any suggestions? Thanks
Related
I'm developing with MONGODB service & Express server running and React app compiling on my Windows 10 with 4GB RAM (HDD).
These are my optimization setups to improve my hardware performance, I guess some of them are now automatically revised by Windows itself.
My virtualization is enabled.
Most tips on https://youtu.be/nVy4GAtkh7Q including to Disable Privacy Settings, High Performance Power Settings and to Disable Indexing, excluding to Disable Firewall and the execution of any program.
I have used: https://github.com/10se1ucgo/DisableWinTracking
I'm now using Opera since it's more lighter than Chrome.
I'm disabling Windows Defender while my local servers are running.
Setups that I'm not preferred to use:
Not preferred to use Chrome 'cause my React app's tab is sometimes freezing.
Not to debloat Windows with https://github.com/W4RH4WK/Debloat-Windows-10 since it have a possibility to mess up something.
Not to permanently deactivate Windows Defender.
Not to disable Opera hardware acceleration 'cause the 3D graphics without acceleration is like in slow mo.
Current issues:
Opera is sometimes crashing (still better than freezing).
VS Code still experiencing lag.
Is there anything that I can do to improve the performance of my 4GB (HDD) hardware (while I'm in short to buy a powerful hardware)? Is there a recommended setup for MERN stack development?
I have a very weird bug that I just can't understand.
I am currently using the WPFMediaKit library in one of my programs.
When using the library in a near empty new "demo" wpf solution, the image from the USB Camera source is rendered perfectly to the MediaCaptureElement class.
However, using a more complex solution, the same library (without changes), the frame gets rendered black. I can see there is connection to the camera and everything goes well, DirectShow graph is built normally and everything just looks fine, besides the black frames. I can even open the camera properties and see it pushing out frames as usual.
Also, this only happens on Dell E6540 (With an AMD and Intel HD gpu) if it's Windows 7. Windows 8/10 work fine. Have tried a lot of drivers nothing seems to change the output.
I have no clue what to do or what to try.
After many hours and just after deciding to post this question, I found the answer.
The more complex solution, under the AMD Settings application was set to use "High Performance" mode, this mode was automatically enabled on Windows 7 for some reason. Disabling that and setting it to "none" or "lower power" fixed the issue.
Doesn't change the fact that there is an issue with laptops with dedicated AMD GPUs, probably something to do with DirectX/Direct3D which is used to render the frames.
Observed behaviour (everything here is on Windows 10):
I run Visual Studio (tried 13 and 15, both behave the same) logged into user A
After starting up, VS takes virtually no CPU time (<1%)
I log into user B, without signing out of A
VS imediately starts using A LOT of CPU time (~25% on my 4 cores with hyper threading)
I can go back and forth between A and B, and it goes back and forth between low and high CPU usage
This is all without any projects or files opened, though it also happens in that case.
I noticed this because I was originally investigating similar behaviour of a WPF application (after a user reported this issue).
While trying to isolate the problem, I found that even a completely new WPF project, with just a single empty window, behaves exactly the same (whether or not run through Visual Studio).
Through profiling and debugging I found that the app seems to spend a huge amount of time handling windows messages.
Specifically I found that it seems to be almost exclusively WM_PAINT messages (we are talking easily hundreds or thousands of messages per second - as many as the CPU can handle it seems).
No other programs I have running (chrome, skype, sublime text, ..) behaves this way.
Has anybody else seen this kind of behaviour?
And/or any ideas what could cause this, or how I could investigate this further?
Naturally, I cannot fix Visual Studio (unless the problem is with my setup somehow) but I hope there is something I can do about my WPF application.
As per Hans Passant's suggestion in the comments, I reported this problem to Microsoft here:
http://connect.microsoft.com/VisualStudio/feedback/details/2390593/wpf-apps-use-a-lot-of-cpu-time-when-logged-into-different-user
As it turns out this indeed seems to have been a bug in WPF, which is fixed in the current version of Windows 10 (probably specifically since the Anniversary Update (version 1607)).
Hence the solution: Make sure to update your OS.
my windows form size is 1305,617.
When I remote login into my dev machine the windows form size gets cut down to 1036,617 and I am unable to widen it beyond 1036. I have tried with a bigger monitor but same issue
Any idea why?? and how to fix it?
I am using framework 2.0 C#
So I increased the resolution of the monitor I was using to RDP and that fixed the problem.
I've got a user running my WPF app on a Mac with VMWare, In Win 7, and most of the text in the app is unreadable. I've ran this on my own VMWare-MacBook pro setup, and it seems to be fine. Here's a screenshot from the user:
http://i.stack.imgur.com/QCzwn.png
The font for the missing or illegible text I expect should be Segoe UI, as is the text for the words "Combat Manager" that appear in a larger size on the screen, although I have not explicitly set the font face.
Any idea what the cause might be?
When we had this and other issues with some of our test staff, it was because they had the memory settings turned too low for the video emulation to handle WPF. VMWare defaults to somewhere around 256 MB for total RAM for the guest OS. Try turning that up to 2 GB or higher. You can also tinker with the video settings for the VM. In addition, check the font size and DPI settings on the guest OS.
Update to the latest VMWare Workstation software and install the latest VMWare tools. There was a version of 7.0.x that had this issue. In our case you couldn't see the text at all.
My VMWare version: 7.1.4
OS: Windows 7 x86
Had the same issue, the solution for me was to update the WMVare Tools to the latest version (as of today). (VMware Tools version 8.4.6)