Honestly, I do not know what causes this bug, either VC complier, or Vavoom executable. This happens almost every time I modify my progs. When I compile them for the first time and launch the game most often it fails to load progs (it displays an error saying about TProgs::Load or something). Then, I just recompile progs once more and no error happens.

You can use the -debug parameter when loading your mod to see the error it sends, when using the parameter there should be a file called debug.txt in your basev folder.

Yeah, I know that. I always run Vavoom with "Create debug file" option checked. But it still does not say much. Just a single string telling that there was an "external error" while loading progs.

Some time after I began to receive a message while compiling progs: clprogs.vc:112: Segmentation violation. It appears sometimes under Win98 and always under WinXP. I checked what's on 112th line of clprogs. It wasn't in clprogs.vc actually, but in one of the included files - common/defs.vc. Exactly the line: "#define NUM_CSHIFTS 8" When I comment it there's no such error. Then I uncomment it, there is. I found out, that when I just write there "#define NUM_CSHIFTS" it works, but when I give it some numerical value, for ex.: #define NUM_CSHIFTS 1, it causes error. When value is not numerical it works. (for ex. #define NUM_CSHIFTS AAA) Honestly, I still suppose that some of my modifications can cause that error, since original Hexen progs compile normally. I will continue testing. EDIT: That's funny, but it seems that the whole thing does not spoil compiling process at all. Progs still load and work normally. Maybe it is some sort of memory leak in vcc.exe?

Finally it seems i have found what causes that "segmentation violation" in my progs. It is one of my files, that I include to "clprogs.vc". There is a declaration of two variables of type string. When I comment them error does not happen, but when I uncomment them it happens again. I do not know what's the problem there, that's why I ask anyone, who is able, to look at my file and say what's wrong with it. Here's the link: <!-- m --><a class="postlink" href="http://www.shadowweaver.narod.ru/unheir/source/journal.vc">http://www.shadowweaver.narod.ru/unheir ... journal.vc</a><!-- m --> Declarations that I mentioned are:

string sJNoEntryString = "Text loading error"; string Jstatements[NUMJSTATEMENTS] = {"entry", "enabled", "lump", "%%page%%"}

Global variables are not allowed anymore, so this is not applicable anymore.