![]()
#Lightzone x86 or amd64 installThe gist of it was that I still had to install Mono and Gecko. I didn’t understand why my –install-recommends command to install Wine hadn’t installed Mono. ![]() ![]() #Lightzone x86 or amd64 how toBut once it was done –once I knew how to do it, as summarized below - it was not so bad. Figuring out how to finish the installation was a hassle. I would soon find that, despite appearances, I actually did not yet have Wine fully installed. ![]() In his writeup, Tung did not mention security, so apparently the choice of Stable over Development branches did not imply that the choice of Stable would leave me at a severe disadvantage in terms of security updates. ZDNet (Tung, 2021) indicated that Wine 6.0 was a big upgrade, released in January 2021, so at this point it was (“only”) nine months old. This Stable version (6.0.1) compared to the current Development version, which was apparently 6.16. This process resulted in a substantial addition (~1.5GB) to the system. The final two lines installed Wine and verified that I had installed Wine 6.0.1. Lines three through six installed the WineHQ Ubuntu repository. The third command should return “i386” to indicate that the 32-bit architecture was now installed. (In that case, possibly my older post on 32-bit Wine would be helpful.) The second command would install the 32-bit architecture if it was not already installed. If the first command did not return “amd64,” the system was apparently not suited for the 64-bit Wine installation that I intended. Sudo apt install -install-recommends winehq-stable Sudo add-apt-repository 'deb hirsute main' Sudo -H gpg -o /etc/apt// -dearmor winehq.key To install Wine Stable in Ubuntu 21.04, I interpreted HTML Validator ( 2021) as recommending these commands (see explanation, below) (see also WineHQ): dpkg -print-architecture The Wine User’s Guide acknowledged that some installation methods (like much about Wine) could be outdated. For other, possibly but not necessarily newer guides, see Lifewire, Ubuntu, and It’s FOSS. The Wine User’s Guide suggested several methods of installing Wine. It appeared, in short, that DoubleKiller was a good candidate for the Stable branch. #Lightzone x86 or amd64 windowsThere appeared to be no entries for it in the WineHQ database, but my own previous post indicated that it was among the Windows programs that I had been able to install but had not yet tested in Wine. Possibly some aspects of the following discussion will vary for initial installations that start out in a physical machine.Īccording to WineHQ said, there were three main branches of Wine: Development, “recommended for users who want or need the lastest features and bugfixes” Staging, which “includes several hundred experimental patches that are not yet ready for inclusion in the main branch” and Stable, “on an annual release cycle … intended for users whose applications and games already work well in the existing code.”ĭoubleKiller had debuted by 2002. I didn’t switch over to the physical environment until after I had gotten DoubleKiller running in Wine, as described below. #Lightzone x86 or amd64 windows 10Note that I was working in an Ubuntu virtual machine, running in VMware Player on a Windows 10 host. But the general solution appeared to involve installing Wine in Ubuntu, and then running DoubleKiller in Wine. My search did not turn up specific guidance on that. This post focuses on getting DoubleKiller to work in that Linux setting. The other post presents the overall development of the Ubuntu file comparison computer. ![]() The general idea was that this might give me relatively early notice that ransomware was starting to encrypt my system - especially if the Linux system conducting this comparison was not infected by the ransomware (which mostly seemed to infect Windows systems). This semi-manual process allowed me to conduct an occasional visual inspection of what had changed on my data drive. In Windows, my preferred file comparison scheme involved Beyond Compare, for making sure that the target drive contained all of the files stored on the source drive, and DoubleKiller Pro, for identifying and removing duplicates (usually consisting of files that had been in one folder but had now been moved to another). As described in another post, I was setting up an old computer to function as a file comparison and text indexing station. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |