overhaul css + minor edits
This commit is contained in:
parent
8f040abbe8
commit
209a64d77b
8 changed files with 118 additions and 93 deletions
|
@ -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!!!") }}
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue