Johan de Klerk said:
I have about 90 customers getting this error on Win 2000 and Win XP
computers "The procedure entry point SMapLS could not be located in
the dynamic link library KERNEL32.DLL".
I have Windows XP Pro SP-1. When using PC Mag's FileSnoop or the
depends.exe (Dependency Walker) from Visual Studio 6 on kernel32.dll,
there is no entry point (aka export function or externDef) called
SMapLS. However, I only have one processor so I do not have the SMP
version of the kernel installed. I don't have them available right now,
but maybe you have instances of Windows 95 and 98 to look at their
kernel32.dll file to see if they have an SMapLS entry point (export)
defined. I saw the SMapLS exported function defined in kernel32.dll at
http://www.geocities.jp/nuu_yan/VC/export/kernel32.txt but the author
never bothered to mention from *which* version of Windows this listing
was taken. My guess is that it was for Windows 95.
Sounds like they installed something that works under Windows 9x but
isn't usable under an NT-based version of Windows. "If you get this
message when opening the control panel on WindowsXP/2000 that means you
have remnants of the Windows 98/ME driver on your system"
(
http://www.aardvarkaudio.com/support/troubleshooting_page.html#aarkthk)
.. So ask your customers if they did a *clean* install of Windows XP or
if they migrated by doing a pollutive upgrade from Windows 9x (which
carries along old unneeded or incompatible files and registry entries) .
They might've later installed a device driver that was meant for Windows
9x, or installed a program that had them reboot to install a Win9x
driver or itself makes that function call. Usually a clean (fresh)
reinstall of Windows XP solves the problem - because they haven't yet
loaded whatever was the old and incompatible driver or program (but if
they are the ones doing the reinstall again then it is likely they may
make the same mistake). Upgrading from Windows 9x/ME to an NT-based
version of Windows often causes problems. Fresh installs are safer.
Yeah, an upgrade is quicker (only because you don't have to install the
applications) but it is also very *dirty*!
I suspect you have customers that did an upgrade from Windows 9x/ME and
brought over a bunch of incompatible crap in the upgrade, or they later
"updated" their drivers and used the wrong one (i.e., the Windows 9x
version of some VXD driver instead of the Windows NT-based version), or
they are running a program that just isn't compatible under Windows NT
and they'll have to get a newer version of the program.
