[DRG]

Further to the above.

The aberrant behaviour my game and computer exhibited when that 995 scenario was in my scenarios folder was far beyond anything I had experienced in the past 20+ years involving the game so understand I was NOT HAPPY at that time I wrote that.

In my case even scenhack locked up once and yes I did try three times to get it to run but every time I got to the last page where it was something really unpleasant occurred. In one case the entire list of scenarios disappeared and I was left with "Load scenario list" at the top of the game screen and nothing but blank space below it AND the page froze there and I could not get out. Another time I "snuck up" on the last page instead of using GOTO and the game froze up and crashed but just before that I could see the list of scenarios but it stopped after 994 then it crashed and that is why I purged the scenario and the zip from my computer because also after the crashes my computer wasn't quite acting normally so I did a full reboot then deleted 995 and 995zip and it and the game is running OK again but that got me thinking if it was crashing when the page it was on appeared and in that one case the list stopped displaying when it got to 995 then *maybe* the problem is in the CMT or the TXT files. The second time I tried to view it with scenhack it would show me the units and there was nothing reported as being a problem. That does not explain why it froze up scenhack the first time I tried it but here is something you might try as a last resort

1/delete or rename the existing 995 CMT ( XXspscn995.cmt for example )
2/make a copy of any other CMT then rename it manually to spscn995.CMT
3/Rename spscn995. TXT the same as I suggested above--- XXspscn995.txt

Startup your game then try using GOTO to get to slot 974 then use NEXT to get to the last page and see if you get a crash.

What the game uses to display the info on the "Load scenario list" is the CMT and the TXT file ( so not the DAT that is what runs the scenario )

So if the CMT or TXT is corrupted somehow that could be what is causing the crashes, not the actual scenario itself.

Try that and get back to me with your results. The scenario does not need a txt file to run but it will need a CMT so pick one that does work and you can rename it later (if this works).

If a new CMT stops the crashing and allows the scenario to run then we can take a hard look at the TXT file but if "removing" the txt file and using a new CMT still causes lockups and crashes then that scenario is junk but give those tests a try as I hate to lose scenarios like that


Don