MS Logon II fails Entry Point DecodePointer not found

[GStegemann]

When attempting to set up MS Logon II under Windows 2000 either Edit Settings or UltraVNC itself fails with the following error message:

"The Procedure entry Point DecodePointer could not be located in the dynamic link library KERNEL32.dll".

This Windows API Call is definitely not defined in Windows 2000. Does this mean that MS Logon will not work under Windows 2000 anymore?

And when I attempt just to setup MS Logon I the logon fails with "auth.dll missing".

--
Gerhard

[redge]

did you installed uvnc 1.0.9.5 version for windows 2000 ?
if no, uninstall and install the good version for w2k

[GStegemann]

Yes, I installed 1.0.9.5 running the Installer, but without deinstalling 1.0.8.2.

Question: what is the good version for W2K?


--
Gerhard

[redge]

save your ultravnc.ini somewhere
uninstall full reboot delete folder ultravnc and install
replace ultravnc.ini with your own.

[GStegemann]

save your ultravnc.ini somewhere
uninstall full reboot delete folder ultravnc and install
replace ultravnc.ini with your own.

I did a clean re-install. But no change. Still the same errors.

---
Gerhard

[redge]

I no have w2k for verify, need to wait another user testing

edit: added user

[gutberle]

Hi Redge,

I am having the exact same problems Guido describes.

1.0.8.2 ran very nicely on all my W2K machines, but 1.0.9.5 fails consistently on all machines with the "Decode Pointer" not found in kernel32.dll message, which is both given when I try to configure MSLOGON from the Admin Properties dialog and also from unvc_settings.exe.

When I try to connect, the connection between client and server per se is made, the userid and pwd is requested and can be entered and sent, but then a message similar to "You selected MSLOGON, but authssp.dll could not be found" is given on the server and the login fails on the client.

I tried your uninstall/reboot/deletedir/reinstall/reinstate ultravnc.ini suggestion to Guido, but this does not change the situation at all.

I can of course not say if it is only the routines used to setup MSLOGON II that require DecodePointer, but I guess not being able to set it up would already suffice to break connectivity and according to the web Decode Pointer definitely is lacking from W2Ks kernel32.dll and is only present from WinXP onward.

P.S. I just did a little bit of testing:
1. Explicitly setting the path to the UNVNC directory to help in finding authssp.dll does not help.
2. I also did a complete deinstall and cleanup, then installed 1.0.9.1 for regression testing and this fails in the very same way. The break is thus between 1.0.8.2 and 1.0.9.1

Regards,
Ingmar

[Rudi De Vos]

I will take a look...

I guess the bins are compiled with VS2010, MS dropped support
for w2K in that compiler ( shame...)

The compiler use stuff that w2k kernel doesn't know -> pointer error

workaround:
download the 108 zip and use the auth dll from 108.
Between 108 and 109 the mslogon dll's didn't changed.

[gutberle]

Hi Rudi,

I tried your suggestion and replaced the 1.0.9.5 authssp.dll with the 1.0.8.2 one and I can indeed connect then. However, I have to use the 1.0.8.2 viewer for this, since the 1.0.9.5 viewer does not work anymore once the older authssp.dll is installed. Also, FileTransfer does not work then either, among other things. - All in all, your suggestion sadly is no option, since it breaks more 1.0.9.5 functionality than it fixes.

Here's my request:

Could you please consider going back to VS2008 for compiling the 1.0.9.x code? Please remember that it is especially the W2K setups that need a fast and stable VNC application, much more than the newer WinOSs, since W2K does not even have RDP, whereas all newer OSs have RDP connectivity (at least in Pro versions).

If you move to VS2010 now and possibly not even for a real code/coding advantage, you would leave W2K behind from now on and for good, which would mean no more security and bug fixes, speedups, etc. for a lot of us who still have W2K machines, typically in small office setups like mine.

You would thus be doing many of us a massive favor if you would consider recompiling in VS2008 so that W2K is not left out. Needless to say I would gladly volunteer for testing this.

Regards,
Ingmar

[GStegemann]

If you move to VS2010 now and possibly not even for a real code/coding advantage, you would leave W2K behind from now on and for good, which would mean no more security and bug fixes, speedups, etc. for a lot of us who still have W2K machines, typically in small office setups like mine.

You would thus be doing many of us a massive favor if you would consider recompiling in VS2008 so that W2K is not left out. Needless to say I would gladly volunteer for testing this.

Maybe the following links are helpful:

http://stackoverflow.com/questions/2484 ... -c-runtime

http://blog.kalmbach-software.de/2010/0 ... or-vc2010/

--
Gerhard

[redge]

in case if your uvnc is not default language english (german in this case)
rename or delete lang.dll located %systemroot%\system32 conflict with uvnc if not same version translated.

in this example:
1.0.8.2 lang.dll if still exist trouble basic function of new uvnc 1.0.9.1/1.0.9.5 and there no new lang.dll updated.

if there no language file trouble at all
try this update tested by timo without error (but don't remember if he had tested with mslogon or not. let try yourself and let us feedback, thank you
http://www.uvnc.eu/download/winvnc10951h.zip