Jonathan Osuch wrote:
Tim Wegner wrote:
I'm really curious to see what it can and cannot do. ...... Now if you want some help on this we have a problem, unless the old C compiler is on Rich's developer CD. Who besides you and me has the tools to build it?
One path to take may be to push on to the 32-bit compiler.
If you really wanted more individuals helping this along, you should consider going with an environment that the majority have access to and use regularly, such as Microsoft Visual C++ 6.0 or higher. And it would probably allow WinFract to get converted quicker to 32-bit, or even 64-bit.
We need to put the sstools.ini file in another spot. NT/W2000/XP users without administrative rights will have problems with putting it in the %Windows% directory.
It should be in the same directory path as the executable, which is where I have mine. Unless you wish each user to be able to have their own unique settings. Then it probably will need to be in: C:\Documents and Settings\[user-logon]\Application Data\ Most users are likely already the Administrator of their own PC, seeing how it will rarely be loaded on computers in a business or work environment.
By the way, I see no harm in putting this out for people to play with. It's well marked as a developer version. Having people play with it might help.
It might help to have a list of what is broken. At least, once it all isn't broken.
Always the best way to find problems: let people play with it. This tactic works well for all the major apllcation software companies. ;-} Sincerely, P.N.L. ------------------------------------------------- http://home.att.net/~Paul.N.Lee/PNL_Fractals.html http://www.Nahee.com/Fractals/