Door/Drawer Front Designer Problems...

[Joe Dusel]

Whenever I select the Door/Drawer Front Designer and select either Doors or Drawers followed by selecting any of the types (Conestoga, Slab, etc.) the software immediately crashes. I did notice that there seemed to be some sort of update earlier today when I first opened the program. Is something in the software broken? Is anyone else having this same problem?

Thanks,

Joe

[DanEpps]

Don't take it personally Joe, but I think its just you.

Do you get any error message? Does eCabinets close or just freeze?

[Justin Melhiser]

Joe
I can not reproduce this. Could you give me the steps from start to finish? Do you have a certain cabinet or job file loaded when you go to the Door/Drawer Front designer?

[Gary Urlacher]

I had a similar problem. I was using two monitors. I found that e cabinets crashed all the time for me until I went into the windows set up
and told it not to extend my desktop to the second screen.

Now, I have no second screen but ecabinets has not crashed once since then.

My 2 cents

Gary

[Rick Palechuk]

Dual monitors and no problems here.

[DanEpps]

Dual monitors and no problems here.

Same here.

[Joe Dusel]

Thanks guys. My assumption at this point is that one of the programs I recently installed wrote over the mfc80.dll file or ntdll.dll file, since this is what the crash dialog is complaining about. (It complains twice as it goes down in flames...) I'm figuring I will need to re-install the ecabs software.

The steps for me to cause this are:
1) Start the program.
2)Select the Door/Drawer Front Designer.
3)Select any of the sources.

The program then crashes.

It's been so hot lately that it may be that my computer is overheating. I sure hope this heat wave breaks soon.

Thanks,

Joe

[Daniel Menard]

Have you tried rerunning the update ( build 4 )

I noticed that sometimes when you run the update it does not seem to install completely.
I usually recommend that you save it to you desktop and then you run it.

It may ask you to MODIFY , REPAIR OR REMOVE. Try the Repair.

[Joe Dusel]

I re-ran the update (build 4) but unfortunately it did not help.

Next step is to re-load the software.

Thanks,

Joe

[Joe Dusel]

Well, I reloaded the software from the disk and then reloaded build 4, but I'm still having the same problem. The program crashes complaining about mfc80.dll 8.0.50727.1833. Is this possibly the wrong version for eCabinet Systems?

If so, is there an easy way to fix this?

Thanks,

Joe

[Rick Palechuk]

I don't know if this will help Joe, but it might give you a clue. mfc80.dll is a module associated with Microsoft® Visual Studio® 2005 from Microsoft

[Joe Dusel]

Yep, and it's obviously a DLL that eCabs uses. I'm wondering if eCabs just has a problem with this version of the DLL. I'm also going to make a guess that eCabs is defaulting to run the latest version of the mfc80.dll and it's not quite 100% compatible with this 1833 version.

Joe

[Joe Dusel]

Well, I got the eCabs software running, but I probably broke something else.

I ended up mucking with a WinSxS policy file. 8.0.50727.1833.policy. Here's the new content of the file:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<!-- Copyright © 1981-2001 Microsoft Corporation -->
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">

<assemblyIdentity type="win32-policy" name="policy.8.0.Microsoft.VC80.MFC" version="8.0.50727.1833" processorArchitecture="x86" publicKeyToken="1fc8b3b9a1e18e3b"/>
<dependency>
<dependentAssembly>
<assemblyIdentity type="win32" name="Microsoft.VC80.MFC" processorArchitecture="x86" publicKeyToken="1fc8b3b9a1e18e3b"/>
<!--
<bindingRedirect oldVersion="8.0.41204.256-8.0.50608.0" newVersion="8.0.50727.1833"/>
<bindingRedirect oldVersion="8.0.50727.42-8.0.50727.1833" newVersion="8.0.50727.1833"/>
-->
<bindingRedirect oldVersion="8.0.41204.256-8.0.50608.0" newVersion="8.0.50727.762"/>
<bindingRedirect oldVersion="8.0.50727.42-8.0.50727.762" newVersion="8.0.50727.762"/>

</dependentAssembly>
</dependency>
</assembly>


I commented out the newVersion code referring to 1833 and replaced it with 762.

Joe

[DanEpps]

Are you running Vista Joe?

You shouldn't be hacking away at SxS policy files as you could be breaking other programs or parts of Windows itself.

[Joe Dusel]

You are right Dan, but unfortunately I need the program running since I'm in the middle of a project. I'm using XP.

Thanks for your concern! I will keep the fire extinguisher handy and a bottle of cheap wine in case I need to drown my sorrows. Oh what the heck, I can use it to celebrate as well.

Joe