From the beginning when I switched from mga32 to mga64, there was big
trouble regarding wine.
I need to have 16 and 32 bit windows executables running, and this seems
only possible by installing wine32 in addition to wine64.

This requires to also install further i586 packages to allow wine32
running.

Unfortunately, when 64bit packages with same or similar names have to be updated, then mcc requests to delete all i586 packages with same name.

Hence, wine32 then no longer works, until all these are reinstalled by
hand (!).

Interestingly, Ubuntu linux only has one wine64, which can serve 16, 32,
64 bit windows executables. So, none of these problems occur.

Why does mageia stick to this oldfashioned wine32 vs. wine64 nonsense?

BR,

Markus

--- MBSE BBS v1.1.0 (Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

Hello Markus!

Sunday August 04 2024 08:41, Markus Robert Kessler wrote to All:

From the beginning when I switched from mga32 to mga64, there was big trouble regarding wine.
I need to have 16 and 32 bit windows executables running, and this
seems only possible by installing wine32 in addition to wine64.

This requires to also install further i586 packages to allow wine32
running.

Unfortunately, when 64bit packages with same or similar names have to
be updated, then mcc requests to delete all i586 packages with same
name.

Hence, wine32 then no longer works, until all these are reinstalled by
hand (!).

Interestingly, Ubuntu linux only has one wine64, which can serve 16,
32, 64 bit windows executables. So, none of these problems occur.

Why does mageia stick to this oldfashioned wine32 vs. wine64 nonsense?

I seem to recall some time back that there was no provision for upgrading
from 32 to 64 bit.

The only solution was to install a fresh 64 bit version and transfer data
that did not need a conversion over from old to new.

Your problems seem to indicate that this is still the case.

Installing a 64 bit version allows you to run 32bit applications as mga
will then install the required extra libs when and as needed providing you
use mga package manager to install all apps. Therefore it is wise to do
this with the packages available within mga FIRST before trying outside of
it.

Just my 5 pence worth.

Vincent


SEEN-BY: 25/0 21 250/0 1 2 3 4 5 8 13 14 15 263/0 362/6 467/4 712/1321

On 8/4/2024 12:41 AM, Markus Robert Kessler wrote:

From the beginning when I switched from mga32 to mga64, there was big trouble regarding wine.
I need to have 16 and 32 bit windows executables running, and this seems
only possible by installing wine32 in addition to wine64.

This requires to also install further i586 packages to allow wine32
running.

Unfortunately, when 64bit packages with same or similar names have to be updated, then mcc requests to delete all i586 packages with same name.

Hence, wine32 then no longer works, until all these are reinstalled by
hand (!).

Interestingly, Ubuntu linux only has one wine64, which can serve 16, 32,
64 bit windows executables. So, none of these problems occur.

Why does mageia stick to this oldfashioned wine32 vs. wine64 nonsense?

BR,

Markus

Also, Win64 has no support for WOW (16-bit windows apps), so that may
be why you need the 32-bit version to run 16 bit apps.

--- MBSE BBS v1.1.0 (Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 8/4/2024 3:03 PM, Vincent Coen wrote:

Hello Markus!

Sunday August 04 2024 08:41, Markus Robert Kessler wrote to All:

> From the beginning when I switched from mga32 to mga64, there was big
> trouble regarding wine.
> I need to have 16 and 32 bit windows executables running, and this
> seems only possible by installing wine32 in addition to wine64.

> This requires to also install further i586 packages to allow wine32
> running.

> Unfortunately, when 64bit packages with same or similar names have to
> be updated, then mcc requests to delete all i586 packages with same
> name.

> Hence, wine32 then no longer works, until all these are reinstalled by
> hand (!).

> Interestingly, Ubuntu linux only has one wine64, which can serve 16,
> 32, 64 bit windows executables. So, none of these problems occur.

> Why does mageia stick to this oldfashioned wine32 vs. wine64 nonsense?

Also, 64-bit windows didn't support WOW (16-bit apps), so that may be
why you needed to install the 32-bit version.



--- MBSE BBS v1.1.0 (Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

red floyd wrote on 6/8/24 10:59 am:

On 8/4/2024 12:41 AM, Markus Robert Kessler wrote:

From the beginning when I switched from mga32 to mga64, there was
big trouble regarding wine. I need to have 16 and 32 bit windows
executables running, and this seems only possible by installing
wine32 in addition to wine64.

This requires to also install further i586 packages to allow
wine32 running.

Unfortunately, when 64bit packages with same or similar names have
to be updated, then mcc requests to delete all i586 packages with
same name.

Hence, wine32 then no longer works, until all these are reinstalled
by hand (!).

Interestingly, Ubuntu linux only has one wine64, which can serve
16, 32, 64 bit windows executables. So, none of these problems
occur.

Why does mageia stick to this oldfashioned wine32 vs. wine64
nonsense?

BR,

Markus

Also, Win64 has no support for WOW (16-bit windows apps), so that
may be why you need the 32-bit version to run 16 bit apps.

Hmmm!! I thought the 'WOW' was to indicate the Windows 32 bit OS had
been 'modified' to run on 64 bit Hardware.

But what would I know??
--
Daniel

--- MBSE BBS v1.1.0 (Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)