Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Visual Studio.NET / General / November 2006

Tip: Looking for answers? Try searching our database.

Errors: printf.c & no compiler tool is associated with the file extension (*.h)

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
2005 - 12 Nov 2006 04:20 GMT
Hi

I have two sets of code that compiles using
Turbo C++ for DOS version 1.01 from
http://community.borland.com/article/0,1410,21751,00.html

What is that I need to do so that it cmpiles on Visual Studio as well?

First code:
When I tried one of it &  it needed some *.h files.  I copied them
(from the
Turbo C environment) and put it in there - now it says
"no compiler tool is associated with the file extension"

I am not happy with the Turbo C++ for DOS version 1.01.

That is why I am trying it on Visual Studio - could someone offer help
so that I can make it to work?

Second code:
Another code, it compiles fine on VS6 but when I run, it asks me where
"printf.c" file is - it doesn't satisfactorily run either?

Thanks
Ben Voigt - 14 Nov 2006 15:54 GMT
> Hi
>
[quoted text clipped - 9 lines]
> Turbo C environment) and put it in there - now it says
> "no compiler tool is associated with the file extension"

.h files don't get compiled, they are used by the preprocessor when
compiling .cpp files.

What header files were they?  Visual C++ comes with a pretty comprehensive
set.

> I am not happy with the Turbo C++ for DOS version 1.01.
>
[quoted text clipped - 4 lines]
> Another code, it compiles fine on VS6 but when I run, it asks me where
> "printf.c" file is - it doesn't satisfactorily run either?

Sounds like the program crashed and the debugger is trying to show you where
(inside printf).  printf crashed because it used a bad pointer you gave it.
Use the call stack to find the line in your program that called printf --  
that is where the problem lies.

> Thanks

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.