Program no long runs in new Wine ver. Get "Bad EXE format"

[murkyin14]

Previous versions:
RHEL 6.2
wine-1.2.3

New versions:
CentOS 7.0
wine-1.7.22

The program's installer runs fine (same installer program used for the old and new version of wine). In the previous wine, the program goes into C:\Program Files whereas in the new wine version, the program is installed in C:\Program Files (x86). This may be a clue.
When I try to run the installed program in the new wine version, I receive the error

Code: Select all

wine: Bad EXE format for C:\Program Files (x86)\Microbotics, Inc\Core Files\MIDG Display Utility\midgdspl.exe.

I run "file" on the executable file and the old version it says:

Code: Select all

midgdspl.exe: PE32 executable for MS Windows (GUI) Intel 80386 32-bit

and on the new version it says:

Code: Select all

midgdspl.exe: PE32 executable (GUI) Intel 80386, for MS Windows

I am thinking that there is a problem with the wine running 32 / 64 bit but I am not sure how to remedy the situation.
I tried creating a 32-bit prefix under wine-1.7.22 but it doesn't look like I can do that since I cannot find a wine-core.i686 package.
If anyone wants to give it a try, the program I am trying to install is at http://www.microboticsinc.com/Downloads ... 0XP-64.zip

[dimesio]

I am thinking that there is a problem with the wine running 32 / 64 bit but I am not sure how to remedy the situation.
I tried creating a 32-bit prefix under wine-1.7.22 but it doesn't look like I can do that since I cannot find a wine-core.i686 package.

How did you try to create a 32 bit wineprefix, and what happened--what was the console output?

If you only installed 64 bit Wine, without the 32 bit parts needed for WoW64, that could be the cause of your problem. As for which package to install, ask your distro, or contact the package maintainer; packages are built by the distros, not here. You other choice is to build Wine yourself.

[murkyin14]

I am thinking that there is a problem with the wine running 32 / 64 bit but I am not sure how to remedy the situation.
I tried creating a 32-bit prefix under wine-1.7.22 but it doesn't look like I can do that since I cannot find a wine-core.i686 package.

How did you try to create a 32 bit wineprefix, and what happened--what was the console output?

If you only installed 64 bit Wine, without the 32 bit parts needed for WoW64, that could be the cause of your problem. As for which package to install, ask your distro, or contact the package maintainer; packages are built by the distros, not here. You other choice is to build Wine yourself.

This is what I get when I tried to create the new prefix with:

Code: Select all

$ WINEARCH=win32 WINEPREFIX=~/.wine32 winecfg
wine: created the configuration directory '~/.wine32'
wine: '~/.wine32' is a 32-bit installation, it cannot support 64-bit applications.

and winecfg did not run.

I cannot find packages for 32 bit wine under Redhat or CentOS 7 so I guess my only choice is to build it myself?

[dimesio]

It does look like you only have 64 bit Wine installed. You should report the problem to the package maintainer; pure 64 bit Wine is largely useless, as most Windows apps are still 32 bit.

If there is no package, you will have to build Wine yourself. Unless you have 64 bit Windows apps you are trying to run, I recommend just building 32 bit Wine on 64 bit, as creating a shared WoW64 setup is more complicated, even on a true multiarch distro. The instructions in our wiki for building on CentOS are pretty outdated, but they should get you started in figuring out which packages you need to install for Wine's build dependencies. http://wiki.winehq.org/WineOn64bit

[subdriven]

Since you're running CentOS 7 and CentOS 7 hasn't released 32-bit packages (because Red Hat isn't/hasn't going to either), then I think we're kinda screwed. I'm in the same boat here and if you find a workaround I'm all ears.

[subdriven]

murkyin14:
Looks like I jumped the gun a bit; there are 32-bit packages and ways to get Wine installed. Check out this forum post at CentOS. I've not run though it yet but it looks promising.
https://www.centos.org/forums/viewtopic ... 48&t=47325