I like games of all types and sometimes try to make them. IT Professional who likes mechanical keyboards and weird hobby electronics too much. He/Him.

  • 1 Post
  • 33 Comments
Joined 1 year ago
cake
Cake day: June 13th, 2023

help-circle


  • OK, time to come clean. I had assumed the other old people would have this at the ready, but when the confused responses came in, I just rolled with it and now I’m bored with the joke.

    This is for BECMI. The question itself is real, though, I’ve heard of better Thief progressions, and I don’t want to just top out at 14 like most people do since I never got to play with the Masters or Immortals sets and I want to try it at least once so I know how it plays.







  • My bet is on either thermals or power supply.

    Not likely to be RAM, since issues there are more likely to either prevent the machine starting in the first place, or lock up if it fails while the machine is in operation.

    Not likely to be CMOS battery since that generally wouldn’t cause the machine to shut off, it just preserves firmware settings between power cycles.

    In theory, there could be an intermitted short happening somewhere and the PSU’s OCP is kicking in, but I’ve never come across something like that. Similarly, there could be a problem with an internal power cable connection doing the same, but it sounds like you’ve already checked that.

    I would test with a different PSU if you can. Thermals should be easy to check for too with the many pieces of available software to keep track of such things.




  • I’m going to be honest, Klingons in the TNG era always felt too goofy to me. They weren’t a proud warrior culture so much as borderline clownish space vikings who spent more time getting drunk than actually conquering anything. A redesign and change in how their culture(s) present on screen was welcome for me, and I think Discovery did a great job. I even liked the way they recontextualized the Klingon language, to make it sound more alien and more threataning than the staccato, oft-mispronounced mess that we got in the TNG era.

    That said, I also think there was a missed opportunity with them. For a long time, I’ve had a head canon of the different looks of Klingons throughout all of the eras could be chalked up to these all being distinct peoples from within the Klingon Empire. It stands to reason that over a long enough time scale, an empier spanning multiple stars would start to consider people not originally from their homeworld “Klingon,” even if they might be genetically different. I always thought it would be cool if the TOS smooth forehead Klingons were actually just one species that were culturally Klingon, where the Worf-type were another, and the General Chang type was yet another. It would provide a way to smooth over the aeshetic differences with an in-universe explanation that doesn’t require any retconning except for a handful of episodes from ENT that die-hards didn’t like anyway.

    But oh, well. One can dream.









  • It’s been several years since I worked with Manjaro, so I don’t remember which specific apps I ran into problems with, but the general idea is this:

    Manjaro holds back packages for several weeks behind vanilla Arch, so packages from the AUR are often built on versions of their dependencies that aren’t yet available to Manjaro users. This can result in apps not installing properly (or at all), or apps that were previously installed without issue suddenly breaking when they attempt to update.

    This isn’t actually specific to Manjaro – other Arch-derivatives like Garuda can also run into this problem. You’ll find that any Arch-based distro that makes significant changes to Arch (like holding back packages, or distributing versions of packages different to the ones in the Arch repositories) can have issues if it’s attempting to use things from the AUR. Arch derivatives that make no changes to the base system, and just use the vanilla Arch repositories don’t have this problem. Endeavour OS is an example of this, as the only changes it makes are additive – they have their own extra packages, but don’t change any core functionality from vanilla Arch.

    EposVox on youtube ran into some issues with Garuda about a year ago, and those are of the same flavor as what I experienced on Manjaro, even if they aren’t identical issues.