Problem with the PE causing Ecabs to close

[Sean O' Hare]

I've started having a problem with Ecabs closing every time I try to use a cabinet with PE cuts applied. Cabinets I've used before now cause the program to crash. I can create a new cabinet & apply cuts, but if I try to change anything afterwards it closes. Nothing on my system has changed except an update of AVG, and I've tried running ecabs with it disabled with the same result. I've also tried excluding the paths as suggested by Scott. I'm using V6 Build 6 & have tried running repair from the update. Help.

Thanks

[Scott G Vaal]

Sean,

Does it close as soon as you load the cabinet or do you have to do another step(s) before it crashes? If you would, please attach one of you cabinets that cause the problem and I will see how it behaves for me. Also, what operating system are you running?

[Sean O' Hare]

Scott,

it loads ok but closes if I try to adjust the cabinet. I've attached a simple 1 (I hope). System is Windows XP.

Thanks

[Scott G Vaal]

Sean,

I do not have any trouble resizing this cabinet. I tried it on an old XP station and my Win7 machine. I changed to metric (which I assume you are running in) and changed the Height, Width, and Depth and no troubles.

Please do this for me:
Directly after the crash, go to the Windows Event Viewer.
* Select Start, then Right-click on My Computer, select Manage from the R-click menu.
* On the Computer Management dialog, Double-click Event Viewer, then Double-click Application.
* In the view area, look under the Type column and find the newest red X Error listed and Double-click on it. Should get a Event Properties dialog.
* In the Description area, see if it lists a faulting module. It will probably read something like the following:

Faulting application ecabinets.exe, version ?.?.??.?, faulting module
?????.dll, version ?.?.?????.???, fault address ??????????.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

You can copy and paste this description field here on the forum.

[Sean O' Hare]

Scott,

this is what I get. It also closes if I try to alter a stretcher.

0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 65 63 61 ure eca
0018: 62 69 6e 65 74 73 2e 65 binets.e
0020: 78 65 20 36 2e 30 2e 35 xe 6.0.5
0028: 37 2e 30 20 69 6e 20 65 7.0 in e
0030: 63 61 62 69 6e 65 74 73 cabinets
0038: 2e 65 78 65 20 36 2e 30 .exe 6.0
0040: 2e 35 37 2e 30 20 61 74 .57.0 at
0048: 20 6f 66 66 73 65 74 20 offset
0050: 30 30 66 36 63 62 34 65 00f6cb4e
0058: 0d 0a ..

Thanks,

[Scott G Vaal]

Sean,

That is not what I was hoping to see. I was expecting something more like this:

Faulting application ecabinets.exe, version ?.?.??.?, faulting module
?????.dll, version ?.?.?????.???, fault address ??????????.

Did you get your info from the Event Viewer as I detailed in the last post?

I would update your driver for you graphics card, even if you had done so not too long ago. I had my XP machine at home revert back to an older version after a windows update occurred (or at least it seemed to be due to that... been wrong before though). If you have the driver installation from a previous update still on your PC, try installing that one again.

[Sean O' Hare]

Scott,

Faulting applications ecabinets.exe. version 6.0.57.0. faulting module ecabinets.exe. version 6.0.57.0. fault address 0x00f6cb4e.

I've updated the driver, but no change.
Should I remove & reinstall ecabs? If so, what files do I need to save to avoid losing existing jobs?

Thank you,

[Scott G Vaal]

Should I remove & reinstall ecabs? If so, what files do I need to save to avoid losing existing jobs?

It is worth a shot to try that. The uninstall will not remove any user created or modified files. So you should be ok with your jobs etc.. With that said though, you should still have a backup of your files somewhere. So do a backup prior to un/re-installing with all the options checked that matter to you. (find this under {File} then {Backup/Restore Settings}.

[Sean O' Hare]

Scott,
fyi, uninstall/reinstall solved the problem.

Thanks

[Scott G Vaal]

Sean,

Great to here. Thanks for the response back.