![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hi, on some XP-Systems Persavive SQU 2000i-client generates on startup the following error-message: ntvdm.exe SUnMapLS_IP_EBP_40 not found in "kernal32.dll" If you ignore the message, all things seem to be working correct. (the application is a 16-Bit-exe using the btrieve-thunking capabiliitiies of the PSQL-Clients.) Does anybody knows, whats the reason for this? regards M. Malarski |
#3
| |||
| |||
|
|
FYI: "The procedure entry point SUnMapLS_IP_EBP_40 could not be located in the dynamic link library KERNEL32.DLL." message is returned when MIF is loaded. Description: "The procedure entry point SUnMapLS_IP_EBP_40 could not be located in the dynamic link library KERNEL32.DLL." message is returned when MIF is loaded. Windows 98 was upgraded to Windows XP. During the XP upgrade, the user was asked to uninstall the Novell client. Environment: Pervasive.SQL 2000i Service Pack 4 BETA Calwin32.dll Clnwinth.dll SunMapLS Cause: Uninstalling the Novell client left behind Novell client components CALWIN32.DLL, CLNWIN32.DLL, CLXWIN32.DLL and CLNWINTH.DLL. Our MIF will use CALWIN32.DLL to help parse the path if CALWIN32.DLL is found in the path. Solution: 1. Manually delete CALWIN32.DLL, CLNWIN32.DLL, CLXWIN32.DLL and CLNWINTH.DLL from the System32 directory. 2. Reboot. Published: Nov. 2001 Thank you for that information, it solves the problm immediately. nmm wrote: Hi, on some XP-Systems Persavive SQU 2000i-client generates on startup the following error-message: ntvdm.exe SUnMapLS_IP_EBP_40 not found in "kernal32.dll" If you ignore the message, all things seem to be working correct. (the application is a 16-Bit-exe using the btrieve-thunking capabiliitiies of the PSQL-Clients.) Does anybody knows, whats the reason for this? regards M. Malarski |
![]() |
| Thread Tools | |
| Display Modes | |
| |