Jump to content

UCyborg

Platinum Sponsor
  • Posts

    2,598
  • Joined

  • Last visited

  • Days Won

    28
  • Donations

    100.00 USD 
  • Country

    Slovenia

Posts posted by UCyborg

  1. @innuendo33 @MrGRiM

    Thank you for your answers. The new "feature" also has a bug that when you right-click on the search bar, you don't get the usual context menu. Works fine once reverted.

    Can always go back to 1809 and try some newer build in the future. I'm mostly interested in bug fixes for the existent features.

  2. The audio just died on my desktop recently.

    This guy apparently stumbled on the same issue:

    https://community.spiceworks.com/topic/2238479-windows-10-no-audio-output-device-is-installed

    Though the circumstances are a bit different. Only one thing is certain; when some state gets messed up on Windows, one is very lucky to be able to find the cure that doesn't involve reinstall.

    So things are quiet now. I wonder if trying to debug the audio service would reveal anything. Deleting stuff under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\MMDevices (Capture and Render under Audio) doesn't help, though the entries reappear when getting Device Manager to detect and add the devices again. I deleted them after turning off Windows Audio Endpoint Builder and Windows Audio services.

  3. Microsoft's documentation on selecting a device in Direct3D 9

    The 2nd step of needed tasks for a Direct3D application running in a window:

    Quote

    It enumerates adapters, looking for the adapter whose monitor covers the client area. If the client area is owned by more than one adapter, then the application can choose to drive each adapter independently, or to drive a single adapter and have Direct3D transfer pixels from one device to another at presentation. The application can also disregard two preceding steps and use the D3DADAPTER_DEFAULT adapter. Note that this might result in slower operation when the window is placed on a secondary monitor.

    I haven't seen the highlighted effect on newer systems (Win7+, haven't tested Vista), but on XP, even running Serpent browser on the second screen with a video playing made things so bad that even the mouse cursor started lagging; that and the general choppiness. Hacking xul.dll to make it select a different adapter restores the performance on the second screen, but that only helps if one prefers to have it on the particular screen exclusively.

    Similar with Direct3D games running in a window, turn on the FPS display or some 3rd party overlay displaying it if game doesn't have its own. When on main screen, everything is fine, move it to another screen; bam, FPS count drops, CPU usage goes up.

  4. On 5/25/2019 at 1:38 AM, mirh said:

    Friendly reminder that wined3d is just slow because it sucks with buffer management, not because opengl has any particular unholy fault.

    I wasn't implying that there was anything wrong with OpenGL, but there's not much difference in the end for the end user; one party messes up and that's it.

    On 5/25/2019 at 1:38 AM, mirh said:

    p.s. I was under the impression there was some kind of vulkan driver for nvidia cards?

    Someone compiled the runtime libraries for XP, but the actual implementation in the driver is missing. Vulkan 1.1 is out since March 2018, when no company is writing graphics drivers for XP anymore.

  5. Updated from 17763.615 to 17763.832 and after booting into it I noticed several security settings were changed:

    • Password must meet complexity requirements: Disabled -> Enabled
    • Administrator and Guest accounts have been enabled
    • Devices: Prevent users from installing printer drivers when connecting to shared printers: Disabled -> Enabled
    • Interactive logon: Do not require CTRL+ALT+DEL: Not Defined -> Disabled
    • Shutdown: Allow system to be shut down without having to log on (this one might have been changed too, not sure)

    Users group has lost the following rights:

    • Change the time zone
    • Remove computer from docking station
    • Shut down the system

    Guest used to be present in the following rights assignments:

    • Allow log on locally
    • Deny log on locally (these two are conflicting, so I suppose the result is the same in the end after change)
    • Deny access to this computer from the network

    This list is from my memory. Should cover at least 75% changes, I didn't note them down. All settings can be found by launching secpol.msc and navigating to Account Policies and Local Policies.

    I removed the old updates in from recovery environment with DISM in reverse order in which they were installed, including SSU update (have to modify some *.mum files to get it removed) and then installed the current ones.

    Did I do something wrong or do recent updates always change these things even if you do it the usual way? Nobody is talking about those as far as I'm aware of.

  6. I wonder if LineageOS has the option for good 'ol USB Mass Storage mode. For Sony Xperia E3 at least with stock OS based on Android 4.4.4, it's not an issue because it has the option in settings. It's still a fairly modern device, only 5 years old.

    I never used unrooted phone for long though, just find it too restricting. Banking apps often refuse to work on rooted phones and even some stuff in entertainment category... Sure you can unroot and certain modifications for which you needed root permissions stay, obvious exception being the apps that need root access to operate normally, but it's just an extra stupid barrier for the people who know what they're doing.

  7. On 9/23/2019 at 3:33 PM, Tripredacus said:

    The DISM commands to check/restore health are to be run in the OS, not from the recovery command prompt.

    Just adding a note; you can actually run those from recovery environment. At least from my limited experience, running it from there and pointing it to a good installation as repair source (mounted WIM image) that has the same updates as problematic installation seems to be the most reliable way to achieve some actual results.

  8. 6 hours ago, ~♥Aiko♥Chan♥~ said:

    The rest of the NT 6 series at least does its job properly:wacko:

    Not really. Ran them all, they all have issues.

    6 hours ago, ~♥Aiko♥Chan♥~ said:

    Absurd how MS can screw up a perfectly good OS every time.

    A perfectly good OS doesn't exist, not in objective sense at least.

  9. One way is using RDP Wrapper. It won't work out-of-the-box on updated Windows builds since the author doesn't update it anymore so you'll have to search through the issues page or elsewhere to get the information about what to add to rdpwrap.ini, located at C:\Program Files\RDP Wrapper after installation. When modifying rdpwrap.ini, make sure to leave an empty line at the end to avoid unexpected crashes.

    rdpwrap.ini contains instructions on how to work with particular version of termsrv.dll, which is what makes accepting Remote Desktop connections possible. Remote Desktop Services service has to be restarted for changes to take effect, but if the process that hosts it also hosts other services, then they all have to be stopped (and restarted in the end) before restarting Remote Desktop Services service.

    There's also a thread on MDL forums discussing patching of termserv.dll file directly on disk, as well as RDP Wrapper method. The former method is clunkier, as it involves getting yourself permission over termserv.dll at C:\Windows\System32, then using the hex editor to search and replace several bytes. If you use that method, changing the name of the original file then making a copy with correct name and making modifications to it will leave the original copy in the component store (though I haven't tested whether this actually stops DISM from complaining about corrupted file if you run a scan - maybe it still complains about unlinked file unless that is SFC's job :dubbio:- about which I'm positive would react to the change if ran).

    I'd go with the wrapper unless you find a special reason to mess with termserv.dll directly.

  10. It was fine just a week ago, but today, my PC hit 100 days of uptime and I noticed explorer.exe launches with 200 MB of RAM consumption just showing an empty desktop and a taskbar. Then it goes up with time, I got to about 440 MB yesterday. My usage patterns haven't changed, I just updated GPU drivers, but that was on 5th of October.

    Just wondering if anyone encountered this and if the reboot solved it and if not, what was done to fix it?

    Looking at the changelog of newer updates, the build I'm on now has quite some (unrelated, hopefully) issues, but I'm not feeling confident about updating immediately as there's always something. They never tell you what they broke, they just say they fixed something which at some point was actually working properly. I'll wait until the next patch Tuesday at least.

    Anyway. two more things that might be related or might not be; sometime after 70 days of uptime, I had to disable AppX Deployment Service because it was making my computer unusable, it ran at logon and got stuck in some messed up state that it wasn't even able to accept stop command while grinding the disk non-stop. If left unattended, Process Hacker would count several gigabytes of read data. After terminating its process, it stayed quiet.

    The second thing, Process Hacker shows 1,14 GB of crap in the page file while Task Manager reads 1,4 GB of paged pool usage. I remember this was much worse with Windows 8.1, the numbers were rising about 3x times faster. Some background system process leaking memory? I don't know if it would happen with previous Windows versions with my setup because I almost never ran them for more than a day.

  11. A word of caution to anyone running Vista on a VMware virtual machine - VMware Tools version 11.0.0 comes with an user mode OpenGL driver that expects K32EnumProcessModulesEx in kernel32.dll, which only exists on Windows 7+, thus one may unexpectedly get an error about the missing function when trying to run an OpenGL application, then application reporting it was unable to find an accelerated OpenGL driver or failing in some other way.

    The last compatible VMware Tools version is 10.3.10. This should be reported as it seems like an oversight rather than intentional breakage, plus the function is actually supported on Vista, just resides in a different DLL, so it would be trivial to fix.

×
×
  • Create New...