21.0 FPSM Messages

FPSM-X-001: Notice: An 80x87 floating-point emulator is already present. FPSM will not attempt to register another.

Source: FPSM.NLM
Explanation: The emulator provided by FPSM.NLM is not needed, probably because the chip provides its own 80x87 floating point emulator.
Action: No action is needed.

FPSM-X-002: Error number registering the 80x87 emulator.

Source: FPSM.NLM
Possible Cause: The FPSM.NLM, clib.nlm, and related programs were not loaded because a software inconsistency or resource shortage prevented the FPSM.NLM from registering the floating point emulator.
Action: Note which NLM™ programs that are loaded might interfere with the FPSM.NLM program's need to register the floating point emulator.

Make sure the CLIB.NLM, FPSM.NLM, LIB0.NLM, NIT.NLM, NLMLIB.NLM, REQUESTR.NLM, and THREADS.NLM NLM programs are all the same version. These NLM programs are usually distributed as a set. To find a set of these NLM programs, refer to an authorized distribution source, such as http://support.novell.com.

FPSM-X-004: FPSM failed to allocate its local call gate resource tag. There may not be enough server memory, or server memory may be corrupted. This is not fatal.

Source: FPSM.NLM
Explanation: This message appears if system memory is low.
Action: Load NLM programs in the kernel address space instead of in a protected address space. Check server memory and add more memory if necessary. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.