Loading comment...
Readit NewsLoading parent story...
Loading parent story...
Loading comment...
Loading parent story...
Loading comment...
efreak commented on Valve: HDMI Forum Continues to Block HDMI 2.1 for Linux heise.de/en/news/Valve-HD... · Posted by u/OsrsNeedsf2P
No one wants HDMI. No one.
My monitor works fine with HDMI
It worked fine with VGA and DVI as well (it has all four, but my current PC doesn't have DVI or VGA outputs).
It works fine with Displayport...until I turn it off, and then it won't go back on.
I could solve this by connecting the monitor with HDMI, but this is my secondary monitor; my primary is an older but nicer (16:10, brighter, etc) monitor that only has DVI and VGA, while my PC only has DP and HDMI outputs, and the only adapter I've found that works with them is the HDMI-DVI adapter I use, leaving me only DP to connect my secondary.
This is the process I have to go through to get my monitor working after turning it off when connected through displayport:
1. Turn off the computer (I'm not clear if fast shutdown or hibernate has any effect here) 2. Unplug the computer (or switch off the PSU) 3. Press the power button (to speed up the next step slightly) 4. Wait for residual power to drain from the motherboard (30s-3 minutes) 5. Reconnect computer to power 6. Turn PC back on
If I don't fully shut down the computer, such that it reinitializes the displays completely, it never recognizes that there's a monitor attached to displayport. My understanding is that this is because the DID (or equivalent) is powered by the monitor itself, and not by the computer, and when you turn off the monitor (as I do at night to keep the bright-af led off; this also prevents Windows from waking the display every few hours but that can be done by disabling the monitor with Win+P), somewhere between the OS and the motherboard the logical port gets completely shut down until a full reset.
Loading parent story...
Loading comment...
efreak commented on Microsoft makes Zork open-source opensource.microsoft.com/... · Posted by u/tabletcorry
bummer
> The code relies on old internal Infocom toolchains (ZILCH compiler, WATFOR,
> mainframe environment) that are not open and likely not preserved.
Read the notes on the repository itself:
> Basic Information on the Contents of This Repository > > It is mostly important to note that there is currently no known way to compile the source code in this repository into a final "Z-machine Interpreter Program" (ZIP) file using an official Infocom-built compiler. There is a user-maintained compiler named ZILF that has been shown to successfully compile these .ZIL files with minor issues. There are .ZIP files in some of the Infocom Source Code repositories but they were there as of final spin-down of the Infocom Drive and the means to create them is currently lost. > > ... > > In general, Infocom games were created by taking previous Infocom source code, copying the directory, and making changes until the game worked the way the current Implementor needed. Structure, therefore, tended to follow from game to game and may or may not accurately reflect the actual function of the code.
Loading parent story...
Loading comment...
Loading parent story...
Loading comment...
Loading parent story...
Loading comment...
Charging for self-hosted runners is an interesting choice. That's the same cost as their smallest hosted runners [1]
[1] - https://docs.github.com/en/billing/reference/actions-runner-...