https://bugs.winehq.org/show_bug.cgi?id=43629
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Evernote 6.6.4.5512 can't |Evernote 6.3.3.3502 can't |create note without native |create note without native |wininet |wininet URL|https://evernote.en.uptodow |https://web.archive.org/web |n.com/windows/download/1208 |/20161006015426/cdn1.everno |233 |te.com/win6/public/Evernote | |_6.3.3.3502.exe CC| |focht@gmx.net
--- Comment #2 from Anastasius Focht focht@gmx.net --- Hello Fabian,
--- quote --- adding stable download link. --- quote ---
https://evernote.en.uptodown.com/windows/download/1208233
Unfortunately many of these third-party software mirror services, such as softpedia.com, uptodown.com, cnet.com etc. can't be considered "stable". They definitely drop old versions. There are few sites such as oldversion.com, filehippo.com, filehorse.com which seem keep all old downloads but they don't mirror all kinds of software. Even then I wouldn't trust them and rather find/create a snapshot via archive.org
In this case I went as follows, remembering we already have quite a number of Evernote bugs:
https://bugs.winehq.org/buglist.cgi?bug_file_loc=archive.org%20evernote&...
(search all open/closed bugs which contain 'evernote' and 'archive.org' in the URL field)
One of the results returned the following archive.org URL(s):
https://web.archive.org/web/20200403152332/http://cdn1.evernote.com/win6/pub...
Using that pattern execute CDX API query on archive.org to figure out if the CDN from the snapshot URL has any matching/similar versions:
--- snip --- $ wget http://web.archive.org/cdx/search/cdx?url=%22cdn1.evernote.com/win6/public/*" -q -O - | grep application/ | grep 6.3.3
com,evernote,cdn1)/win6/public/evernote_6.3.3.3502.exe 20160930075250 https://cdn1.evernote.com/win6/public/Evernote_6.3.3.3502.exe application/octet-stream 200 KWUOS5RMEVPDZX2WEXIKMLLYHJRS6WFL 99767744 com,evernote,cdn1)/win6/public/evernote_6.3.3.3502.exe 20161006015426 https://cdn1.evernote.com/win6/public/Evernote_6.3.3.3502.exe application/octet-stream 200 KWUOS5RMEVPDZX2WEXIKMLLYHJRS6WFL 99763695 com,evernote,cdn1)/win6/public/evernote_6.3.3.3502.exe 20161026103545 https://cdn1.evernote.com/win6/public/Evernote_6.3.3.3502.exe application/octet-stream 200 KWUOS5RMEVPDZX2WEXIKMLLYHJRS6WFL 99763686 com,evernote,cdn1)/win6/public/evernote_6.3.3.3502.exe 20201209093028 https://cdn1.evernote.com/win6/public/Evernote_6.3.3.3502.exe application/octet-stream 200 KWUOS5RMEVPDZX2WEXIKMLLYHJRS6WFL 99841073 com,evernote,cdn1)/win6/public/evernote_6.3.3.3502.exe 20201226033631 https://cdn1.evernote.com/win6/public/Evernote_6.3.3.3502.exe application/octet-stream 200 KWUOS5RMEVPDZX2WEXIKMLLYHJRS6WFL 99841042 --- snip ---
I've selected:
https://web.archive.org/web/20161006015426/cdn1.evernote.com/win6/public/Eve...
$ sha1sum Evernote_6.3.3.3502.exe 55a8e9762c255e3cdf5625d0a62d783a632f58ab Evernote_6.3.3.3502.exe
$ du -sh Evernote_6.3.3.3502.exe 98M Evernote_6.3.3.3502.exe
One starting point would be to closely check the built-in application tracing 'activity log' under 'Help' menu when using builtin vs. native. There might be also differences when running the app under Windows. Just replacing one component with native doesn't necessarily mean it works as intended. Sometimes it goes through a different error handling/recovery path, resulting in "seems to work".
Regards