lynxize/website
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

webp-ify more

Browse source
This commit is contained in:
lynxize 2025-04-25 09:55:31 -06:00
parent 94ff22870b
commit 266cea0f65
Signed by: lynxize
GPG key ID: 8615849B8532CD77
46 changed files with 18 additions and 18 deletions
Download patch file Download diff file Expand all files Collapse all files

18
content/blog/solidworks-on-linux.md
View file

@ -23,12 +23,12 @@ I'm just going to go with that.
## Wine
My first thought was "well, will it just work with [Wine](https://winehq.org)?"
{{ image(src="/assets/solidworks/wine-installer.png", alt="SolidWorks installer under Wine", caption="So far so good") }}
{{ image(src="/assets/solidworks/wine-installer.webp", alt="SolidWorks installer under Wine", caption="So far so good") }}
No, [of course not](https://appdb.winehq.org/objectManager.php?sClass=application&iId=318).
It's never that easy, is it.
{{ image(src="/assets/solidworks/wine-installer-broken.png", alt="Broken (blank) SolidWorks popup", caption="Should have seen that coming...") }}
{{ image(src="/assets/solidworks/wine-installer-broken.webp", alt="Broken (blank) SolidWorks popup", caption="Should have seen that coming...") }}
There is [an existing script](https://github.com/cryinkfly/SOLIDWORKS-for-Linux) to get SolidWorks to run under [Wine](https://www.winehq.org/),
but even after dissecting it and trying various things with [winetricks](https://github.com/Winetricks/winetricks), I never got the installer
@ -47,7 +47,7 @@ At this point I was getting fairly frustrated and decided to spin up a VM instea
## VM
Using [virt-manager](https://github.com/virt-manager/virt-manager) I set up a quick Windows 10 VM, but quickly hit a wall.
{{ image(src="/assets/solidworks/installer-license.png", alt="SolidWorks license error", caption="Great...") }}
{{ image(src="/assets/solidworks/installer-license.webp", alt="SolidWorks license error", caption="Great...") }}
I'm not paying for my own license. I only use SolidWorks for school projects, and therefore use my school's license, and,
well, I'm not exactly interested in spending [around $3000 per year](https://www.solidworks.com/how-to-buy/solidworks-plans-pricing)
@ -111,19 +111,19 @@ Next you'll need the VirtIO SCSI guest drivers.
[here](https://github.com/virtio-win/virtio-win-pkg-scripts/blob/master/README.md), which is where I found them.
Grab the ISO, and add it as a virtual CDROM.
{{ image(src="/assets/solidworks/add-driver-cdrom.png", alt="Adding the virtio driver iso as a CDROM", caption="") }}
{{ image(src="/assets/solidworks/add-driver-cdrom.webp", alt="Adding the virtio driver iso as a CDROM", caption="") }}
Next, go to **Boot Options** and ensure the SCSI disk and the Windows installer are both selected.
{{ image(src="/assets/solidworks/boot-options.png", alt="Both devices selected in virt-manager's boot device order", caption="") }}
{{ image(src="/assets/solidworks/boot-options.webp", alt="Both devices selected in virt-manager's boot device order", caption="") }}
Now start the VM, and go through the normal Windows install process until it inevitably complains about not finding any drive to install on.
{{ image(src="/assets/solidworks/windows-no-drives.png", alt="Windows finds no drives to install on", caption="") }}
{{ image(src="/assets/solidworks/windows-no-drives.webp", alt="Windows finds no drives to install on", caption="") }}
Select "Load driver," and select the appropriate driver for the architecture and Windows version.
{{ image(src="/assets/solidworks/windows-install-driver.png", alt="Installing the VirtIO SCSI controller driver", caption="") }}
{{ image(src="/assets/solidworks/windows-install-driver.webp", alt="Installing the VirtIO SCSI controller driver", caption="") }}
Now the device should appear, and you can continue installing Windows as normal.
@ -131,13 +131,13 @@ Once it tries to reboot, remove both virtual SATA CDROMs, and boot into the new
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!!!") }}
{{ image(src="/assets/solidworks/victory.webp", alt="SolidWorks open in a Windows 10 VM", caption="Finally! It works!!!") }}
## Other Things
Interestingly, *Windows itself* still knows it's virtualized.
{{ image(src="/assets/solidworks/task-manager.png", alt="Task Manager showing that Windows is virtualized", caption="Virtual machine: Yes") }}
{{ image(src="/assets/solidworks/task-manager.webp", alt="Task Manager showing that Windows is virtualized", caption="Virtual machine: Yes") }}
You can fix this by [disabling the "hypervisor" feature](https://forum.level1techs.com/t/hiding-hypervisor-from-vm-guest/132755).
```xml