A brief supplement to my last post.
I now note that those panels didn’t refer to the Mono issue, but other warnings I received when trying to install .NET 4.6.2.
One of the first complaints Winetricks generated, after the complaint about the 64-bit WINEPREFIX, was of the following text:
“Mono does not appear to be installed.”
This was the reason for my leading question.
Something isn’t right, there – the file name indicates it’s downloading .NET framework 3, not 4.6.
I believe the NET updates are cumulative. So it attempts to install 3.0, 4.0, 5.0 as well as 6.0. It has repeatedly, or at least frequently, stalled at requesting me to rename .
Since NET 3.0 is so old, it may be 32 Bit. Since my LMDE 3 system is 64 Bit, as well as (I believe) Scrivener being 64 Bit, I created a 64 Bit WINEPREFIX in order to install it.
I have since created a 32 Bit WINEPREFIX also. I’ve found some guidance about editing <.bashrc> to include a line for the 32 Bit WINEPREFIX; I obviously have to be very careful in modifying this file, and will create a system backup w/ DFSee before doing so. Hopefully, I will complete both later today.
This perhaps then will allow updating of all of the NET Framework through 4.6.2.
This process has been so confusing and frustrating that I completely forgot the Net designations. Instead of “3.0, 4.0, 5.0 as well as 6.0”, I should have said “3.0, 4.0, 4.5 as well as 4.6”.
This process has been so frustrating that I’m now reconciled to having to use Win 7 for the Scrivener application already installed there.
I’ll probably check back periodically to see if any new suggestions appear here or on the Linux Mint forums. But I have to spend the time using Scrivener rather than trying to get it registered under Wine.
OK, I tried a new “line of attack” …
I decided, per a recommendation here, to give Crossover a whirl. It did download and install the Net 4.0 framework including 4.6.2. On starting Scrivener under Crossover it NO LONGER complains about the Net framework.
However, I did receive the below two error messages on attempting to register my version. Maybe I’ll have to contact L&L about them. But at least I got over the main hurdle …
Unfortunately Crossover did not get me over the main hurdle.
On trying a second time to register I received the two (2) below error messages. I have now installed Scrivener 1.9.16 at least three (3) times under Crossover but each time have been unsuccessful in registering it.
The initial times I used the file downloaded from L&L’s Web Site. Later I discovered it is listed as an Available Application, and used it. Regrettably, the failure was the same each time.
I believe I have selected the bottle as both Win 7 and Win 7 64-Bit, neither working and both complaining that it required Net 4.5 - though Crossover showed it had downloaded and installed Net 4.6.2; the two (2) respective error messages are below (as well as receiving the other two already supplied). A representative of Codeweavers suggested I possibly try a Win 10 bottle. I would prefer some guidance, as to whether a Win 10 bottle might work, before following that suggestion.
Does anyone have any suggestions of a remedy for this problem?
I run the Linux version and the latest version 1 for Windows, and work on projects in parallel between them with no problems. There are changes in internal project layout, but that is nothing I notice, as long as I do not open the projects on iOS Scrivener or on the beta 3 version.
Using the Linux version from an AppImage is stable and fast, and works on all Linux systems I have tested on, 32 and 64 bit alike.
Not sure at all why you’re having such problems. The dotNET packages are not well supported in Wine, but they should work for this purpose. I have done several installs to see that it works properly, and I haven’t had it fail.
A “Windows 10 bottle” is exactly the same as any other bottle, except it has a field in the registry saying it’s Windows 10 instead of saying whatever version it is otherwise saying. That hasn’t made any difference for me.
When it comes to Scrivener on Linux, listen to garpu.
That said, outside of core, never trust a distro version of ANYTHING in linux to be the latest. The more it is in the contrib section the less likely you are to get a recent version. If you are familiar with linux you will know that any linux code run on any linux distribution. This isn’t MS vs Apple here where the kernels are incompatible. The difference in distros is about packaging and FS layout. Spend some time learning to build packages from source or use non-distro based installation scripts and you will never have to look for distribution packages again.
Take that last point to heart.
This is a combined reply to The Swede and Jaysen.
I did (after a bit of confusion) easily install Scrivener for Linux 1.9.0.1 Beta and it appears to run w/out problem. I also used it to open the essay (about 65% to 80% composed under Scrivener for Windows 1.9.16). (I created a folder in Documents for Scrivener and then subfolders for each of Linux and Windows compositions (the latter for the current essay version if I can get Crosstalk to cooperate)).
My worry about using the Linux version to complete it is that it is a very long essay w/ multiple footnotes - which upon completion I will self-publish - and wanted to avoid a situation where after completion i discovered a portion composed in Windows was missing - and then having to start afresh in Windows on the additions. I do acknowledge that the version opened in Linux does appear from the one section I have looked at to have the text, formatting, and footnotes composed in Windows. A previous poster, in a thread in this forum, or the Linux Mint, forum, cautioned against relying on consistency of the text in the Linux version for a file composed in the Windows version, causing my hesitancy for reliance on the former for this project. (I do plan to used the Linux version for all future compositions.)
I am an absolute newbie in Linux, having for the last quarter century worked primarily in OS/2 and its various later distributions. And now having passed the 3/4 Century mark I likely have little time remaining to learn too much new in command line work and scripting. My platform is Linux Mint Debian 3, and the PlayOnLinux and WineTricks versions which are available through the Software Manager are definitely out of date; I’m sure this is the primary cause of my problems. It perhaps is also handicapped by my removal of Wine, PlayOnLinux and Winetricks - only done though after my problems w/ it and doubt of its utility here - in order to make room in Root; I tend to doubt it though since Crosstalk was supposed to install the required dependencies (including Net) and seemed to do so.
I suppose that I will try in the next few days to see if I can retrieve from WineHQ the Net 4.5 and 4.6 updates - the Crosstalk log file showing that the 2.0 and 4.0 Framework was installed - and see if I can somehow install them under Debian and associate them w/ Crosstalk.
Just an addendum to my preceding post.
I apparently hadn’t been infused w/ enough morning coffee when I composed it … The reference to “Crosstalk” should of course be read to mean “Crossover”. As I just opened it to see if it could remedy the Net conundrum, I realized my error.
Yeah…even on Slackware, I’ve got to recompile a not-insignificant amount of stuff to get things to where I need. And with WINE, it’s a constantly-evolving thing, so fixes happen every two weeks or so. (Or every fortnight, for those across the Pond.)
A lot of those fixes might seem inconsequential, if you don’t game, but they all affect WINE’s core functionality. Like a lot of the vcruntime changes between versions 2 and 4 were aimed at gaming, but helped Scrivener function without a lot of overrides. I suspect once they get the speechsdk issue nailed down (It was a regression in 5.0), it’ll likely not need any overrides. (God only knows when that will happen, depending on what else it breaks, who has time to debug and bisect, and if anyone can do regression testing between WINE 4.19 and WINE 5.0.)
The “development” version of WINE sounds scary, compared to “stable,” but “stable” was released a year ago, and is already out of date. The development one sometimes breaks things, but those regressions are rare, in my experience.
A lot of software, you can totally skate with older versions, but WINE isn’t one of them. (Like video card drivers or Mesa, and so on.)
Hang on, what, exactly, are you downloading from WineHQ? The only mono that’s distributed there is wine-mono, which is known not to work with Paddle. You need the real .Net framework (4.6 or above) that’s distributed via microsoft and winetricks. (Winetricks has some changes to make it actually install, whereas if you download the redistributable direct from microsoft, it might not work.)
Back in the day, we did have to coax Microsoft to let us Linux folks download things like vcrun 2005, and hope it installed on the wineprefix. Winetricks is so much easier. 
(.net = mono for windows. Rather, mono is .net for Linux. Sometimes you can use linux mono to run Windows .net programs, but those are few and far between. The game, Vintage Story, is one of them. So was Terraria about 10 years ago. Paddle, the license activation program for Scrivener, is one of them that absolutely needs the Windows .Net framework to function.)
I’ve made so many posts on various forums and in e-mails - here, on a Linux Mint one, and to L&L and Code Weavers, I’m not sure which I mentioned previously and to which you are referring.
It’s probably, though, <NDP462-KB3151800-x86-x64-AllOS-ENU.exe>. In order to save space in Root, and as they weren’t helping me anyway, I decided to uninstall Wine, PlayOn Linux, and Winetricks, and to try Crossover. The install window showed it downloading and installing Net Framework 4.0, and also downloading 4.6.2. In the Crossover log there wasn’t any clear reference to installation of 4.6.2, so I made inquiry of Code Weavers a few days ago on this issue; I’ve yet to receive a response.
One of the additional issues I addressed was whether installation of the above file, using its Wine Configuration or Tools menu was possible; it seemed to me this might insure I got Scrivener to recognize 4.5 and 4.6.2. Crossover installed Scrivener fine, but I’m still dealing w/ the Paddle issue. (In the meantime I’m regrettably using Scrivener under Win 7 so as to be sure not to lose or have to duplicate text I’m composing in my very long current essay.)
[On the last point I note that Devin, as stated in his 4/13 6:06 PM post, and The Swede, as stated in his 4/22 7:13 AM post, seem to “have different mileage” on consistency of texts composed in Windows 1.9.16 and Linux 1.9.0.1 Beta. If the only difference lies w/in certain menu options, this is meaningless to me. My only concern is whether the binder categories and text (including footnotes) for a file composed under the former will fully and accurately open under the latter. I find Scrivener invaluable - particularly for what I am doing now, which is generating and then organizing a plethora of text files, each containing different thoughts - in order to create discrete separate chapters and coherent organization w/in them. Nevertheless, once I am done, I intend to compile them in ODT format for final composition and, then, finalization - since I am more familiar w/ Open Office formatting. If I can confidently open the current 1.9.16 file in 1.9.0.1 Beta, insert additional text and use the Corkboard for rearrangement, I would be a “happy camper” indeed.]
As I heard it is going well
In my experience, moving back and forth between 1.9.16 on Windows and 1.9.0.1 on Linux works flawlessly. There are no issues what so ever. That said, I stick to functionality which is in 1.9.0.1 since my main writing platforms are Linux based, and I can’t be bothered to deal with the .NET issue any more.
The only time I have had any weird issues is when I have done edits on the iOS version of Scrivener. Then the 1.9.0.1 will get confused, and lose those edits. They are not gone from inside the project, and can be recovered, but that version will not see them. Thus, I am no longer using the iOS version.
Thanks for the comment.
I perhaps shouldn’t have been so worried about the compatibility and thereby wasted so much time. The fact the essay appears it will be approaching 200 pages (w/ numerous footnotes), using a 6" x 9" page format, is the reason it concerned me. But, from the brief review of the 1.9.16 version opened in 1.9.0.1, it seemed the same and maybe I should just have proceeded w/ the latter.
I’ve already compiled it into ODT and now am doing the “polishing” using OpenOffice. (I’m going to try to start using LibreOffice more so I can get used to the differences in appearance.
And from now on 1.9.0.1 will be the, only version i use. In addition to your advice, the text (at least in the way both of them are configured on my systems) is certainly clearer and larger in 1.9.0.1., (an important issue for my 75 year old eyes.)
Thanks.
Apologies it was so late. I got really sick, and haven’t been active with anything online, really.
Glad to hear you’re working the project out though. Best of luck with it!
Ack. 
Hopefully it’s not covid-19. How you feeling now? I had a friend with La 'Rona, and he was pretty damn sick for a good month or two.
It was. I was down and out for weeks. Really did a number on me.
Better, but not great. Still very weak, and problems focusing. No energy to even do things I enjoy. But it’s getting better, so I have hope.
Yeah, it can hit like that. Was a very long trip for me, and it’s not quite over yet.
Ugh. Here’s hoping it goes and stays gone, and the next brain swab comes out clean! Or are they doing antibody testing there yet?