Configuration Manager Problems

[billybob]

I am new to programming and crystalspace so bear with me.
I am trying to run an application and I get this error:

ERROR: Failed to initialize configuration manager!
Error saving configuration 'AppTest.cfg'.

I showed this problem to a few programmers I know and they couldn't figure it out.

Please help I have been stuck here for awhile and would like to get moving again.

*admin: changed the topic to something more descriptive from: "n0oob question"*

[dingobloo]

Which application are you trying to run would be nice information to have.

The error itself is somewhat self explanitory but cannot tell us the reason why it did not load, it might be that you havnt setup the configuration manager in your application, or the configuration manager failed to compile.

[sunshine]

This error occurs when your application is unable to find its own configuration file, which is AppTest.cfg, in this case. The actual cause could be any of several reasons, such as the fact that AppTest.cfg is not present in the appropriate VFS directory, or that the VFS plugin failed to load, or that VFS failed to find its vfs.cfg configuration file(s).

[billybob]

I am trying to run the first crystalspace tutorial and I did try looking for AppTest.cfg and couldn't find it .

[sunshine]

Which tutorial, exactly? Anyhow, if you don't have a configuration file, you can pass in NULL in place of the configuration file name.

[billybob]

I tried putting NULL in place of AppTest.cfg and it worked!
Thanks, you guys are awesome!

[Recon]

I had the same problem , I got passed this error by changing

  // Load application-specific configuration file.
  if (!csInitializer::SetupConfigManager(r,
      "/my/vfs/path/AppSol.cfg", GetApplicationName()))
    return ReportError("Failed to initialize configuration manager!");

to

  // Load application-specific configuration file.
  if (!csInitializer::SetupConfigManager(r,
      "/this/AppSol.cfg", GetApplicationName()))
    return ReportError("Failed to initialize configuration manager!");

this seemed to fix the error as a AppSol.cfg file was created in the current directory. Think it might be usefull later on!

Regards