Easel (Windows v.0.3.2) Install Hangs -- SOLUTION

Easel
1

Every time there is an Easel driver upgrade, the installer hangs on the last step and I’ve got to jump through hoops to fix it. This is because I have an existing node.js install, and the installer assumes that either you don’t have node, or your existing install is compatible. This is a bad assumption. I have the 64 bit version of node, but easel requires the 32 bit version for its native code modules.

Here’s what I’ve found fixes the issues:

  • Open services.msc (Start → Run, type services.msc). Find Easel, right click, stop.
  • Download the 32 bit node installer here. Install only node and npm, don’t let it mess with your path.
  • In CMD, navigate to C:\EaselLocal.
  • Delete node_modules. These were installed using the wrong node version.
  • Use the explicit path to the 32 bit npm to install, i.e. “C:\Program Files (x86)\node\npm” install. This will install the correct 32 bit modules.
  • nssm edit EaselLocal
  • Change the path to the 32 bit version of node.
  • Profit.

This really needs to be fixed by the installer. This has been occurring for well over a year at this point.

2

Hi, before I walk through these steps, I just wanna make sure I’m having the same problem you had… It hangs in “Verifying installation…”. Is that where your’s was hanging?

3

Yes, that is where my installation was hanging.

4

Ok, thanks much for posting these steps…
I have no idea how you figured this out, but I’ll take your word for it and give it a try.
I had also posted a general question pointing to your post and saying “Is this really the only solution??”.
As you say, this should certainly be addressed by the installer, not the “intallee”.
Can’t really complain though, my overall x-carve/easel experience thus far has been great.
Thanks much!

5

Ok, did everything in the list and then used Easel to do a job. Everything worked fine (no difference than prior to the new driver installation attempt); however how do I know if I’m working with the new driver?
After running through your steps, should I have ran the installer again (I didn’t)?
Thanks,
Ed

6

Easel will tell you if you aren’t on the current version of the driver. Also: no after you ran the installer the first time this completes the installation. You don’t need to run it again.

7

Hi, know this is an old post but hoping you can help, easel worked fine on my dell laptop but it died and trying to use my old Lenovos and freezes on driver install every time

Ive done most of what you said but am stuck on

Use the explicit path to the 32 bit npm to install, i.e. “C:\Program Files (x86)\node\npm” install . This will install the correct 32 bit modules

Not sure what I’m supposed to do here, when I type that in cmd nothing happens, can you baby steps it for me? Im ok with IT but not an IT person!

Thanks

8

I’m not an IT guy either, but I’ve never encountered an error like that. If it were me, I’d go to the control panel/ add and remove programs,and remove easel completely.

At that point you could hook the machine back up and go through computer set up. That’s what I’d do. The set up asks about current drivers and links to them, which may need to be extracted.

Not sure what else you can do unless a computer person has an answer for you. As always, YMMV.

9

Thanks for the reply, the issue is with the current drivers they don’t finalise the installation on my Lenovo W541 or T430, no idea why like I say it was never an issue on my dell laptop

Had to resort to saving the gcode and using Candle to cnc, but the set up is different and I’ve already ruined something that was urgent to make as it seems with candle you need to zero your Z manually every time you cut with different bits unlike just using easel for all of it :frowning: