Getting Started2 - 7Virtual Memory Settings for Windows 3.1The settings for virtual memory can be changed in Microsoft Windows 3.1 throughthe Control Panel, 386 Enhanced.Make sure that, in the Virtual Memory dialog box, the following are disabled:• Use 32-Bit Disk Access• Use 32-Bit File Access (available in Windows For Workgroups only)Failure to do this may result in disk access errors during the file conversion ormerge process.For maximum performance, it is recommended that the current settings for theswap file be set as Permanent.Windows 3.1 Protection and MultitaskingMicrosoft Windows 3.1 is not a true protected environment: it does not protectitself fully from misbehaving applications, nor does it protect the applicationsthemselves from one another. As well, under Windows 3.1 you cannot multitaskbecause a running application is not guaranteed CPU time at regular intervals.As a major consequence of the low level of protection in Windows 3.1, when anapplication crashes with a General Protection Fault (GPF) error message or anyother Windows fatal error, the integrity of the system cannot be guaranteedanymore. Under such circumstances, stop MMR immediately and terminateWindows; then, restart Windows which restarts MMR. If you do not terminate andrestart Windows, all subsequent operation may encounter problems.Because Windows 3.1 does not offer multitasking, MMR Communications isvulnerable to other applications holding the CPU for long periods of time. MMRCommunications requires regular CPU time to download files from Meridian Mail.If MMR Communications is delayed, the communications link with Meridian Mailcan terminate and cause a download in progress to fail. Consequently, you shouldnot run other programs, even another MMR program, while MMRCommunications downloads. For example, running reports, either scheduled or ondemand, in MMR Reports during a download can cause that download to fail. Evenusing File Manager to copy between a floppy disk and the hard drive could causethe download to fail.