question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

rcedit.exe failed with exit code 193. wine: Bad EXE format

See original GitHub issue

Please describe your issue: i have centos 7 64 bit node v6.10.2

electron-packager hello-win32-ia32_old hello --platform=win32 --arch=ia32 --overwrite --no-prune

using above command i have build but getting below errro

Packaging app for platform win32 ia32 using electron v1.6.8 rcedit.exe failed with exit code 193. wine: Bad EXE format for Z:\usr\lib\node_modules\electron-packager\node_modules\rcedit\bin\rcedit.exe.

**Please provide either a failing minimal testcase (with a link to the code) or detailed steps

[root@aasd electron-quick-start]# npm start

electron-quick-start@1.0.0 start /root/electron-quick-start electron .

npm ERR! Linux 3.10.0-514.16.1.el7.x86_64 npm ERR! argv “/usr/bin/node” “/usr/local/bin/npm” “start” npm ERR! node v6.10.2 npm ERR! npm v4.0.5 npm ERR! code ELIFECYCLE npm ERR! electron-quick-start@1.0.0 start: electron . npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the electron-quick-start@1.0.0 start script ‘electron .’. npm ERR! Make sure you have the latest version of node.js and npm installed. npm ERR! If you do, this is most likely a problem with the electron-quick-start package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! electron . npm ERR! You can get information on how to open an issue for this project with: npm ERR! npm bugs electron-quick-start npm ERR! Or if that isn’t available, you can get their info via: npm ERR! npm owner ls electron-quick-start npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request: npm ERR! /root/electron-quick-start/npm-debug.log

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:9 (4 by maintainers)

github_iconTop GitHub Comments

12reactions
maleptcommented, May 25, 2017

No, you can certainly build Windows packages on non-Windows, 64-bit host platforms. In fact, the CI for this project does just that on both macOS and (Ubuntu 14.04) Linux. On Debian/Ubuntu-derived Linux distributions, if you only have wine64 installed, it prints the following instructions to help you install the 32-bit version of wine:

it looks like multiarch needs to be enabled.  as root, please
execute "dpkg --add-architecture i386 && apt-get update &&
apt-get install wine32"

If you need instructions on how to do this for CentOS, I would suggest looking in CentOS-specific support channels.

0reactions
stephen-smithcommented, Sep 12, 2019

On Debian/Ubuntu-derived Linux distributions, if you only have wine64 installed, it prints the following instructions

Those are great instructions, but they aren’t printed down all failure paths.

% npm run build_win

> logviewer@1.0.0 build_win /home/me/git/LogViewer
> electron-packager . --platform=win32 --arch=x64  --icon=src/assets/images/app.ico --overwrite

Packaging app for platform win32 x64 using electron v6.0.9
WARNING: Found 'electron' but not as a devDependency, pruning anyway
rcedit.exe failed with exit code 193. wine: created the configuration directory '/home/me/.wine'
Could not load wine-gecko. HTML rendering will be disabled.
Could not load wine-gecko. HTML rendering will be disabled.
wine: configuration in '/home/me/.wine' has been updated.
wine: Bad EXE format for Z:\home\me\git\LogViewer\node_modules\rcedit\bin\rcedit.exe.

npm ERR! Linux 5.0.0-27-generic
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "run" "build_win"
npm ERR! node v8.10.0
npm ERR! npm  v3.5.2
npm ERR! code ELIFECYCLE
npm ERR! logviewer@1.0.0 build_win: `electron-packager . --platform=win32 --arch=x64  --icon=src/assets/images/app.ico --overwrite`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the logviewer@1.0.0 build_win script 'electron-packager . --platform=win32 --arch=x64  --icon=src/assets/images/toshiba.ico --overwrite'.
Exit Code: 1 % cat /etc/debian_version
buster/sid
Read more comments on GitHub >

github_iconTop Results From Across the Web

rcedit.exe failed with exit code 193. wine: Bad EXE format
My solution is now this: FROM node:10 RUN dpkg --add-architecture i386 && apt-get update && apt-get install wine wine32 -y RUN npm install ......
Read more >
[Solved]-rcedit.exe failed with exit code 193. wine
Coding example for the question rcedit.exe failed with exit code 193. wine: Bad EXE format-docker.
Read more >
Wine: Bad EXE format
When I tried to start the Installer, I get an error saying Bad EXE format. File: GMStudio-Installer-1.99.466.exe: PE32 executable (GUI) Intel ...
Read more >
Packaging for windows fails under some Linuxes and our ...
Error : rcedit.exe failed with exit code 193. wine: Bad EXE format for Z:\usr\lib\node_modules\nativefier\node_modules\rcedit\bin\rcedit.exe .
Read more >
rcedit.exe failed with exit code 193. wine: Bad EXE format
rcedit.exe failed with exit code 193. wine: Bad EXE format. Answer a question I got following error message, If I try to build...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found