Actually, it was your description that put me on the right track (not the poetry). Thanks again.
EDIT: After a conversation with BIS I have some update about vssver.scc. This is what Placebo has to say:
vssver.scc are "Microsoft Visual Source Safe" files, having files in source safe means that when someone wants to work on it they must check it out and it's locked for anyone else, that way you can have numerous people working on files without changes being lost or for example something being fixed by two people at once.
I can only assume that their inclusion in the original campaign was nothing more than an oversight (the original campaign pre-dates my employment here).
My trial and error method has showed me that the file
can affect a campaign, though.
One of my endtriggers in a campaign behaves strange (the game either freezes or crashes when trigger fires) if vssver.scc is included in the campaign folder.
The results varies, depending on wich folder the vssver.scc is in. Since both results are unwanted I recommend complete removal of all vssver.scc files from the entire folder tree of the campaign (in the CWC1985 campaign there are several copies, in Resistance there is only one, and Red Hammer has none).
In numerous other cases, the game runs fine even if vssver.scc is included. (Most user made campaigns IÂ've seen has one, included in the root folder, because their folder structures are copied from the official Resistance Campaign.)
vssver.scc doenÂ't seem to affect mission in Single Mission or Editor modes. The unwanted side effects donÂ't come until they are merged into a campaign.
Maybe not the most important discovery in the history of OFP, but hopefully it will save campaign makers unneccessary testing time when otherwise working missions start to crash inside the campaign. (I spent 14 hours, hence all energy put in this thread.)
Sorry if my early theories was a little bit off the track...
:-\