BuildDSM won't run!

[dparks]

I cannot get BuildDSM to run. It always produces the following error message:

"This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix the problem."

I get this error if I drop an OEM folder onto the .exe, or if I try to run the exe by double-clicking.

Other background info:
1) Win XP, SP2, firewall & virus protection disabled.
2) Error occurs using BuildDSM from the 1.0.0, 1.0.1, and 1.0.2 kitchens released in the past few days.
3) Error occurs if I drop an OEM I made, and also if I drop any other OEM/Optional folder from the kitchen.
4) I've read thru the entire kitchen guide and searched the forum for clues, but can't find a solution.

I appreciate any help you can provide. Thanks.

[dparks]

Follow-up:

BuildDSM will run for me on another machine. Can I take my OEM folders to that machine, run them thru BuildDSM there, and then just bring them back to the first machine to run BuildOS? Or does the whole kitchen need to be present when running BuildDSM?

[phoenx06]

Originally Posted by dparks

Follow-up:

BuildDSM will run for me on another machine. Can I take my OEM folders to that machine, run them thru BuildDSM there, and then just bring them back to the first machine to run BuildOS? Or does the whole kitchen need to be present when running BuildDSM?

I'd just move the whole kitchen around with ya

[TheRocoLoco]

Originally Posted by dparks

I cannot get BuildDSM to run. It always produces the following error message:

"This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix the problem."

I get this error if I drop an OEM folder onto the .exe, or if I try to run the exe by double-clicking.

I get this error also, I'd love to know if there is a fix.

[boyo]

It sounds like it could be some kind of runtime file dependency is missing or corrupted.

[kevdawg]

Do you have the latest .NET framework installed?

[jt3]

I was thinking the exact opposite, actually. What if you DO have the latest, and shouldn't?

For me, the machines that wouldn't work had the 2.0 version, while the one that did, only had the 1.1 version (or maybe... it didn't have .NET at all... it was an "out of the box" HP install).

I've been wondering for awhile whether or not the 2.0 .NET install broke it, but I haven't been able to check it out.

[kevdawg]

I found today that when i had two optional OEM folders that were the same program just different version in the OEM folder it would break BuildDSM.exe or BuildOS.exe (I am assuming those are the same) and thus crash.

[Maxx134]

Originally Posted by kevdawg

I found today that when i had two optional OEM folders that were the same program just different version in the OEM folder it would break BuildDSM.exe or BuildOS.exe (I am assuming those are the same) and thus crash.

Does it say the same message in first post?

For me "BuildDSM" and "JoinU.exe" only ran on my HP laptop..
Viewing the processes with Spybot, I found they were using 2 DLLs that I did not have, namely "mfc80ENU.dll" and "mfc80u.dll" but alas putting them in either of my Gateway laptops did not make any difference, so I will try removing all my old kitchens next to see if that makes a difference.

I removed 2.0 .NET 3.0 and even 1.1 in vain so thats not it.

[Dmtalon]

I'm just glad it's not only me (not that I'm glad you guys are having problems or anything ) but I consider myself pretty computer savy, and my PC stays pretty up-to-date and very rarely do I have any goofy problems.

But as I posed in the "bugs" thread for 1.0.4 I too get the same error message...