Starter Kit Trouble

Hey I downloaded the MediaShare Starter Kit and it said it was already ready to build and run. When I try to build it I get a error for both the projects in the solution. This is what I get:

------ Build started: Project: CommunicationFramework, Configuration: Release Win32 ------
Embedding manifest...
Project : error PRJ0003 : Error spawning 'cmd.exe'.
Build log was saved at "file://c:\Documents and Settings\Dagaen\Desktop\Messenger\Source\CommunicationFramework\Release\BuildLog.htm"
CommunicationFramework - 1 error(s), 0 warning(s)
------ Build started: Project: MediaShare, Configuration: Release Win32 ------
Compiling resources...
.\app.rc(10) : fatal error RC1015: cannot open include file 'afxres.h'.
Build log was saved at "file://c:\Documents and Settings\Dagaen\Desktop\Messenger\Source\MediaShare\Release\BuildLog.htm"
MediaShare - 1 error(s), 0 warning(s)
========== Build: 0 succeeded, 2 failed, 0 up-to-date, 0 skipped ==========

Does anyone know why its doing this

Answer this question

Starter Kit Trouble

cdbrown
YAC. Yet Another Case of "MFC is not included in the Express edition".
Ricky Kelley
I tryed to simply make a form with a textbox on it- and got the same old "cmd.exe" problem. does this mean that with the Express version you cant even make simple GUIs
Erik Thomas
Thx- that helped. one thing I noticed is that the PATH environmental variable is shared by many programs (for me it was shared by my the Java 2 SDK, AutoCAD, and VC)
Botond Baika
Congrats! Something is messed up in your system's configuration. To fix that, click Start + Settings + Control Panel, System, Environment variables. In the "System variables" box, you need Comspec=c:\windows\system32\cmd.exe. In that same box, also check the Path variable; ensure that c:\windows\system32 is included in that variable's value.
David Walp - Microsoft
copying 'cmd.exe' from the system32 directory into our VC/bin directory makes it work :)
LockyBoy1
Oops, I missed that. Sounds like the compiler has trouble starting the command shell. First try: Start + Run, "cmd". Next, try Start + Run, "c:\windows\system32\cmd.exe". If that works, type "path" and press Enter. Check if "c:\windows\system32" is included in the list of paths.
amenhotep
That's normal.
Starter Kit Trouble

Answer this question