sedrosken
Florida Man
I have to scale 1080p to 130ish to keep it readable at 14", and I've found a lot of my clients get mileage out of the scaling due to similarly (though usually to a worse degree) poor vision.
I have to scale 1080p to 130ish to keep it readable at 14", and I've found a lot of my clients get mileage out of the scaling due to similarly (though usually to a worse degree) poor vision.
Doesn't the scale go up in steps of 25 starting at 100? How are you setting it at 130? Unless it works differently on laptops.I have to scale 1080p to 130ish to keep it readable at 14", and I've found a lot of my clients get mileage out of the scaling due to similarly (though usually to a worse degree) poor vision.
Not me, once I had enough money to choose I started running 40"+ monitors. The last few have been 42" 4k with 150% scale. Before that I ran for a while with 2x 49" 5k ultrawide stacked vertically, still at 150%. That setup was interesting, but not as useful for monotasking. Now I'm considering a 16-21" 4k secondary for reference material.Sounds like dd.
You can set custom scaling if you want. It's a better idea than using nonstandard screen resolutions.
Do you guys use your systems with Memory Integrity on or off?
Fun fact, on Windows 11 Home, if you disable location services in settings (during the initial setup), you cannot manually set the timezone of the system via the Settings UI. (It's greyed out). Setting the timezone is now tied to enablement of location services. There are two workarounds:
- User powershell to set the time zone (see Get-TimeZone and Set-TimeZone).
- Via Settings UI, Enable location services enabling all apps, set a manual location, wait 20 secs for the timezone to change to the zone appropriate for the location automatically, and then disable location services. This will fix the timezone.