Well iostream.h isn't the standard name (it was in the old days, but not anymore).
Try
#include <iostream>
using namespace std;
Oh, and main returns int, not void.
Salem
Posting Sage
11,531 posts since Dec 2005
Reputation Points: 5,875
Solved Threads: 953
Skill Endorsements: 27
Read Me
You'll also need to set the PATH environment variable as well, so you can run the compiler from any directory and just bcc32\bin
Also, you should begin by creating say c:\projects which will contain all your code projects. Don't be tempted to try and develop code within the compiler installation directory structure.
Salem
Posting Sage
11,531 posts since Dec 2005
Reputation Points: 5,875
Solved Threads: 953
Skill Endorsements: 27
You should only need the \bin directory in your path, as that also helps it locate the .cfg file where the include path information is also stored.
system or user?
The system path is what all user's of your machine will see. The user path is of course unique to you. If it's only you using the machine, it's a fairly moot point.
You can check the result by opening a new cmd.exe and typing 'path' to display the current path. If that shows the \bin directory, you should be good to go.
Salem
Posting Sage
11,531 posts since Dec 2005
Reputation Points: 5,875
Solved Threads: 953
Skill Endorsements: 27
Did you update the PATH environment variables via the system settings dialogs?
From a new cmd.exe, does the 'PATH' command show the compiler install directory?
Salem
Posting Sage
11,531 posts since Dec 2005
Reputation Points: 5,875
Solved Threads: 953
Skill Endorsements: 27
> Can not compile from any other cme.exe.
Well the new PATH only takes effect in new cmd.exe files you run. Instances which were running before you updated the settings will not see the change.
Salem
Posting Sage
11,531 posts since Dec 2005
Reputation Points: 5,875
Solved Threads: 953
Skill Endorsements: 27
Question Answered as of 5 Years Ago by
Salem
and
timonsinger