overhaul css + minor edits

This commit is contained in:
lynxize 2025-04-16 21:49:54 -06:00
parent 8f040abbe8
commit 209a64d77b
Signed by: lynxize
GPG key ID: 8615849B8532CD77
8 changed files with 118 additions and 93 deletions

View file

@ -3,7 +3,7 @@ title = "I'm sick of AI"
date = 2025-01-15
+++
{% warning() %}
{% important() %}
This is a bit of an unhinged rant, feel free to completely ignore it.
If you're not in the mood to read somebody's upset rant about AI taking over, just do yourself a favor and skip this.
{% end %}

View file

@ -4,7 +4,7 @@ date = 2024-04-10
updated = 2024-07-30
+++
{% note() %}
**I am not a keyboard nerd**. Full respect to any of you out there, but I am not one, nor do I plan to become one anytime soon.
**I am NOT a keyboard nerd**. Full respect to any of you out there, but I am not one, nor do I plan to become one anytime soon.
Don't take this as a "definitive guide" to anything, it was just me messing around.
{% end %}
@ -56,7 +56,7 @@ But, come on, that's *so dreadfully boring*. I wasn't interested in customizing
Apparently their definition of "customizable" lighting doesn't quite align with mine.
There's a little computer inside there, there's bound to be *something* more I can do with it...
# Screwing around with a Windows VM
# Screwing around in a VM
After googling around for a while, I stumbled upon [this reddit post](https://www.reddit.com/r/Keychron/comments/lbk2fk/a_very_odd_workaround_for_the_rgb_software/)
advertising a supposed way to program the lighting using somewhat sketchy-seeming third-party software.

View file

@ -10,7 +10,7 @@ If you don't care about the context, you can just [skip to the guide](#instructi
The title is somewhat disingenuous, it's less "SolidWorks on Linux" and more "SolidWorks in a Windows VM without Pissing Off The License Server" but that's not as good of a title.
# Context
- I need SolidWorks 2023 for school.
- I need SolidWorks for school.
- I finally built a PC capable of running it.
- I use Linux (~~arch btw~~).
@ -80,9 +80,9 @@ I have no idea whether bypassing the VM check violates some part of the terms of
Do this at your own risk.
{% end %}
Start by starting up a new Windows 10 (11 should work too, haven't tested) VM using `virt-manager`.
Start by starting up a new Windows VM (I used 10, but 11 should work too) using `virt-manager`.
Don't go through the Windows installer setup, and instead go to the machine details.
Don't go through the Windows installer setup, and instead edit the machine details.
## Virtual SCSI Drives
Make sure the virtual storage is set to use `SCSI`, not `SATA`.
@ -129,10 +129,6 @@ Now the device should appear, and you can continue installing Windows as normal.
Once it tries to reboot, remove both virtual SATA CDROMs, and boot into the new installation to finish setup.
{% important() %}
You **have to remove both of them** or SolidWorks will detect it!
{% end %}
After that, the installer should just work! SolidWorks no longer thinks it's in a VM, and installs normally!
{{ image(src="/assets/solidworks/victory.png", alt="SolidWorks open in a Windows 10 VM", caption="Finally! It works!!!") }}