Re: How to use Wine, How to get Gecko to install and work
On 02.07.24 02:57, George at Clug wrote: I wanted to know "how to configure and use Wine to run a Windows program". And that's why you should try out Bottles, because it's not just plain Wine. If you succeed with it, you can check the source code, what exactly they are doing that enables better success rates. E.g. they offer some sort of a desktop to run programs inside. In a few cases this helps solve some issues. No specific programs in mind, but MS Office could be an example. Afaik, this can only be possible with Crossover, my guess is they use some closed source components that allow to run even MS Office or Adobes Suite. But for everyone else, if you don't use dirt old versions of these programs, it's just impossible to run them as they are very stubborn about not to run on anything but Windows and macOS, no matter how hard you try. There are YouTube videos of people showing off that they succeed with this, but of course they never share how. So either these are just fake or they found a way to tell which dlls the programs are missing and just copied them from an existing Windows installation. Who knows. So you are better of trying apps that have an actual chance of ever being able to run on Linux. Maybe a good starting point is KeePass. Officially only supports Windows, but with explicit support for Mono, and Debian even has a package that sets up the Wine environment to run it inside. As Mario pointed, one example would be to have a modern web browser with DRM. DRM is already present in various browsers, just not necessarily the highest level. But question is if that can even be emulated. Because if it was that easy, there would be guides for that. Many games are only released as Windows programs. Fortunately Steam has achieved amazing results for running Windows games in Linux. True. That's what Proton is for, with a mix of DXVK and the sorts. At this stage I am only testing the concept, to see what is possible, what works, and what does not work. That's what Wine's AppDB is for: https://appdb.winehq.org/ To see what I need to understand so I can configure Wine for any given Windows application. That's just a naive dream, and it's highly questionable if that will ever be possible, most likely not. There are just too many programs depending on bad design decisions of Windows, like allowing just any terribly written Kernel level driver to do whatever the hell it wants. Valve is only this successful with Proton because they e.g. hired Collabora to develop and upstream APIs for the Linux Kernel to handle system calls Linux doesn't and will never support. Better stick to what's known to be supported, unless you want to develop for Wine itself. If you want to run a program with it, most likely others have tried that already, so you don't need to start from scratch. And you don't need to waste your time with things that will never work.
Re: How to use Wine, How to get Gecko to install and work
Thanks for your reply Jeff, On Tuesday, 02-07-2024 at 10:16 Jeffrey Walton wrote: > On Mon, Jul 1, 2024 at 6:33 PM George at Clug wrote: > > > > To all who replied, Thanks. > > > > Sadly after further testing I still have very little success with Wine. > > > > When I installed WineHQ's Wine Installation, Gecko and Mono were able to be > > installed. I noticed a rpcss.exe (from memory) in Taskmgr. This at least > > allowed me to display the initial web page in Wine's Iexplore. But sadly it > > did not help me in successfully installing the current Windows versions of > > Firefox or Chrome, or other programs I was having challenges with. > > > > I also tried PlayOnLinux [for installing Firefox or Chrome] without any > > success. > > > > The "Time vs ROI" for this endeavour suggests to me, that for now, I should > > just use Linux native programs. > > I think this is probably wandering off-topic, but I'll toss it out there... > > When in Rome, do as the Romans do. That means you run Windows programs > on WIndows VMs, and Linux programs on Linux VMs. Don't try to use Wine > to run Windows programs on Linux; and don't try to use a POSIX > subsystem to run Linux programs on WIndows. Mixing and matching is not > worth the aggravation. I had hopes using Wine was easier than I have found it to be. Your comment above has merit. There has been so many versions of Windows over the years, so many different programs with specific DLL and API needs. In part, I understand the challenge of having a system emulate another OS. I ran dual boot for a time, and I still have one Windows 10 PC for running games but have not used it for some time now, like you suggested, I only run programs that can run on Linux, if they don't run in Linux, I do not use them. Others I know would still like to run some particular Windows program. > > You never stated what problem you are trying to solve. I wanted to know "how to configure and use Wine to run a Windows program". No specific programs in mind, but MS Office could be an example. I also used Windows versions of Scite, Putty, WinSCP as test examples, only because they are smaller programs and I am familiar with using the programs in a Windows environment. As Mario pointed, one example would be to have a modern web browser with DRM. Many games are only released as Windows programs. Fortunately Steam has achieved amazing results for running Windows games in Linux. At this stage I am only testing the concept, to see what is possible, what works, and what does not work. To see what I need to understand so I can configure Wine for any given Windows application. > I'm guessing > there's a native Linux replacement for it so you don't need to wine > and iexplore. Iexplore I was referring to, is a program that comes with Wine, for the purposes of testing that your Wine installation has some level of basic working configuration for running Windows programs. > > Jeff >
Re: How to use Wine, How to get Gecko to install and work
On Mon, Jul 1, 2024 at 6:33 PM George at Clug wrote: > > To all who replied, Thanks. > > Sadly after further testing I still have very little success with Wine. > > When I installed WineHQ's Wine Installation, Gecko and Mono were able to be > installed. I noticed a rpcss.exe (from memory) in Taskmgr. This at least > allowed me to display the initial web page in Wine's Iexplore. But sadly it > did not help me in successfully installing the current Windows versions of > Firefox or Chrome, or other programs I was having challenges with. > > I also tried PlayOnLinux without any success. > > The "Time vs ROI" for this endeavour suggests to me, that for now, I should > just use Linux native programs. I think this is probably wandering off-topic, but I'll toss it out there... When in Rome, do as the Romans do. That means you run Windows programs on WIndows VMs, and Linux programs on Linux VMs. Don't try to use Wine to run Windows programs on Linux; and don't try to use a POSIX subsystem to run Linux programs on WIndows. Mixing and matching is not worth the aggravation. You never stated what problem you are trying to solve. I'm guessing there's a native Linux replacement for it so you don't need to wine and iexplore. Jeff
Re: How to use Wine, How to get Gecko to install and work
To all who replied, Thanks. Sadly after further testing I still have very little success with Wine. When I installed WineHQ's Wine Installation, Gecko and Mono were able to be installed. I noticed a rpcss.exe (from memory) in Taskmgr. This at least allowed me to display the initial web page in Wine's Iexplore. But sadly it did not help me in successfully installing the current Windows versions of Firefox or Chrome, or other programs I was having challenges with. I also tried PlayOnLinux without any success. The "Time vs ROI" for this endeavour suggests to me, that for now, I should just use Linux native programs. Regards, George. On Monday, 01-07-2024 at 15:48 didier gaumet wrote: > Le 01/07/2024 à 01:24, George at Clug a écrit : > [...] > > I have not found useful documentation that can get me over the "Could not > > find Wine Gecko", "Failed to init Gecko" error messages. > [...] > > Hello, > > disclaimer: I have not used Wine in ages, so I cannot be of real help > > Note, you could tell what Debian distro you are using (12 Bookworm?) and > if you have enabled multiarch support in it. > > the Debian wiki page about Wine is here: > https://wiki.debian.org/Wine > it states that for whatever reason "Windows software may require Mono > for .NET, and Gecko for any HTML rendering. Debian has disabled these by > default and do not provide packages.": > Windows software may require Mono for .NET, and Gecko for any HTML > rendering. Debian has disabled these by default and do not provide > packages. > > The WineHQ page about Gecko is here: > https://wiki.winehq.org/Gecko > > Two posts about solving Wine/Gecko problems on Debian Bookworm: > https://forums.debian.net/viewtopic.php?t=154513 > https://forum.winehq.org/viewtopic.php?t=38245 > >
Re: How to use Wine, How to get Gecko to install and work
On Mon, Jul 01, 2024 at 10:45:39AM -0400, Stefan Monnier wrote: > > As a general rule I am willing to accept RPMs, pacman ?? packages, and > > .debs, when they are from the Distribution's own package libraries, or > > hardware vendor supported, as otherwise I don't know the people providing > > the package. I have this strange belief that when a developer supplies > > a package to the Distribution owner for inclusion in their libraries, the > > Distribution owner does some level of verification/validation that the > > package plays nicely with the distribution and other applications. Maybe > > even some security checking? > > I'm with you, here. AFAIK Debian packaging does not in and of itself > come with any sort of "security checking", tho. So, if there are > security benefits (personally, I do believe there are) they are mostly > indirect result of the packaging process, e.g. in the presence of extra > eyes, or in the need to investigate the details of the licensing, or the > need to follow the rules about where files are placed, or in the > avoidance of vendoring, or in the "slow" pace of stable releases, ... I think there is a bit more to it. Imagine now you have 30 flatpaks, everyone bringing in its own snowflake version of... uh... libxz [1], say, and suddenly there is a backdoor. Sixteen of the startups providing the flatpaks have gone bust or were bought up by $BIGCORP. Now, what. > For that same reason, I try to stay away from things like Snap/Flatpak > which seem to be a way to skip all that "process" and run effectively > black-boxes, thereby preventing you access to the usual transparency > benefits of Free Software. That would be my approach too. Of course, $VENDOR offering the thing as a .deb is no guarantee either. I know of one which comes with two complete copies of PostgreSQL server, because... why not. So I try to stick to distro-native packages as far as possible. But hey. Everyone's entitled to ruin their health howewer they like :) Cheers [1] Just a random example, of course. And the person who discovered that backdoor happens to be Debian maintainer, but hey. -- t signature.asc Description: PGP signature
Re: How to use Wine, How to get Gecko to install and work
> As a general rule I am willing to accept RPMs, pacman ?? packages, and > .debs, when they are from the Distribution's own package libraries, or > hardware vendor supported, as otherwise I don't know the people providing > the package. I have this strange belief that when a developer supplies > a package to the Distribution owner for inclusion in their libraries, the > Distribution owner does some level of verification/validation that the > package plays nicely with the distribution and other applications. Maybe > even some security checking? I'm with you, here. AFAIK Debian packaging does not in and of itself come with any sort of "security checking", tho. So, if there are security benefits (personally, I do believe there are) they are mostly indirect result of the packaging process, e.g. in the presence of extra eyes, or in the need to investigate the details of the licensing, or the need to follow the rules about where files are placed, or in the avoidance of vendoring, or in the "slow" pace of stable releases, ... For that same reason, I try to stay away from things like Snap/Flatpak which seem to be a way to skip all that "process" and run effectively black-boxes, thereby preventing you access to the usual transparency benefits of Free Software. It's been a long time since I last used Wine (FWIW, it was to run the Windows version of Emacs, to try and reproduce a bug locally ), but IIUC the software you intend to run via Wine will probably be what I'd usually describe as "proprietary crap" a.k.a black boxes, so it seems to be one of the cases where the use of Snap/Flatpak should not make things much worse. Stefan
Re: How to use Wine, How to get Gecko to install and work
On 01.07.24 11:13, George at Clug wrote: As a general rule I am willing to accept RPMs, pacman ?? packages, and .debs, when they are from the Distribution's own package libraries, or hardware vendor supported, Hardware vendor distributed installation files usually should not be used, especially not over the distributions packages and especially not when it comes to GPUs. Nvidias own drivers are infamous for having terrible installers. If you need them, install them the way your distro recommends. So if you'd install hardware vendor packages but not other third party packages, you should really think about your decisions, as they don't make any sense. I have this strange belief that when a developer supplies a package to the Distribution owner for inclusion in their libraries At least not how Debian works. As the package's developer, nobody would stop you from being the maintainer of the Debian package in the official repo, but in general everybody can step up for that job. So a package being in Debian's repos is no guarantee for anything, especially not if not maintained by the core developers. But of course, maintainers need to stick to a rule book too, if they don't, their maintainer status will be revoked and their packages removed. Also, that's why to use Flatpaks and not just some random .debs - including the ones from hardware vendors not really giving a fuck. With Flatpaks, you can easily see if it's maintained by the developer or not. Also, they are isolated and have quite user-friendly permission management. Of course no software is bug-free, but it's better than nothing. Especially when you compare Flatpaks with Debian contrib or non-free packages. , the Distribution owner does some level of verification/validation that the package plays nicely with the distribution and other applications. Maybe even some security checking? I wonder if anyone agrees with me, or not? Good question, how far Debian goes here. The automated testing will most likely catch the biggest issues, but then that's irrelevant with universal formats like AppImage, Snap and Flatpak, as they don't really interact with other packages. And especially during the 6 months of feature freezes before a release, users on testing can very well tell how well all the packages work together and report bugs so worst case a package causing issues can be replaced by an older version that works better. Then again, that's irrelevant with universal packages too. Now the security part is a good question. It's well known that Debian developers try to fix any security issues as fast as possible, especially in Stable, even doing backports themselves if needed. But I have no idea how far Debian goes with preliminary security checks, before packages reach stable. Also, due to Debian enforcing some sanity on packages, everything that should be a dependency in its own package will be made into one, no matter what the developer wants. And only having to patch one package to fix a security issue in many - think issues in OpenSSL and the likes - is always better than having to patch every single package using it. That's the great benefit of Debian over e.g. Flatpak, though Flatpak does move the most common dependencies into runtimes to achieve something similar. But it won't enforce this. But on the other hand, being containerized does decrease the need for some patches as the security issue may just be much more difficult to abuse, as an attacker would not only have to exploit it but also have to break out of the container. So it's all quite relative. There seems to be way too many methods of packaging these days. That's why AppImages, Snaps and Flatpaks where invented, it's just way too difficult to support them all. And with sane default behavior and containerization, Flatpak is by far the best of the universal formats. I also think there are way too many distributions of Linux too, but if people have the time, I should not rail against them. I prefer to stay with as close to the original source distribution as possible, though I have yet to apply this to compiling from Gentoo Linux. That's freedom - especially of choice - for you. But beyond the big distros, you should only touch the myriad of distros when you know what you are doing.
Re: How to use Wine, How to get Gecko to install and work
On Monday, 01-07-2024 at 18:37 Richard wrote: > This has nothing to do with maturity. Thanks for picking that point up. I was not sure how to explain my reasoning. I will try to give a better explanation. As a general rule I am willing to accept RPMs, pacman ?? packages, and .debs, when they are from the Distribution's own package libraries, or hardware vendor supported, as otherwise I don't know the people providing the package. I have this strange belief that when a developer supplies a package to the Distribution owner for inclusion in their libraries, the Distribution owner does some level of verification/validation that the package plays nicely with the distribution and other applications. Maybe even some security checking? I wonder if anyone agrees with me, or not? > Only with the existence of someone > willing to maintain it - and its dependencies if needed. They don't publish > it as anything else than a Flatpak as that's by far the easiest way to make > sure it works for everyone, and thus they don't officially support any > other packaging frameworks. And since they don't just support Wine but also > Proton, and games benefit a lot from the latest drivers and libraries, so > packaging it for more conservative distros would entirely defeat at least > half of its purpose. And I guess Flatpaks isolation from the rest of the > system can be helpful in other ways too. There seems to be way too many methods of packaging these days. I also think there are way too many distributions of Linux too, but if people have the time, I should not rail against them. I prefer to stay with as close to the original source distribution as possible, though I have yet to apply this to compiling from Gentoo Linux. At one time in my IT career I was involved with package management and installation of software in a corporate environment and still suffer some level of PTSD over a few applications that were problematic. There are times when I definitely would have to agree with you "I guess Flatpaks isolation from the rest of the system can be helpful in other ways too", both in terms of security and stability. > > So either learn to accept other packaging formats or learn to live with the > fact that you may miss out on a lot if you don't invest a lot of time > figuring out how to compile the software by hand. You are correct, my choice does cause me to live without software that does not supported in Debian's package library. Though I do make a few exceptions. I base my decision on a strange notion that Debian packaged software gives a better level of Security, which is likely misguided, but that has been my choice so far. I reserve the right to change my decision whenever it suites me, as I am about to try WineHQ's version of Wine. ; ) Thanks for your reply and for making me explain my current reasoning in a (hopefully) better way. George. > > Am Mo., 1. Juli 2024 um 06:13 Uhr schrieb George at Clug < > c...@goproject.info>: > > > Mostly I only install software that is available in the Debian or Arch > > repositories, and I cannot find Bottles in the Debian Repository. I do not > > use snaps or flatpacks. Maybe I should but I don't. > > Hopefully one day, Bottles will mature to the point it can go through the > > Debian packaging system. I appreciate Debian's packaging systems. > > >
Re: How to use Wine, How to get Gecko to install and work
This has nothing to do with maturity. Only with the existence of someone willing to maintain it - and its dependencies if needed. They don't publish it as anything else than a Flatpak as that's by far the easiest way to make sure it works for everyone, and thus they don't officially support any other packaging frameworks. And since they don't just support Wine but also Proton, and games benefit a lot from the latest drivers and libraries, so packaging it for more conservative distros would entirely defeat at least half of its purpose. And I guess Flatpaks isolation from the rest of the system can be helpful in other ways too. So either learn to accept other packaging formats or learn to live with the fact that you may miss out on a lot if you don't invest a lot of time figuring out how to compile the software by hand. Am Mo., 1. Juli 2024 um 06:13 Uhr schrieb George at Clug < c...@goproject.info>: > Mostly I only install software that is available in the Debian or Arch > repositories, and I cannot find Bottles in the Debian Repository. I do not > use snaps or flatpacks. Maybe I should but I don't. > Hopefully one day, Bottles will mature to the point it can go through the > Debian packaging system. I appreciate Debian's packaging systems. >
Re: How to use Wine, How to get Gecko to install and work
Hello, Absolutely no idea if it will help you solve your problem but the Archwiki has an potentially interesting tip for reverting the Debian default behavior: https://wiki.archlinux.org/title/Wine#Prevent_installing_Mono/Gecko so, perhaps setting the WINEDLLOVERRIDES environment variable to something other than "mscoree=d;mshtml=d" (=e ?) could permit Wine to download/install internet explorer
Re: How to use Wine, How to get Gecko to install and work
On Monday, 01-07-2024 at 15:48 didier gaumet wrote: > Le 01/07/2024 à 01:24, George at Clug a écrit : > [...] > > I have not found useful documentation that can get me over the "Could not > > find Wine Gecko", "Failed to init Gecko" error messages. > [...] > > Hello, > > disclaimer: I have not used Wine in ages, so I cannot be of real help > > Note, you could tell what Debian distro you are using (12 Bookworm?) and Yes, Debian 12, Bookworm. (current stable) > if you have enabled multiarch support in it. yes. # dpkg --add-architecture i386 && apt update > > the Debian wiki page about Wine is here: > https://wiki.debian.org/Wine > it states that for whatever reason "Windows software may require Mono > for .NET, and Gecko for any HTML rendering. Debian has disabled these by > default and do not provide packages.": > Windows software may require Mono for .NET, and Gecko for any HTML > rendering. Debian has disabled these by default and do not provide > packages. I am now wondering what "is intentionally disabled" might actually mean. I am hoping that it means that Debian's wine will not automatically install Gecko/Mono, and not mean that even if you go ahead and manually install these packages they will not be used. But the effect seems to be the later. > > The WineHQ page about Gecko is here: > https://wiki.winehq.org/Gecko > > Two posts about solving Wine/Gecko problems on Debian Bookworm: > https://forums.debian.net/viewtopic.php?t=154513 > https://forum.winehq.org/viewtopic.php?t=38245 "...this year, running debian 12.2 "bookworm" on the same laptop and using the wine 8.0 delivered with "bookworm" I have been unable to get a working iexplore..." "Consider using a sandboxer such as firejail to sandbox wine, such a configuration is outside the scope of this guide. " "https://packages.debian.org/bookworm/firejail; - "Firejail is a SUID security sandbox program that reduces the risk of security breaches by restricting the running environment of untrusted applications using Linux namespaces and seccomp-bpf. It allows a process and all its descendants to have their own private view of the globally shared kernel resources, such as the network stack, process table, mount table. " Implementing Firejail sounds like a good project for later on. "You may wish to keep all your games in the same wine prefix, or have each game in its separate wine prefix. If you are using a traditional desktop environment, Wine will create .desktop files that remember the wineprefix for you. " Interesting links. And the same issue as I am having. I think I found these while searching for solutions. Sadly "$winetricks ie8" left me with a non=working iexplore. As far as I know, I have: "I created ~/.cache/wine and put the wine-gecko 2.47.3 msi there: " And added mono too. "apt install fonts-wine ttf-mscorefonts-installer" At one time I believe I also installed directly from WineHQ repository too, but after not much success, relating to 'no idea what I am doing' as far as setting up an environment for Windows programs, I reverted back to just using Debian's packages. https://wiki.winehq.org/Debian Well I might as well keep testing and trying... if I have any success, I will post back. Thanks for your comments, it gives me hope to keep working on this. George. > >
Re: How to use Wine, How to get Gecko to install and work
Le 01/07/2024 à 01:24, George at Clug a écrit : [...] I have not found useful documentation that can get me over the "Could not find Wine Gecko", "Failed to init Gecko" error messages. [...] Hello, disclaimer: I have not used Wine in ages, so I cannot be of real help Note, you could tell what Debian distro you are using (12 Bookworm?) and if you have enabled multiarch support in it. the Debian wiki page about Wine is here: https://wiki.debian.org/Wine it states that for whatever reason "Windows software may require Mono for .NET, and Gecko for any HTML rendering. Debian has disabled these by default and do not provide packages.": Windows software may require Mono for .NET, and Gecko for any HTML rendering. Debian has disabled these by default and do not provide packages. The WineHQ page about Gecko is here: https://wiki.winehq.org/Gecko Two posts about solving Wine/Gecko problems on Debian Bookworm: https://forums.debian.net/viewtopic.php?t=154513 https://forum.winehq.org/viewtopic.php?t=38245
Re: How to use Wine, How to get Gecko to install and work
Richard,
Thanks for your reply.
On Sunday, 30-06-2024 at 17:11 Richard wrote:
> Depends on what you are trying to do.
I am trying to understand how to use Wine so that I can install various Windows
programs and have them work.
With the knowledge I would like to help others who are even less technical than
myself, as some people have their favourite Windows program they still want to
run.
For example, I understand that you can test your Wine installation by using
iexplore, but this fails to display the page. I see it useful to resolve this
issue at this point before trying to install two other actual programs which I
would like to install but also have blank pages where there is supposed to be
text.
I have not found useful documentation that can get me over the "Could not find
Wine Gecko", "Failed to init Gecko" error messages.
$ wine iexplore
Could not find Wine Gecko. HTML rendering will be disabled.
010c:err:mshtml:create_document_object Failed to init Gecko, returning
CLASS_E_CLASSNOTAVAILABLE
Another issue I would like to resolve, is it possible to get a rpc service
running?. This service is not showing in Task Manager. I assume it is actually
possible, but I do know know how and have not succeeded.
err:ole:start_rpcss Failed to open RpcSs service
https://www.coretechnologies.com/blog/windows-services/rpcss/
Maybe some of these OLE messages are related to the RPC service?
074c:err:mscoree:CLRRuntimeInfo_GetRuntimeDirectory error reading registry key
for installroot
074c:err:ole:apartment_getclassobject DllGetClassObject returned error
0x80040111 for dll L"C:\\windows\\system32\\msimtf.dll"
074c:err:ole:com_get_class_object no class object
{c1ee01f2-b3b6-4a6a-9ddd-e988c088ec82} could be created for context 0x401
074c:err:ole:apartment_getclassobject DllGetClassObject returned error
0x80040111 for dll L"C:\\windows\\system32\\msimtf.dll"
074c:err:ole:com_get_class_object no class object
{c1ee01f2-b3b6-4a6a-9ddd-e988c088ec82} could be created for context 0x401
0330:err:rpc:I_RpcReceive we got fault packet with status 0xc004f012
0330:err:rpc:I_RpcReceive we got fault packet with status 0xc004f012
0330:err:rpc:I_RpcReceive we got fault packet with status 0xc004f012
> But in my experience, if you don't
> need to do some heavy work to maybe get something to work,
Now you have a point there. To be honest, there was only one Windows program I
personally wanted to run, and it is non-essential anyway (and it works in Wine
without changing the Wine installation).
PlayOnLinux is running one of the programs I have been testing with, but my
thoughts is that if PlayOnLinux can, then so should Wine. I just want to know
how to use Wine.
> take a look at
> Bottles [1].
Mostly I only install software that is available in the Debian or Arch
repositories, and I cannot find Bottles in the Debian Repository. I do not use
snaps or flatpacks. Maybe I should but I don't.
Hopefully one day, Bottles will mature to the point it can go through the
Debian packaging system. I appreciate Debian's packaging systems.
> It's kinda a GUI for Wine and Proton and seems to have some
> tricks up its sleeves. So take a look at it, maybe it can do everything you
> are trying to do.
>
> Best
> Richard
>
> [1]: https://usebottles.com/
>
> On Sun, Jun 30, 2024, 06:33 George at Clug wrote:
>
> > Hi,
> >
> > Does anyone know of really simple but comprehensive instructions on how to
> > use and configure Wine, that you can send me links to?
> >
> > [...]
> >
> >
> > George.
> >
> >
>
Re: How to use Wine, How to get Gecko to install and work
You can try this tool : https://github.com/winegui/WineGUI On Sun, Jun 30, 2024 at 1:58 PM Richard wrote: > Depends on what you are trying to do. But in my experience, if you don't > need to do some heavy work to maybe get something to work, take a look at > Bottles [1]. It's kinda a GUI for Wine and Proton and seems to have some > tricks up its sleeves. So take a look at it, maybe it can do everything you > are trying to do. > > Best > Richard > > [1]: https://usebottles.com/ > > On Sun, Jun 30, 2024, 06:33 George at Clug wrote: > >> Hi, >> >> Does anyone know of really simple but comprehensive instructions on how >> to use and configure Wine, that you can send me links to? >> >> [...] >> >> >> George. >> >> -- Mario.
Re: How to use Wine, How to get Gecko to install and work
Depends on what you are trying to do. But in my experience, if you don't need to do some heavy work to maybe get something to work, take a look at Bottles [1]. It's kinda a GUI for Wine and Proton and seems to have some tricks up its sleeves. So take a look at it, maybe it can do everything you are trying to do. Best Richard [1]: https://usebottles.com/ On Sun, Jun 30, 2024, 06:33 George at Clug wrote: > Hi, > > Does anyone know of really simple but comprehensive instructions on how to > use and configure Wine, that you can send me links to? > > [...] > > > George. > >
How to use Wine, How to get Gecko to install and work
Hi,
Does anyone know of really simple but comprehensive instructions on
how to use and configure Wine, that you can send me links to?
Does anyone know how to solve the below issue:
$ wine iexplore
Could not find Wine Gecko. HTML rendering will be disabled.
010c:err:mshtml:create_document_object Failed to init Gecko, returning
CLASS_E_CLASSNOTAVAILABLE
(Of course in iexplore the web page "https://www.winehq.org/; is
blank)
This is just one of many examples of how really don't know how to
configure Wine once it has been installed, and I have run "wine
winecfg".
I have found many people reporting this issue on the Internet, but
never an answer that resolves the issue for me.
$ wget
https://dl.winehq.org/wine/wine-mono/8.0.0/wine-mono-8.0.0-x86.msi
$ wget
https://dl.winehq.org/wine/wine-gecko/2.47.4/wine-gecko-2.47.4-x86.msi
$ wget
https://dl.winehq.org/wine/wine-gecko/2.47.4/wine-gecko-2.47.4-x86_64.msi
$ wine msiexec /i wine-mono-8.0.0-x86.msi
$ wine msiexec /i wine-gecko-2.47.4-x86.msi
$ wine msiexec /i wine-gecko-2.47.4-x864.msi
$ wine uninstaller --list
{F220C345-2975-4A47-8686-3F2C41F773B7}|||Wine Gecko (32-bit)
{AA28AA7D-CA50-44EB-AF34-7F99E4662CF1}|||Wine Gecko (64-bit)
{55B609D4-ABF3-52AF-8723-C81E75B86D50}|||Wine Mono Runtime
{9F22663D-4E4B-5B49-A04C-22EDFD519AC5}|||Wine Mono Windows Support
$ wine iexplore
Could not find Wine Gecko. HTML rendering will be disabled.
010c:err:mshtml:create_document_object Failed to init Gecko, returning
CLASS_E_CLASSNOTAVAILABLE
George.
Wine 32 y 64 simultáneamente
El 28/4/24 a las 17:15, JavierDebian escribió: Debian es hermoso Excepto con wine. Siempre lo instalo desde WineHQ. Hola, Gracias ¿ sabes si se puede instalar simultaneamente el 32 y 64 bits?¿ como funciona con Plauonlinux? Saludos, Julián bullseye es LTS, por lo que tendrá soporte hasta 30/03/2026 bookworm también, y estará hasta 30/06/2028 https://wiki.debian.org/LTS JAP -- Julian Daich Buen día. Sí, se puede, modificando los prefijos de los contenedores https://forum.winehq.org/viewtopic.php?t=37150 Una cosa: No secuestres hilos, es decir, cambiar el tópico del tema en una conversación. JAP
Re: Wine in bullseye, which way to go?
Am 02.02.2024 um 15:10:32 Uhr schrieb Greg Wooledge: > It's dying, I would say. Not all the way dead just yet. That's why I think it's time to change to amd64 before it is completely dead. > The next release will not offer an *installer* for i386, but upgrades > from Debian 12 i386 to Debian 13 i386 might continue to work. IIRC those packages will still exist for backwards compatibility for certain application, but I read the rumor that no current i386 kernel will be available. -- Gruß Marco Spam und Werbung bitte an ichschickerekl...@cartoonies.org
Re: Wine in bullseye, which way to go?
On 2/2/24 9:10 PM, Greg Wooledge wrote: I am not sure what do you mean by "install that architecture". I have been using i386 versions of Debian, and I do not plan to reinstall it now just because the CPU may allow that. At some point, you will have to make a decision. i386 is going to stop being supported sooner or later. Yeah, I know that. Until then I will try to get the most out of this i386 installation as-is. In any case, I managed to get rid of some 250+ amd64 packages that came with pretty useless wine (5.0.3-3) installation from the bullseye repo. After deinstalling wine & related software (in Synaptic), I ran apt-get update, apt-get upgrade, and apt autoremove. It freed cca 1GB. After reboot, all was clean, so I decided to go with wine via WineHQ. I followed their published procedure for bullseye installation, and after a while it ended up with wine version 9, which for now seems functional. Will update the list in days to come ... Misko
Re: Wine in bullseye, which way to go?
On Fri, Feb 2, 2024 at 2:59 PM Marco Moock wrote: > Am 01.02.2024 um 18:03:47 Uhr schrieb sko...@uns.ac.rs: > > > I am not sure what do you mean by "install that architecture". I have > > been using i386 versions of Debian, and I do not plan to reinstall it > > now just because the CPU may allow that. So instead, I ask whether it > > was expected and properly when Synaptic installed lots of 64-bit > > stuff during Wine installation from repo. Was it ok or not? Or shall > > I remove it and follow instructions from WineHQ website? > > According to documentation I found in the internet, it is possible to > upgrade a Debian system to the amd64 architecture. > Maybe do that, but do a full backup before. > > i386 is dead for Debian, the next release won't be available for i386. > It is about time i386 is killed off. 64bit processors have been in production for over 20 years now. I am all for getting the most out of hardware but considering you can get a Intel Core2 Laptop with 4GB of RAM for less that $100 refurbished there is no real reason to keep i386 around. As long as you have a i386 kernel, you can't use amd64 software on it. > > -- > Gruß > Marco > > Spam und Werbung bitte an ichschickerekl...@cartoonies.org > > -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/ ⠈⠳⣄⠀⠀
Re: Wine in bullseye, which way to go?
On Fri, Feb 02, 2024 at 08:59:18PM +0100, Marco Moock wrote: > According to documentation I found in the internet, it is possible to > upgrade a Debian system to the amd64 architecture. That isn't an upgrade, and it isn't a supported operation. Some people have *done* it, but it's very much at-your-own-risk. > Maybe do that, but do a full backup before. I wouldn't recommend it, certainly not for someone who's operating with less than a full understanding of the situation. > i386 is dead for Debian, the next release won't be available for i386. It's dying, I would say. Not all the way dead just yet. The next release will not offer an *installer* for i386, but upgrades from Debian 12 i386 to Debian 13 i386 might continue to work. That bears its own risks. Support for i386 is likely to be less than full. Things will probably start breaking and not getting fixed, more and more often as the years roll on, until it's officially declared dead. > As long as you have a i386 kernel, you can't use amd64 software on it. This is true. > Am 01.02.2024 um 18:03:47 Uhr schrieb sko...@uns.ac.rs: > > > I am not sure what do you mean by "install that architecture". I have > > been using i386 versions of Debian, and I do not plan to reinstall it > > now just because the CPU may allow that. At some point, you will have to make a decision. i386 is going to stop being supported sooner or later.
Re: Wine in bullseye, which way to go?
Am 01.02.2024 um 18:03:47 Uhr schrieb sko...@uns.ac.rs: > I am not sure what do you mean by "install that architecture". I have > been using i386 versions of Debian, and I do not plan to reinstall it > now just because the CPU may allow that. So instead, I ask whether it > was expected and properly when Synaptic installed lots of 64-bit > stuff during Wine installation from repo. Was it ok or not? Or shall > I remove it and follow instructions from WineHQ website? According to documentation I found in the internet, it is possible to upgrade a Debian system to the amd64 architecture. Maybe do that, but do a full backup before. i386 is dead for Debian, the next release won't be available for i386. As long as you have a i386 kernel, you can't use amd64 software on it. -- Gruß Marco Spam und Werbung bitte an ichschickerekl...@cartoonies.org
Re: Wine in bullseye, which way to go?
> Am 01.02.2024 schrieb sko...@uns.ac.rs: > >> CPU op-mode(s): 32-bit, 64-bit > Model name: Pentium(R) Dual-Core CPU T4500 > > That processor can run amd64 Debian, so install that architecture. > > I am not sure what do you mean by "install that architecture". I have been using i386 versions of Debian, and I do not plan to reinstall it now just because the CPU may allow that. So instead, I ask whether it was expected and properly when Synaptic installed lots of 64-bit stuff during Wine installation from repo. Was it ok or not? Or shall I remove it and follow instructions from WineHQ website?
Re: Wine in bullseye, which way to go?
Am 01.02.2024 schrieb sko...@uns.ac.rs: > CPU op-mode(s): 32-bit, 64-bit Model name: Pentium(R) Dual-Core CPU T4500 That processor can run amd64 Debian, so install that architecture.
Re: Wine in bullseye, which way to go?
> Am 01.02.2024 schrieb Miroslav Skoric : > >> This time I was puzzled when noticed that Synaptic installed lots of >> amd64 packages even though my system is i386. > > Run > uname -a > lscpu > > and post it here. > > If your system is i386 only, amd64 software can't run on it. > Remove that architecture from dpkg. > > uname -a Linux localhost 5.10.0-27-686 #1 SMP Debian 5.10.205-2 (2023-12-31) i686 GNU/Linux lscpu Architecture: i686 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian Address sizes: 36 bits physical, 48 bits virtual CPU(s): 2 On-line CPU(s) list:0,1 Thread(s) per core: 1 Core(s) per socket: 2 Socket(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 23 Model name: Pentium(R) Dual-Core CPU T4500 @ 2.30 GHz Stepping: 10 CPU MHz:1316.130 CPU max MHz:2300. CPU min MHz:1200. BogoMIPS: 4588.77 L1d cache: 64 KiB L1i cache: 64 KiB L2 cache: 1 MiB Vulnerability Gather data sampling: Not affected Vulnerability Itlb multihit:KVM: Mitigation: VMX unsupported Vulnerability L1tf: Vulnerable Vulnerability Mds: Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled Vulnerability Meltdown: Vulnerable Vulnerability Mmio stale data: Unknown: No mitigations Vulnerability Retbleed: Not affected Vulnerability Spec rstack overflow: Not affected Vulnerability Spec store bypass:Vulnerable Vulnerability Spectre v1: Mitigation; usercopy/swapgs barriers and __u ser pointer sanitization Vulnerability Spectre v2: Mitigation; Retpolines, STIBP disabled, RSB filling, PBRSB-eIBRS Not affected Vulnerability Srbds:Not affected Vulnerability Tsx async abort: Not affected Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ht tm pbe nx lm constant_ tsc arch_perfmon pebs bts cpuid aperfmperf p ni dtes64 monitor ds_cpl est tm2 ssse3 cx16 xtpr pdcm xsave lahf_lm dtherm
Re: Wine in bullseye, which way to go?
Am 01.02.2024 schrieb Miroslav Skoric : > This time I was puzzled when noticed that Synaptic installed lots of > amd64 packages even though my system is i386. Run uname -a lscpu and post it here. If your system is i386 only, amd64 software can't run on it. Remove that architecture from dpkg.
Wine in bullseye, which way to go?
Hi! As I have some Windows software (for ham radio) that does not have adequate Linux versions, I wanted to install Wine and some related packages from the bullseye repository (wine, q4wine, winetricks, playonlinux, etc). By the way, I had Wine with buster earlier, and most Windows software worked more or less flawlessly, but I deinstalled all that software and Wine before I upgraded buster to bullseye. This time I was puzzled when noticed that Synaptic installed lots of amd64 packages even though my system is i386. Also, it removed some packages, and also reported few errors or like. Finally, no Windows software wanted to run, instead q4wine returned "Exit -1" or like. See bellow some details for particular packages installation: (Wine) Removing portaudio19-dev:i386 (19.6.0-1.1) ... Removing libjack-dev (1:0.125.0-3+b1) ... dpkg: libjack0:i386: dependency problems, but removing anyway as you requested: mpv depends on libjack-jackd2-0 (>= 1.9.10+20150825) | libjack-0.125; however: Package libjack-jackd2-0 is not installed. Package libjack-0.125 is not installed. Package libjack0:i386 which provides libjack-0.125 is to be removed. mplayer depends on libjack-jackd2-0 (>= 1.9.10+20150825) | libjack-0.125; however: Package libjack-jackd2-0 is not installed. Package libjack-0.125 is not installed. Package libjack0:i386 which provides libjack-0.125 is to be removed. libportaudio2:i386 depends on libjack-jackd2-0 (>= 1.9.10+20150825) | libjack-0.125; however: Package libjack-jackd2-0 is not installed. Package libjack-0.125 is not installed. Package libjack0:i386 which provides libjack-0.125 is to be removed. libfluidsynth2:i386 depends on libjack-jackd2-0 (>= 1.9.10+20150825) | libjack-0.125; however: Package libjack-jackd2-0 is not installed. Package libjack-0.125 is not installed. Package libjack0:i386 which provides libjack-0.125 is to be removed. libavdevice58:i386 depends on libjack-jackd2-0 (>= 1.9.10+20150825) | libjack-0.125; however: Package libjack-jackd2-0 is not installed. Package libjack-0.125 is not installed. Package libjack0:i386 which provides libjack-0.125 is to be removed. libasound2-plugins:i386 depends on libjack-jackd2-0 (>= 1.9.10+20150825) | libjack-0.125; however: Package libjack-jackd2-0 is not installed. Package libjack-0.125 is not installed. Package libjack0:i386 which provides libjack-0.125 is to be removed. gstreamer1.0-plugins-good:i386 depends on libjack-jackd2-0 (>= 1.9.10+20150825) | libjack-0.125; however: Package libjack-jackd2-0 is not installed. Package libjack-0.125 is not installed. Package libjack0:i386 which provides libjack-0.125 is to be removed. Removing libjack0:i386 (1:0.125.0-3+b1) ... Setting up gcc-10-base:amd64 (10.2.1-6) ... Setting up libgcc-s1:amd64 (10.2.1-6) ... Setting up libcrypt1:amd64 (1:4.4.18-4) ... Setting up libc6:amd64 (2.31-13+deb11u7) ... Setting up libgpg-error0:amd64 (1.38-2) ... Setting up libgcrypt20:amd64 (1.8.7-6) ... Setting up liblz4-1:amd64 (1.9.3-2) ... Setting up liblzma5:amd64 (5.2.5-2.1~deb11u1) ... Setting up libzstd1:amd64 (1.4.8+dfsg-2.1) ... Setting up libexpat1:amd64 (2.2.10-2+deb11u5) ... Setting up libgraphite2-3:amd64 (1.3.14-1) ... Setting up liblcms2-2:amd64 (2.12~rc1-2) ... Setting up libpixman-1-0:amd64 (0.40.0-1.1~deb11u1) ... Setting up libcdparanoia0:amd64 (3.10.2+debian-13.1) ... Setting up ipp-usb (0.9.17-3+b4) ... ipp-usb.service is a disabled or a static unit, not starting it. Setting up libvo-amrwbenc0:amd64 (0.1.3-2) ... Setting up libxau6:amd64 (1:1.0.9-1) ... Setting up libraw1394-11:amd64 (2.1.2-2) ... Setting up libkeyutils1:amd64 (1.6.1-2) ... Setting up libgpm2:amd64 (1.20.7-8) ... Setting up libmpg123-0:amd64 (1.26.4-1) ... Setting up libogg0:amd64 (1.3.4-0.1) ... Setting up libspeex1:amd64 (1.2~rc1.2-1.1) ... Setting up libshine3:amd64 (3.1.1-2) ... Setting up libtwolame0:amd64 (0.4.0-2) ... Setting up libdatrie1:amd64 (0.2.13-1) ... Setting up libgsm1:amd64 (1.0.18-2) ... Setting up libvisual-0.4-0:amd64 (0.4.0-17) ... Setting up libcapi20-3:amd64 (1:3.27-3+b1) ... Setting up libglvnd0:amd64 (1.3.2-1) ... Setting up libssl1.1:amd64 (1.1.1w-0+deb11u1) ... Setting up libaom0:amd64 (1.0.0.errata1-3+deb11u1) ... Setting up libbrotli1:amd64 (1.0.9-2+b2) ... Setting up libsqlite3-0:amd64 (3.34.1-3) ... Setting up libsasl2-modules:amd64 (2.1.27+dfsg-2.1+deb11u1) ... Setting up libffi7:amd64 (3.3-6) ... Setting up libvkd3d1:i386 (1.1-5) ... Setting up libnghttp2-14:amd64 (1.43.0-1+deb11u1) ... Setting up libunistring2:amd64 (0.9.10-4) ... Setting up libdeflate0:amd64 (1.7-1) ... Setting up zlib1g:amd64 (1:1.2.11.dfsg-2+deb11u2) ... Setting up libidn2-0:amd64 (2.3.0-5) ... Setting up libcom-err2:amd64 (1.46.2-2) ... Setting up libgomp1:amd64 (10.2.1-6) ... Setting up libxvidcore4:amd64 (2:1.3.7-1) ... Setting up libunwind8:amd64 (1.3.2-2) ... Setting up libx264-160:amd64 (2:0.160.3011+gitcde9a93-2.1
Re: wine virtualbox ...
El PLayOnLinux és un assistent amb perfils d'instal·lació per a Wine. Inclou un perfil per a Garmin Express, la qual cosa vol dir que algú ja s'ha barallat abans amb les dificultats d'aquest aplicatiu, i ha automatitzat la recepta per a Wine mitjançant un perfil de PlayOnLinux. Altra gent documenta les seves experiències aquí: https://appdb.winehq.org/objectManager.php?sClass=application=17447 Evidentment una màquina virtual amb Windows a dins no porta tant maldecaps, però consumeix més recursos. El 4/11/23 a les 21:18, Jordi ha escrit: El dv. 03 de 11 de 2023 a les 08:14 +0100, en/na Narcis Garcia va escriure: El PlayOnLinux ja porta un assistent per a instal·lar l'aplicació de Garmin. Està a repositoris de Debian. He estat mirant això del PlayOnLinux i rés, Només és un altre instal.lador del wine, del qual en sorgeixen altres errors, prefereixo fer-ho a ma. De moment sembla que el wine em funciona però no és capaç d'accedir als dispositius usb, només ho pot fer com a unitats de disc, tal i com ho fa amb el Garmin. He pensat que en lloc d'instal.lar el virtualbox i trobar-me diversos problemes, millor fer un usb windows live ja que no és del meu interès sortir massa del programari natiu de Debian. Salutacions Jordi -- Narcis Garcia __ I'm using this dedicated address because personal addresses aren't masked enough at this mail public archive. Public archive administrator should remove and omit any @, dot and mailto combinations against automated addresses collectors.
Re: wine virtualbox ...
On Sat, 4 Nov 2023 at 21:18, Jordi <215...@runbox.com> wrote: > El dv. 03 de 11 de 2023 a les 08:14 +0100, en/na Narcis Garcia va > escriure: > > El PlayOnLinux ja porta un assistent per a instal·lar l'aplicació de > > Garmin. Està a repositoris de Debian. > > > > > > He estat mirant això del PlayOnLinux i rés, Només és un altre > instal.lador del wine, del qual en sorgeixen altres errors, prefereixo > fer-ho a ma. > > De moment sembla que el wine em funciona però no és capaç d'accedir als > dispositius usb, només ho pot fer com a unitats de disc, tal i com ho > fa amb el Garmin. He pensat que en lloc d'instal.lar el virtualbox i > trobar-me diversos problemes, millor fer un usb windows live ja que no > és del meu interès sortir massa del programari natiu de Debian. > Hola, Jordi, Si tens prou espai de disc i memòria tens l'opció de fer servir Windows en una màquina virtual. Amb libvirt, per exemple, prèviament a l'arrencada de la màquina virtual amb Windows, li pots assignar un dispositiu USB extern connectat (Garmin) amb visibilitat des de la màquina. T'ho comento per tal que no hagis de reiniciar Debian per iniciar l'USB amb el Windows Live. Cordialment, Josep > > Salutacions > > Jordi > > -- -- Salutacions...Josep --
Re: wine virtualbox ...
El dv. 03 de 11 de 2023 a les 08:14 +0100, en/na Narcis Garcia va escriure: > El PlayOnLinux ja porta un assistent per a instal·lar l'aplicació de > Garmin. Està a repositoris de Debian. > > He estat mirant això del PlayOnLinux i rés, Només és un altre instal.lador del wine, del qual en sorgeixen altres errors, prefereixo fer-ho a ma. De moment sembla que el wine em funciona però no és capaç d'accedir als dispositius usb, només ho pot fer com a unitats de disc, tal i com ho fa amb el Garmin. He pensat que en lloc d'instal.lar el virtualbox i trobar-me diversos problemes, millor fer un usb windows live ja que no és del meu interès sortir massa del programari natiu de Debian. Salutacions Jordi
Re: wine virtualbox ... Clau privada publicada
gràcies a veure si aquesta setmana ho puc fer. El 4 de novembre de 2023 19:58:47 CET, Narcis Garcia ha escrit: >Et recomano aquesta guia: >https://gnupg.org/howtos/ca/GPGMiniHowto-3.html > >Exportar una clau pública a un fitxer, com a còpia de seguretat i per a >enviar-la als contactes: >$ gpg --export -a "cor...@example.net" > publica.key > >Exportar una clau privada a un fitxer, com a còpia de seguretat i per a >reutilitzar-la en ordinadors PROPIS: >$ gpg --export-secret-key -a "cor...@example.net" > privada.key > > >El 4/11/23 a les 17:45, Marc FP Riseup ha escrit: >> Cert >> >> Jo no ho tinc gens clar això de claus publiques i privades però no sé on >> trobar informació al respecte que em pugui treure de dubtes. >> >> Gràcies >> >> >> El 3/11/2023 a les 8:35, Narcis Garcia ha escrit: >>> Aleshores, la clau privada en qüestió ha deixat de ser privada. >>> >>> Marc, et recomano MOLT que generis noves claus pel compte de correu-e (el >>> que no és de Gmail), i aleshores revoquis les claus que estaves fent servir. >>> >>> També tingues en compte que els missatges xifrats que haguessis rebut amb >>> aquelles claus ara exposades, han deixat de ser indesxifrables. >>> >>> >>> El 3/11/23 a les 8:27, Ernest Adrogué ha escrit: 2023-11- 3, 08:08 (+0100); Narcis Garcia escriu: > Ei Marc, has escrit amb un xifrat (suposo que per a la clau d'en Jordi), > però amb còpia a la llista. Et refereixes a aquest bloc? >> -BEGIN PGP PRIVATE KEY BLOCK- >> Version: GnuPG v2 >> >> lQPGBFh3b4wBCADcg72dc5yZ09XfZbMbDI/bkssf4We5Zb1y6gagJ6wx/hQxp5yI Sembla que no és un text xifrat, sinó més aviat una clau privada. Salutacions >>> >> > >-- > >Narcis Garcia > >__ >I'm using this dedicated address because personal addresses aren't masked >enough at this mail public archive. Public archive administrator should remove >and omit any @, dot and mailto combinations against automated addresses >collectors. >
Re: wine virtualbox ... Clau privada publicada
Et recomano aquesta guia: https://gnupg.org/howtos/ca/GPGMiniHowto-3.html Exportar una clau pública a un fitxer, com a còpia de seguretat i per a enviar-la als contactes: $ gpg --export -a "cor...@example.net" > publica.key Exportar una clau privada a un fitxer, com a còpia de seguretat i per a reutilitzar-la en ordinadors PROPIS: $ gpg --export-secret-key -a "cor...@example.net" > privada.key El 4/11/23 a les 17:45, Marc FP Riseup ha escrit: Cert Jo no ho tinc gens clar això de claus publiques i privades però no sé on trobar informació al respecte que em pugui treure de dubtes. Gràcies El 3/11/2023 a les 8:35, Narcis Garcia ha escrit: Aleshores, la clau privada en qüestió ha deixat de ser privada. Marc, et recomano MOLT que generis noves claus pel compte de correu-e (el que no és de Gmail), i aleshores revoquis les claus que estaves fent servir. També tingues en compte que els missatges xifrats que haguessis rebut amb aquelles claus ara exposades, han deixat de ser indesxifrables. El 3/11/23 a les 8:27, Ernest Adrogué ha escrit: 2023-11- 3, 08:08 (+0100); Narcis Garcia escriu: Ei Marc, has escrit amb un xifrat (suposo que per a la clau d'en Jordi), però amb còpia a la llista. Et refereixes a aquest bloc? -BEGIN PGP PRIVATE KEY BLOCK- Version: GnuPG v2 lQPGBFh3b4wBCADcg72dc5yZ09XfZbMbDI/bkssf4We5Zb1y6gagJ6wx/hQxp5yI Sembla que no és un text xifrat, sinó més aviat una clau privada. Salutacions -- Narcis Garcia __ I'm using this dedicated address because personal addresses aren't masked enough at this mail public archive. Public archive administrator should remove and omit any @, dot and mailto combinations against automated addresses collectors.
Re: wine virtualbox ... Clau privada publicada
Cert Jo no ho tinc gens clar això de claus publiques i privades però no sé on trobar informació al respecte que em pugui treure de dubtes. Gràcies El 3/11/2023 a les 8:35, Narcis Garcia ha escrit: Aleshores, la clau privada en qüestió ha deixat de ser privada. Marc, et recomano MOLT que generis noves claus pel compte de correu-e (el que no és de Gmail), i aleshores revoquis les claus que estaves fent servir. També tingues en compte que els missatges xifrats que haguessis rebut amb aquelles claus ara exposades, han deixat de ser indesxifrables. El 3/11/23 a les 8:27, Ernest Adrogué ha escrit: 2023-11- 3, 08:08 (+0100); Narcis Garcia escriu: Ei Marc, has escrit amb un xifrat (suposo que per a la clau d'en Jordi), però amb còpia a la llista. Et refereixes a aquest bloc? -BEGIN PGP PRIVATE KEY BLOCK- Version: GnuPG v2 lQPGBFh3b4wBCADcg72dc5yZ09XfZbMbDI/bkssf4We5Zb1y6gagJ6wx/hQxp5yI Sembla que no és un text xifrat, sinó més aviat una clau privada. Salutacions
Re: wine virtualbox ...
Aquest cap de setmana m´hi dedicaré, gracies. Salutacions Jordi El dv. 03 de 11 de 2023 a les 08:14 +0100, en/na Narcis Garcia va escriure: > El PlayOnLinux ja porta un assistent per a instal·lar l'aplicació de > Garmin. Està a repositoris de Debian. > > > El 2/11/23 a les 16:26, 215...@runbox.com ha escrit: > > Si, i ha anat força bé. Ara estic encallat però amb la gestió que > > fa > > wine amb els ports usb. Garmin Express s'executa però no troba el > > dispositiu suposo perquè no existeix /dev/ttyUSBx sinó alguna altra > > forma de arribar al dispositiu. > > Salutacions > > Jordi > > > > Sent from MailDroid <https://goo.gl/ODgwBb> > > > > -Original Message- > > From: Marc FP > > To: Jordi <215...@runbox.com> > > Cc: Debian User catala > > Sent: dj., 02 de nov. 2023 15:43 > > Subject: Re: wine virtualbox ... > > > > Suposo que ja ho has vist, però per si de cas... > > https://christitus.com/garmin-express-linux/ > > <https://christitus.com/garmin-express-linux/> > > No serveix aquest enllaç?? > > > > > > > > El dijous, 2 de novembre de 2023, Marc FP ( > <mailto:marc.fur...@gmail.com>>) va escriure: > > > Hola, > > > jo no puc ajudar-te, però si que et demano que ens diguis com ha > > acabat tot plegat.... > > > Gràcies per tot i molta sort!!! > > > > > > > > > El dijous, 2 de novembre de 2023, Jordi (<215...@runbox.com > > <mailto:215...@runbox.com>>) va escriure: > > >> Bon dia, estic intentant instal.lar wine per poder fer servir > > el > > >> programa "Garmin Express". Després de dos dies el wine i el > > "Garmin > > >> Express" funcionen entre cometes. L'ultim problema que m'ha > > sorgit és > > >> que no detecta l'usb ja que, suposo, /dev/ttyUSBx ja no > > existeix i no > > >> sé que ficar-li al "wine regedit", el rellotge si que queda > > muntat al > > >> linux com a disc. > > >> > > >> Em fa una mica de pudor tenir tot aquest microsoft instal.lat a > > >> l'ordinador. Algú te alguna experiència similar ? No sé si > > continuar > > >> trencant-me les banyes amb el wine, instal.lar virtualbox o no > > sé > > >> alguna idea? > > >> > > >> Salutacions > > >> Jordi. > > >> > > >> > > > > > > -- > > > -BEGIN PGP PRIVATE KEY BLOCK- > > > Version: GnuPG v2 > > > > > > lQPGBFh3b4wBCADcg72dc5yZ09XfZbMbDI/bkssf4We5Zb1y6gagJ6wx/hQxp5yI > > > wwnmVotwTmfLAyA2DDcNWIIfLFavhi5NZXk0h0XAEIfhIiSAiiNLAxX5XMNI66VI > > > WQyIYXQdkCQavbJQRioR3Es1upoLrPwIwCQSZv3gjNVWIBlUcfOApKVkHRcFIRcG > > > NDhzS/IIhIu7FvcHqh6/Md2P6G74s9qY+CAI3L3YdxciZhJQsgWvBmxNABFXwYXe > > > bKFoVicc29m/sm+aRLlEv16xmfZ74UnLIi3P7DB6+KTzdUGE2uvemR493Hdjn1Q/ > > > yYU7NnHOAMKmmSDskYZf0trIbsKS7tkTECdBABEBAAH+BwMC1djWmSY9LkPpqK78 > > > 3tPxyXnkP2gm+cKyCh6HhJZi0l1ANb4iP1fEua3Ncd3z/12C80R7e0QS/MmomjBV > > > ij8QXd14jlkYnuQJ8cgUNxTx1SB7XFaeu4bxWIjbJ/Fgyhv9gOUjTQi2vlI7h7R/ > > > ZHYCdACxJe8msW5UX60HKZ5nIiyXxiJoCzjvN04FIqxk0Oj95HUigrNm6L4yHFcz > > > qmBuc3GlQ6cLNVtoSVX9ol0azwAGlQGU4TEQpZ/uNgyvc3badmBF7FfGYZltNnkA > > > J5U5TGoMvJUnK9YxSh//8Jia9CU0kRANQcSS8LF3NszzjDHDoeHg+6TrwcgA4qHR > > > ZQ4cP0sNtQQQCISwgOUBpyeCdXionSSVtOi+n7RHee1hq3r703yp2lJUyy2fCyHs > > > 1baWAtXBRT7rCMWLviky+z9bRWAvtDj6I0xBdJuQLRv9bgYifS0AcrK6Yn0yjWD4 > > > F9Wqz/lMzaZlErMvvX2qBVsX+HW4Ea8Oi2UnFnwUsYuUAZWJL5SU3wEvq6UFnv1O > > > 3wUr4smykTtb3p7vYg3Vo10lDI65ybXxzMAWQ7S0+7AcpViGjXqxoYmldQc482k8 > > > yx/bLZ6FaT5nnL9trFVNju4CapPyXcQmRB3RL9NllwVyNQAeGbVuIyaf9pVop4NF > > > sAsaO34eCAAkyf+1XLaBoaav9cLN4iNXHcE1R1sPwN4XU8hKpb/ocTC+piIY3wNO > > > g9Szo61Yzt3NC1RwCdoKKsZ4kdCT2if0bTi+q7xj9sfpkByaWO2mjb+Dr58Hzzci > > > dUZcmCkUwAUXwlnVJhAEmVhWhta1Xg3qJXgB1Kh0AS3JwZe66xUE2lUJrRfn60q2 > > > rGfAcSjXtfTTXxqsBVy4/blxpLlc2HnytkNpguGp9C1KRJjpFvqDQ4NcaS54SmkE > > > fa5Cs/bTy8H+tCRtYXJjIGZ1cnRpw6AgPG1hcmNmdXJ0aWFAcmlzZXVwLm5ldD6J > > > ATcEEwEIACEFAlh3b4wCGwMFCwkIBwIGFQgJCgsCBBYCAwECHgECF4AACgkQPH9i > > > oVK9SwFd4wf9GBD+QIV2oRjxQsXQGSvRtUKJowod0iveKxcJpjskaGaX/qI2pEP8 > > > OH5E6XezO4p2/2NKceWFFxOpGSGGm10yVfwU4av2XksMKPcNt6fUjh+d9tJBb7Cz > > > JLUkpoNluqBj21lWCKo0CSqZ+dED8ZmAXC3pEq/C10mcj/7YaSJdgpFic61Y6k7y > > > vNUwjPivoOz3Mr8wil9kyt2WzGDljYoR+9CKHz7p
Re: wine virtualbox ... Clau privada publicada
Aleshores, la clau privada en qüestió ha deixat de ser privada. Marc, et recomano MOLT que generis noves claus pel compte de correu-e (el que no és de Gmail), i aleshores revoquis les claus que estaves fent servir. També tingues en compte que els missatges xifrats que haguessis rebut amb aquelles claus ara exposades, han deixat de ser indesxifrables. El 3/11/23 a les 8:27, Ernest Adrogué ha escrit: 2023-11- 3, 08:08 (+0100); Narcis Garcia escriu: Ei Marc, has escrit amb un xifrat (suposo que per a la clau d'en Jordi), però amb còpia a la llista. Et refereixes a aquest bloc? -BEGIN PGP PRIVATE KEY BLOCK- Version: GnuPG v2 lQPGBFh3b4wBCADcg72dc5yZ09XfZbMbDI/bkssf4We5Zb1y6gagJ6wx/hQxp5yI Sembla que no és un text xifrat, sinó més aviat una clau privada. Salutacions -- Narcis Garcia
Re: wine virtualbox ...
2023-11- 3, 08:08 (+0100); Narcis Garcia escriu: > Ei Marc, has escrit amb un xifrat (suposo que per a la clau d'en Jordi), > però amb còpia a la llista. Et refereixes a aquest bloc? > > -BEGIN PGP PRIVATE KEY BLOCK- > > Version: GnuPG v2 > > > > lQPGBFh3b4wBCADcg72dc5yZ09XfZbMbDI/bkssf4We5Zb1y6gagJ6wx/hQxp5yI Sembla que no és un text xifrat, sinó més aviat una clau privada. Salutacions
Re: wine virtualbox ...
El PlayOnLinux ja porta un assistent per a instal·lar l'aplicació de Garmin. Està a repositoris de Debian. El 2/11/23 a les 16:26, 215...@runbox.com ha escrit: Si, i ha anat força bé. Ara estic encallat però amb la gestió que fa wine amb els ports usb. Garmin Express s'executa però no troba el dispositiu suposo perquè no existeix /dev/ttyUSBx sinó alguna altra forma de arribar al dispositiu. Salutacions Jordi Sent from MailDroid <https://goo.gl/ODgwBb> -Original Message- From: Marc FP To: Jordi <215...@runbox.com> Cc: Debian User catala Sent: dj., 02 de nov. 2023 15:43 Subject: Re: wine virtualbox ... Suposo que ja ho has vist, però per si de cas... https://christitus.com/garmin-express-linux/ <https://christitus.com/garmin-express-linux/> No serveix aquest enllaç?? El dijous, 2 de novembre de 2023, Marc FP (<mailto:marc.fur...@gmail.com>>) va escriure: > Hola, > jo no puc ajudar-te, però si que et demano que ens diguis com ha acabat tot plegat > Gràcies per tot i molta sort!!! > > > El dijous, 2 de novembre de 2023, Jordi (<215...@runbox.com <mailto:215...@runbox.com>>) va escriure: >> Bon dia, estic intentant instal.lar wine per poder fer servir el >> programa "Garmin Express". Després de dos dies el wine i el "Garmin >> Express" funcionen entre cometes. L'ultim problema que m'ha sorgit és >> que no detecta l'usb ja que, suposo, /dev/ttyUSBx ja no existeix i no >> sé que ficar-li al "wine regedit", el rellotge si que queda muntat al >> linux com a disc. >> >> Em fa una mica de pudor tenir tot aquest microsoft instal.lat a >> l'ordinador. Algú te alguna experiència similar ? No sé si continuar >> trencant-me les banyes amb el wine, instal.lar virtualbox o no sé >> alguna idea? >> >> Salutacions >> Jordi. >> >> > > -- > -BEGIN PGP PRIVATE KEY BLOCK- > Version: GnuPG v2 > > lQPGBFh3b4wBCADcg72dc5yZ09XfZbMbDI/bkssf4We5Zb1y6gagJ6wx/hQxp5yI > wwnmVotwTmfLAyA2DDcNWIIfLFavhi5NZXk0h0XAEIfhIiSAiiNLAxX5XMNI66VI > WQyIYXQdkCQavbJQRioR3Es1upoLrPwIwCQSZv3gjNVWIBlUcfOApKVkHRcFIRcG > NDhzS/IIhIu7FvcHqh6/Md2P6G74s9qY+CAI3L3YdxciZhJQsgWvBmxNABFXwYXe > bKFoVicc29m/sm+aRLlEv16xmfZ74UnLIi3P7DB6+KTzdUGE2uvemR493Hdjn1Q/ > yYU7NnHOAMKmmSDskYZf0trIbsKS7tkTECdBABEBAAH+BwMC1djWmSY9LkPpqK78 > 3tPxyXnkP2gm+cKyCh6HhJZi0l1ANb4iP1fEua3Ncd3z/12C80R7e0QS/MmomjBV > ij8QXd14jlkYnuQJ8cgUNxTx1SB7XFaeu4bxWIjbJ/Fgyhv9gOUjTQi2vlI7h7R/ > ZHYCdACxJe8msW5UX60HKZ5nIiyXxiJoCzjvN04FIqxk0Oj95HUigrNm6L4yHFcz > qmBuc3GlQ6cLNVtoSVX9ol0azwAGlQGU4TEQpZ/uNgyvc3badmBF7FfGYZltNnkA > J5U5TGoMvJUnK9YxSh//8Jia9CU0kRANQcSS8LF3NszzjDHDoeHg+6TrwcgA4qHR > ZQ4cP0sNtQQQCISwgOUBpyeCdXionSSVtOi+n7RHee1hq3r703yp2lJUyy2fCyHs > 1baWAtXBRT7rCMWLviky+z9bRWAvtDj6I0xBdJuQLRv9bgYifS0AcrK6Yn0yjWD4 > F9Wqz/lMzaZlErMvvX2qBVsX+HW4Ea8Oi2UnFnwUsYuUAZWJL5SU3wEvq6UFnv1O > 3wUr4smykTtb3p7vYg3Vo10lDI65ybXxzMAWQ7S0+7AcpViGjXqxoYmldQc482k8 > yx/bLZ6FaT5nnL9trFVNju4CapPyXcQmRB3RL9NllwVyNQAeGbVuIyaf9pVop4NF > sAsaO34eCAAkyf+1XLaBoaav9cLN4iNXHcE1R1sPwN4XU8hKpb/ocTC+piIY3wNO > g9Szo61Yzt3NC1RwCdoKKsZ4kdCT2if0bTi+q7xj9sfpkByaWO2mjb+Dr58Hzzci > dUZcmCkUwAUXwlnVJhAEmVhWhta1Xg3qJXgB1Kh0AS3JwZe66xUE2lUJrRfn60q2 > rGfAcSjXtfTTXxqsBVy4/blxpLlc2HnytkNpguGp9C1KRJjpFvqDQ4NcaS54SmkE > fa5Cs/bTy8H+tCRtYXJjIGZ1cnRpw6AgPG1hcmNmdXJ0aWFAcmlzZXVwLm5ldD6J > ATcEEwEIACEFAlh3b4wCGwMFCwkIBwIGFQgJCgsCBBYCAwECHgECF4AACgkQPH9i > oVK9SwFd4wf9GBD+QIV2oRjxQsXQGSvRtUKJowod0iveKxcJpjskaGaX/qI2pEP8 > OH5E6XezO4p2/2NKceWFFxOpGSGGm10yVfwU4av2XksMKPcNt6fUjh+d9tJBb7Cz > JLUkpoNluqBj21lWCKo0CSqZ+dED8ZmAXC3pEq/C10mcj/7YaSJdgpFic61Y6k7y > vNUwjPivoOz3Mr8wil9kyt2WzGDljYoR+9CKHz7p+vS4JrR26ka83fPPAqWfgw1o > /QHrTFy6ujy3TpgwFPYQ3Dt8B+j2xP1UQO7pMNwp6BSFJAsg0lRXTepn+enDrH2d > yoriAC/0+7wL0GUtyrWN2yyqJQVYpwwT6J0DxgRYd2+MAQgAruVsIXU+I1gAq3IB > zh8w0LlNwbaWHCodtBU9fEU4eZCvpz8OLb+GoEVe4WI+LcxhiyJVc+EX16TpNziY > w54zufMsXo8UfBTGzvIBzWITKqA81pzOoVPTvP9GRmQ0oMw5gzEvNefmNfN400Tv > gSu575gofRr6SdfFScioN1fcTetP5hLE4DtDpoecoicwTLo186anzuCkqsh4p1ii > Gi+fBol6DW0J+3bl1gZPZStLHHGgG9q1vWpXJVfcATAFt2D1+q4DVux5adF2YgMi > jOEG+CncCcRekAxUgroyGyG/atp/c7CqmVgB7kxTdZ2cyHis3CaCcRWFQSavUMPb > 0hWB3wARAQAB/gcDArd4zGRFn/ol6bxUdVkubpZkrzfPUQN+Y5fhHtKsQUzX9CjA > ruWFIjYUTSUz2vrve6VOVcGqVpkRRp82HjiyFjd9oVkzq0Eo7DcdJi3XhzMoZV/k > KbwzAbw1nOrQLA2/uXg07+ujVhazypI6hkjQR/YLIJzkZ2XzD3gdYS2J8Eam5cOx > bdrH6EoigqR3KtA3W5tqcRMLfGBrBxMKVF6KySxIAUNgWbYQ8DJOto5YHwegqo4N > Qb6JNsd4QoaZo1tvCg6mlQYW3cOEe9P3uBgnw1nMYcAiHqU0NKgHNfzbepMgFey4 > bqfSqcl2FqiZw+h0R1RejDkbqXLEoBc7BzqgIHM5QmqUZO1/UaaYoVO6j4Pcb7ll > HbSx0foGK4gkOcIkgiCANNPiVpblX4ycHYq/PvwromP+haMI2e3RlNcRosJzJsnp > TF2/aM7oWCHnBO4m4WWnss+8/nIQ6XdcJBrzJSc21LPxU321BS5OE5xgEVs3ZgBC > JjZ
Re: wine virtualbox ...
Ei Marc, has escrit amb un xifrat (suposo que per a la clau d'en Jordi), però amb còpia a la llista. Com que la resta de subscriptorxs de la llista no tenim la clau PGP de desxifrat d'en Jordi (així ha de ser), doncs veiem un correu amb un bloc de text illegible. El 2/11/23 a les 15:33, Marc FP ha escrit: Hola, jo no puc ajudar-te, però si que et demano que ens diguis com ha acabat tot plegat Gràcies per tot i molta sort!!! El dijous, 2 de novembre de 2023, Jordi (<215...@runbox.com <mailto:215...@runbox.com>>) va escriure: > Bon dia, estic intentant instal.lar wine per poder fer servir el > programa "Garmin Express". Després de dos dies el wine i el "Garmin > Express" funcionen entre cometes. L'ultim problema que m'ha sorgit és > que no detecta l'usb ja que, suposo, /dev/ttyUSBx ja no existeix i no > sé que ficar-li al "wine regedit", el rellotge si que queda muntat al > linux com a disc. > > Em fa una mica de pudor tenir tot aquest microsoft instal.lat a > l'ordinador. Algú te alguna experiència similar ? No sé si continuar > trencant-me les banyes amb el wine, instal.lar virtualbox o no sé > alguna idea? > > Salutacions > Jordi. > > -- -BEGIN PGP PRIVATE KEY BLOCK- Version: GnuPG v2 lQPGBFh3b4wBCADcg72dc5yZ09XfZbMbDI/bkssf4We5Zb1y6gagJ6wx/hQxp5yI wwnmVotwTmfLAyA2DDcNWIIfLFavhi5NZXk0h0XAEIfhIiSAiiNLAxX5XMNI66VI WQyIYXQdkCQavbJQRioR3Es1upoLrPwIwCQSZv3gjNVWIBlUcfOApKVkHRcFIRcG NDhzS/IIhIu7FvcHqh6/Md2P6G74s9qY+CAI3L3YdxciZhJQsgWvBmxNABFXwYXe bKFoVicc29m/sm+aRLlEv16xmfZ74UnLIi3P7DB6+KTzdUGE2uvemR493Hdjn1Q/ yYU7NnHOAMKmmSDskYZf0trIbsKS7tkTECdBABEBAAH+BwMC1djWmSY9LkPpqK78 3tPxyXnkP2gm+cKyCh6HhJZi0l1ANb4iP1fEua3Ncd3z/12C80R7e0QS/MmomjBV ij8QXd14jlkYnuQJ8cgUNxTx1SB7XFaeu4bxWIjbJ/Fgyhv9gOUjTQi2vlI7h7R/ ZHYCdACxJe8msW5UX60HKZ5nIiyXxiJoCzjvN04FIqxk0Oj95HUigrNm6L4yHFcz qmBuc3GlQ6cLNVtoSVX9ol0azwAGlQGU4TEQpZ/uNgyvc3badmBF7FfGYZltNnkA J5U5TGoMvJUnK9YxSh//8Jia9CU0kRANQcSS8LF3NszzjDHDoeHg+6TrwcgA4qHR ZQ4cP0sNtQQQCISwgOUBpyeCdXionSSVtOi+n7RHee1hq3r703yp2lJUyy2fCyHs 1baWAtXBRT7rCMWLviky+z9bRWAvtDj6I0xBdJuQLRv9bgYifS0AcrK6Yn0yjWD4 F9Wqz/lMzaZlErMvvX2qBVsX+HW4Ea8Oi2UnFnwUsYuUAZWJL5SU3wEvq6UFnv1O 3wUr4smykTtb3p7vYg3Vo10lDI65ybXxzMAWQ7S0+7AcpViGjXqxoYmldQc482k8 yx/bLZ6FaT5nnL9trFVNju4CapPyXcQmRB3RL9NllwVyNQAeGbVuIyaf9pVop4NF sAsaO34eCAAkyf+1XLaBoaav9cLN4iNXHcE1R1sPwN4XU8hKpb/ocTC+piIY3wNO g9Szo61Yzt3NC1RwCdoKKsZ4kdCT2if0bTi+q7xj9sfpkByaWO2mjb+Dr58Hzzci dUZcmCkUwAUXwlnVJhAEmVhWhta1Xg3qJXgB1Kh0AS3JwZe66xUE2lUJrRfn60q2 rGfAcSjXtfTTXxqsBVy4/blxpLlc2HnytkNpguGp9C1KRJjpFvqDQ4NcaS54SmkE fa5Cs/bTy8H+tCRtYXJjIGZ1cnRpw6AgPG1hcmNmdXJ0aWFAcmlzZXVwLm5ldD6J ATcEEwEIACEFAlh3b4wCGwMFCwkIBwIGFQgJCgsCBBYCAwECHgECF4AACgkQPH9i oVK9SwFd4wf9GBD+QIV2oRjxQsXQGSvRtUKJowod0iveKxcJpjskaGaX/qI2pEP8 OH5E6XezO4p2/2NKceWFFxOpGSGGm10yVfwU4av2XksMKPcNt6fUjh+d9tJBb7Cz JLUkpoNluqBj21lWCKo0CSqZ+dED8ZmAXC3pEq/C10mcj/7YaSJdgpFic61Y6k7y vNUwjPivoOz3Mr8wil9kyt2WzGDljYoR+9CKHz7p+vS4JrR26ka83fPPAqWfgw1o /QHrTFy6ujy3TpgwFPYQ3Dt8B+j2xP1UQO7pMNwp6BSFJAsg0lRXTepn+enDrH2d yoriAC/0+7wL0GUtyrWN2yyqJQVYpwwT6J0DxgRYd2+MAQgAruVsIXU+I1gAq3IB zh8w0LlNwbaWHCodtBU9fEU4eZCvpz8OLb+GoEVe4WI+LcxhiyJVc+EX16TpNziY w54zufMsXo8UfBTGzvIBzWITKqA81pzOoVPTvP9GRmQ0oMw5gzEvNefmNfN400Tv gSu575gofRr6SdfFScioN1fcTetP5hLE4DtDpoecoicwTLo186anzuCkqsh4p1ii Gi+fBol6DW0J+3bl1gZPZStLHHGgG9q1vWpXJVfcATAFt2D1+q4DVux5adF2YgMi jOEG+CncCcRekAxUgroyGyG/atp/c7CqmVgB7kxTdZ2cyHis3CaCcRWFQSavUMPb 0hWB3wARAQAB/gcDArd4zGRFn/ol6bxUdVkubpZkrzfPUQN+Y5fhHtKsQUzX9CjA ruWFIjYUTSUz2vrve6VOVcGqVpkRRp82HjiyFjd9oVkzq0Eo7DcdJi3XhzMoZV/k KbwzAbw1nOrQLA2/uXg07+ujVhazypI6hkjQR/YLIJzkZ2XzD3gdYS2J8Eam5cOx bdrH6EoigqR3KtA3W5tqcRMLfGBrBxMKVF6KySxIAUNgWbYQ8DJOto5YHwegqo4N Qb6JNsd4QoaZo1tvCg6mlQYW3cOEe9P3uBgnw1nMYcAiHqU0NKgHNfzbepMgFey4 bqfSqcl2FqiZw+h0R1RejDkbqXLEoBc7BzqgIHM5QmqUZO1/UaaYoVO6j4Pcb7ll HbSx0foGK4gkOcIkgiCANNPiVpblX4ycHYq/PvwromP+haMI2e3RlNcRosJzJsnp TF2/aM7oWCHnBO4m4WWnss+8/nIQ6XdcJBrzJSc21LPxU321BS5OE5xgEVs3ZgBC JjZya2FgMnieeqa48Sb86rWO054CuWSWwm6z7Fmm6azuK/Hdq3NxRvoWbjeVjGWZ 7hGZv4VV9EMbGnM2C6/PK13dl3Ro3pIhWnEGV3mcPH0/aatuOdPJoeiquxgQkSID JUgl81VcSv8wH0xedV254xBhcio5zy9Nz7oapATKONXwLrLn7yjcYPOLesv/evEE Jcf4dGEdHOgXVqPKOG9hO5YinUCb4JhB6zOCbhuI2B/bJpRFHGPMSqjDcS70LV1d ekmSIjpmhCywo9xVvUSZGUr/cBoU+BUmtyrJoJeyFpNjNt14xtc//ka+Kqy6W3Yw pxSPtoOSMos5HL89o8E7MS0TVO0C2HphMFo82ou5Znz5DiswzTkKp4R4MpmTkq02 Oct+RNfpAqUYCAkG1IYvtZ2JC5Q1cSG3qIoTG1iCbFJ/1YkBHwQYAQgACQUCWHdv jAIbDAAKCRA8f2KhUr1LAeUKCAC6QT8yXBF7Q5PSNzx9B5lDYj7oDaMvz4o/BfQ3 K8uj969tVIAgaax3kqw2i2Z+NJQucW72QxLe0L7ryH9DGWV22IvSshP+yyI+iVLa q03O0wWahddl4eXVYb0rwL7S9NBoDa6degZsOrmca0Mxow9L8XumhTLtvnRE4rbA Ed7Wge5YAy+cg3beluzHtGq9KUFbWxn1LUiFYm/8+IisJUpcsNmDawoSTbh5ndDZ qFjntFvWBTTJXUPcjSs71EC4G1FvMKxqWIGZHpe/4CGneZB5eHn12GF1V8U1uBzQ r3VQzKb7AmM/wB81MqgB6MG7E9j8PfYbApzIOWn+xvrE4VPS =A2n2 -END PGP PRIVATE KEY BLOCK- -- Narcis Garcia __ I'm using this dedicated address because personal addresses aren't masked enough at
Re: wine virtualbox ...
Si, i ha anat força bé. Ara estic encallat però amb la gestió que fa wine amb els ports usb. Garmin Express s'executa però no troba el dispositiu suposo perquè no existeix /dev/ttyUSBx sinó alguna altra forma de arribar al dispositiu. Salutacions Jordi Sent from MailDroid -Original Message- From: Marc FP To: Jordi <215...@runbox.com> Cc: Debian User catala Sent: dj., 02 de nov. 2023 15:43 Subject: Re: wine virtualbox ... Suposo que ja ho has vist, però per si de cas... https://christitus.com/garmin-express-linux/ No serveix aquest enllaç?? El dijous, 2 de novembre de 2023, Marc FP () va escriure: > Hola, > jo no puc ajudar-te, però si que et demano que ens diguis com ha acabat tot plegat > Gràcies per tot i molta sort!!! > > > El dijous, 2 de novembre de 2023, Jordi (<215...@runbox.com>) va escriure: >> Bon dia, estic intentant instal.lar wine per poder fer servir el >> programa "Garmin Express". Després de dos dies el wine i el "Garmin >> Express" funcionen entre cometes. L'ultim problema que m'ha sorgit és >> que no detecta l'usb ja que, suposo, /dev/ttyUSBx ja no existeix i no >> sé que ficar-li al "wine regedit", el rellotge si que queda muntat al >> linux com a disc. >> >> Em fa una mica de pudor tenir tot aquest microsoft instal.lat a >> l'ordinador. Algú te alguna experiència similar ? No sé si continuar >> trencant-me les banyes amb el wine, instal.lar virtualbox o no sé >> alguna idea? >> >> Salutacions >> Jordi. >> >> > > -- > -BEGIN PGP PRIVATE KEY BLOCK- > Version: GnuPG v2 > > lQPGBFh3b4wBCADcg72dc5yZ09XfZbMbDI/bkssf4We5Zb1y6gagJ6wx/hQxp5yI > wwnmVotwTmfLAyA2DDcNWIIfLFavhi5NZXk0h0XAEIfhIiSAiiNLAxX5XMNI66VI > WQyIYXQdkCQavbJQRioR3Es1upoLrPwIwCQSZv3gjNVWIBlUcfOApKVkHRcFIRcG > NDhzS/IIhIu7FvcHqh6/Md2P6G74s9qY+CAI3L3YdxciZhJQsgWvBmxNABFXwYXe > bKFoVicc29m/sm+aRLlEv16xmfZ74UnLIi3P7DB6+KTzdUGE2uvemR493Hdjn1Q/ > yYU7NnHOAMKmmSDskYZf0trIbsKS7tkTECdBABEBAAH+BwMC1djWmSY9LkPpqK78 > 3tPxyXnkP2gm+cKyCh6HhJZi0l1ANb4iP1fEua3Ncd3z/12C80R7e0QS/MmomjBV > ij8QXd14jlkYnuQJ8cgUNxTx1SB7XFaeu4bxWIjbJ/Fgyhv9gOUjTQi2vlI7h7R/ > ZHYCdACxJe8msW5UX60HKZ5nIiyXxiJoCzjvN04FIqxk0Oj95HUigrNm6L4yHFcz > qmBuc3GlQ6cLNVtoSVX9ol0azwAGlQGU4TEQpZ/uNgyvc3badmBF7FfGYZltNnkA > J5U5TGoMvJUnK9YxSh//8Jia9CU0kRANQcSS8LF3NszzjDHDoeHg+6TrwcgA4qHR > ZQ4cP0sNtQQQCISwgOUBpyeCdXionSSVtOi+n7RHee1hq3r703yp2lJUyy2fCyHs > 1baWAtXBRT7rCMWLviky+z9bRWAvtDj6I0xBdJuQLRv9bgYifS0AcrK6Yn0yjWD4 > F9Wqz/lMzaZlErMvvX2qBVsX+HW4Ea8Oi2UnFnwUsYuUAZWJL5SU3wEvq6UFnv1O > 3wUr4smykTtb3p7vYg3Vo10lDI65ybXxzMAWQ7S0+7AcpViGjXqxoYmldQc482k8 > yx/bLZ6FaT5nnL9trFVNju4CapPyXcQmRB3RL9NllwVyNQAeGbVuIyaf9pVop4NF > sAsaO34eCAAkyf+1XLaBoaav9cLN4iNXHcE1R1sPwN4XU8hKpb/ocTC+piIY3wNO > g9Szo61Yzt3NC1RwCdoKKsZ4kdCT2if0bTi+q7xj9sfpkByaWO2mjb+Dr58Hzzci > dUZcmCkUwAUXwlnVJhAEmVhWhta1Xg3qJXgB1Kh0AS3JwZe66xUE2lUJrRfn60q2 > rGfAcSjXtfTTXxqsBVy4/blxpLlc2HnytkNpguGp9C1KRJjpFvqDQ4NcaS54SmkE > fa5Cs/bTy8H+tCRtYXJjIGZ1cnRpw6AgPG1hcmNmdXJ0aWFAcmlzZXVwLm5ldD6J > ATcEEwEIACEFAlh3b4wCGwMFCwkIBwIGFQgJCgsCBBYCAwECHgECF4AACgkQPH9i > oVK9SwFd4wf9GBD+QIV2oRjxQsXQGSvRtUKJowod0iveKxcJpjskaGaX/qI2pEP8 > OH5E6XezO4p2/2NKceWFFxOpGSGGm10yVfwU4av2XksMKPcNt6fUjh+d9tJBb7Cz > JLUkpoNluqBj21lWCKo0CSqZ+dED8ZmAXC3pEq/C10mcj/7YaSJdgpFic61Y6k7y > vNUwjPivoOz3Mr8wil9kyt2WzGDljYoR+9CKHz7p+vS4JrR26ka83fPPAqWfgw1o > /QHrTFy6ujy3TpgwFPYQ3Dt8B+j2xP1UQO7pMNwp6BSFJAsg0lRXTepn+enDrH2d > yoriAC/0+7wL0GUtyrWN2yyqJQVYpwwT6J0DxgRYd2+MAQgAruVsIXU+I1gAq3IB > zh8w0LlNwbaWHCodtBU9fEU4eZCvpz8OLb+GoEVe4WI+LcxhiyJVc+EX16TpNziY > w54zufMsXo8UfBTGzvIBzWITKqA81pzOoVPTvP9GRmQ0oMw5gzEvNefmNfN400Tv > gSu575gofRr6SdfFScioN1fcTetP5hLE4DtDpoecoicwTLo186anzuCkqsh4p1ii > Gi+fBol6DW0J+3bl1gZPZStLHHGgG9q1vWpXJVfcATAFt2D1+q4DVux5adF2YgMi > jOEG+CncCcRekAxUgroyGyG/atp/c7CqmVgB7kxTdZ2cyHis3CaCcRWFQSavUMPb > 0hWB3wARAQAB/gcDArd4zGRFn/ol6bxUdVkubpZkrzfPUQN+Y5fhHtKsQUzX9CjA > ruWFIjYUTSUz2vrve6VOVcGqVpkRRp82HjiyFjd9oVkzq0Eo7DcdJi3XhzMoZV/k > KbwzAbw1nOrQLA2/uXg07+ujVhazypI6hkjQR/YLIJzkZ2XzD3gdYS2J8Eam5cOx > bdrH6EoigqR3KtA3W5tqcRMLfGBrBxMKVF6KySxIAUNgWbYQ8DJOto5YHwegqo4N > Qb6JNsd4QoaZo1tvCg6mlQYW3cOEe9P3uBgnw1nMYcAiHqU0NKgHNfzbepMgFey4 > bqfSqcl2FqiZw+h0R1RejDkbqXLEoBc7BzqgIHM5QmqUZO1/UaaYoVO6j4Pcb7ll > HbSx0foGK4gkOcIkgiCANNPiVpblX4ycHYq/PvwromP+haMI2e3RlNcRosJzJsnp > TF2/aM7oWCHnBO4m4WWnss+8/nIQ6XdcJBrzJSc21LPxU321BS5OE5xgEVs3ZgBC > JjZya2FgMnieeqa48Sb86rWO054CuWSWwm6z7Fmm6azuK/Hdq3NxRvoWbjeVjGWZ > 7hGZv4VV9EMbGnM2C6/PK13dl3Ro3pIhWnEGV3mcPH0/aatuOdPJoeiquxgQkSID > JUgl81VcSv8wH0xedV254xBhcio5zy9Nz7oapATKONXwLrLn7yjcYPOLesv/evEE > Jcf4dGEdHOgXVqPKOG9hO5YinUCb4JhB6zOCbhuI2B/bJpRFHGPMSqjDcS70LV1d > ekmSIjpmhCywo9xVvUSZGUr/cBoU+BUmtyrJoJeyFpNjNt14xtc//ka+Kqy6W3Yw > pxSPtoOSMos5HL89o8E7MS0TVO0C2HphM
Re: wine virtualbox ...
Hola, jo no puc ajudar-te, però si que et demano que ens diguis com ha acabat tot plegat Gràcies per tot i molta sort!!! El dijous, 2 de novembre de 2023, Jordi (<215...@runbox.com>) va escriure: > Bon dia, estic intentant instal.lar wine per poder fer servir el > programa "Garmin Express". Després de dos dies el wine i el "Garmin > Express" funcionen entre cometes. L'ultim problema que m'ha sorgit és > que no detecta l'usb ja que, suposo, /dev/ttyUSBx ja no existeix i no > sé que ficar-li al "wine regedit", el rellotge si que queda muntat al > linux com a disc. > > Em fa una mica de pudor tenir tot aquest microsoft instal.lat a > l'ordinador. Algú te alguna experiència similar ? No sé si continuar > trencant-me les banyes amb el wine, instal.lar virtualbox o no sé > alguna idea? > > Salutacions > Jordi. > > -- -BEGIN PGP PRIVATE KEY BLOCK- Version: GnuPG v2 lQPGBFh3b4wBCADcg72dc5yZ09XfZbMbDI/bkssf4We5Zb1y6gagJ6wx/hQxp5yI wwnmVotwTmfLAyA2DDcNWIIfLFavhi5NZXk0h0XAEIfhIiSAiiNLAxX5XMNI66VI WQyIYXQdkCQavbJQRioR3Es1upoLrPwIwCQSZv3gjNVWIBlUcfOApKVkHRcFIRcG NDhzS/IIhIu7FvcHqh6/Md2P6G74s9qY+CAI3L3YdxciZhJQsgWvBmxNABFXwYXe bKFoVicc29m/sm+aRLlEv16xmfZ74UnLIi3P7DB6+KTzdUGE2uvemR493Hdjn1Q/ yYU7NnHOAMKmmSDskYZf0trIbsKS7tkTECdBABEBAAH+BwMC1djWmSY9LkPpqK78 3tPxyXnkP2gm+cKyCh6HhJZi0l1ANb4iP1fEua3Ncd3z/12C80R7e0QS/MmomjBV ij8QXd14jlkYnuQJ8cgUNxTx1SB7XFaeu4bxWIjbJ/Fgyhv9gOUjTQi2vlI7h7R/ ZHYCdACxJe8msW5UX60HKZ5nIiyXxiJoCzjvN04FIqxk0Oj95HUigrNm6L4yHFcz qmBuc3GlQ6cLNVtoSVX9ol0azwAGlQGU4TEQpZ/uNgyvc3badmBF7FfGYZltNnkA J5U5TGoMvJUnK9YxSh//8Jia9CU0kRANQcSS8LF3NszzjDHDoeHg+6TrwcgA4qHR ZQ4cP0sNtQQQCISwgOUBpyeCdXionSSVtOi+n7RHee1hq3r703yp2lJUyy2fCyHs 1baWAtXBRT7rCMWLviky+z9bRWAvtDj6I0xBdJuQLRv9bgYifS0AcrK6Yn0yjWD4 F9Wqz/lMzaZlErMvvX2qBVsX+HW4Ea8Oi2UnFnwUsYuUAZWJL5SU3wEvq6UFnv1O 3wUr4smykTtb3p7vYg3Vo10lDI65ybXxzMAWQ7S0+7AcpViGjXqxoYmldQc482k8 yx/bLZ6FaT5nnL9trFVNju4CapPyXcQmRB3RL9NllwVyNQAeGbVuIyaf9pVop4NF sAsaO34eCAAkyf+1XLaBoaav9cLN4iNXHcE1R1sPwN4XU8hKpb/ocTC+piIY3wNO g9Szo61Yzt3NC1RwCdoKKsZ4kdCT2if0bTi+q7xj9sfpkByaWO2mjb+Dr58Hzzci dUZcmCkUwAUXwlnVJhAEmVhWhta1Xg3qJXgB1Kh0AS3JwZe66xUE2lUJrRfn60q2 rGfAcSjXtfTTXxqsBVy4/blxpLlc2HnytkNpguGp9C1KRJjpFvqDQ4NcaS54SmkE fa5Cs/bTy8H+tCRtYXJjIGZ1cnRpw6AgPG1hcmNmdXJ0aWFAcmlzZXVwLm5ldD6J ATcEEwEIACEFAlh3b4wCGwMFCwkIBwIGFQgJCgsCBBYCAwECHgECF4AACgkQPH9i oVK9SwFd4wf9GBD+QIV2oRjxQsXQGSvRtUKJowod0iveKxcJpjskaGaX/qI2pEP8 OH5E6XezO4p2/2NKceWFFxOpGSGGm10yVfwU4av2XksMKPcNt6fUjh+d9tJBb7Cz JLUkpoNluqBj21lWCKo0CSqZ+dED8ZmAXC3pEq/C10mcj/7YaSJdgpFic61Y6k7y vNUwjPivoOz3Mr8wil9kyt2WzGDljYoR+9CKHz7p+vS4JrR26ka83fPPAqWfgw1o /QHrTFy6ujy3TpgwFPYQ3Dt8B+j2xP1UQO7pMNwp6BSFJAsg0lRXTepn+enDrH2d yoriAC/0+7wL0GUtyrWN2yyqJQVYpwwT6J0DxgRYd2+MAQgAruVsIXU+I1gAq3IB zh8w0LlNwbaWHCodtBU9fEU4eZCvpz8OLb+GoEVe4WI+LcxhiyJVc+EX16TpNziY w54zufMsXo8UfBTGzvIBzWITKqA81pzOoVPTvP9GRmQ0oMw5gzEvNefmNfN400Tv gSu575gofRr6SdfFScioN1fcTetP5hLE4DtDpoecoicwTLo186anzuCkqsh4p1ii Gi+fBol6DW0J+3bl1gZPZStLHHGgG9q1vWpXJVfcATAFt2D1+q4DVux5adF2YgMi jOEG+CncCcRekAxUgroyGyG/atp/c7CqmVgB7kxTdZ2cyHis3CaCcRWFQSavUMPb 0hWB3wARAQAB/gcDArd4zGRFn/ol6bxUdVkubpZkrzfPUQN+Y5fhHtKsQUzX9CjA ruWFIjYUTSUz2vrve6VOVcGqVpkRRp82HjiyFjd9oVkzq0Eo7DcdJi3XhzMoZV/k KbwzAbw1nOrQLA2/uXg07+ujVhazypI6hkjQR/YLIJzkZ2XzD3gdYS2J8Eam5cOx bdrH6EoigqR3KtA3W5tqcRMLfGBrBxMKVF6KySxIAUNgWbYQ8DJOto5YHwegqo4N Qb6JNsd4QoaZo1tvCg6mlQYW3cOEe9P3uBgnw1nMYcAiHqU0NKgHNfzbepMgFey4 bqfSqcl2FqiZw+h0R1RejDkbqXLEoBc7BzqgIHM5QmqUZO1/UaaYoVO6j4Pcb7ll HbSx0foGK4gkOcIkgiCANNPiVpblX4ycHYq/PvwromP+haMI2e3RlNcRosJzJsnp TF2/aM7oWCHnBO4m4WWnss+8/nIQ6XdcJBrzJSc21LPxU321BS5OE5xgEVs3ZgBC JjZya2FgMnieeqa48Sb86rWO054CuWSWwm6z7Fmm6azuK/Hdq3NxRvoWbjeVjGWZ 7hGZv4VV9EMbGnM2C6/PK13dl3Ro3pIhWnEGV3mcPH0/aatuOdPJoeiquxgQkSID JUgl81VcSv8wH0xedV254xBhcio5zy9Nz7oapATKONXwLrLn7yjcYPOLesv/evEE Jcf4dGEdHOgXVqPKOG9hO5YinUCb4JhB6zOCbhuI2B/bJpRFHGPMSqjDcS70LV1d ekmSIjpmhCywo9xVvUSZGUr/cBoU+BUmtyrJoJeyFpNjNt14xtc//ka+Kqy6W3Yw pxSPtoOSMos5HL89o8E7MS0TVO0C2HphMFo82ou5Znz5DiswzTkKp4R4MpmTkq02 Oct+RNfpAqUYCAkG1IYvtZ2JC5Q1cSG3qIoTG1iCbFJ/1YkBHwQYAQgACQUCWHdv jAIbDAAKCRA8f2KhUr1LAeUKCAC6QT8yXBF7Q5PSNzx9B5lDYj7oDaMvz4o/BfQ3 K8uj969tVIAgaax3kqw2i2Z+NJQucW72QxLe0L7ryH9DGWV22IvSshP+yyI+iVLa q03O0wWahddl4eXVYb0rwL7S9NBoDa6degZsOrmca0Mxow9L8XumhTLtvnRE4rbA Ed7Wge5YAy+cg3beluzHtGq9KUFbWxn1LUiFYm/8+IisJUpcsNmDawoSTbh5ndDZ qFjntFvWBTTJXUPcjSs71EC4G1FvMKxqWIGZHpe/4CGneZB5eHn12GF1V8U1uBzQ r3VQzKb7AmM/wB81MqgB6MG7E9j8PfYbApzIOWn+xvrE4VPS =A2n2 -END PGP PRIVATE KEY BLOCK-
Re: wine virtualbox ...
Suposo que ja ho has vist, però per si de cas... https://christitus.com/garmin-express-linux/ No serveix aquest enllaç?? El dijous, 2 de novembre de 2023, Marc FP () va escriure: > Hola, > jo no puc ajudar-te, però si que et demano que ens diguis com ha acabat tot plegat > Gràcies per tot i molta sort!!! > > > El dijous, 2 de novembre de 2023, Jordi (<215...@runbox.com>) va escriure: >> Bon dia, estic intentant instal.lar wine per poder fer servir el >> programa "Garmin Express". Després de dos dies el wine i el "Garmin >> Express" funcionen entre cometes. L'ultim problema que m'ha sorgit és >> que no detecta l'usb ja que, suposo, /dev/ttyUSBx ja no existeix i no >> sé que ficar-li al "wine regedit", el rellotge si que queda muntat al >> linux com a disc. >> >> Em fa una mica de pudor tenir tot aquest microsoft instal.lat a >> l'ordinador. Algú te alguna experiència similar ? No sé si continuar >> trencant-me les banyes amb el wine, instal.lar virtualbox o no sé >> alguna idea? >> >> Salutacions >> Jordi. >> >> > > -- > -BEGIN PGP PRIVATE KEY BLOCK- > Version: GnuPG v2 > > lQPGBFh3b4wBCADcg72dc5yZ09XfZbMbDI/bkssf4We5Zb1y6gagJ6wx/hQxp5yI > wwnmVotwTmfLAyA2DDcNWIIfLFavhi5NZXk0h0XAEIfhIiSAiiNLAxX5XMNI66VI > WQyIYXQdkCQavbJQRioR3Es1upoLrPwIwCQSZv3gjNVWIBlUcfOApKVkHRcFIRcG > NDhzS/IIhIu7FvcHqh6/Md2P6G74s9qY+CAI3L3YdxciZhJQsgWvBmxNABFXwYXe > bKFoVicc29m/sm+aRLlEv16xmfZ74UnLIi3P7DB6+KTzdUGE2uvemR493Hdjn1Q/ > yYU7NnHOAMKmmSDskYZf0trIbsKS7tkTECdBABEBAAH+BwMC1djWmSY9LkPpqK78 > 3tPxyXnkP2gm+cKyCh6HhJZi0l1ANb4iP1fEua3Ncd3z/12C80R7e0QS/MmomjBV > ij8QXd14jlkYnuQJ8cgUNxTx1SB7XFaeu4bxWIjbJ/Fgyhv9gOUjTQi2vlI7h7R/ > ZHYCdACxJe8msW5UX60HKZ5nIiyXxiJoCzjvN04FIqxk0Oj95HUigrNm6L4yHFcz > qmBuc3GlQ6cLNVtoSVX9ol0azwAGlQGU4TEQpZ/uNgyvc3badmBF7FfGYZltNnkA > J5U5TGoMvJUnK9YxSh//8Jia9CU0kRANQcSS8LF3NszzjDHDoeHg+6TrwcgA4qHR > ZQ4cP0sNtQQQCISwgOUBpyeCdXionSSVtOi+n7RHee1hq3r703yp2lJUyy2fCyHs > 1baWAtXBRT7rCMWLviky+z9bRWAvtDj6I0xBdJuQLRv9bgYifS0AcrK6Yn0yjWD4 > F9Wqz/lMzaZlErMvvX2qBVsX+HW4Ea8Oi2UnFnwUsYuUAZWJL5SU3wEvq6UFnv1O > 3wUr4smykTtb3p7vYg3Vo10lDI65ybXxzMAWQ7S0+7AcpViGjXqxoYmldQc482k8 > yx/bLZ6FaT5nnL9trFVNju4CapPyXcQmRB3RL9NllwVyNQAeGbVuIyaf9pVop4NF > sAsaO34eCAAkyf+1XLaBoaav9cLN4iNXHcE1R1sPwN4XU8hKpb/ocTC+piIY3wNO > g9Szo61Yzt3NC1RwCdoKKsZ4kdCT2if0bTi+q7xj9sfpkByaWO2mjb+Dr58Hzzci > dUZcmCkUwAUXwlnVJhAEmVhWhta1Xg3qJXgB1Kh0AS3JwZe66xUE2lUJrRfn60q2 > rGfAcSjXtfTTXxqsBVy4/blxpLlc2HnytkNpguGp9C1KRJjpFvqDQ4NcaS54SmkE > fa5Cs/bTy8H+tCRtYXJjIGZ1cnRpw6AgPG1hcmNmdXJ0aWFAcmlzZXVwLm5ldD6J > ATcEEwEIACEFAlh3b4wCGwMFCwkIBwIGFQgJCgsCBBYCAwECHgECF4AACgkQPH9i > oVK9SwFd4wf9GBD+QIV2oRjxQsXQGSvRtUKJowod0iveKxcJpjskaGaX/qI2pEP8 > OH5E6XezO4p2/2NKceWFFxOpGSGGm10yVfwU4av2XksMKPcNt6fUjh+d9tJBb7Cz > JLUkpoNluqBj21lWCKo0CSqZ+dED8ZmAXC3pEq/C10mcj/7YaSJdgpFic61Y6k7y > vNUwjPivoOz3Mr8wil9kyt2WzGDljYoR+9CKHz7p+vS4JrR26ka83fPPAqWfgw1o > /QHrTFy6ujy3TpgwFPYQ3Dt8B+j2xP1UQO7pMNwp6BSFJAsg0lRXTepn+enDrH2d > yoriAC/0+7wL0GUtyrWN2yyqJQVYpwwT6J0DxgRYd2+MAQgAruVsIXU+I1gAq3IB > zh8w0LlNwbaWHCodtBU9fEU4eZCvpz8OLb+GoEVe4WI+LcxhiyJVc+EX16TpNziY > w54zufMsXo8UfBTGzvIBzWITKqA81pzOoVPTvP9GRmQ0oMw5gzEvNefmNfN400Tv > gSu575gofRr6SdfFScioN1fcTetP5hLE4DtDpoecoicwTLo186anzuCkqsh4p1ii > Gi+fBol6DW0J+3bl1gZPZStLHHGgG9q1vWpXJVfcATAFt2D1+q4DVux5adF2YgMi > jOEG+CncCcRekAxUgroyGyG/atp/c7CqmVgB7kxTdZ2cyHis3CaCcRWFQSavUMPb > 0hWB3wARAQAB/gcDArd4zGRFn/ol6bxUdVkubpZkrzfPUQN+Y5fhHtKsQUzX9CjA > ruWFIjYUTSUz2vrve6VOVcGqVpkRRp82HjiyFjd9oVkzq0Eo7DcdJi3XhzMoZV/k > KbwzAbw1nOrQLA2/uXg07+ujVhazypI6hkjQR/YLIJzkZ2XzD3gdYS2J8Eam5cOx > bdrH6EoigqR3KtA3W5tqcRMLfGBrBxMKVF6KySxIAUNgWbYQ8DJOto5YHwegqo4N > Qb6JNsd4QoaZo1tvCg6mlQYW3cOEe9P3uBgnw1nMYcAiHqU0NKgHNfzbepMgFey4 > bqfSqcl2FqiZw+h0R1RejDkbqXLEoBc7BzqgIHM5QmqUZO1/UaaYoVO6j4Pcb7ll > HbSx0foGK4gkOcIkgiCANNPiVpblX4ycHYq/PvwromP+haMI2e3RlNcRosJzJsnp > TF2/aM7oWCHnBO4m4WWnss+8/nIQ6XdcJBrzJSc21LPxU321BS5OE5xgEVs3ZgBC > JjZya2FgMnieeqa48Sb86rWO054CuWSWwm6z7Fmm6azuK/Hdq3NxRvoWbjeVjGWZ > 7hGZv4VV9EMbGnM2C6/PK13dl3Ro3pIhWnEGV3mcPH0/aatuOdPJoeiquxgQkSID > JUgl81VcSv8wH0xedV254xBhcio5zy9Nz7oapATKONXwLrLn7yjcYPOLesv/evEE > Jcf4dGEdHOgXVqPKOG9hO5YinUCb4JhB6zOCbhuI2B/bJpRFHGPMSqjDcS70LV1d > ekmSIjpmhCywo9xVvUSZGUr/cBoU+BUmtyrJoJeyFpNjNt14xtc//ka+Kqy6W3Yw > pxSPtoOSMos5HL89o8E7MS0TVO0C2HphMFo82ou5Znz5DiswzTkKp4R4MpmTkq02 > Oct+RNfpAqUYCAkG1IYvtZ2JC5Q1cSG3qIoTG1iCbFJ/1YkBHwQYAQgACQUCWHdv > jAIbDAAKCRA8f2KhUr1LAeUKCAC6QT8yXBF7Q5PSNzx9B5lDYj7oDaMvz4o/BfQ3 > K8uj969tVIAgaax3kqw2i2Z+NJQucW72QxLe0L7ryH9DGWV22IvSshP+yyI+iVLa > q03O0wWahddl4eXVYb0rwL7S9NBoDa6degZsOrmca0Mxow9L8XumhTLtvnRE4rbA > Ed7Wge5YAy+cg3beluzHtGq9KUFbWxn1LUiFYm/8+IisJUpcsNmDawoSTbh5ndDZ > qFjntFvWBTTJXUPcjSs71EC4G1FvMKxqWIG
Re: wine virtualbox ...
El dj. 02 de 11 de 2023 a les 13:26 +0100, en/na Narcis Garcia va escriure: > Fa uns quants anys que jo també vaig intentar fer executar el > programari > de Garmin a GNU/Linux, i crec recordar que el problema era el mateix: > L'accés a USB. > > Em van quedar dues alternatives: Una màquina virtual (que jo feia amb > Qemu) i l'aplicació web de Garmin. > L'aplicació web de Garmin i andoid (Garmin connect) no actualitza el micro programari del rellotge, només és pot fer amb windows o mac amb Garmin Express. Salutacions Jordi
Re: wine virtualbox ...
Fa uns quants anys que jo també vaig intentar fer executar el programari de Garmin a GNU/Linux, i crec recordar que el problema era el mateix: L'accés a USB. Em van quedar dues alternatives: Una màquina virtual (que jo feia amb Qemu) i l'aplicació web de Garmin. El 2/11/23 a les 12:54, Jordi ha escrit: Bon dia, estic intentant instal.lar wine per poder fer servir el programa "Garmin Express". Després de dos dies el wine i el "Garmin Express" funcionen entre cometes. L'ultim problema que m'ha sorgit és que no detecta l'usb ja que, suposo, /dev/ttyUSBx ja no existeix i no sé que ficar-li al "wine regedit", el rellotge si que queda muntat al linux com a disc. Em fa una mica de pudor tenir tot aquest microsoft instal.lat a l'ordinador. Algú te alguna experiència similar ? No sé si continuar trencant-me les banyes amb el wine, instal.lar virtualbox o no sé alguna idea? Salutacions Jordi. -- Narcis Garcia __ I'm using this dedicated address because personal addresses aren't masked enough at this mail public archive. Public archive administrator should remove and omit any @, dot and mailto combinations against automated addresses collectors.
Re: Odd Wine issue with nvidia-tesla-470-driver
Disregard. I made a mistake and found the error in my ways.
Odd Wine issue with nvidia-tesla-470-driver
I found an odd issue on Debian Bookworm with nvidia-tesla-470-driver installed and the i386 arch installed as a secondary arch (dpkg --add-architecture i386). When installing wine it tries to pull in nvidia-390 packages and breaks. Has anyone seen this before or is there a workaround? I suspect nvidia-tesla-470-driver doesn't have as many packages in i386 as amd64 does -or- there is a dependency in wine that doesn't expects the normal nvidia-driver and not nvidia-tesla.
Re: debian stretch wine
mattias: > Ãr verkligen wine 5.1x det lägsta för stretch? Enl. https://packages.debian.org/search?keywords=wine=names=all=all sÃ¥ har stretch v1.8.7, ska du ha 5.0.3 är den anpassad till bullseye. > GÃ¥r inte uppgradera dÃ¥ hälften av speglarna är döda Finns det Ã¥tminstonde en spegel sÃ¥ gÃ¥r att uppgradera. Listan finns här: https://www.debian.org/mirror/list UmeÃ¥ verkar ha stretch: http://ftp.acc.umu.se/debian/dists/stretch/ > Men gÃ¥r väll inte ta wine frÃ¥n debian 10 och köra in? Normalt sett inte pga. beroenden. Du kan prova med att bygga frÃ¥n källkod, se längst ned pÃ¥: https://wiki.winehq.org/Download Hälsningar, /Karl Hammar
debian stretch wine
Jaja jag vet att stretch är tämligen gammaltMen har inget valÄr verkligen wine 5.1x det lägsta för stretch?Går inte uppgradera då hälften av speglarna är dödaMen går väll inte ta wine från debian 10 och köra in? Skickades från E-post för Windows
Re: [SOLVED] Re: crash with wine and nvidia-driver
Am Samstag, 15. Oktober 2022, 20:37:41 CEST schrieb piorunz: Hi Piotr, tried before as you suggested: deleting all configs of wine without success. I also tried wine7.0 from winehq, but this did not work and wanted to deinstall many of my applications, like digicam or similar. Hope, that debian will update wine soon to version 7, but maybe they will never do on debian/stable. Maybe in the next release Happy gaming and best regards Hans > On 15/10/2022 18:18, Hans wrote: > > Am Samstag, 15. Oktober 2022, 15:08:40 CEST schrieb piorunz: > > Hi Piotr, > > > > sadly this did not work. However, I got a solution: > > > > I purged all wine packages from debian, then reinstalled wine, but only > > minimalistic, say, all necessary packages. > > > > I spared all suggested packages - and it worked now. No crash any more and > > "primusrun glxgears -info" is now running. > > Great! But maybe it was wine configuration files, you seem to be using > only default profile ~/.wine, and maybe files there (Windows > installation so to speak) got corrupted. So not reinstallation necessary. > I suggest to delete/move/manipulate default profile ~/.wine next time, > to save time. And ultimately, you can start using Lutris to manage your > Wine profiles or do it manually by using shortcut for example: > WINEPREFIX=/home/path... wine something.exe > > And lastly if you serious about gaming then latest Wine is good option, > not using Wine 5 from Debian stable but latest and greatest Wine 7. > I am gaming on wine-staging (v7.18 at the moment) and it's great. > https://wiki.winehq.org/Debian > > -- > With kindest regards, Piotr. > > ⢀⣴⠾⠻⢶⣦⠀ > ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system > ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/ > ⠈⠳⣄
Re: [SOLVED] Re: crash with wine and nvidia-driver
On 15/10/2022 18:18, Hans wrote: Am Samstag, 15. Oktober 2022, 15:08:40 CEST schrieb piorunz: Hi Piotr, sadly this did not work. However, I got a solution: I purged all wine packages from debian, then reinstalled wine, but only minimalistic, say, all necessary packages. I spared all suggested packages - and it worked now. No crash any more and "primusrun glxgears -info" is now running. Great! But maybe it was wine configuration files, you seem to be using only default profile ~/.wine, and maybe files there (Windows installation so to speak) got corrupted. So not reinstallation necessary. I suggest to delete/move/manipulate default profile ~/.wine next time, to save time. And ultimately, you can start using Lutris to manage your Wine profiles or do it manually by using shortcut for example: WINEPREFIX=/home/path... wine something.exe And lastly if you serious about gaming then latest Wine is good option, not using Wine 5 from Debian stable but latest and greatest Wine 7. I am gaming on wine-staging (v7.18 at the moment) and it's great. https://wiki.winehq.org/Debian -- With kindest regards, Piotr. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/ ⠈⠳⣄
[SOLVED] Re: crash with wine and nvidia-driver
Am Samstag, 15. Oktober 2022, 15:08:40 CEST schrieb piorunz: Hi Piotr, sadly this did not work. However, I got a solution: I purged all wine packages from debian, then reinstalled wine, but only minimalistic, say, all necessary packages. I spared all suggested packages - and it worked now. No crash any more and "primusrun glxgears -info" is now running. Additionally also the games prior not working with nvidia legacy driver are working now, too. It looks for me, some additional package forced the crash, but I can nor say, which one. It is no need, to look at, because wine in debian/stable is rather old (it is version 5, whilst the actual version is now version 7). I suppose, debian will update this package soon, as even for debian/stable version 5 is too old IMHO. Thank you all for any help. Best regards Hans > On 13/10/2022 17:43, Hans wrote: > > As I am not believing, this is related to the game (as ALL games are > > crashing), I believe, it is related to a systematical error in the > > relationship between wine and nvidia-driver. > > To verify this hypothesis, run for example: > primusrun wine notepad.exe > primusrun winecfg > > See if that opens. > > -- > With kindest regards, Piotr. > > ⢀⣴⠾⠻⢶⣦⠀ > ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system > ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/ > ⠈⠳⣄
Re: crash with wine and nvidia-driver
On 13/10/2022 17:43, Hans wrote: As I am not believing, this is related to the game (as ALL games are crashing), I believe, it is related to a systematical error in the relationship between wine and nvidia-driver. To verify this hypothesis, run for example: primusrun wine notepad.exe primusrun winecfg See if that opens. -- With kindest regards, Piotr. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/ ⠈⠳⣄
running outdated software (was: crash with wine and nvidia-driver)
Am 13.10.2022 um 18:43 schrieb Hans: > Hi folks, > > maybe someone got into the same problem as me and can help. Well, i cannot help. Sorry But i am very used to running outdated software, as i am living the old recipe to "never change a working system". The only thing, that i am doing is to separate different configurations into virtual machines, where i still am able to run Windows XP (as an example). Intentionally i am accepting to fall back in time, if the alternatove is to deal with buggy software or combinations thereof. Only recently, i discovered, that one of my long-living problems that had me stay with a 6 year old software combination is no longer present in a more recent software stack. In order to find out such changes, i HAVE TO check the functionality of more recent releases from time to time, which - in order to ensure proper isolation from my main system - requires a second bootable copy of the main OS. Long story short: I suggest you create alternatives in order to check more recent software. Because not only your situation tennds to evolve into a more and more unique corner case, but also you lose touch to the cutting edge of developers, who would not be interested to fix past problems, as there is practically no merit in doing so. Another example of mine: I did stay with firefox-esr from 2 years ago, in order of being able to use plugins, that had not yet been transformed to the new mozilla doctrine. But after some time, i found another combination of plugins fulfilling my needs just as well as the old ones did, so i decided to jump to a more recent version of the fox. It is not such a bright idea to be stubborn and sticking to the older versions, among ther reasons: because i would have turned onto the only one (world-wide) using that specific software stack, thus having a unique fingerprint and killing anonymity... I suggest not clinging to your specific software combo too frenetically. But i am sharing your sort of trouble more or less regularly and thus feel with you. best of luck, DdB > As I am not believing, this is related to the game (as ALL games are > crashing), I believe, it is related to a systematical error in the > relationship between wine and nvidia-driver. My own experiences with wine were not all that pleasant. Nowadays, i try to avoid it as best as i can, nuked all the places, where i had integrated it into my regular system usage. > (...) > So, I hope, someone might got into the same issue, too, and could fix it. > > Any help is welcome. > > Thank you very much! > > Best regards > > Hans
crash with wine and nvidia-driver
Hi folks, maybe someone got into the same problem as me and can help. I am using a laptop with a graphic chip in the intel-cpu and an extern graphic card from NVidia. The nvidia chip is an NVS4200M and running with kernel module *legacy-340xx* Yes, I know, NVidia and also Debian says, it shall be *-legacy-390xx-*, but 390xx will not run. 340xx is well running, and "primusrun glxgears -info" is telling, the kernel is loaded and it is the nvidia kernel/module. But that should not be our problem. My issue is, that starting ANY wine application (like a game or something else) using "primusrun wine bla.exe" is turning ito a segfault. As I am not believing, this is related to the game (as ALL games are crashing), I believe, it is related to a systematical error in the relationship between wine and nvidia-driver. Please note: Running all these applications without primusrun or optirun, so using the internal graphic chip, everything is running, but slow. I read in many forums, but whenever thisissue appears, the writers are always pointing to a special game or application, but (maybe) did not recognize, this is a general issue. The system running here is debian/stable and I know, the wine version is rather old (version 5, the actual one is version 7.x), but I personally believe, this should not amtter, as the nvidia driver 340xx is old, too. Note beside: 390xx and 340xx can not be build any more, as the kernel-header- files or the compiler had changed since 5.10.12, some files are missing. There is already a bugreport related to this by me. (Luckily I have a package as backup available). I do not know, where to look any more and how to discover, what is happening. Tried starting using strace, but this did not show me any usefull output. So, I hope, someone might got into the same issue, too, and could fix it. Any help is welcome. Thank you very much! Best regards Hans
[SOLVED] Re: Can not get wine-repo authenticated
Am Sonntag, 21. August 2022, 10:23:38 CEST schrieb Hans: I am answering myself: The problem was caused by the following entry: > > - added the repo > echo deb [signed-by=/usr/share/keyrings/winehq-archive-keyring.gpg] > http://dl.winehq.org/wine-builds/debian/ bullseye main | tee > /etc/apt/sources.list.d/ winehq.list > The term "[signed-by=/usr/share/keyrings/winehq-archive-keyring.gpg]" is somehow not been used by debian and makes this problem. After deleting this entry, it worked perfectly. So the correct entry in /etc/apt/sourceslist.d/ winehq.list should be just this: deb http://dl.winehq.org/wine-builds/debian/ bullseye main Hope this helps others, too. Best regards Hans
Can not get wine-repo authenticated
Dear list, I tried to add wine-repo to the sources list, but debian will not recognize its key. Since apt-key is deprecated I did as recommended: Logged in as root (I never use sudo) - Then did the command curl https://dl.winehq.org/wine-builds/winehq.key | gpg --dearmor > /usr/share/keyrings/winehq- archive-keyring.gpg % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 100 3220 100 32200 0 18192 0 --:--:-- --:--:-- --:--:-- 18089 - Verified the key is in /usr/share/keyrings/ - added the repo echo deb [signed-by=/usr/share/keyrings/winehq-archive-keyring.gpg] http://dl.winehq.org/wine-builds/debian/ bullseye main | tee /etc/apt/sources.list.d/ winehq.list - checked the entry in /etc/apt/sources.list.d/winehq.list deb [signed-by=/usr/share/keyrings/winehq-archive-keyring.gpg] http://dl.winehq.org/wine-builds/debian/ bullseye main - as it looks all good, doing: LANG=C apt update Hit:11 https://linux.teamviewer.com/deb stable InRelease Hit:12 https://deb.opera.com/opera-stable stable InRelease Hit:13 http://inverse.ca/downloads/PacketFence/debian/11.3 bullseye InRelease Err:4 http://dl.winehq.org/wine-builds/debian bullseye InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 76F1A20FF987672F Hit:14 https://www.kismetwireless.net/repos/apt/release/bullseye bullseye InRelease Reading package lists... Done *W: *GPG error: http://dl.winehq.org/wine-builds/debian bullseye InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 76F1A20FF987672F *E: *The repository 'http://dl.winehq.org/wine-builds/debian bullseye InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. I rechecked several times, but can not find, why the key is not recognized. The only reason I could imagine, that the key is orphaned. But then the doku of wine on its site is also orphaned. What did I miss? Any ideas? Best regards Hans
Re: Wine fails because of missing libgcc_s_dw2-1.dll
Hello! Opened a bug report against Wine, because I was not sure about what package was the culprit. #1006725 It was reasigned to libz-mingw-w64 and a few moments ago I downloaded the updated package from the repository. Everything works fine now. Thanks to everyone who made this possible.
Re: Wine fails because of missing libgcc_s_dw2-1.dll
On Donnerstag, 3. März 2022 12:17:37 -03 Miguel A. Vallejo wrote: > Thank you! > > I filled a bug report. Let's see what happens now. Just because I mentioned installing DLLs by means of winetricks: beware of using winetricks in this situation. Obviously it installs DLLs which are not compatible with the current wine packages. After trying this I had some Win-programs coming up nicely, or even better than before the Debian Sid updates but went haywire when they started their own update routines of data. Trying to resolve this and by using wintricks for some DLLs I now managed to have the programs start and appear as running applications but they are not showing any windows in X11 - duh ... -- Eike Lantzsch ZP6CGE
Re: Wine fails because of missing libgcc_s_dw2-1.dll
Thank you! I filled a bug report. Let's see what happens now.
Re: Wine fails because of missing libgcc_s_dw2-1.dll
> I'm looking for the exact package that contains zlib1.dll but I can't > find it. Libwine depends on libz-mingw-w64 but the zlib1.dll there is > not the same as the one wine puts in the drive_c directory. The one in > drive_c directory is a PE32 DLL and the one provided with > libz-mingw-w64 is a 64 bit one. On Stable: apt-file search zlib1.dll libterralib-doc: /usr/share/doc/libterralib-dev/examples/Debug/zlib1.dll libz-mingw-w64: /usr/i686-w64-mingw32/lib/zlib1.dll libz-mingw-w64: /usr/x86_64-w64-mingw32/lib/zlib1.dll Seems both 32 and 64 bit dll are included in the package. Regards, Christian -- http://www.cb-fraggle.de
Re: Wine fails because of missing libgcc_s_dw2-1.dll
> > I'm pretty sure the problem is the Wine DLL files were built without > > the -static-libgcc flag > > > > Time to file a bug? > > > > I think it is I'm looking for the exact package that contains zlib1.dll but I can't find it. Libwine depends on libz-mingw-w64 but the zlib1.dll there is not the same as the one wine puts in the drive_c directory. The one in drive_c directory is a PE32 DLL and the one provided with libz-mingw-w64 is a 64 bit one. I confirmed zlib1.dll needs libgcc_s_dw2-1.dll and this one needs libwinpthread-1.dll and... I can see a DLL hell in advance. Where does this zlib1.dll come from? It appears everytime wine creates a drive_c directory, even for a new user.
Re: Wine fails because of missing libgcc_s_dw2-1.dll
On donderdag 03 maart 2022 14:38:32 (+01:00), Miguel A. Vallejo wrote: > > Not entirely sure, but I think this is the issue: > > More and more Wine DLL files are built with mingw. > > The libwine package already depends on libz-mingw. > > Probably the 'gcc-mingw-w64-i686-win32-runtime' package should now be > > installed as well. > > > > Does the program work when you install this package? > > Installed gcc-mingw-w64-i686-win32-runtime (and gcc-mingw-w64-base > because of dependencies) but still not working. > > These packages install some DLLs in /usr/lib/gcc/i686-w64-mingw32 so > win32 programs can't load them there. Also note libgcc_s_dw2-1.dll is > not provided with these packages. > Strange, I get: $ dpkg -L gcc-mingw-w64-i686-win32-runtime | grep libgcc_s /usr/lib/gcc/i686-w64-mingw32/10-win32/libgcc_s_dw2-1.dll I had hoped that the Wine packages would refer to that, but unfortunately that is not the case. > I'm pretty sure the problem is the Wine DLL files were built without > the -static-libgcc flag > > Time to file a bug? > I think it is
Re: Wine fails because of missing libgcc_s_dw2-1.dll
> Not entirely sure, but I think this is the issue: > More and more Wine DLL files are built with mingw. > The libwine package already depends on libz-mingw. > Probably the 'gcc-mingw-w64-i686-win32-runtime' package should now be > installed as well. > > Does the program work when you install this package? Installed gcc-mingw-w64-i686-win32-runtime (and gcc-mingw-w64-base because of dependencies) but still not working. These packages install some DLLs in /usr/lib/gcc/i686-w64-mingw32 so win32 programs can't load them there. Also note libgcc_s_dw2-1.dll is not provided with these packages. I'm pretty sure the problem is the Wine DLL files were built without the -static-libgcc flag Time to file a bug?
Re: Wine fails because of missing libgcc_s_dw2-1.dll
On woensdag 02 maart 2022 20:01:09 (+01:00), Miguel A. Vallejo wrote: > Hello > > After the recent update of Wine packages in Sid, some programs do not > run because of a missing libgcc_s_dw2-1.dll. They all worked just fine > with the previous version. > > ~$ wine SpaceEngine.exe > 014c:err:module:import_dll Library libgcc_s_dw2-1.dll (which is needed > by L"Z:\\home\\eoz\\Programs\\SpaceEngine\\system\\zlib1.dll") not > found > 014c:err:module:import_dll Loading library zlib1.dll (which is needed > by L"Z:\\home\\eoz\\Programs\\SpaceEngine\\system\\libtiff3.dll") > failed ( > error c07b). > 014c:err:module:import_dll Library libtiff3.dll (which is needed by > L"Z:\\home\\eoz\\Programs\\SpaceEngine\\system\\SpaceEngine.exe") not > found > 014c:err:module:LdrInitializeThunk Importing dlls for > L"Z:\\home\\eoz\\Programs\\SpaceEngine\\system\\SpaceEngine.exe" > failed, status c135 > > I looked in my backups and I never had any libgcc_s_dw2-1.dll > installed in my system, but now it seems to be needed. > > Any ideas? Thanks in advance > > Not entirely sure, but I think this is the issue: More and more Wine DLL files are built with mingw. The libwine package already depends on libz-mingw. Probably the 'gcc-mingw-w64-i686-win32-runtime' package should now be installed as well. Does the program work when you install this package?
Re: Wine fails because of missing libgcc_s_dw2-1.dll
On Mittwoch, 2. März 2022 18:34:22 -03 Miguel A. Vallejo wrote:
> Hello!
>
> Finding and placing missing DLLs into the Windows directory of Wine is
> easy.
>
> I think the problem is the windows executables in wine have not been
> compiled with the -static-libgcc option of MinGW, so not including all
> these libgcc DDLs can be considered a bug itself.
>
> But compiling it without -static-libgcc can be considered a bug also.
>
> This is why I'm asking.
We are talking about closed source here, don't we? I don't see any
straight forward way to know how the programs have been compiled except
reverse engineering. Not going to do that. Contacting the provider of
the Windows-Programs IMHO would not help either because "it works on xxx
version of MS-Windows".
If the problem is a bug or changes in Wine (6.0.2 is a development
version - no?) Wine-HQ would be the right place to ask, I think.
Either way debian-users does not seem to be the right mailing list for
this kind of problems.
Unless this is a packaging problem ("...repack..."?) but I don't know.
I can't help I'm afraid.
..._ _.__ __... ...__
._._.
--
Eike Lantzsch ZP6CGE
Re: Wine fails because of missing libgcc_s_dw2-1.dll
Hello! Finding and placing missing DLLs into the Windows directory of Wine is easy. I think the problem is the windows executables in wine have not been compiled with the -static-libgcc option of MinGW, so not including all these libgcc DDLs can be considered a bug itself. But compiling it without -static-libgcc can be considered a bug also. This is why I'm asking.
Re: Wine fails because of missing libgcc_s_dw2-1.dll
On Mittwoch, 2. März 2022 16:01:09 -03 Miguel A. Vallejo wrote: > Hello > > After the recent update of Wine packages in Sid, some programs do not > run because of a missing libgcc_s_dw2-1.dll. They all worked just fine > with the previous version. > > ~$ wine SpaceEngine.exe > 014c:err:module:import_dll Library libgcc_s_dw2-1.dll (which is needed > by L"Z:\\home\\eoz\\Programs\\SpaceEngine\\system\\zlib1.dll") not > found > 014c:err:module:import_dll Loading library zlib1.dll (which is needed > by L"Z:\\home\\eoz\\Programs\\SpaceEngine\\system\\libtiff3.dll") > failed ( > error c07b). > 014c:err:module:import_dll Library libtiff3.dll (which is needed by > L"Z:\\home\\eoz\\Programs\\SpaceEngine\\system\\SpaceEngine.exe") not > found > 014c:err:module:LdrInitializeThunk Importing dlls for > L"Z:\\home\\eoz\\Programs\\SpaceEngine\\system\\SpaceEngine.exe" > failed, status c135 > > I looked in my backups and I never had any libgcc_s_dw2-1.dll > installed in my system, but now it seems to be needed. > > Any ideas? Thanks in advance Hi Hello! When I didn't find libgcc_s_dw2-1.dll at first, installing the other missing libraries by using winetricks I was able to start my applications at least. Start with zlib1.dll - that is in winetricks. Then copy the other libraries into the pertinent folders of your windows folder of your wine installation. libgcc_s_dw2-1.dll can be found here https://www.sts-tutorial.com/download/start/Mjc2NA==[1] and libtiff3.dll can be faound herehttps://everydll.com/gnuwin32/libtiff3-dll/#download-dll[2] Google is your friend - this time - ..._ _.__ __... ...__ -- Eike Lantzsch ZP6CGE [1] https://www.sts-tutorial.com/download/start/Mjc2NA== [2] https://everydll.com/gnuwin32/libtiff3-dll/#download-dll
Wine fails because of missing libgcc_s_dw2-1.dll
Hello After the recent update of Wine packages in Sid, some programs do not run because of a missing libgcc_s_dw2-1.dll. They all worked just fine with the previous version. ~$ wine SpaceEngine.exe 014c:err:module:import_dll Library libgcc_s_dw2-1.dll (which is needed by L"Z:\\home\\eoz\\Programs\\SpaceEngine\\system\\zlib1.dll") not found 014c:err:module:import_dll Loading library zlib1.dll (which is needed by L"Z:\\home\\eoz\\Programs\\SpaceEngine\\system\\libtiff3.dll") failed ( error c07b). 014c:err:module:import_dll Library libtiff3.dll (which is needed by L"Z:\\home\\eoz\\Programs\\SpaceEngine\\system\\SpaceEngine.exe") not found 014c:err:module:LdrInitializeThunk Importing dlls for L"Z:\\home\\eoz\\Programs\\SpaceEngine\\system\\SpaceEngine.exe" failed, status c135 I looked in my backups and I never had any libgcc_s_dw2-1.dll installed in my system, but now it seems to be needed. Any ideas? Thanks in advance
Re: First time WINE user looking for tutorial
On 10/10/2021 05:47 PM, Tom Dial wrote: On 10/10/21 04:14, Richard Owlett wrote: On 10/09/2021 10:24 AM, Patrick Bartek wrote: On Sat, 9 Oct 2021 09:40:21 -0500 Richard Owlett wrote: (Omitted) Just be forewarned, WINE is not the catchall solution to running Windows apps: The more involved codewise the program is like games or Photoshop, the more problems you'll have. For context, I've been providing informal support to a local couple for decades. He is a retired pastor, now a missionary. They need a new computer and as part of my support, I'll be purchasing a replacement. As I've not used Windows since WinXP and they are pure Windows users I planned to dual boot Windows and Debian. Debian primarily for its maintenance tools. I hope WINE will run enough of their "must have" apps that I can use that as a selling point to move from Windows to Linux. In those cases, just run Windows in a virtual machine which is what I do for ALL Windows apps I need. Less or virtually no gotchas! On my personal machines I would have no motivation to install a VM. However, I'll investigate the pros/cons of having their machine run a VM in which I would run Debian as a demo. Full disclosure: I have not run WINE for 20 years or more, and assume without argument that it is much improved over what it was then. I run VMs regularly under Linux (using KVM), but the current ones are either Linux or FreeBSD; I haven't done a Windows VM for years. That said, it is not the right solution for the problem you describe. And with due respect to Patrick, I do not think running windows in a (presumably) Linux VM is a good solution either. Description tangled as well being in flux. I will supply them with a Windows machine. For my convenience it will have a VM running Debian. The only use being considered now for WINE is my personal home machines. I have supported my wife's various computers for about 25 years under an oral service agreement providing that I will install software as requested, maintain the OS and installed software regularly, analyze and correct software and hardware problems as necessary, and replace the hardware as appropriate. That, and no more, under threat of Serious Issues. That has brought the suffering of Windows 95, now long in the past, and over time reinforced the validity of the first rule I was given as a novice mainframe system programmer 30 years ago: "We install vanilla." Running an emulator like WINE, or Windows in a Linux (?) VM, would likely lead to operational issues arising from interfaces that are not overly well documented and therefore hard to analyze. Resolution often would have to based on web search results of uncertain accuracy and reliability, and consequent false starts and customer dissatisfaction. Either would cause you excessive work and likely enough bring unhappiness to both you and those you aim to assist. Agreed. I recommend you select, with your users' concurrence, a suitable factory refurbished business-grade laptop[1] from a major manufacturer. I have used HP, but Dell, Lenovo, and maybe others probably have similar programs. Refurbished business laptops are a bit costlier than new consumer laptops with comparable performance, but they also are built to a higher standard of reliability and come with significantly less preloaded crapware. They also (HP experience here) may have useful built in diagnostic tools and support software/firmware maintenance support, and they come with a full new unit warranty; in my experience, any defects are minor and cosmetic. I've already talking to such a local vendor. I've bought several Lenovos from them and have observed how they interact with non-tech customers. Also, IIUC they can provide on customer site service. For the use case you describe, I also recommend a service agreement, if available, that provides pick up and delivery service. The HP ones (presently $137 for three year coverage) are fairly inexpensive. While they are unlikely to be used, I consider them worthwhile unless there is a serious cost constraint). Such equipment will come with preinstalled and configured Windows, and current Microsoft maintenance support is quite good and relatively trouble free. And when problems do arise, Microsoft or manufacturer support is likely to be usable to resolve it; they certainly will be as good as random WWW support for a home-brew OS and software setup. Linux tools are undeniable useful in some cases, but will rarely be necessary for a vanilla or nearly vanilla Windows setup. For those instances where they are, it always is nice to have a bootable CD, DVD, or USB key with Linux and a set of common tools on it. I generally use a recent Debian DVD #1 for this and install any missing tools as necessary once it is booted and running. Having Debian in a VM would be nice, but not a deal breaker. Regards Tom Dial [1] Manufacturers also will offer refurbished business desktop or w
Re: First time WINE user looking for tutorial
On 10/10/2021 11:03 AM, Andrew M.A. Cater wrote: On Sun, Oct 10, 2021 at 05:14:36AM -0500, Richard Owlett wrote: On 10/09/2021 10:24 AM, Patrick Bartek wrote: On Sat, 9 Oct 2021 09:40:21 -0500 Richard Owlett wrote: Just be forewarned, WINE is not the catchall solution to running Windows apps: The more involved codewise the program is like games or Photoshop, the more problems you'll have. For context, I've been providing informal support to a local couple for decades. He is a retired pastor, now a missionary. They need a new computer and as part of my support, I'll be purchasing a replacement. As I've not used Windows since WinXP and they are pure Windows users I planned to dual boot Windows and Debian. Debian primarily for its maintenance tools. I hope WINE will run enough of their "must have" apps that I can use that as a selling point to move from Windows to Linux. In all honesty, I wouldn't do that: don't force a dual boot on anyone that isn't an expert computer user. They could readily get confused / boot into the wrong OS. That was one of my concerns having done that to myself on my own machines. If I decide to have Debian on their machine it *will be* by using a VM. Better, in this instance, to buy a new computer with Windows and whatever office software they might need and for you to learn enough to use Windows 10 or 11. I can use Windows, I just want Debian tools available to me. If you get Windows Pro, you could readily use Debian over WSL2 if you had to. Reading https://en.wikipedia.org/wiki/Windows_Subsystem_for_Linux raises all sorts of "red flags". Reminds me of why I abandoned M$ in days of WinXP. On a new computer, don't take the risk of making it dual boot, perhaps having to reinstall Windows, "voiding warranty" and creating a further rod for your back in support. Agreed! This is, perhaps, an unusual viewpoint to take - but I have been involved in trying to set up a special purpose machine for someone who didn't appreciate the help that I was endeavouring to provide, queried costs and so on. > I ended up paying money out of my own pocket to fix items because I was guilt-tripped into it. I'm fortunately in a different situation. I've given better support for free than what they got from the big box store where they bought their current machine. As part of my support the missions agency I'm supplying the machine and its upkeep. In those cases, just run Windows in a virtual machine which is what I do for ALL Windows apps I need. Less or virtually no gotchas! As a Linux user, on your own machine, absolutely. Again, you do need to know what you're doing this for and the limitations of Windows - it's something I have considered for folk who are predominantly Linux users but have to use Windows occasionally for work. On my personal machines I would have no motivation to install a VM. However, I'll investigate the pros/cons of having their machine run a VM in which I would run Debian as a demo. Are there good FOSS or low cost VMs for Windows machines? Microsoft's WSL2 is the closest you'll get. That and Debian are no cost options - but in that instance, you have to get your Debian instance from the Microsoft store. That requirement eliminates WSL2 from consideration. I'm investigating Virtualbox and VM Ware. Thanks All best, as ever, Andy Cater
Re: First time WINE user looking for tutorial
On 10/10/21 04:14, Richard Owlett wrote: > On 10/09/2021 10:24 AM, Patrick Bartek wrote: >> On Sat, 9 Oct 2021 09:40:21 -0500 >> Richard Owlett wrote: (Omitted) > > >> >> Just be forewarned, WINE is not the catchall solution to running >> Windows apps: The more involved codewise the program is like games or >> Photoshop, the more problems you'll have. > > For context, I've been providing informal support to a local couple for > decades. He is a retired pastor, now a missionary. They need a new > computer and as part of my support, I'll be purchasing a replacement. As > I've not used Windows since WinXP and they are pure Windows users I > planned to dual boot Windows and Debian. Debian primarily for its > maintenance tools. I hope WINE will run enough of their "must have" apps > that I can use that as a selling point to move from Windows to Linux. > >> In those cases, just run Windows in a virtual machine which is what I do >> for ALL Windows apps I need. Less or virtually no gotchas! > > On my personal machines I would have no motivation to install a VM. > However, I'll investigate the pros/cons of having their machine run a VM > in which I would run Debian as a demo. > Full disclosure: I have not run WINE for 20 years or more, and assume without argument that it is much improved over what it was then. I run VMs regularly under Linux (using KVM), but the current ones are either Linux or FreeBSD; I haven't done a Windows VM for years. That said, it is not the right solution for the problem you describe. And with due respect to Patrick, I do not think running windows in a (presumably) Linux VM is a good solution either. I have supported my wife's various computers for about 25 years under an oral service agreement providing that I will install software as requested, maintain the OS and installed software regularly, analyze and correct software and hardware problems as necessary, and replace the hardware as appropriate. That, and no more, under threat of Serious Issues. That has brought the suffering of Windows 95, now long in the past, and over time reinforced the validity of the first rule I was given as a novice mainframe system programmer 30 years ago: "We install vanilla." Running an emulator like WINE, or Windows in a Linux (?) VM, would likely lead to operational issues arising from interfaces that are not overly well documented and therefore hard to analyze. Resolution often would have to based on web search results of uncertain accuracy and reliability, and consequent false starts and customer dissatisfaction. Either would cause you excessive work and likely enough bring unhappiness to both you and those you aim to assist. I recommend you select, with your users' concurrence, a suitable factory refurbished business-grade laptop[1] from a major manufacturer. I have used HP, but Dell, Lenovo, and maybe others probably have similar programs. Refurbished business laptops are a bit costlier than new consumer laptops with comparable performance, but they also are built to a higher standard of reliability and come with significantly less preloaded crapware. They also (HP experience here) may have useful built in diagnostic tools and support software/firmware maintenance support, and they come with a full new unit warranty; in my experience, any defects are minor and cosmetic. For the use case you describe, I also recommend a service agreement, if available, that provides pick up and delivery service. The HP ones (presently $137 for three year coverage) are fairly inexpensive. While they are unlikely to be used, I consider them worthwhile unless there is a serious cost constraint). Such equipment will come with preinstalled and configured Windows, and current Microsoft maintenance support is quite good and relatively trouble free. And when problems do arise, Microsoft or manufacturer support is likely to be usable to resolve it; they certainly will be as good as random WWW support for a home-brew OS and software setup. Linux tools are undeniable useful in some cases, but will rarely be necessary for a vanilla or nearly vanilla Windows setup. For those instances where they are, it always is nice to have a bootable CD, DVD, or USB key with Linux and a set of common tools on it. I generally use a recent Debian DVD #1 for this and install any missing tools as necessary once it is booted and running. Regards Tom Dial [1] Manufacturers also will offer refurbished business desktop or workstation equipment. I like laptops not only for their portability, but because, having only one piece, they simpler to deal with. > Are there good FOSS or low cost VMs for Windows machines? > > Thanks
Re: First time WINE user looking for tutorial
On Sun, Oct 10, 2021 at 02:05:20PM -0700, Patrick Bartek wrote: I use VirtualBox for my VM needs, but why would you need to: Google Earth has versions that run natively on Windows, OSX and Linux or you can run it in most any web browsers -- https://earth.google.com/ -- regardless of OS. It has been several years since I had need for Earth. Thanks for the update. RLH
Re: First time WINE user looking for tutorial
On Sun, 10 Oct 2021 05:14:36 -0500 Richard Owlett wrote: > On 10/09/2021 10:24 AM, Patrick Bartek wrote: > > On Sat, 9 Oct 2021 09:40:21 -0500 > > Richard Owlett wrote: > > > >> [snip] > > > > > Just be forewarned, WINE is not the catchall solution to running > > Windows apps: The more involved codewise the program is like games > > or Photoshop, the more problems you'll have. > > For context, I've been providing informal support to a local couple > for decades. He is a retired pastor, now a missionary. They need a > new computer and as part of my support, I'll be purchasing a > replacement. As I've not used Windows since WinXP and they are pure > Windows users I planned to dual boot Windows and Debian. Debian > primarily for its maintenance tools. I hope WINE will run enough of > their "must have" apps that I can use that as a selling point to move > from Windows to Linux. If all they've ever used is Windows, leave it at that. Don't attempt to switch them to Linux. It will be more trouble than it's worth. Get them a laptop with Windows, clean the preinstalled and CPU cycles eating background crap off of it, bring it up-to-date, and you're done. > > In those cases, just run Windows in a virtual machine which is what > > I do for ALL Windows apps I need. Less or virtually no gotchas! > > On my personal machines I would have no motivation to install a VM. > However, I'll investigate the pros/cons of having their machine run a > VM in which I would run Debian as a demo. Unless they really NEED Debian or Linux, don't bother. If you want to demo Linux just get one of the many "live" versions to boot the system. Then they can play with it without installing. And it won't do anything to their existing Windows install. > Are there good FOSS or low cost VMs for Windows machines? Windows has it's own VM. Can't remember its name, but I'd recommend VirtualBox instead -- https://www.virtualbox.org/ . It's free and has versions that run on Linux or Windows, among others. B
Re: First time WINE user looking for tutorial
On Sun, 10 Oct 2021 03:28:42 + "Russell L. Harris" wrote: > On Sat, Oct 09, 2021 at 08:24:38AM -0700, Patrick Bartek wrote: > >On Sat, 9 Oct 2021 09:40:21 -0500 > >Richard Owlett wrote: > > >Just be forewarned, WINE is not the catchall solution to running > >Windows apps: The more involved codewise the program is like games or > >Photoshop, the more problems you'll have. In those cases, just run > >Windows in a virtual machine which is what I do for ALL Windows apps > >I need. Less or virtually no gotchas! > > Richard, Can you recommend a virtual machine for Debian which can run > Google Earth? > > Richard didn't write that, I did -- Patrick. I use VirtualBox for my VM needs, but why would you need to: Google Earth has versions that run natively on Windows, OSX and Linux or you can run it in most any web browsers -- https://earth.google.com/ -- regardless of OS. B
Re: First time WINE user looking for tutorial
On Sun, Oct 10, 2021 at 05:14:36AM -0500, Richard Owlett wrote: > On 10/09/2021 10:24 AM, Patrick Bartek wrote: > > On Sat, 9 Oct 2021 09:40:21 -0500 > > Richard Owlett wrote: > > > > > > Just be forewarned, WINE is not the catchall solution to running > > Windows apps: The more involved codewise the program is like games or > > Photoshop, the more problems you'll have. > > For context, I've been providing informal support to a local couple for > decades. He is a retired pastor, now a missionary. They need a new computer > and as part of my support, I'll be purchasing a replacement. As I've not > used Windows since WinXP and they are pure Windows users I planned to dual > boot Windows and Debian. Debian primarily for its maintenance tools. I hope > WINE will run enough of their "must have" apps that I can use that as a > selling point to move from Windows to Linux. > In all honesty, I wouldn't do that: don't force a dual boot on anyone that isn't an expert computer user. They could readily get confused / boot into the wrong OS. Better, in this instance, to buy a new computer with Windows and whatever office software they might need and for you to learn enough to use Windows 10 or 11. If you get Windows Pro, you could readily use Debian over WSL2 if you had to. On a new computer, don't take the risk of making it dual boot, perhaps having to reinstall Windows, "voiding warranty" and creating a further rod for your back in support. This is, perhaps, an unusual viewpoint to take - but I have been involved in trying to set up a special purpose machine for someone who didn't appreciate the help that I was endeavouring to provide, queried costs and so on. I ended up paying money out of my own pocket to fix items because I was guilt-tripped into it. > > In those cases, just run Windows in a virtual machine which is what I do > > for ALL Windows apps I need. Less or virtually no gotchas! > As a Linux user, on your own machine, absolutely. Again, you do need to know what you're doing this for and the limitations of Windows - it's something I have considered for folk who are predominantly Linux users but have to use Windows occasionally for work. > On my personal machines I would have no motivation to install a VM. However, > I'll investigate the pros/cons of having their machine run a VM in which I > would run Debian as a demo. > > Are there good FOSS or low cost VMs for Windows machines? Microsoft's WSL2 is the closest you'll get. That and Debian are no cost options - but in that instance, you have to get your Debian instance from the Microsoft store. > > Thanks > > > All best, as ever, Andy Cater > > > >
Re: First time WINE user looking for tutorial
On 10/09/2021 10:28 PM, Russell L. Harris wrote: On Sat, Oct 09, 2021 at 08:24:38AM -0700, Patrick Bartek wrote: On Sat, 9 Oct 2021 09:40:21 -0500 Richard Owlett wrote: Just be forewarned, WINE is not the catchall solution to running Windows apps: The more involved codewise the program is like games or Photoshop, the more problems you'll have. In those cases, just run Windows in a virtual machine which is what I do for ALL Windows apps I need. Less or virtually no gotchas! Richard, Can you recommend a virtual machine for Debian which can run Google Earth? I have never used a VM. See my reply to Patrick.
Re: First time WINE user looking for tutorial
On 10/09/2021 10:24 AM, Patrick Bartek wrote: On Sat, 9 Oct 2021 09:40:21 -0500 Richard Owlett wrote: I just installed WINE64 on a Bullseye system. I'm looking for a basic tutorial. Got no promising hits from DuckDuckGo or Google. I did some unproductive roaming of https://www.winehq.org/ . Really? "No promising hits?" I did an "install set up wine" DuckDuckGo search and got numerous useful hits. Of course, if you're looking for a Bullseye specific tutorial, I doubt if you' find one -- too new. Your search terms were better than mine ;/ I included "+tutorial" as a keyword and top hits were how to use git to submit patches. Maybe, these will help: https://itsfoss.com/use-windows-applications-linux/ https://linuxhint.com/install-use-wine-linux/ They gave me what I hoped for in posting -- additional search terms that relate some of my goals. In addition to both being the type of tutorial I was looking for, the second does not have the string "tutorial" in any context. Just be forewarned, WINE is not the catchall solution to running Windows apps: The more involved codewise the program is like games or Photoshop, the more problems you'll have. For context, I've been providing informal support to a local couple for decades. He is a retired pastor, now a missionary. They need a new computer and as part of my support, I'll be purchasing a replacement. As I've not used Windows since WinXP and they are pure Windows users I planned to dual boot Windows and Debian. Debian primarily for its maintenance tools. I hope WINE will run enough of their "must have" apps that I can use that as a selling point to move from Windows to Linux. In those cases, just run Windows in a virtual machine which is what I do for ALL Windows apps I need. Less or virtually no gotchas! On my personal machines I would have no motivation to install a VM. However, I'll investigate the pros/cons of having their machine run a VM in which I would run Debian as a demo. Are there good FOSS or low cost VMs for Windows machines? Thanks
Re: First time WINE user looking for tutorial
On Sat, Oct 09, 2021 at 08:24:38AM -0700, Patrick Bartek wrote: On Sat, 9 Oct 2021 09:40:21 -0500 Richard Owlett wrote: Just be forewarned, WINE is not the catchall solution to running Windows apps: The more involved codewise the program is like games or Photoshop, the more problems you'll have. In those cases, just run Windows in a virtual machine which is what I do for ALL Windows apps I need. Less or virtually no gotchas! Richard, Can you recommend a virtual machine for Debian which can run Google Earth? -- How should one chase a thousand, and two put ten thousand to flight, except their Rock had sold them, and the Lord had shut them up? - Deuteronomy 32:30
Re: First time WINE user looking for tutorial
On Sat, 9 Oct 2021 09:40:21 -0500 Richard Owlett wrote: > I just installed WINE64 on a Bullseye system. I'm looking for a basic > tutorial. Got no promising hits from DuckDuckGo or Google. I did some > unproductive roaming of https://www.winehq.org/ . Really? "No promising hits?" I did an "install set up wine" DuckDuckGo search and got numerous useful hits. Of course, if you're looking for a Bullseye specific tutorial, I doubt if you' find one -- too new. Maybe, these will help: https://itsfoss.com/use-windows-applications-linux/ https://linuxhint.com/install-use-wine-linux/ Just be forewarned, WINE is not the catchall solution to running Windows apps: The more involved codewise the program is like games or Photoshop, the more problems you'll have. In those cases, just run Windows in a virtual machine which is what I do for ALL Windows apps I need. Less or virtually no gotchas! B
First time WINE user looking for tutorial
I just installed WINE64 on a Bullseye system. I'm looking for a basic tutorial. Got no promising hits from DuckDuckGo or Google. I did some unproductive roaming of https://www.winehq.org/ . I haven't used Windows since days of WinXP and I want to introduce a Windows using friend to Debian. Blind leading blind ;/ Suggestions? TIA
Re: iTunesSetup.exe in wine?
From: Floris Renaud
Date: Thu, 07 Oct 2021 07:50:37 +
> You can read the WineHQ wiki for more information about prefixes:
> https://wiki.winehq.org/FAQ#Wineprefixes
Thanks Floris.
> Do you have the same error if you try:
> WINEPREFIX=~/itunes wine iTunesSetup.exe
Transcript follows. (Apology for questionable use of data.) During
that output, notifications about Mono and Gecko appeared. The Mono
notification is at http://easthope.ca/WineNotification.png . Appears
that Mono and Gecko are needed to use iTunes successfully whereas
Debian packages are not available. Ref.
https://wiki.debian.org/Wine#Mono_and_Gecko There might be a good
reason for absence from the Debian package archive. =8~)
For zero or a few dollars, someone in the city will unbrick the
iPhone. Wine is interesting but making it work for a small task is a
stretch.
Thanks for the help, ... P.
peter@joule:~$ WINEPREFIX=~/itunes wine iTunesSetup.exe
wine: created the configuration directory '/home/peter/itunes'
0050:err:ole:StdMarshalImpl_MarshalInterface Failed to create ifstub, hr
0x80004002
0050:err:ole:CoMarshalInterface Failed to marshal the interface
{6d5140c1-7436-11ce-8034-00aa006009fa}, hr 0x80004002
0050:err:ole:apartment_get_local_server_stream Failed: 0x80004002
0048:err:ole:StdMarshalImpl_MarshalInterface Failed to create ifstub, hr
0x80004002
0048:err:ole:CoMarshalInterface Failed to marshal the interface
{6d5140c1-7436-11ce-8034-00aa006009fa}, hr 0x80004002
0048:err:ole:apartment_get_local_server_stream Failed: 0x80004002
0048:err:ole:start_rpcss Failed to open RpcSs service
0040:err:setupapi:SetupDefaultQueueCallbackW copy error 1812 L"@wineusb.sys,-1"
-> L"C:\\windows\\inf\\wineusb.inf"
Could not find Wine Gecko. HTML rendering will be disabled.
wine: configuration in L"/home/peter/itunes" has been updated.
0114:fixme:file:NtLockFile I/O completion on lock not implemented yet
0114:fixme:ntdll:NtQuerySystemInformation info_class
SYSTEM_PERFORMANCE_INFORMATION
0114:err:mscoree:LoadLibraryShim error reading registry key for installroot
0114:err:mscoree:LoadLibraryShim error reading registry key for installroot
0114:err:mscoree:LoadLibraryShim error reading registry key for installroot
0114:err:mscoree:LoadLibraryShim error reading registry key for installroot
0138:fixme:wbemprox:client_security_SetBlanket 62EA17A8, 0013B220, 10, 0,
(null), 3, 3, , 0x
0138:fixme:wbemprox:client_security_Release 62EA17A8
0138:fixme:ntdll:NtQuerySystemInformation info_class
SYSTEM_PERFORMANCE_INFORMATION
0154:fixme:exec:SHELL_execute flags ignored: 0x0100
0160:fixme:file:NtLockFile I/O completion on lock not implemented yet
0160:fixme:ntdll:NtQuerySystemInformation info_class
SYSTEM_PERFORMANCE_INFORMATION
0160:err:mscoree:LoadLibraryShim error reading registry key for installroot
0160:err:mscoree:LoadLibraryShim error reading registry key for installroot
0160:err:mscoree:LoadLibraryShim error reading registry key for installroot
0160:err:mscoree:LoadLibraryShim error reading registry key for installroot
0184:fixme:wbemprox:client_security_SetBlanket 62EA17A8, 00137568, 10, 0,
(null), 3, 3, , 0x
0184:fixme:wbemprox:client_security_Release 62EA17A8
0184:fixme:ntdll:NtQuerySystemInformation info_class
SYSTEM_PERFORMANCE_INFORMATION
01d8:fixme:hnetcfg:netfw_rules_Item 00142C38, L"Apple Push Service", 0172FB9C
01cc:fixme:msi:internal_ui_handler internal UI not implemented for message
0x0b00 (UI level = 5)
01d0:fixme:msi:internal_ui_handler internal UI not implemented for message
0x0b00 (UI level = 5)
0160:err:mscoree:LoadLibraryShim error reading registry key for installroot
0160:err:mscoree:LoadLibraryShim error reading registry key for installroot
0160:err:mscoree:LoadLibraryShim error reading registry key for installroot
0160:err:mscoree:LoadLibraryShim error reading registry key for installroot
023c:fixme:hnetcfg:fw_app_put_Enabled 001393D0, -1
024c:fixme:winsock:WSCUnInstallNameSpace
({b600e6e9-553b-4a19-8696-335e5c896153}) Stub!
024c:fixme:winsock:WSCInstallNameSpace (L"mdnsNSP" L"C:\\Program
Files\\Bonjour\\mdnsNSP.dll" 0x000c 0x0001
{b600e6e9-553b-4a19-8696-335e5c896153}) Stub!
025c:fixme:heap:RtlSetHeapInformation 1 0 stub
025c:fixme:heap:RtlSetHeapInformation 1 0 stub
0268:fixme:advapi:RegisterEventSourceW ((null),L"Bonjour Service"): stub
0268:fixme:advapi:ReportEventA
(CAFE4242,0x0004,0x,0x0064,,0x0001,0x,0119FA8C,):
stub
0268:fixme:advapi:ReportEventW
(CAFE4242,0x0004,0x,0x0064,,0x0001,0x,00121380,):
stub
0268:fixme:winsock:WSAIoctl WS_SIO_UDP_CONNRESET stub
0268:fixme:winsock:WSAIoctl WS_SIO_UDP_CONNRESET stub
0268:fixme:winsock:WS_setsockopt Unknown IPPROTO_IPV6 optname 0x0013
0268:err:winsock:WSAIo
Re: iTunesSetup.exe in wine?
On Thursday 07 October 2021 05:40:42 (+02:00), pe...@easthope.ca wrote: > From: Floris Renaud > Date: Wed, 06 Oct 2021 21:54:31 + > > What version of Wine do you use? > > peter@joule:/home/peter$ dpkg -l | grep wine > ii wine-stable 6.0.1~bullseye-1 i386 WINE Is Not An Emulator - runs MS > Windows programs > ii wine-stable-i386 6.0.1~bullseye-1 i386 WINE Is Not An Emulator - runs MS > Windows programs > ii winehq-stable 6.0.1~bullseye-1 i386 WINE Is Not An Emulator - runs MS > Windows programs > > peter@joule:/home/peter$ head -n 1 /etc/os-release > PRETTY_NAME="Debian GNU/Linux 11 (bullseye)" > > peter@joule:/home/peter$ uname -a > Linux joule 5.10.0-8-686-pae #1 SMP Debian 5.10.46-5 (2021-09-23) i686 > GNU/Linux > > > ITunes version 12.8.0.150 seems to install and work normally with > > Wine 6.18 ¹ in a clean Wineprefix ². > > What is meant by "clean Wineprefix"? > > Rather than pursue 6.18, I might pay a shop a few dollars to reset the > iPhone. > > Thanks! ... P. > A clean Wineprefix is a virtual Windows installation without other programs installed. You can read the WineHQ wiki for more information about prefixes: https://wiki.winehq.org/FAQ#Wineprefixes Do you have the same error if you try: WINEPREFIX=~/itunes wine iTunesSetup.exe
Re: iTunesSetup.exe in wine?
From: Floris Renaud Date: Wed, 06 Oct 2021 21:54:31 + > What version of Wine do you use? peter@joule:/home/peter$ dpkg -l | grep wine ii wine-stable 6.0.1~bullseye-1 i386 WINE Is Not An Emulator - runs MS Windows programs ii wine-stable-i386 6.0.1~bullseye-1 i386 WINE Is Not An Emulator - runs MS Windows programs ii winehq-stable6.0.1~bullseye-1 i386 WINE Is Not An Emulator - runs MS Windows programs peter@joule:/home/peter$ head -n 1 /etc/os-release PRETTY_NAME="Debian GNU/Linux 11 (bullseye)" peter@joule:/home/peter$ uname -a Linux joule 5.10.0-8-686-pae #1 SMP Debian 5.10.46-5 (2021-09-23) i686 GNU/Linux > ITunes version 12.8.0.150 seems to install and work normally with > Wine 6.18 ¹ in a clean Wineprefix ². What is meant by "clean Wineprefix"? Rather than pursue 6.18, I might pay a shop a few dollars to reset the iPhone. Thanks! ... P. -- 48.7693 N 123.3053 W mobile: +1 778 951 5147 VoIP: +1 604 670 0140
Re: iTunesSetup.exe in wine?
On Wednesday 06 October 2021 22:13:53 (+02:00), pe...@easthope.ca wrote:
> From: Floris Renaud
> Date: Wed, 06 Oct 2021 10:27:20 +
> > An older version of iTunes does seem to work.
> > https://bugs.winehq.org/show_bug.cgi?id=47165
>
> Thanks. Version 12.8.x is claimed to work. This is 12.8.0.150.
>
> peter@joule:~$ wine iTunesSetup.exe
> 00d8:fixme:heap:RtlSetHeapInformation 1 0 stub
> 00d8:fixme:heap:RtlSetHeapInformation 1 0 stub
> 00e4:fixme:advapi:RegisterEventSourceW ((null),L"Bonjour Service"): stub
> 00e4:fixme:advapi:ReportEventA
> (CAFE4242,0x0004,0x,0x0064,,0x0001,0x,0119FA8C,):
> stub
> 00e4:fixme:advapi:ReportEventW
> (CAFE4242,0x0004,0x,0x0064,,0x0001,0x,001213F0,):
> stub
> 00e4:fixme:winsock:WSAIoctl WS_SIO_UDP_CONNRESET stub
> 00e4:fixme:winsock:WSAIoctl WS_SIO_UDP_CONNRESET stub
> 00e4:fixme:winsock:WS_setsockopt Unknown IPPROTO_IPV6 optname 0x0013
> 00e4:err:winsock:WSAIoctl -> ?('', 12, 18) request failed with status 0x2733
> 00e4:fixme:advapi:ReportEventA
> (CAFE4242,0x0004,0x,0x0064,,0x0001,0x,0119FA8C,):
> stub
> 00e4:fixme:advapi:ReportEventW
> (CAFE4242,0x0004,0x,0x0064,,0x0001,0x,001219C0,):
> stub
> 0098:fixme:service:svcctl_EnumServicesStatusExW resume handle not supported
> 0098:fixme:service:svcctl_EnumServicesStatusExW resume handle not supported
> 0098:fixme:service:svcctl_EnumServicesStatusExW resume handle not supported
> 0098:fixme:service:svcctl_EnumServicesStatusExW resume handle not supported
> 00e4:fixme:advapi:ReportEventA
> (CAFE4242,0x0004,0x,0x0064,,0x0001,0x,0119FA8C,):
> stub
> 00e4:fixme:advapi:ReportEventW
> (CAFE4242,0x0004,0x,0x0064,,0x0001,0x,001219C0,):
> stub
> 00e4:fixme:netapi32:NetGetJoinInformation Semi-stub (null) 0x119fb44 0x119fb3c
> 00e4:fixme:winsock:WSAIoctl WS_SIO_UDP_CONNRESET stub
> 00e4:fixme:winsock:WSAIoctl WS_SIO_UDP_CONNRESET stub
> 00e4:fixme:winsock:WSAIoctl WS_SIO_UDP_CONNRESET stub
> 00e4:fixme:winsock:WSAIoctl WS_SIO_UDP_CONNRESET stub
> 00e4:fixme:winsock:WSAIoctl WS_SIO_UDP_CONNRESET stub
> 00e4:fixme:winsock:WS_setsockopt Unknown IPPROTO_IPV6 optname 0x0013
> 0118:fixme:file:NtLockFile I/O completion on lock not implemented yet
> 0118:fixme:ntdll:NtQuerySystemInformation info_class
> SYSTEM_PERFORMANCE_INFORMATION
> 0118:err:mscoree:LoadLibraryShim error reading registry key for installroot
> 0118:err:mscoree:LoadLibraryShim error reading registry key for installroot
> 0118:err:mscoree:LoadLibraryShim error reading registry key for installroot
> 0118:err:mscoree:LoadLibraryShim error reading registry key for installroot
> 012c:fixme:wbemprox:client_security_SetBlanket 62EA17A8, 0013B178, 10, 0,
> (null), 3, 3, , 0x
> 012c:fixme:wbemprox:client_security_Release 62EA17A8
> 012c:fixme:ntdll:NtQuerySystemInformation info_class
> SYSTEM_PERFORMANCE_INFORMATION
>
> Is fixme a serious problem?
>
> How can
> 0118:err:mscoree:LoadLibraryShim error reading registry key for installroot
> be fixed? Something needed in the registry?
>
> Thanks! ... P.
>
What version of Wine do you use?
ITunes version 12.8.0.150 seems to install and work normally with Wine 6.18 ¹
in a clean Wineprefix ².
¹) https://wiki.winehq.org/Debian
²) https://wiki.winehq.org/FAQ#Wineprefixes
Re: iTunesSetup.exe in wine?
From: Floris Renaud
Date: Wed, 06 Oct 2021 10:27:20 +
> An older version of iTunes does seem to work.
> https://bugs.winehq.org/show_bug.cgi?id=47165
Thanks. Version 12.8.x is claimed to work. This is 12.8.0.150.
peter@joule:~$ wine iTunesSetup.exe
00d8:fixme:heap:RtlSetHeapInformation 1 0 stub
00d8:fixme:heap:RtlSetHeapInformation 1 0 stub
00e4:fixme:advapi:RegisterEventSourceW ((null),L"Bonjour Service"): stub
00e4:fixme:advapi:ReportEventA
(CAFE4242,0x0004,0x,0x0064,,0x0001,0x,0119FA8C,):
stub
00e4:fixme:advapi:ReportEventW
(CAFE4242,0x0004,0x,0x0064,,0x0001,0x,001213F0,):
stub
00e4:fixme:winsock:WSAIoctl WS_SIO_UDP_CONNRESET stub
00e4:fixme:winsock:WSAIoctl WS_SIO_UDP_CONNRESET stub
00e4:fixme:winsock:WS_setsockopt Unknown IPPROTO_IPV6 optname 0x0013
00e4:err:winsock:WSAIoctl -> ?('', 12, 18) request failed with status 0x2733
00e4:fixme:advapi:ReportEventA
(CAFE4242,0x0004,0x,0x0064,,0x0001,0x,0119FA8C,):
stub
00e4:fixme:advapi:ReportEventW
(CAFE4242,0x0004,0x,0x0064,,0x0001,0x,001219C0,):
stub
0098:fixme:service:svcctl_EnumServicesStatusExW resume handle not supported
0098:fixme:service:svcctl_EnumServicesStatusExW resume handle not supported
0098:fixme:service:svcctl_EnumServicesStatusExW resume handle not supported
0098:fixme:service:svcctl_EnumServicesStatusExW resume handle not supported
00e4:fixme:advapi:ReportEventA
(CAFE4242,0x0004,0x,0x0064,,0x0001,0x,0119FA8C,):
stub
00e4:fixme:advapi:ReportEventW
(CAFE4242,0x0004,0x,0x0064,,0x0001,0x,001219C0,):
stub
00e4:fixme:netapi32:NetGetJoinInformation Semi-stub (null) 0x119fb44 0x119fb3c
00e4:fixme:winsock:WSAIoctl WS_SIO_UDP_CONNRESET stub
00e4:fixme:winsock:WSAIoctl WS_SIO_UDP_CONNRESET stub
00e4:fixme:winsock:WSAIoctl WS_SIO_UDP_CONNRESET stub
00e4:fixme:winsock:WSAIoctl WS_SIO_UDP_CONNRESET stub
00e4:fixme:winsock:WSAIoctl WS_SIO_UDP_CONNRESET stub
00e4:fixme:winsock:WS_setsockopt Unknown IPPROTO_IPV6 optname 0x0013
0118:fixme:file:NtLockFile I/O completion on lock not implemented yet
0118:fixme:ntdll:NtQuerySystemInformation info_class
SYSTEM_PERFORMANCE_INFORMATION
0118:err:mscoree:LoadLibraryShim error reading registry key for installroot
0118:err:mscoree:LoadLibraryShim error reading registry key for installroot
0118:err:mscoree:LoadLibraryShim error reading registry key for installroot
0118:err:mscoree:LoadLibraryShim error reading registry key for installroot
012c:fixme:wbemprox:client_security_SetBlanket 62EA17A8, 0013B178, 10, 0,
(null), 3, 3, , 0x
012c:fixme:wbemprox:client_security_Release 62EA17A8
012c:fixme:ntdll:NtQuerySystemInformation info_class
SYSTEM_PERFORMANCE_INFORMATION
Is fixme a serious problem?
How can
0118:err:mscoree:LoadLibraryShim error reading registry key for installroot
be fixed? Something needed in the registry?
Thanks! ... P.
--
48.7693 N 123.3053 W
mobile: +1 778 951 5147
VoIP: +1 604 670 0140
Re: iTunesSetup.exe in wine?
On Wed, 6 Oct 2021 17:02:05 +1100 Keith Bainbridge wrote: > > On 6/10/21 07:48, pe...@easthope.ca wrote: > > A bricked iPhone directs "connect to iTunes". > > > > Attempting to run iTunesSetup.exe on wine yields the following. > > Ideas? > > > > Thx, ... P. > > > > peter@joule:~$ wine iTunesSetup.exe > > 0104:fixme:file:NtLockFile I/O completion on lock not implemented yet > > 0104:fixme:ntdll:NtQuerySystemInformation info_class > > SYSTEM_PERFORMANCE_INFORMATION > > 0104:err:mscoree:LoadLibraryShim error reading registry key for installroot > > 0104:err:mscoree:LoadLibraryShim error reading registry key for installroot > > 0104:err:mscoree:LoadLibraryShim error reading registry key for installroot > > 0104:err:mscoree:LoadLibraryShim error reading registry key for installroot > > 0128:fixme:wbemprox:client_security_SetBlanket 62EA17A8, 0013B3A8, 10, 0, > > (null), 3, 3, , 0x > > 0128:fixme:wbemprox:client_security_Release 62EA17A8 > > 0128:fixme:ntdll:NtQuerySystemInformation info_class > > SYSTEM_PERFORMANCE_INFORMATION > > 0104:err:msi:ITERATE_Actions Execution halted, action L"LaunchConditions" > > returned 1603 > > 0024:fixme:kernelbase:AppPolicyGetProcessTerminationMethod FFFA, > > 0031FEAC > > peter@joule:~$ > > > > > > > Option one: play-on-linux > > Option 2: CrossOver a commercial app, based on wine but with > non-open-source and paid for content. Its main claim to fame was that it > would run MSOffice better. There is a trial period. The OP can also consider Lutris: https://lutris.net/games/itunes/ I've used it for other things, not iTunes, but it has worked quite well for me, and it can be simpler and less intimidating than straight Wine. > This link lists a few more options which I'd not heard of until I went > looking for the name of Crossover: > > https://alternativeto.net/software/wine/?platform=linux Celejar
Re: iTunesSetup.exe in wine?
On Tuesday 05 October 2021 22:48:10 (+02:00), pe...@easthope.ca wrote: > A bricked iPhone directs "connect to iTunes". > > Attempting to run iTunesSetup.exe on wine yields the following. > Ideas? > > Thx, ... P. > > peter@joule:~$ wine iTunesSetup.exe > 0104:fixme:file:NtLockFile I/O completion on lock not implemented yet > 0104:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION > 0104:err:mscoree:LoadLibraryShim error reading registry key for installroot > 0104:err:mscoree:LoadLibraryShim error reading registry key for installroot > 0104:err:mscoree:LoadLibraryShim error reading registry key for installroot > 0104:err:mscoree:LoadLibraryShim error reading registry key for installroot > 0128:fixme:wbemprox:client_security_SetBlanket 62EA17A8, 0013B3A8, 10, 0, (null), 3, 3, , 0x > 0128:fixme:wbemprox:client_security_Release 62EA17A8 > 0128:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION > 0104:err:msi:ITERATE_Actions Execution halted, action L"LaunchConditions" returned 1603 > 0024:fixme:kernelbase:AppPolicyGetProcessTerminationMethod FFFA, 0031FEAC > peter@joule:~$ > > The latest version of iTunes does not work well with Wine. (Or with wine-staging or wine-ge-custom). An older version of iTunes does seem to work. https://bugs.winehq.org/show_bug.cgi?id=47165 Floris
Re: iTunesSetup.exe in wine?
On 6/10/21 07:48, pe...@easthope.ca wrote: A bricked iPhone directs "connect to iTunes". Attempting to run iTunesSetup.exe on wine yields the following. Ideas? Thx, ... P. peter@joule:~$ wine iTunesSetup.exe 0104:fixme:file:NtLockFile I/O completion on lock not implemented yet 0104:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION 0104:err:mscoree:LoadLibraryShim error reading registry key for installroot 0104:err:mscoree:LoadLibraryShim error reading registry key for installroot 0104:err:mscoree:LoadLibraryShim error reading registry key for installroot 0104:err:mscoree:LoadLibraryShim error reading registry key for installroot 0128:fixme:wbemprox:client_security_SetBlanket 62EA17A8, 0013B3A8, 10, 0, (null), 3, 3, , 0x 0128:fixme:wbemprox:client_security_Release 62EA17A8 0128:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION 0104:err:msi:ITERATE_Actions Execution halted, action L"LaunchConditions" returned 1603 0024:fixme:kernelbase:AppPolicyGetProcessTerminationMethod FFFA, 0031FEAC peter@joule:~$ Option one: play-on-linux Option 2: CrossOver a commercial app, based on wine but with non-open-source and paid for content. Its main claim to fame was that it would run MSOffice better. There is a trial period. This link lists a few more options which I'd not heard of until I went looking for the name of Crossover: https://alternativeto.net/software/wine/?platform=linux -- All the best Keith Bainbridge keithrbaugro...@gmail.com
iTunesSetup.exe in wine?
A bricked iPhone directs "connect to iTunes". Attempting to run iTunesSetup.exe on wine yields the following. Ideas? Thx, ... P. peter@joule:~$ wine iTunesSetup.exe 0104:fixme:file:NtLockFile I/O completion on lock not implemented yet 0104:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION 0104:err:mscoree:LoadLibraryShim error reading registry key for installroot 0104:err:mscoree:LoadLibraryShim error reading registry key for installroot 0104:err:mscoree:LoadLibraryShim error reading registry key for installroot 0104:err:mscoree:LoadLibraryShim error reading registry key for installroot 0128:fixme:wbemprox:client_security_SetBlanket 62EA17A8, 0013B3A8, 10, 0, (null), 3, 3, , 0x 0128:fixme:wbemprox:client_security_Release 62EA17A8 0128:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION 0104:err:msi:ITERATE_Actions Execution halted, action L"LaunchConditions" returned 1603 0024:fixme:kernelbase:AppPolicyGetProcessTerminationMethod FFFA, 0031FEAC peter@joule:~$ -- 48.7693 N 123.3053 W mobile: +1 778 951 5147 VoIP: +1 604 670 0140
Re: _INTRODUCTION_ to installing/using Wine?
On Mon 27 Sep 2021 at 14:28:37 -0500, Richard Owlett wrote:
> On 09/26/2021 08:54 AM, piorunz wrote:
> > On 26/09/2021 14:42, Richard Owlett wrote:
> > > I have not used any version of Windows since WinXP and have the AMD64
> > > flavor of Debian 10.7 installed on the relevant machine.
> > >
> > > I wish to do two things:
> > > 1. Explore some text manipulation applications I used then
> > > (obviously 32 bit apps).
> > > 2. Explore Bible study tools used by others at church
> > > (32 or 64 bit ???).
> > >
> > > I have found references [1][2] suitable for addressing specific detailed
> > > questions. I'm looking for introductory material -- especially such that
> > > would cause me to think of questions I should consider before proceeding.
> > > Suggestions?
> > > TIA
> > >
> > > References:
> > > 1. https://wiki.debian.org/Wine
> > > 2. https://www.winehq.org/
> > > Goes into much detail but does not have an "overview only" page.
> >
> > After you install Wine (your reference materials covers that), simply
> > execute in terminal "wine name_of_your_exe" from the folder where .exe is.
> >
> > That's all.
>
> I *DOUBT* it as:
> 1. I'm well past "three score and ten" ;}
Of what possible relevance is that? There are other users who use the
same argument, often giving extensive excrutiating biographical details.
A user may doubt the advice given, but I thought piorunz's helpful post
deserved a less ageist response.
> 2. [1] explicitly states:
> > Users on a 64-bit system should make sure that both wine32
> > and wine64 (...) are installed ...
>
> Careful reading of [1] and [2] {w/apologies to J. Caesar} suggests:
> " All .exe are divided into three flavors:
> 1. pure 32 bit
> 2. pure 64 bit
> 3. pure hodgepodge
> "
> >
> > If something doesn't work, install required components using winetricks.
> > Simply install package winetricks, open it, and navigate graphically to
> > install .Net Frameworks, C++ redistributables and whatever else your
> > Windows app needs to operate.
>
> Is not that paragraph sufficient justification for my question?
Without a doubt it is.
--
Brian.
Re: _INTRODUCTION_ to installing/using Wine?
On 27/09/2021 20:28, Richard Owlett wrote:
That's all.
I *DOUBT* it as:
1. I'm well past "three score and ten" ;}
2. [1] explicitly states:
> Users on a 64-bit system should make sure that both wine32
> and wine64 (...) are installed ...
Yes, you have problem with that?
Careful reading of [1] and [2] {w/apologies to J. Caesar} suggests:
" All .exe are divided into three flavors:
1. pure 32 bit
2. pure 64 bit
3. pure hodgepodge
Not sure what are you on about here.
If something doesn't work, install required components using winetricks.
Simply install package winetricks, open it, and navigate graphically to
install .Net Frameworks, C++ redistributables and whatever else your
Windows app needs to operate.
Is not that paragraph sufficient justification for my question?
YMMV
ROFL
YMMV, yeah. Works perfectly fine for me though. I use Wine profiles,
Wine devel from WineHQ, Lutris Wine, Steam Proton Wine. Everything
polished and purposely used, no problems whatsoever, I use Forex trading
program 24/7/365 in Wine, among many other things. My "mileage" is great.
Let me know if you have any real questions.
--
With kindest regards, Piotr.
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄
Re: _INTRODUCTION_ to installing/using Wine?
On 09/26/2021 08:54 AM, piorunz wrote:
On 26/09/2021 14:42, Richard Owlett wrote:
I have not used any version of Windows since WinXP and have the AMD64
flavor of Debian 10.7 installed on the relevant machine.
I wish to do two things:
1. Explore some text manipulation applications I used then
(obviously 32 bit apps).
2. Explore Bible study tools used by others at church
(32 or 64 bit ???).
I have found references [1][2] suitable for addressing specific detailed
questions. I'm looking for introductory material -- especially such that
would cause me to think of questions I should consider before proceeding.
Suggestions?
TIA
References:
1. https://wiki.debian.org/Wine
2. https://www.winehq.org/
Goes into much detail but does not have an "overview only" page.
After you install Wine (your reference materials covers that), simply
execute in terminal "wine name_of_your_exe" from the folder where .exe is.
That's all.
I *DOUBT* it as:
1. I'm well past "three score and ten" ;}
2. [1] explicitly states:
> Users on a 64-bit system should make sure that both wine32
> and wine64 (...) are installed ...
Careful reading of [1] and [2] {w/apologies to J. Caesar} suggests:
" All .exe are divided into three flavors:
1. pure 32 bit
2. pure 64 bit
3. pure hodgepodge
"
If something doesn't work, install required components using winetricks.
Simply install package winetricks, open it, and navigate graphically to
install .Net Frameworks, C++ redistributables and whatever else your
Windows app needs to operate.
Is not that paragraph sufficient justification for my question?
YMMV
ROFL
;}
--
With kindest regards, Piotr.
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄
Re: _INTRODUCTION_ to installing/using Wine?
On 26/09/2021 14:42, Richard Owlett wrote: I have not used any version of Windows since WinXP and have the AMD64 flavor of Debian 10.7 installed on the relevant machine. I wish to do two things: 1. Explore some text manipulation applications I used then (obviously 32 bit apps). 2. Explore Bible study tools used by others at church (32 or 64 bit ???). I have found references [1][2] suitable for addressing specific detailed questions. I'm looking for introductory material -- especially such that would cause me to think of questions I should consider before proceeding. Suggestions? TIA References: 1. https://wiki.debian.org/Wine 2. https://www.winehq.org/ Goes into much detail but does not have an "overview only" page. After you install Wine (your reference materials covers that), simply execute in terminal "wine name_of_your_exe" from the folder where .exe is. That's all. If something doesn't work, install required components using winetricks. Simply install package winetricks, open it, and navigate graphically to install .Net Frameworks, C++ redistributables and whatever else your Windows app needs to operate. -- With kindest regards, Piotr. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org ⠈⠳⣄
_INTRODUCTION_ to installing/using Wine?
I have not used any version of Windows since WinXP and have the AMD64 flavor of Debian 10.7 installed on the relevant machine. I wish to do two things: 1. Explore some text manipulation applications I used then (obviously 32 bit apps). 2. Explore Bible study tools used by others at church (32 or 64 bit ???). I have found references [1][2] suitable for addressing specific detailed questions. I'm looking for introductory material -- especially such that would cause me to think of questions I should consider before proceeding. Suggestions? TIA References: 1. https://wiki.debian.org/Wine 2. https://www.winehq.org/ Goes into much detail but does not have an "overview only" page.
Re: Avonturen met virt-manager en wine
Paul van der Vlis schreef op di 14-09-2021 om 15:53 [+0200]: > Op 14-09-2021 om 15:50 schreef Paul van der Vlis: > > Ik had altijd begrepen dat ze alleen groeiden, en nooit kleiner > > werden. > > Dat je daarvoor een conversie moet doen die veel ruimte kost. Ik > > zit hiermee bijvoorbeeld met mijn mailserver, daar wordt veel > > gewist. > > Dit staat er in mijn aantekeningen, om te verkleinen: > qemu-img convert -p -O qcow2 kvm52.qcow2 kvm52-klein.qcow2 > > Maar dan heb je dus tijdelijk veel ruimte nodig. > > Misschien dat trim het ook zelf kan... Windows-VM's doen voor zover ik gevonden heb geen discard/trim op schijven die via de "virtio" bus zijn aangesloten. In elk geval niet automatisch. Als je de disks via een (Virtio) SCSI controller op de VM aansluit gebeurt dit wél. De .qcow2 files op de host worden na zo'n discard ook kleiner. (dit werkt ook als je "sparse volumes" in LVM gebruikt in plaats van qcow-bestanden) -Martijn
Re: Avonturen met virt-manager en wine
Op 14-09-2021 om 15:50 schreef Paul van der Vlis: Ik had altijd begrepen dat ze alleen groeiden, en nooit kleiner werden. Dat je daarvoor een conversie moet doen die veel ruimte kost. Ik zit hiermee bijvoorbeeld met mijn mailserver, daar wordt veel gewist. Dit staat er in mijn aantekeningen, om te verkleinen: qemu-img convert -p -O qcow2 kvm52.qcow2 kvm52-klein.qcow2 Maar dan heb je dus tijdelijk veel ruimte nodig. Misschien dat trim het ook zelf kan... Groet, Paul -- Paul van der Vlis Linux systeembeheer Groningen https://www.vandervlis.nl/
Re: Avonturen met virt-manager en wine
Hallo Wouter en anderen,
Op 14-09-2021 om 13:55 schreef Wouter Verhelst:
Hoi Paul,
Persoonlijk werk ik liever met system VMs (en zelfs virsh geeft je een
warning als je user context VMs probeert aan te maken), maar de keuze is
er dus.
Op een server is dat inderdaad beter, maar ik was hier bezig in een
desktop context. Windows applicaties draaien onder Linux.
Wat me nog negatief opviel was dat je alleen virtuele harddisks kon aanmaken
die de volledige grootte hebben.
Nee, dat is niet correct:
root@pc181009:/var/lib/libvirt/images# ls -lh debian.qcow2
-rw--- 1 root root 21G 25 aug 18:33 debian.qcow2
root@pc181009:/var/lib/libvirt/images# du -sh debian.qcow2
2,2Gdebian.qcow2
Wat raar zeg, blijkbaar geeft ls -lh dus niet altijd de juiste waarde??
Toch wel, maar wat het je toont is niet wat jij denkt dat het is ;-)
>
"ls -l" geeft je de apparent size; "ls -s" geeft je de hoeveelheid
blocks die in gebruik zijn. De twee zijn niet dezelfde waarde
Is hier misschien iets aan veranderd?
Nee hoor; sparse files bestaan al *heel* lang. Wikipedia legt redelijk
goed uit hoe ze functioneren:
https://en.wikipedia.org/wiki/Sparse_file
Ik dacht dat ik op de server wel de gebruikte ruimte kreeg met "ls -lh",
maar misschien moet ik dit beter controleren.
Het bestand is een "sparse file": dat lijkt in mijn geval 21G groot
te zijn, maar neemt in werkelijkheid slechts 2.2G in beslag. Als het
OS in de VM ook de relevante trim/discard SCSI en ATA calls
gebruikt, dan zal qemu dat opnieuw vrijgeven (mijn Windows VM doet
dat niet en gebruikt dus de volledige content van de virtuele hard
disk, maar mijn Linux VMs doen het allemaal wel goed).
Gut, bij mij doen de Linux VM's dat niet. Ik moet wellicht de host
upgraden.
Het kan ook gewoon config binnen de VM zijn hoor. Kijk na of je
trim/discard aan hebt staan op je mounted filesystems.
Alternatief heb ik misschien een foutje gemaakt en doet qemu helemaal
geen fallocate() om het bestand terug sparse te maken, maar worden
alleen sparse files aangemaakt bij het aanmaken van de VM. Deze VM is
nog niet zó geweldig veel gebruikt, dus het kan zijn dat dat de reden is
dat het bestand nog niet helemaal gealloceerd is...
Ik had altijd begrepen dat ze alleen groeiden, en nooit kleiner werden.
Dat je daarvoor een conversie moet doen die veel ruimte kost. Ik zit
hiermee bijvoorbeeld met mijn mailserver, daar wordt veel gewist.
Je kan verder ook andere storage backends configureren:
rechtermuisknop op "QEMU/KVM" -> Details -> Storage -> op "+" klikken
onderaan links -> Type openklappen. Bij mij zie ik:
dir: Bestandssysteem map
disk: Fysiek schijf apparaat
fs: Pre-geformatteerd blok apparaat
gluster: Gluster Filesystem
iscsi: iSCSI doel
logical: LVM volume group
mpath: Multi-pad apparaat opsommen
netfs: Netwerk geëxporteerde map
rbd: RADOS Block Device/Ceph
scsi: SCSI host adapter
sheepdog: Sheepdog Filesystem
zfs: ZFS Pool
Interessant, vooral die "dir" kende ik nog niet.
Eh, dat is de default, en is waarschijnlijk ook degene die je gebruikt ;-)
("dir" maakt gewoon .qcow2-bestanden aan in een directory ergens op het
bestandssysteem)
Ah. Ik dacht even dat je de gegevens ook gewoon direct in een directory
kon zetten, zoals bij een chroot. Maar dus niet.
Groet,
Paul
--
Paul van der Vlis Linux systeembeheer Groningen
https://www.vandervlis.nl/
Re: Avonturen met virt-manager en wine
Hoi Paul,
On Sat, Sep 11, 2021 at 10:38:01PM +0200, Paul van der Vlis wrote:
> Op 08-09-2021 om 17:44 schreef Wouter Verhelst:
[...]
> > Je weet dat dat niet toegestaan is volgens de licentie?
>
> Nee, wist ik niet precies. Maar was te verwachten.
Tjah :)
[...]
> > > Wat me nog opviel was dat virt-manager root rechten nodig heeft. Maar je
> > > kunt er vrij simpel voor zorgen dat hij dat blijvend krijgt door ergens
> > > een
> > > vinkje te zetten. De disks van je virtuele machines komen niet in je
> > > home-directory maar ergens in /var/lib/libvirt.
> >
> > Je kan ook je gebruiker aan de juiste groep toevoegen:
> >
> > sudo adduser wouter libvirt
> >
> > Nu heeft de gebruiker 'wouter' rechten om de VMs in de "system" libvirtd
> > te beheren.
>
> Bij nader inzien had ik dat waarschijnlijk ook gedaan.
>
> > Alternatief is het ook perfect mogelijk om een libvirtd in
> > gebruikerscontext te draaien, maar dan kan je alleen NAT netwerken
> > gebruiken (naast een aantal andere minimale beperkingen). Als je dat
> > wilt proberen, dan doe je
> >
> > Bestand -> Verbinding toevoegen... -> QEMU/KVM gebruikerssessie
> >
> > VMs in een gebruikerssessie draaien onder de UID van de gebruiker ipv de
> > "libvirt" UID, en virtuele hard disks worden dan in
> > $HOME/.local/share/libvirt/images geschreven.
>
> Aha. Zal ik in mijn gedachten houden. Wellicht beter inderdaad.
Goh. In sommige situaties is dat handiger, ja, maar zeker niet altijd;
vooral als je geen systemd gebruikt is dat geen goed idee (want dan
worden je VMs niet correct afgesloten bij het afsluiten van het
systeem). Ook is een VM in user context niet direct beschikbaar van
buiten het virtuele netwerk (zelfs niet vanop de host), omwille van
NAT-only netwerken en zo.
Persoonlijk werk ik liever met system VMs (en zelfs virsh geeft je een
warning als je user context VMs probeert aan te maken), maar de keuze is
er dus.
[...]
> > > Wat me nog negatief opviel was dat je alleen virtuele harddisks kon
> > > aanmaken
> > > die de volledige grootte hebben.
> >
> > Nee, dat is niet correct:
> >
> > root@pc181009:/var/lib/libvirt/images# ls -lh debian.qcow2
> > -rw--- 1 root root 21G 25 aug 18:33 debian.qcow2
> > root@pc181009:/var/lib/libvirt/images# du -sh debian.qcow2
> > 2,2Gdebian.qcow2
>
> Wat raar zeg, blijkbaar geeft ls -lh dus niet altijd de juiste waarde??
Toch wel, maar wat het je toont is niet wat jij denkt dat het is ;-)
"ls -l" geeft je de apparent size; "ls -s" geeft je de hoeveelheid
blocks die in gebruik zijn. De twee zijn niet dezelfde waarde
> Is hier misschien iets aan veranderd?
Nee hoor; sparse files bestaan al *heel* lang. Wikipedia legt redelijk
goed uit hoe ze functioneren:
https://en.wikipedia.org/wiki/Sparse_file
> > Het bestand is een "sparse file": dat lijkt in mijn geval 21G groot
> > te zijn, maar neemt in werkelijkheid slechts 2.2G in beslag. Als het
> > OS in de VM ook de relevante trim/discard SCSI en ATA calls
> > gebruikt, dan zal qemu dat opnieuw vrijgeven (mijn Windows VM doet
> > dat niet en gebruikt dus de volledige content van de virtuele hard
> > disk, maar mijn Linux VMs doen het allemaal wel goed).
>
> Gut, bij mij doen de Linux VM's dat niet. Ik moet wellicht de host
> upgraden.
Het kan ook gewoon config binnen de VM zijn hoor. Kijk na of je
trim/discard aan hebt staan op je mounted filesystems.
Alternatief heb ik misschien een foutje gemaakt en doet qemu helemaal
geen fallocate() om het bestand terug sparse te maken, maar worden
alleen sparse files aangemaakt bij het aanmaken van de VM. Deze VM is
nog niet zó geweldig veel gebruikt, dus het kan zijn dat dat de reden is
dat het bestand nog niet helemaal gealloceerd is...
> > Je kan verder ook andere storage backends configureren:
> >
> > rechtermuisknop op "QEMU/KVM" -> Details -> Storage -> op "+" klikken
> > onderaan links -> Type openklappen. Bij mij zie ik:
> >
> > dir: Bestandssysteem map
> > disk: Fysiek schijf apparaat
> > fs: Pre-geformatteerd blok apparaat
> > gluster: Gluster Filesystem
> > iscsi: iSCSI doel
> > logical: LVM volume group
> > mpath: Multi-pad apparaat opsommen
> > netfs: Netwerk geëxporteerde map
> > rbd: RADOS Block Device/Ceph
> > scsi: SCSI host adapter
> > sheepdog: Sheepdog Filesystem
> > zfs: ZFS Pool
>
> Interessant, vooral die "dir" kende ik nog niet.
Eh, dat is de default, en is waarschijnlijk ook degene die je gebruikt ;-)
("dir" maakt gewoon .qcow2-bestanden aan in een directory ergens op het
bestandssysteem)
Groeten,
--
w@uter.{be,co.za}
wouter@{grep.be,fosdem.org,debian.org}
Re: Avonturen met virt-manager en wine
Op 08-09-2021 om 17:44 schreef Wouter Verhelst: On Wed, Sep 01, 2021 at 04:08:40PM +0200, Paul van der Vlis wrote: [...] Nu hoorde ik dat je Windows 10 ook gewoon als ISO kon downloaden. Een kennis had hier wat meer verstand van, en die heeft dat toen gedaan. Omdat ik hier vele oudere laptops heb, hebben we gewoon van een willekeurige laptop een Windows7 registratie-code afgehaald, en dat bleek te functioneren binnen de Windows10 Pro virtuele machine. Ook al was de (virtuele) hardware anders. Je weet dat dat niet toegestaan is volgens de licentie? Nee, wist ik niet precies. Maar was te verwachten. Die licentie is enkel en alleen geldig voor de laptop waar de sticker op plakt. Bij moderne hardware heb je geen sticker meer, maar zit er een licentiecode in de ACPI tables (ten minste als je een laptop met Windows erop koopt). Als dat het geval is, dan heb je onder /sys/firmware/acpi/tables een bestand "MSDM" en een bestand "SLIC" staan waarin de relevante gegevens te vinden zijn, en je kan die (mits wat prullen) doorlussen naar een VM. Op mijn laptop deed ik dat als volgt: - dmidecode -t 0 Dat geeft de volgende uitvoer: # dmidecode 3.3 Getting SMBIOS data from sysfs. SMBIOS 3.1.1 present. Handle 0x, DMI type 0, 26 bytes BIOS Information Vendor: Dell Inc. Version: 1.16.3 Release Date: 03/05/2021 Address: 0xF Runtime Size: 64 kB ROM Size: 16 MB Characteristics: PCI is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported EDD is supported Japanese floppy for NEC 9800 1.2 MB is supported (int 13h) 5.25"/1.2 MB floppy services are supported (int 13h) 3.5"/720 kB floppy services are supported (int 13h) 3.5"/2.88 MB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) ACPI is supported USB legacy is supported Smart battery is supported BIOS boot specification is supported Function key-initiated network boot is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 1.16 - dmidecode -t 1 Uitvoer: # dmidecode 3.3 Getting SMBIOS data from sysfs. SMBIOS 3.1.1 present. Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: Dell Inc. Product Name: Latitude 5590 Version: Not Specified Serial Number: D5X3HR2 UUID: 4c4c4544-0035-5810-8033-c4c04f485232 Wake-up Type: Power Switch SKU Number: 0817 Family: Latitude - cp /sys/firmware/acpi/tables/MSDM /var/lib/libvirt/images/MSDM.raw - cp /sys/firmware/acpi/tables/SLIC /var/lib/libvirt/images/SLIC.raw - Zorg ervoor dat je Windows VM niet draait en dat het bestaat. - virsh edit Dat laatste commando opent een editor, en daar zorg je er dan voor dat er dit in staat: Pas het tweede en vierde "qemu:arg" aan met de relevante informatie uit de relevante "dmidecode" commando's. Proficiat, je bent nu een geldige licentie aan het gebruiken! Bedankt! (het zou wel handig zijn als virt-manager daar gewoon een vinkje voor had, maar...) Ook die spice-guest-tools deden het prima. We hadden overigens gekozen voor de 32-bit versie van Windows10, omdat die veel minder geheugen nodig heeft (minimaal 1GB). Dus copy/paste van tekst werkt prima (iets anders heb ik niet geprobeerd), de muis gaat vloeiend naar de client, en het herschalen van het venster met de virtuele machine gaat prima. Ook kon ik USB-apparaten van de host redirecten. Overigens lukte dit niet met een SD-kaart-lezer, maar dat bleek geen USB device te zijn. Waar ik nog wel flinke problemen mee had was met het netwerk. Dat deed het in eerste instantie prima, alleen na een reboot van de host-machine niet meer. En daardoor wilden de virtuele machines niet meer starten. Na lang zoeken vond ik ergens in Virt-manager een optie om het netwerk automatisch te starten, als ik me niet vergis in "bewerken | verbinding details". Zonder dat starten de VM's niet, zelfs niet als ze geen netwerk kaart hebben. Je kan ook dat in virsh doen: net-autostart default Oh kijk! Wat me nog opviel was dat virt-manager root rechten nodig heeft. Maar je kunt er vrij simpel voor zorgen dat hij dat blijvend krijgt door ergens een vinkje te zetten. De disks van je virtuele machines komen niet in je home-directory maar ergens in /var/lib/libvirt. Je kan ook je gebruiker aan de juiste groep toevoegen: sudo adduser
Re: Avonturen met virt-manager en wine
On Wed, Sep 01, 2021 at 04:08:40PM +0200, Paul van der Vlis wrote: [...] > Nu hoorde ik dat je Windows 10 ook gewoon als ISO kon downloaden. Een kennis > had hier wat meer verstand van, en die heeft dat toen gedaan. Omdat ik hier > vele oudere laptops heb, hebben we gewoon van een willekeurige laptop een > Windows7 registratie-code afgehaald, en dat bleek te functioneren binnen de > Windows10 Pro virtuele machine. Ook al was de (virtuele) hardware anders. Je weet dat dat niet toegestaan is volgens de licentie? Die licentie is enkel en alleen geldig voor de laptop waar de sticker op plakt. Bij moderne hardware heb je geen sticker meer, maar zit er een licentiecode in de ACPI tables (ten minste als je een laptop met Windows erop koopt). Als dat het geval is, dan heb je onder /sys/firmware/acpi/tables een bestand "MSDM" en een bestand "SLIC" staan waarin de relevante gegevens te vinden zijn, en je kan die (mits wat prullen) doorlussen naar een VM. Op mijn laptop deed ik dat als volgt: - dmidecode -t 0 Dat geeft de volgende uitvoer: # dmidecode 3.3 Getting SMBIOS data from sysfs. SMBIOS 3.1.1 present. Handle 0x, DMI type 0, 26 bytes BIOS Information Vendor: Dell Inc. Version: 1.16.3 Release Date: 03/05/2021 Address: 0xF Runtime Size: 64 kB ROM Size: 16 MB Characteristics: PCI is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported EDD is supported Japanese floppy for NEC 9800 1.2 MB is supported (int 13h) 5.25"/1.2 MB floppy services are supported (int 13h) 3.5"/720 kB floppy services are supported (int 13h) 3.5"/2.88 MB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) ACPI is supported USB legacy is supported Smart battery is supported BIOS boot specification is supported Function key-initiated network boot is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 1.16 - dmidecode -t 1 Uitvoer: # dmidecode 3.3 Getting SMBIOS data from sysfs. SMBIOS 3.1.1 present. Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: Dell Inc. Product Name: Latitude 5590 Version: Not Specified Serial Number: D5X3HR2 UUID: 4c4c4544-0035-5810-8033-c4c04f485232 Wake-up Type: Power Switch SKU Number: 0817 Family: Latitude - cp /sys/firmware/acpi/tables/MSDM /var/lib/libvirt/images/MSDM.raw - cp /sys/firmware/acpi/tables/SLIC /var/lib/libvirt/images/SLIC.raw - Zorg ervoor dat je Windows VM niet draait en dat het bestaat. - virsh edit Dat laatste commando opent een editor, en daar zorg je er dan voor dat er dit in staat: Pas het tweede en vierde "qemu:arg" aan met de relevante informatie uit de relevante "dmidecode" commando's. Proficiat, je bent nu een geldige licentie aan het gebruiken! (het zou wel handig zijn als virt-manager daar gewoon een vinkje voor had, maar...) > Ook die spice-guest-tools deden het prima. We hadden overigens gekozen voor > de 32-bit versie van Windows10, omdat die veel minder geheugen nodig heeft > (minimaal 1GB). Dus copy/paste van tekst werkt prima (iets anders heb ik > niet geprobeerd), de muis gaat vloeiend naar de client, en het herschalen > van het venster met de virtuele machine gaat prima. Ook kon ik USB-apparaten > van de host redirecten. Overigens lukte dit niet met een SD-kaart-lezer, > maar dat bleek geen USB device te zijn. > > Waar ik nog wel flinke problemen mee had was met het netwerk. Dat deed het > in eerste instantie prima, alleen na een reboot van de host-machine niet > meer. En daardoor wilden de virtuele machines niet meer starten. Na lang > zoeken vond ik ergens in Virt-manager een optie om het netwerk automatisch > te starten, als ik me niet vergis in "bewerken | verbinding details". Zonder > dat starten de VM's niet, zelfs niet als ze geen netwerk kaart hebben. Je kan ook dat in virsh doen: net-autostart default > Wat me nog opviel was dat virt-manager root rechten nodig heeft. Maar je > kunt er vrij simpel voor zorgen dat hij dat blijvend krijgt door ergens een > vinkje te zetten. De disks van je virtuele machines komen niet in je > home-directory maar ergens in /var/lib/libvirt. Je kan ook je gebruiker aan de juiste groep toevoegen: sudo adduser wouter libvirt Nu heeft de gebruiker 'wouter' rechten om de VMs in de "system" libvirtd te beheren.
Avonturen met virt-manager en wine
Hallo, Ik heb niet zoveel ervaring met het draaien van Windows programma's onder Linux, maar ik heb een klant die dat graag wou. Wat hier onder staat gaat over Debian 11. In het verleden heb ik wat matige ervaringen gehad met Wine, daarom ben ik wat kritisch tegenover dat programma. Bij mijn klant had ik daarom aangeraden om maar een virtuele machine te gebruiken. In het verleden heb ik voor klanten wel Virtualbox geïnstalleerd, maar dat zit niet meer in Debian en daarom gebruik ik het liever niet. Een punt was in het verleden ook, dat als er een nieuw kernel kwam, dan moest je de modules opnieuw compileren. Bij zoiets kan natuurlijk iets fout gaan. Ik weet eigenlijk niet zeker of dit nog steeds zo is. Maar goed, ik dus maar eens virt-manager geprobeerd. Gewoon simpel te installeren met "apt install virt-manager", en dan neemt hij meteen ook Qemu, KVM, en dergelijke mee. Klant had me Windows XP meegeleverd. Dat installeerde prima en heeft als voordeel dat het erg weinig geheugen gebruikt. Echter, om het prettig te laten functioneren heb je binnen Windows iets nodig wat "spice guest tools" heet. En dat bleek niet te werken in XP. Je hebt die spice tools nodig voor dingen als copy/paste tussen host en client, maar ook om de muis soepel te switchen tussen beide systemen, en voor een betere grafische driver. Na het installeren van die tools had ik nog maar 4 kleuren, het zag er niet uit. Later las ik dat XP niet meer gesupport werd. Hier zijn die tools te downloaden: https://www.spice-space.org/download.html Ik vond ze niet in Debian, terwijl ik de "virtualbox-guest-additions-iso" hier wel vind (in non-free). Dat XP niet goed functioneerde was een flinke tegenvaller. Daarom ben ik ook aan de slag gegaan met Wine. Eigenlijk ging dat vrij goed en soepel, alleen kreeg ik OLE foutmeldingen tijdens de installatie. Mocht iemand weten wat ik daar tegen kan doen, dan hoor ik dat graag. Daarna functioneerde het programma, maar was het niet mogelijk om bijvoorbeeld een foto te verplaatsen met "drag en drop" in de applicatie. Gewone copy/paste deed het wel. Maar een punt bij Wine vind ik altijd, dat je nooit zeker weet of het blijft functioneren, of dat je toch later nog dingen vind die niet functioneren. Ik vond het dus wat onzeker, zeker omdat de klant ver weg woont. Nu hoorde ik dat je Windows 10 ook gewoon als ISO kon downloaden. Een kennis had hier wat meer verstand van, en die heeft dat toen gedaan. Omdat ik hier vele oudere laptops heb, hebben we gewoon van een willekeurige laptop een Windows7 registratie-code afgehaald, en dat bleek te functioneren binnen de Windows10 Pro virtuele machine. Ook al was de (virtuele) hardware anders. Ook die spice-guest-tools deden het prima. We hadden overigens gekozen voor de 32-bit versie van Windows10, omdat die veel minder geheugen nodig heeft (minimaal 1GB). Dus copy/paste van tekst werkt prima (iets anders heb ik niet geprobeerd), de muis gaat vloeiend naar de client, en het herschalen van het venster met de virtuele machine gaat prima. Ook kon ik USB-apparaten van de host redirecten. Overigens lukte dit niet met een SD-kaart-lezer, maar dat bleek geen USB device te zijn. Waar ik nog wel flinke problemen mee had was met het netwerk. Dat deed het in eerste instantie prima, alleen na een reboot van de host-machine niet meer. En daardoor wilden de virtuele machines niet meer starten. Na lang zoeken vond ik ergens in Virt-manager een optie om het netwerk automatisch te starten, als ik me niet vergis in "bewerken | verbinding details". Zonder dat starten de VM's niet, zelfs niet als ze geen netwerk kaart hebben. Wat me nog opviel was dat virt-manager root rechten nodig heeft. Maar je kunt er vrij simpel voor zorgen dat hij dat blijvend krijgt door ergens een vinkje te zetten. De disks van je virtuele machines komen niet in je home-directory maar ergens in /var/lib/libvirt. Wat me nog negatief opviel was dat je alleen virtuele harddisks kon aanmaken die de volledige grootte hebben. Normaal gebruik ik met Qemu disks die "groeien", dus als er meer ruimte nodig is worden ze groter. Dit lukte me in eerste instantie niet met virt-manager. Een 20GB harddisk voor een VM is dus echt 20GB groot. Het is vast mogelijk om het toch op een of andere manier te doen, eventueel buiten virt-manager. De klant wou niet dat Windows bij het internet kon. Wat ik gedaan heb is na installatie de virtuele netwerkkabel verwijderd, dat is ook simpel aan en uit te zetten in de eigenschappen van de virtuele machine (bij de netwerk kaart). De netwerk kaart verwijderen had vast ook gekund. Waar ik ook naar gekeken heb is een soort gedeelde map tussen client en host, maar dat is me niet gelukt. Nu ja, via een USB-stick. Omdat de klant geen netwerk wou heb ik geen Samba geprobeerd, dat had het waarschijnlijk wel gedaan. Wat ik wel geprobeerd heb is iets wat in die Spic
