FreeCommander Forum

I am running FC XE 0.0.0.591 public preview on XP, SP3.
Whenever I start it, I get the following windows error message: "The Procedure Entry point ConvertToGlobalHandle could not be located in the dynamic link library KERNEL32.dll".
This does not happen in the non-beta FC, and after ignoring the message all appears to work correctly.
This is probably a windows problem and not a true FC bug, but does anyone know how to fix it?
I've googled for hours and didn't come up with much.

tia

I also use XP with SP3 and FC XE 0.0.0.591 and there are no problems starting up here...

I really think it's something messed up with my system, just hoping someone can point me in some direction.

I think it's something with the installation. If you've installed FC-XE from "fcxe_setup.zip", then close that version and try the portable version from the page http://www.freecommander.com/fc_beta_en.htm in another folder. It's called FreeCommanderXE.zip and that's the version I myself use, without a problem. If it works for you, you can use the settingfiles from the installed version (like FreeCommander.ini etc) and uninstall that one. Otherwise maybe you can Google yourself to a solution...
Good luck

Thanks for the suggestion.
Tried the portable option, but it didn't work.
I ducked and googled for a day, re-installed kernel32.dll from the original CD, and did a few malware scans.
I don't get the error message on another system with the exact same kernel32.dll, so I'm assuming the problem is not caused by it.
Moving on: I'll just live with the error message until I upgrade my system.

Finally found AN answer: Imgburn had the same error and the suggestion was to rename or delete svrapi.dll.
Renamed it and the error message does not appear.
I don't know the counter indications yet, but the file is not on two other of my computers.

Same problem here, and renaming svrapi does seem to do the trick.
Let me know if you find any downside to the renaming.
Thanks

Before deleting I checked the properties and it looks like it came from Windows 95 Plus Pack with a date of 2006.
The was a long time ago and I know I've had at least 3 new computers and windows installs.
Must have come from some old software install (I still use lots of 16 bit programs) or virus , even though I wear protection.

No problems so far after renaming it.