Thread: BuildDSM won't run!
View Single Post
  #12 (permalink)  
Old 08-15-2007, 11:43 AM
gguruusa's Avatar
gguruusa
Deep Thinker
Offline
Location: Mountain top
  
Join Date: Jan 2007
Posts: 3,252
Reputation: 4726
gguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributions
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
BuildDSM and BuildOS are not the same. BuildDSM doesn't care what other directories you have in OEM or SYS.

Yes, you can run BuildDSM on a different machine and bring the result to another.

BuildDSM will run happily with any or all of the .Net flavors.

BuildDSM requires "mfc80ENU.dll" and "mfc80u.dll". These are the foundation class libraries for unicode character sets. Failure to have these .dlls is the most common reason for getting the "application not configured correctly" error.
Reply With Quote