Update: UltraVNC 1.4.3.6 and UltraVNC SC 1.4.3.6: https://forum.uvnc.com/viewtopic.php?t=37885
Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/viewtopic.php?t=37864

Join us on social networks and share our announcements:
- Website: https://uvnc.com/
- GitHub: https://github.com/ultravnc
- Mastodon: https://mastodon.social/@ultravnc
- Facebook: https://www.facebook.com/ultravnc1
- X/Twitter: https://x.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc

Version 1.0.0 build problem

Post Reply
Skinney46
8
8
Posts: 31
Joined: 2004-11-05 17:27

Version 1.0.0 build problem

Post by Skinney46 »

Hi,

I wonder if anyone can help, I have the V1.0.0 source code and I am trying to build it in debug mode. I have two compile errors:

1) authSSP.cpp(191) error C2065: 'SecureZeroMemory' undeclared identifier.

2) in winvnc:
c1 : Command line error D2004 : '/D' requires an argument.

Does anyone know how to get rid of these errors.

Regards,

Chris.
Skinney46
8
8
Posts: 31
Joined: 2004-11-05 17:27

Post by Skinney46 »

I am building on Windows XP using Visual Studio 7 2002.

Chris.
Guest

Post by Guest »

Did you ever work this out? Or can any body else help, I have the same problem.

Thanks
Skinney46
8
8
Posts: 31
Joined: 2004-11-05 17:27

Post by Skinney46 »

No, I never received a reply on this problem. I will be looking at it again later this week and will post a solution if I work it out.
vertexwahn
Posts: 4
Joined: 2005-05-12 18:48

Post by vertexwahn »

i also tried to build winvnc (debug) (1.0.1 source)
but i got the same errors:

Command line error D2004 : '/D' requires an argument.
Skinney46
8
8
Posts: 31
Joined: 2004-11-05 17:27

Solution to the problem

Post by Skinney46 »

The /D problem can be resolved by opening the properties for the winvnc project, then navigating to C/C++ Command line and removing the '/D' from the Additional options edit area.

Looking at the forums, if you do not have the Windows 2003 platform SDK installed, the solution to the SecureZeroMemory problem seems to remove winvnc dependency on authSSP. Then winvnc builds ok, although the size is smaller than the official binaries released.

Chris.
redge
1000
1000
Posts: 6797
Joined: 2004-07-03 17:05
Location: Switzerland - Geneva

Post by redge »

UltraVNC staff subcribed to MSDN Professional 7.0

so, there a forum place for programmer ;-) (I'm not dev)
http://forum.ultravnc.net/viewforum.php?f=5
UltraVNC 1.0.9.6.1 (built 20110518)
OS Win: xp home + vista business + 7 home
only experienced user, not developer
killersquirrel
8
8
Posts: 27
Joined: 2006-01-02 01:16

Big surprise

Post by killersquirrel »

Your post is unanswered. Man. Thats frustrating.

Anyway, I get the same error here.

After that one, I get this too....

vncSecurityEditor.h(36) : fatal error C1083: Cannot open include file: 'aclui.h': No such file or directory
Marscha
Former moderator
Former moderator
Posts: 464
Joined: 2004-05-14 06:48

Post by Marscha »

authSSP.cpp and vncSecurityEditor.h need the Platform SDK installed and configured in your LIB and INC directories.
Guest

Post by Guest »

:cry: I also got the same error under Microsoft Visual C++ .NET 2003.
"Command line error D2004 : '/D' requires an argument"...


After removing the '/D' from the Additional options edit area, I got different errors.

Can any one please give me a hint on it ?
amichair
Posts: 3
Joined: 2006-10-08 22:45

Re: Version 1.0.0 build problem

Post by amichair »

hi,

I just came across this same "/D requires an argument" problem trying to compile in Microsoft Visual C++ .NET (2003) 32-bit (ur posts are from long ago, and I just keep getting the feeling that UVNC is not really actively being developed - anyone know anything about this?)

anyway, I opened the project and let it convert when prompted. iirc the Release configuration worked as-is, so if that's good enough for u, that's that.

the Debug configuration gave me the above error, and I got it to work by doing the following in the project (Debug) settings:

1. C/C++ -> Command line -> Additional options: remove /D
2. Linker -> Input -> Ignore specific libraries: Libcmtd.lib;libcd.lib
3. Linker -> Input -> Additional dependencies: add Libcmtd.lib
4. in vsocket.cpp changed the include for <iostream.h> to plain <iostream>

and it now compiles and runs ok (at least it seems to...)

Hope this helps someone. I'm a bit concerned that some of this, mainly the iostream change, might change the functionality in some subtle way from the released binaries, so if anyone has any knowledge/insight/different workaround pls post it here...
Post Reply