This seems to be a pretty common problem with Wine and it also seems it is a non-specific error. All the things I've read either go off topic with "why are you installing that rather than ..." or various other non-applicable replies and in some cases no reply at all. This is very frustrating when the very first thing I try to install gets this error. The exe I am using is NOT a bad format. It is a perfectly good installer.
OS: CentOS 7
Wine: 1.7.22
One other error I get, which again from my research seems common with no solution is:
fixme:service:scmdatabase_autostart_services Auto-start service L"MountMgr" failed to start: 2
I don't know if that really matters because the Wine native applications (e.g. notepad) get the same thing, but still work.
I realize the CentOS repo version is "broken by design" (kind of an odd statement) but I think I have the 32 bit version installed.
So my question is how do I shoot this bug? TIA.
Bad EXE Format
Re: Bad EXE Format
Both the "Bad EXE format" and MountMgr errors indicate you don't. Where did you get Wine from? AFAIK, the only way to get 32 bit Wine on CentOS 7 is to build it yourself, and that also involves building the 32 bit dependencies.gw1500se wrote: but I think I have the 32 bit version installed.
Re: Bad EXE Format
Yep, after more research it seems that a 32 bit version of Wine cannot be built on CentOS 7. Even from source the configure script forces 64 bit. I have been thwarted at every step by one thing or another. I even looked at lxc but there also seems to be no way to build a 32 bit container either. Not sure why CentOS is an orphan to Wine but I guess it is time to give up. CentOS just does not seem to be supported any of the usual emulators (Wine, VirtualBox, CorssOver) because of the pure 64 bit environment.