Failed to initialize yada yada!

[ronvenema]

Hey guys, I know this is a worn out subject but I wonder if anyone has found the real cause of this problem.
    Let me explain first that I have a rather complex setup using batch files to switch theaters ie: Pacific, Europe, Raaf, Med, East, WwI. Note that I have 80-90 planes in each theater max. All was going great then last night I added some "stuff". When I tried to start quick flight and quick combat I got the "message". Since I've been through this many times in the past I've smartened up and saved what I think are critical files to a backup folder, not to mention a zipped clean install. I started the the following process of elimination:
    Deleted all *.cdp files.
    Deleted all filelist.dat files.
    Replaced all config and dat files in the root and Info directories.
    Renamed and copied clean copies of the following folders:
    Gauges
    Effects
    Info
    Scenery
    Objects_db
    Texture
    Scenery_db and subs
    Aircraft (only stock installed)
    Ships (ditto)
    Still no joy. What is left that could possibly be causing this erroneous error?
    Btw, renaming the directory and coping a clean copy works, aaargh!

[4_Series_Scania]

Oh no! the

yada yada

error !  ;D

Ooh err, messing about with CFS2 installs has called me many sleepless nights!

I'd first advise you take a good look at Hagars "Lair" http://www.simviation.com/lair/main.htm pay particular attention to the CFS2 section.

In all honesty, I've found multiple installs of CFS2 to be a better solution to CFS2 and custom scenery installs etc, I've got 3 installs, 1 stock for the MSN Zone, 1 medium modified and one with extreme mods (FS2000 scenery installed for example!)

I've found this to be a safer option rather than one big install with 3rd party apps switching hangars (Aircraft folders) and manipulating scenery files etc etc etc

Hagar is the person who probably could help you on this matter, I'm not too sure as to what you've been upto with batch files! - I'd bet a brown paper bag this is the source of your grief!

Hope this helps (?)

Regards,

Paul.

[Hagar]

Hagar is the person who probably could help you on this matter, I'm not too sure as to what you've been upto with batch files! - I'd bet a brown paper bag this is the source of your grief!

Sorry Paul. Much as I would like to help I have no idea of where to start on this occasion.

I assume the batch files ronvenema refers to is the system for running multiple installs of CFS2 from a BAT file on the desktop. I believe this was developed by some French CFS2 enthusiasts & might even be posted here at SimV. I remember checking it out when it was first mentioned. After reading the instructions I decided it was far too complicated, especially if anything went wrong, so I didn't go any further with it. I think the problem here proves I was correct. My motto is KISS (Keep It Simple Stupid).

[Hagar]

Re: The CFS2 "100 plane" limit.

As CFS2 is the only M$ sim that suffers from this limit I always assumed that it's caused by the onboard Mission Builder & not the sim itself. Some people have told me they don't have this problem so I can only assume they didn't install the MB. Note the 3 install options.



I've never tried it myself but I suspect that the Compact Install option does not include the MB. In this case I suspect that you could install as many aircraft as you wish. The only drawback would be that the No-CD patch would not work as it would need to read some files from the CD in order to run.

PS. I posted this for interest only. It's by no means certain that exceeding the aircraft limit is the cause of ronvenema's error messages

[stiz]

First of all i would have seperate installs for each theater of operations the problem with this is that it takes up space.

When you get this error try uninstalling the last add-on you installed and if that dosen't work go to the folder where you have CFS2, select the file and press the delete button on your keyboard. Then reinstall it useing the same name as before (this is how mine are called CFS2 ETO, CFS2 PTO, CFS2 WW1) and re-install the add-ons apart from the last add-on you knew work.

Time comsuming i know but it works.

Stiz

[ronvenema]

Thanks guys for the responses. For clarification yes I did get the original idea from dling a batch file program from the net and modified it to suit my needs. At the time that I was getting the "error" message the batch files were not being used and I was using my WwI collection, about 30 planes. What I was trying to determine was what file (s) were actually being parsed that was creating the error, that is why I was using the process of elimination method. Fyi, I have since done a new install, again, and one by one substituted the old folders and determined that it was a fubar in the ships directory. What I don't understand is why the error didn't clear when I originally swapped the directory with the one from a clean install. Another Ms mystery.

[Hagar]

Glad you fixed it.

Fyi, I have since done a new install, again, and one by one substituted the old folders and determined that it was a fubar in the ships directory. What I don't understand is why the error didn't clear when I originally swapped the directory with the one from a clean install. Another Ms mystery.

Maybe not such a mystery. I suspect that the problem ship was defined incorrectly in Mdlnames.txt or one of the DAT files. If you replaced the Ships directory without also replacing these files (or removing the appropriate entries) the bug would still exist or possibly be worse. There's usually a logical explanation for most of these little problems.

[ronvenema]

Hagar that is the best esplanation that I've heard yet and makes a lot of sense. Nonetheless I think I'll follow your previous advice and KISS with multiple installs at least that way not everything breaks and I can still get my Cfs2 fix:)