Question: How to avoid calling packages multiple times

I use Maple in high school. My students deliver their homework created in Maple. Often this involves solving a number of exercises, say 7. Not all students are completely aware of how the Maple Engine works, so I tell them to put in restarts from time to time, at least when a new exercise begins. This prevents misunderstandings and loss of time which might else happen when calculations in one exercise interferes with calculations in the next exercise. One simple example is that a variable may have been assigned a value in a previous exercise and now they solve for that variable. An error is shown, but my students don't always have the overview to realize their mistake. Therefore I recommend a number of restarts. Doing so has helped reduce the trouble my students have.

Now, good so far. My question here is if there is a feature in Maple to avoid the need to call a package again and again after each restart? Remember a restart unloads the package. My attention has been called upon the existence of an "maple.ini" file placed in the library folder of Maple. If one write the commands to load the actual packages in maple.ini, then the packages are in fact loaded at startup and also after each restart!! There is however a downside doing things in this way: If the Maple file is sent to another person, who has not the exact same maple.ini file installed on his own machine, that person cannot make it work (if he recalculates). Another downside is that one only have "one set" of packages to use after each reset. Now I have been reminded about another possibility: Writing some code in the "Startup Code" via Edit > Startup Code. The good thing here is that this code follows the document, meaning that it can be used by another person. The bad thing is: it does not seem to work after a restart, only at startup. Now it would be nice to have a new kind of "soft restart" command, which does not unload the packages ... But it is not here now. I would be happy to hear if there is a solution for my problem in Maple 14? It must not involve complicated code, since my students are not experts ...

Erik