-
-
Notifications
You must be signed in to change notification settings - Fork 167
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Delta Chat Desktop on Windows Server 2008 R2 #1597
Comments
Hmm... The same problem on Windows Server 2012 R2 |
Can you check out if you have the visual c++ runtime installed? Seems like this is sometimes the problem on windows: Also can you start the .exe from the command line with the "--log-to-console --logLevel debug" arguments? |
It was helped me! |
Just stuck there with 1.3.4 on Win 8.1 x64 More specific symptoms:
No any GUI ! After you kill those processes from Task Manager (and they are not easy to kill ! there is something i could not factor out, maybe one task keeps respawning another or some hard timeouts or something, it takes luck or persistence to make them finally die) the log files gets ONE message in it.
Since you aim at making "novice-friendly" app this is truly wrong! Frankly, to just call raw Windows GDI API no any overly-complex zillion-layers JS framework is required. DC has to have some plain watchdog inside the app that will alert user and save diagnostics if all the industry of virtual machines needed for cute GUI fails to start. For instance, the moment log file is created seom stub info has already to be writting into it. And then i think there is some way to learn if Electron failed to start, even as dumb like just having a dormant thread waiting for 60 seconds for main app windows to arrive or something like that. And while we are at it, should TSV logs really have all those C string escapings? make them much harder to read. |
In 1.4 the logs will have less strings escaped and some padding to be easier human readable #1650 |
looks like its ok for ms when we bundle the files, now I only need to find a good way to get them and to bundle them... time to spin up a windows vm |
another option would be to modify the building of the core for the node bindings: https://www.reddit.com/r/rust/comments/7mif9i/how_to_compile_binaries_without_dependencies_on/ Update 1: neon-bindings/neon#519 looks related, currently I'm not really understanding the comment what needs to be done there, so lets keep this link here, maybe we need it later again. |
Copying all the dll files of the redist to the deltachat instalation folder solved the issue, now I only need to change the build process to do that. |
Hey folks, I have a portable version for you to test https://testrun.org/DeltaChat%201.4.0.testing.exe |
....comparing DeltaChat footprint with VisualIRC footprint, "well, d'oh..." As for test, my win box is not tainted with VC++ runtime, but will i have a clean windows box i will try |
@the-Arioch yeah electron is heavy, though the msvc thing is actually required to run the deltachat core on windows, and that has nothing to do with electron.
the 1,7mb more are not that much considering the electron footprint and we can still save some space by excluding more useless unused files from the final package. |
The apk is also >50MB so 70MB is not that bad.
Really excited to get a "just installs" DC Desktop
version for windows -- a major milestone ;)
…On Tue, Jun 23, 2020 at 03:36 -0700, Simon Laux wrote:
@the-Arioch yeah electron is heavy, though the msvc thing is actually required to run the deltachat core on windows.
There were two options left (unless there are more that I missed):
- Bundle the vcredist installer with our installer, but that doesn't solve the problem for the portable version.
- bundle the relevant files (aka. local deployment)
1,7mb more are not that much considering the electron footprint and we can still save some space by excluding more useless unused files from the final package.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
#1597 (comment)
|
The text was updated successfully, but these errors were encountered: