Open mxamber opened 1 year ago
The "api-ms-win-core-*" libraries should not be required by the newer releases because we are not building the binaries using wine anymore. Did you extract the 0.15.0 release in a different directory or did you replace older files with the newer release? If you did the second, I'd recommend extracting it in an empty directory and try again.
If that should not fix the issue, this could show an incompatibility with Windows 7 with the most current release (and potentially further releases). Maybe that's solvable but I think we would need to build the release using wine again which has some issues.
As a potential workaround, I'd recommend trying to run the application from source as described here.
I deleted the old installation and then extracted into the same directory. I've tried it with a different directory, too.
Is there any dependencies packaged into the binaries that might not work on Win7 anymore? I know Blender ditched Win7 because of a Python update, for instance.
Is there any dependencies packaged into the binaries that might not work on Win7 anymore? I know Blender ditched Win7 because of a Python update, for instance.
I mean the most obvious dependency we build on is Python: https://www.python.org/downloads/windows/
Windows 7 is not supported anymore by Python since release 3.9.0 (which is close to three years old). Security wise most users should not be on Windows 7 anymore to be honest either. But because we might have users with an old machine, not connected with the internet in any way and only dedicated to write their works, I tend to provide an option if feasible.
The better solution without changing the hardware would obviously be installing a supported Linux distribution and use that instead. But I can not know whether users here want to do that or if that makes sense regarding compatibility of other software they use. Manuskript definitely supports all modern Linux distributions afaik. In some software like Blender you might even see performance improvements running it on Linux.
My current assumption is that the Github action which built the binary is using at least Windows 10 (or something comparable) and it's using Python 3.9. I can look into this for the next release again. But currently I would just recommend to run the application from source as described in the wiki. If that's too technical, there's still the option to use older versions.
I'm running in to the same issue. I just downgraded to 14.x
I mean.. is there a process to building a Win7 version with the appropriate Python version? CAN we build our own if we try.
HEY! I'll make you a deal.. you build us a Win7 build for 15.x, and I'll ship you a jar of homemade strawberry jam! This is homemade, mind you. It's so much better than crappy store jelly, your eyes will roll back in your head. :D
I'm running in to the same issue. I just downgraded to 14.x
I mean.. is there a process to building a Win7 version with the appropriate Python version? CAN we build our own if we try.
HEY! I'll make you a deal.. you build us a Win7 build for 15.x, and I'll ship you a jar of homemade strawberry jam! This is homemade, mind you. It's so much better than crappy store jelly, your eyes will roll back in your head. :D
You can try to run the application from source: https://github.com/olivierkes/manuskript/wiki/Run-Manuskript-from-Source-Code-on-Windows
Well.. it sounds easier than doing a fresh build. I think I'll stick with 14 for now though. If version 16 adds some elements or skeletal structure to enhance the world-building aspect, then I'd spend the time doing a custom Git install, if needed. :)
(Likely, I'll just mothball my Windoze side, and switch back to Linux, and use it there. ;) )
I updated to 0.15.0 and get the following error:
"The program couldn't be started because api-ms-win-core-path-|1-1-0.dll is missing. Reinstall" (translated bc my machine isn't in English).
0.13.1 worked just fine on the same machine (Windows 7 64-bit)