Hi Richard,
No. I do not have access.
Do you have an account on dreamhost? That's all it takes to have CVS access, I think. You probably need to get putty/pageant configured properly in order to get going.
I'm not sure that I know what putty/pageant is... Sorry about my ignorance.
Tim gave me ftp access but I could not find any files in the directories.
Hmm. I never tried ftp access until now and yeah, there's nothing useful there. Did you try logging into bazooka.dreamhost.com using the same credentials and the plain-old telnet command in Windows?
Do Start / Run... / telnet.exe bazooka.dreamhost.com
Then login using your credentials. Does that work?
I get the same results as I do for ftp... Empty directories.... See attached file telnet.gif.
I have been struggling with VC++ 2005 Express as some of my old applications have difficulty with basic stdio routines.
stdio should be included with the compiler, although they have things set by default to whine about "deprecated" stdio routines that use unsafe buffer pointers that are susceptible to buffer overrun attacks. I made some changes to the fractint source to disable these warnings on Win32. I don't think the suggested replacement routines are ANSI C yet, but I think MS might be making a proposal to the standards bodies in that regard.
Great :o)
I suspect that even after doing the three steps:
Step 1: Install Visual C++ Express. Step 2: Install the Microsoft Platform SDK. Step 3: Update the Visual C++ directories in the Projects and Solutions section in the Options dialog box.
That there may be some header files missing.
The Express 2005 edition doesn't include ATL or MFC. If you are trying to compile MFC code, then you should wait until the Academic 2003 edition to compile that. FractInt doesn't use any MFC or ATL code, so its got no troubles with this arrangement.
What you describe above should be all you need to get non-MFC Win32 programs to compile. VC++ comes with the necessary header files to compile programs written for ANSI C and C++. The Platform SDK gives you the necessary headers and libraries for compiling programs using the Win32 API.
MFC is a client library on top of Win32 for writing GUI applications. ATL is a template library on top of Win32 and C++ for writing COM object implementations. WTL is a template library on top of Win32 and C++ for writing Win32 GUI applications and ends up providing the same level of abstraction as MFC without the code bloat of MFC's monolithic library style. WTL was inspired by the ability of ATL to create COM object implementations that were small and efficient. In some cases *very* small. You can create useful 8-16K ActiveX controls in C++ with ATL, if you're careful.
No I wasn't using MFC.... Things are never as easy as they seem :o) Best regards, Paul.
