Mapopolis data stays in RAM after shutdown...

[X Gear]

I'm having a problem with Mapopolis. The program and maps are stored on the CF with PowerRun. Sometimes when I shut down the program, the data (.prc & maps) will save back to the CF (noted by the brief saving data message at the top of the screen). But... more times than not, the data remains in RAM. ClieFiles will show the data in both RAM and CF. Also evidenced by the amount of available internal memory being less than normal. Sometimes this will happen and I'll just run Mapopolis and shut it down again, prompting the save back to CF. I also now notice that the system occasionally soft-resets when leaving Mapopolis.

Anyone familiar with these issues? The quick fix would be to just move the program from PowerRun back to the unit, but I don't want to give up that space. I'm hoping that there is a simple step I need to do to ensure proper shutdown.

 

[sebring]

I also have PowerRun, but I don't use it for Mapopolis. Unless you have an OS5 device, I found MSMount is a much better solution for the Mapopolis maps I use most often. I run the Mapopolis app from MS using my launcher (ZLauncher). Maps I don't use as often or that I use to link maps in the MSMount directory, I keep on MS using Mapopolis. These maps are deleted by Mapopolis when I exit the app. Examples of maps I keep on MS using the Mapopolis directory are Major Road maps and other maps I use infrequently.

[FrankG]

Mapopolis is MS aware on its own. Why would you use it in conjunction with either PowerRun or MSMount? It find the maps on the MS by itself and offers to delete them from RAM on exit. I suspect PowerRun or MSMount might defeat that if Mapopolis doesn't realize they were snuck into RAM.

Just an opinion,
Frank

[sebring]

There are a couple of issues with Mapopolis that using MSMount solves:

1) Using MSMount, my most frequently used maps appear to be in RAM, without occupying RAM when not in use. They load much quicker from MSMount than from the Mapopolis MS directory.

2) I am able to keep maps that link other maps separate from the maps they link to avoid the problem of overloading RAM when I select "load contiguous". Major road maps, in particular, can cause a problem when selecting "load contiguous", since they link every county map in a particular state, as well as major roads maps in contiguous state and all that state's county maps.

I really wish Mapopolis would allow for selecting maps to be loaded, instead of just one map at a time or all contiguous maps.

[Flash-57]

When I used PowerRun with Mapopolis, I found that it didn't save my preferences and would delete my maplets. Apparently, saying "no" to leaving maps in RAM deletes the current maplet too. Or something.

Now, I just move the Mapopolis application to the launcher directory of whatever memory stick I have the maps on.

> I really wish Mapopolis would allow for selecting
> maps to be loaded, instead of just one map at
> a time or all contiguous maps.

Well, you can trick it to working the way you want. First, load one map from your memory stick (with "contiguous" unchecked). Then, load another and another. Now that you have a few in RAM, view one from RAM and, this time, select "contiguous".

It will load all contiguous maps from RAM.

[sebring]

Flash, that is exactly how I use it, but instead of having any maps in RAM, I keep my most frequently used maps on MS in my MSMount directory. That being said, it is still a serious pain in the A** that seem could be easily corrected, by just allowing the user to checkmark the maps to load from a single source.