[timothyskinner]

Pop-up attached. Anyone know what I can do to stop this? It started about a year ago and pops up after only a few (6 or 7) terrain changes ?  ScreenShot712.jpg (148.68K)
Number of downloads: 1

[slipperman]

Hi,
Have you noticed any "funnies" with other programs?
One possibility is a faulty memory chip.
If you are using a PC with more than one memory card and if you are able to, try swapping them over - this applies equally to desktops and laptops, although it's normally slightly easier with the latter.

Cheers,
Ged

[timothyskinner]

slipperman, on 19 October 2016 - 05:08 AM, said:

Hi, Have you noticed any "funnies" with other programs?
One possibility is a faulty memory chip.
If you are using a PC with more than one memory card and if you are able to, try swapping them over - this applies equally to desktops and laptops, although it's normally slightly easier with the latter.
Cheers, Ged

Thanks for reply Ged. I ran an overnight Windiag which showed nothing. I suspect something interesting is going on. I put a Flush Memory link on my desktop yesterday
http://helpdeskgeek....s-memory-cache/
which seems to help... local computer repair guy is "thinking about it all"...
Timothy

[Genma Saotome]

One route only or all routes?

If one, you've probably got something really wrong in a lot of your terrain files. If all routes then I'd suspect your hardware.

Which is it?

[copperpen]

I used to get that when running some routes back when using Win7 and MSTS. I suspect that it has something to do with system security not allowing anything to be written to that specific block of memory, or maybe even that the requested memory block does not in fact exist.

[timothyskinner]

Genma Saotome, on 23 January 2017 - 11:29 PM, said:

One route only or all routes?
If one, you've probably got something really wrong in a lot of your terrain files. If all routes then I'd suspect your hardware. Which is it?

Thanks for replying Dave..
It has gradually got worse over a year... now apparent when exporting with TGATool..

[timothyskinner]

copperpen, on 24 January 2017 - 01:53 AM, said:

I used to get that when running some routes back when using Win7 and MSTS. I suspect that it has something to do with system security not allowing anything to be written to that specific block of memory, or maybe even that the requested memory block does not in fact exist.

Hi Mervyn - I am still using XP.. I have asked the local computer guy to put a series of bootable memory tests on a flash stick to see if I can get some clues..

[timothyskinner]

Update..

Yesterday I went through Control Panel, System, Performance, Advanced without finding anything unusual.. or being able to stop the memory "leak"

Today... put in 4GB RAM though XP only says 3.5GB since that is all it is allowed to admit to.
Also chased the computer guy about his supplying me with a XP Pro back-up disk instead of XP Home when he installed a new hard drive a few years ago. I have been unable to run scannow and revert all settings which should do the trick..

[timothyskinner]

Still had Exception Reports this morning though larger memory reduced them..
I then updated page sys size to be half available memory... this has improved the situation a step further..
No sign of computer guy on a Friday afternoon but now I can tackle some jobs I had put aside...

[Jovet]

I don't think this is a hardware problem. There are too many things that can go wrong with MSTS to check out first.

MSTS has known problems when in terrain-adjust mode. One tip is to try and keep the camera pointed at the horizon and definitely avoid pointing it anywhere near straight down at the terrain. I also try to keep the terrain vertex of interest away from the edges of the viewport when I'm adjusting them. Some have had luck getting the RE/AE to work more reliably by putting their display into 16-bit color mode, though I am not sure that this is one of those circumstances. Some routes seem more prone to this than others, in my experience, but I've never been able to nail down exactly why beyond superstition.