cmd

Forum Replies Created

Viewing 10 posts - 1 through 10 (of 11 total)
  • Author
    Posts
  • in reply to: text-align override not working in 3.5.0 #5426
    cmdcmd
    Participant

    This worked fantastically, thanks!

    I think my confusion stemmed from not realizing that wide items behave differently in general, and the descriptions of align and text-align in the Common Options section of the manual. Particularly where text-align says it overrides any align setting:

    Perhaps a note about text-align not being applicable to wide items, and a note that COMMENT is a wide item would be helpful.

    Thanks again, Glenn!

    in reply to: Windows Hard lock on resume from low power states #4848
    cmdcmd
    Participant

    Hi Glen!

    First I didn’t see your response, so sorry for the very late reply: I haven’t caught it happening from a hibernate (but the only hibernate I use on my system is the “built in” one that comes as a part of fast startup.)

    The *good* news is: I reproduced the issue *without* DesktopInfo!

    (Feel free to stop reading here, the rest is more of just me rubber ducking, but you can rest assured that I’m pretty confident it’s not any issue in or around DesktopInfo)

    Bad news is, I reproduced the issue without DesktopInfo 😂. It does seem to happen more often when DesktopInfo is running, so now that’s at least helping me try and track down what’s causing it.

    In the last month I did a repair install (e.g.: “in place upgrade”) of Windows on a whim, hoping that would help, but it’s still happening, so I think that it’s got to be some software I’ve got going (or hardware in general.)

    This morning I had it happen in a way that was a little different than before. The event log kept going after the hard lock, and there was actually a relevant event when it happened.

    Now if I can just figure out what those session IDs mean and why that means all the I/O stops 🙂

    I appreciate you putting up with me and for all your help, Glenn!

    Hope you’re well.

    in reply to: Windows Hard lock on resume from low power states #4624
    cmdcmd
    Participant

    I appreciate the thoughts!

    I’ll touch on in it in a minute, but yeah I doubt it’s actually DesktopInfo that’s causing the lockup itself, given the nature of how it stops *everything*. It presents like a bug from something running in kernel space. AFAIK nothing running in user space has been able to cause a hard lock like this since the win 6.0 driver model.

    “Serious” stress testing not really, but definitely some benchmarking. (Cinebench, Passmark, Geekbench, those sorts of things.) I also do a fair bit of development on this machine, so its cores get worked out by compiles and the sort. I’m coming up on a year of running this CPU now and haven’t run into any other issues that come to mind anyways.

    I will say I’ve updated the UEFI & Chipset drivers a handful of times over the year, and I think (could very well be perception bias) that has reduced the frequency with which I saw the issue.

    I just hit 10 days of uptime since disabling DesktopInfo, which I certainly hadn’t managed to do in the past year. I’m due for a reboot for Windows updates, so I think I’ll start experimenting some: I’ll disable basically everything in my .ini, and every few days I don’t experience the issue, I’ll re-enable a chunk and see if I can narrow down where I may be having the problem from.

    Anyways, back to my kernel guess — If it’s not hardware related, my gut instinct is a race condition in the kernel with either the network interfaces section (due to me having several ‘virtual’ interfaces due to vmware workstation that don’t behave like typical hardware) or some of the WMI calls (of which I have several that update at interval:0, so they’d only run on a hard refresh like seems to happen on resuming from low power states, whatever happens to trigger it then.

    in reply to: Windows Hard lock on resume from low power states #4597
    cmdcmd
    Participant

    I see it didn’t like the attaching of the ini directly, I’ve zipped it and attached it.

    As well, I thought perhaps it pertinent to provide some information about the hardware I’m experiencing this on:
    ASUS TUF Gaming X570-Plus (Wi-Fi)
    Ryzen 5950X (Running at standard clock speed, no PBO.)
    32 GB RAM @ 3200 MHz (Standard XMP profile.)
    GeForce 2080 Ti (Standard clocks. Resizable BAR is enabled.)
    UEFI Boot, Virtualization enabled, currently running Win 11 21H2 22000.258

    Attachments:
    in reply to: Windows 11 Support #4594
    cmdcmd
    Participant

    Hi Nathan,

    You think it’s funny that it still looks like Windows 10 — look at the ReleaseId key — the second half of 2020, despite your DisplayId showing 21H2! 🙂

    Anyways, here’s my solution to get all the build info so far. It’s a bit verbose, but works on all the machines I’m using it on!

    It grabs most things it can from WMI, the OS display name, arch, version (this is the main one, will be the 10.0.xxxxx), install date.
    Then it gets the release ID from the registry. (This is the ‘feature set’ that will be the 1903/20H1/21H1, etc.) It gets it from the key DisplayVersion. However that key wasn’t the one that windows used to use, having moved from the ReleaseId key. So later it will check to see if the value it got from DisplayVersion is empty, and if so, get the value from ReleaseId
    Lastly, it gets the UBR key. The UBR is the .xxx that gets added on to the version shown in winver and the sort. That’s another key that wasn’t always there (can’t quite remember when it was added), so if it’s empty I let it stay empty. Otherwise the last IF sets it to it’s value with the preceding ., so it looks nice tacked onto the osbuild printout.

    I’ve attached a screenshot of what the output looks like.

    Attachments:
    in reply to: WMI query with multiple sets causes stack overflow #3829
    cmdcmd
    Participant

    Incredible! I wish everything had the same sort of turnaround you do, Glenn. Thanks a heap!

    in reply to: WMI query with multiple sets causes stack overflow #3824
    cmdcmd
    Participant

    Awesome news, Glenn!

    I’ll keep my eye open for the next release and will see if I can reproduce it at all and let you know if it got fixed along the way!

    Cheers

    in reply to: WMI query with multiple sets causes stack overflow #3821
    cmdcmd
    Participant

    Hey rtruss, I appreciate that workaround. I was more demonstrating the stack overflow, as it seems to happen with any time I use multiple sets from a WMI query.

    I did manage to work around it for my use case too: if I break each WMI query set into a single set per query, using display and a single, non-‘equals’ set like so:

    Everything works like I’d expect!

    Obviously there’s un-needed overhead in running the query multiple times, but the majority of the data I’m collecting I’m doing with interval:0, so it’s a relatively small issue for now!

    in reply to: chart:bar2 not displaying #3816
    cmdcmd
    Participant

    Looks like between updating to 2.10 (for real!), and re-building my ini bit by bit things seem to be happy now! Thanks so much for the help!

    in reply to: chart:bar2 not displaying #3815
    cmdcmd
    Participant

    Doesn’t look like I can edit my previous post, but: You having me check my version is definitely something: I thought I had updated to 2.10.1.3742, but I must have had it running when I tried to paste the files in! I’m on that version now and not seeing it show up at all, so I’ve broken something else for sure, too!

Viewing 10 posts - 1 through 10 (of 11 total)
Glenn's Page