Discussion Locked

Windows NT error message

0 helpful
13 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We use Goldmine FrontOffice 2000 v5.402 Contact Management software on our NT box with service Pack 5 installed. Everything ran fine until we installed more memory and now we get the following message:
"Procedure entry point UNMAPLS not found in Kernel32.dll", of course removing the memory has no effect and the application no longer runs. Does anyone know why this might happen?, I thought UNMAPLS was a call to translate pointer sizes from 32 to 16 bit on Win95/98 machines. We have reapplied the service pack, changed the memory and the main board, re-installed the software and still no joy. Goldmine runs on every other NT server we have tried with no problem.
If we wipe NT and re-install NT everything works fine for a while but somethinglike changing memory or installing applications that require a re-boot and the error comes back.
I would sure like to get to the bottom of this error.

13 replies

by joetech3

Replace the new memory chip with a different one. The new chip may not be wholely compatible.

by sdfgsdf

check your boot files for anything weird and check your hardware. sounds like it might be a hardware issue, perhaps memory? have you tries technet on microsoft's site for the actual error codes?

by mwhite

Make sure your not mismatching memory sticks try to stay with the same vendor. Can you recreate the error on another server or are you sure that it's totally relative to that particular server. Also try goldmines faq/support page. I hope this helps.

by choonhian

Whenever you add memory, you need to change your page file size. A general guideline is to have a minimum size twice your total RAM size and maximum size three times your total RAM size

by ronnonf

I have seen a problem similar at a client that was running a client/server based accounting package. We replaced the client OS with Win98se and disabled unecessary application from startup (via msconfig). the other part of the solution was it seemedthe client mucked around with the MSVCRT4*.dll file and we needed to reinstall this file.
If this doesn't work you can go to Technet's website (www.microsoft.com/technet) and I recall they had some good ideas.

by law

Pointed me in the right direction, the problem was with a dll begining with MSV* . The problem only showed after a reboot, so the memory thing was a "red herring" as we say

This discussion is closed to new replies.