[Richard42]

I just want to chime in here to say that I recently acquired a non-functioning Octane from a friend. I'm a big vintage computer collector but never owned any SGI machines. After repairing the power supply the machine came to life but the hard drive that it came with did not have a proper IRIX install. So while waiting for a SCSI CD-ROM to arrive from ebay, I set up the LOVE server on an old Acer Ferrari 3200 laptop running Linux Mint and connected the machines with a CAT5 crossover cable. And this software was a huge help. I was able to install everything from CD images super fast and it was a piece of cake. Thanks!

[tomekwojcik]

I made an account on this forum to say "Thank you" for LOVE. I got an Indy from a buddy with broken hard disk. I tried to set up IRIX 6.5.22 in MAME but it would freeze often. I was gonna get an external SCSI CD-ROM and install from CDs but somebody pointed me at LOVE. I set it up in my homelab, and my Indy is now installing software using it over network.

Thanks for this thing. It's a huge help for SGI noobs like myself .

[agentb]

Another big thanks for love, installing 6.5.30 on an Octane from Linux mint and serial console. Guide was great and just what I needed, step by step. I did have cacheline write error which blocked installation but seemed to be resolved with:
setenv console d
Thanks again!

[Anonymoose]

I tried to run the LOVE installer in Windows 11, but keep getting errors that certain libraries are not installed. These are all debug libraries, so not installed by default on Windows systems. Installing Visual studio + SDK's has helped to solve 1 error, 2 remain. Before trying to find the missing DLL files, does the tool actually require the debug versions of the libraries or am I doing something wrong?
The Linux version seems to work just fine.

I'm having this same issue on Windows 10, the DLL's being msvcp140d.dll, vcruntime140d.dll, and ucrtbased.dll. Any help?

[Richard42]

I'm having this same issue on Windows 10, the DLL's being msvcp140d.dll, vcruntime140d.dll, and ucrtbased.dll. Any help?

The easy way to get around this problem is to just download those DLLs and put them in your folder with the LOVE executable. I have not tried to run LOVE on Windows so I don't know how it's packaged but I've done plenty of Windows development in the past and this is the usual solution. Those DLLs should be easy to find online.

The more complicated way to fix this is to to build LOVE for yourself with Visual Studio, in release or debug mode. Again, I haven't built or run LOVE under Windows so I don't know if it ships with vcxproj and sln files or you have to make them yourself, but I built it under linux from source and it was only a single C source file so it shouldn't be terribly hard to do.

[weblacky]

Not that I've tried this, but being somewhat familiar with this I can tell you that basically you're missing the appropriate MS VC++ runtime that the original author linked against in Visual Studio. I normally do static linking to avoid this whole thing but basically there's a redistributor from Microsoft that gets updated every so often: https://learn.microsoft.com/en-us/cpp/wi...9-and-2022

I use visual studio 2019 community edition so I'm used to seeing "142" all around the place. Most likely this was compiled for a visual studio 2015's runtime.

I can't guarantee anything, but this should be pretty standard stuff, doesn't hurt to install these run times anyway for application compatibility in Windows.

Good Luck!

[twix]

I need to update on my previous post : in the end I re-installed the LOVE application, maybe twice, and this solved the problem. No idea what caused the problem initially, but it is working properly now. So keep on reinstalling, or reinstall directly after a reboot.