|
I don't know if this is only ofr Logitech, but I want to GET/SET the mouse direction settings, which can be calibrated using Windows's Mouse Config Panel (well, if you have WinXP, I guess you need Logitech's MouseWare).
Is that possible?
|
|
|
|
|
Hi all!
I'm trying to build a Visual C++ application (a dialog application in Release mode with a simple window that creates a new thread in CWindowDlg). It compiles but in link I get this error:
<br />
LINK : fatal error LNK1561: entry point must be defined<br />
NMAKE : fatal error U1077: 'link.exe' : return code '0x619'<br />
Does anybody know what it means and how I could eliminate it?
Thank you in advance!
|
|
|
|
|
IT sounds like you either don't have a CWinApp class defined (e.g., somewhere you need the line: CMyWinAppDerievdClass theApp;)
Or your your project settings are incorrect and you aren't set to run an MFC project or something.
Remember, even if you win the rat race, you're still a rat.
|
|
|
|
|
Well, I have in my code the line
CWindowApp theApp;
and I have "Use MFC in a shared DLL" so I don't know but I think they are not the problem...
Usually, I can compile and link with no problem, but when I try to create threads then I got this problems in link.
Any idea?
Thanks!
|
|
|
|
|
Are you using the /ENTRY option with the linker?
"The pointy end goes in the other man." - Antonio Banderas (Zorro, 1998)
|
|
|
|
|
Where should I write down this option, please?
Thank you.
|
|
|
|
|
In the .mak file. I assume you have one since nmake was mentioned.
"The pointy end goes in the other man." - Antonio Banderas (Zorro, 1998)
|
|
|
|
|
<br />
todo: cliente.exe servidor.exe servidorV.exe<br />
<br />
cliente.exe: cliente.obj imevoc.obj<br />
link.exe cliente.obj imevoc.obj TAO_Portableserver.lib TAO_RTEvent.lib TAO_CosNaming.lib TAO.lib ace.lib /libpath:"C:\corba\ACE_wrappers\LIB"<br />
<br />
servidor.exe: servidor.obj imevoc.obj imevos.obj imevo_i.obj imevo.obj<br />
link.exe servidor.obj imevo.obj imevoc.obj imevos.obj imevo_i.obj TAO_Portableserver.lib TAO_RTEvent.lib TAO_CosNaming.lib TAO.lib ace.lib /libpath:"C:\corba\ACE_wrappers\LIB" /NODEFAULTLIB:nafxcw.lib <br />
<br />
servidorV.exe: ventana.obj ventanaDlg.obj imevoc.obj imevos.obj imevo_i.obj imevo.obj<br />
link.exe ventana.obj ventanaDlg.obj imevo.obj imevoc.obj imevos.obj imevo_i.obj TAO_Portableserver.lib TAO_RTEvent.lib TAO_CosNaming.lib TAO.lib ace.lib /libpath:"C:\corba\ACE_wrappers\LIB" /ENTRY:"WinMain"<br />
<br />
cliente.obj: cliente.cpp imevoc.h <br />
CL cliente.CPP /MD /W3 /GX /O2 /I "C:\corba\ACE_wrappers" /I "C:\corba\ACE_wrappers\TAO" /I "C:\corba\ACE_wrappers\TAO\orbsvcs" /D "WIN32" /D "NDEBUG" /D "_WINDOWS" /D "_MBCS" /FD /c<br />
<br />
imevoc.obj: imevoc.cpp imevoc.h<br />
CL imevoC.CPP /MD /W3 /GX /O2 /I "C:\corba\ACE_wrappers" /I "C:\corba\ACE_wrappers\TAO" /I "C:\corba\ACE_wrappers\TAO\orbsvcs" /D "WIN32" /D "NDEBUG" /D "_WINDOWS" /D "_MBCS" /FD /c<br />
<br />
imevos.obj: imevos.cpp imevos.h<br />
CL imevos.CPP /MD /W3 /GX /O2 /I "C:\corba\ACE_wrappers" /I "C:\corba\ACE_wrappers\TAO" /I "C:\corba\ACE_wrappers\TAO\orbsvcs" /D "WIN32" /D "NDEBUG" /D "_WINDOWS" /D "_MBCS" /FD /c<br />
<br />
servidor.obj: servidor.cpp imevo_i.h <br />
CL servidor.CPP /MD /W3 /GX /O2 /I "C:\corba\ACE_wrappers" /I "C:\corba\ACE_wrappers\TAO" /I "C:\corba\ACE_wrappers\TAO\orbsvcs" /D "WIN32" /D "NDEBUG" /D "_WINDOWS" /D "_MBCS" /FD /c<br />
<br />
imevo_i.obj: imevo_i.h imevo_i.cpp imevoS.h imevo.h imevo.cpp<br />
CL imevo_i.CPP /MD /W3 /GX /O2 /I "C:\corba\ACE_wrappers" /I "C:\corba\ACE_wrappers\TAO" /I "C:\corba\ACE_wrappers\TAO\orbsvcs" /D "WIN32" /D "NDEBUG" /D "_WINDOWS" /D "_MBCS" /FD /c<br />
<br />
imevo.obj: imevo.h imevo.cpp<br />
CL imevo.CPP /MD /W3 /GX /O2 /D "WIN32" /D "NDEBUG" /D "_WINDOWS" /D "_MBCS" /FD /c<br />
<br />
ventana.obj: ventana.h ventana.cpp<br />
CL ventana.CPP /MD /W3 /GX /O2 /D "WIN32" /D "NDEBUG" /D "_WINDOWS" /D "_AFXDLL" /D "_MBCS" /FD /c<br />
<br />
ventanaDlg.obj: ventanaDlg.h ventanaDlg.cpp<br />
CL ventanaDlg.CPP /MD /W3 /GX /O2 /I "C:\corba\ACE_wrappers" /I "C:\corba\ACE_wrappers\TAO" /I "C:\corba\ACE_wrappers\TAO\orbsvcs" /D "WIN32" /D "NDEBUG" /D "_WINDOWS" /D "_AFXDLL" /D "_MBCS" /FD /c<br />
cliente and servidor are console applications. First I made these console applications because I needed to work with CORBA and I thought that it was the easiest way, but they didn't work quite well so I tried to build the same application with MFC (creating a new thread in the main window that actues as the servidor (server)) but I get that link error.
Here in the make file, servidorV is the equivalent MFC application as servidor (at least I think so).
Thank you for your help.
|
|
|
|
|
It looks like only 1 of the three "link" lines have the /ENTRY option.
"The pointy end goes in the other man." - Antonio Banderas (Zorro, 1998)
|
|
|
|
|
ok, I understand...
My problem now is that I don't know which is the main procedure in the application... I'm working in Visual C++ and my app is called Window (I only wrote /ENTRY:WinMain so I could know if I had understood you).
Thank you.
|
|
|
|
|
Try changing the .mak file to the following in hopes of narrowing down which of the three modules is causing the problem:
todo: cliente.exe<br />
<br />
cliente.exe: cliente.obj imevoc.obj<br />
link.exe cliente.obj imevoc.obj TAO_Portableserver.lib TAO_RTEvent.lib TAO_CosNaming.lib TAO.lib ace.lib /libpath:"C:\corba\ACE_wrappers\LIB"<br />
<br />
cliente.obj: cliente.cpp imevoc.h <br />
CL cliente.CPP /MD /W3 /GX /O2 /I "C:\corba\ACE_wrappers" /I "C:\corba\ACE_wrappers\TAO" /I "C:\corba\ACE_wrappers\TAO\orbsvcs" /D "WIN32" /D "NDEBUG" /D "_WINDOWS" /D "_MBCS" /FD /c<br />
<br />
imevoc.obj: imevoc.cpp imevoc.h<br />
CL imevoC.CPP /MD /W3 /GX /O2 /I "C:\corba\ACE_wrappers" /I "C:\corba\ACE_wrappers\TAO" /I "C:\corba\ACE_wrappers\TAO\orbsvcs" /D "WIN32" /D "NDEBUG" /D "_WINDOWS" /D "_MBCS" /FD /c
If this works, do the same for servidor.exe, and then servidorv.exe.
"The pointy end goes in the other man." - Antonio Banderas (Zorro, 1998)
|
|
|
|
|
The makefile is:
<br />
todo: servidorV.exe<br />
<br />
servidorV.exe: ventana.obj ventanaDlg.obj imevoc.obj imevos.obj imevo_i.obj imevo.obj<br />
link.exe ventana.obj ventanaDlg.obj imevo.obj imevoc.obj imevos.obj imevo_i.obj TAO_Portableserver.lib TAO_RTEvent.lib TAO_CosNaming.lib TAO.lib ace.lib /libpath:"d:\ACE_wrappers\LIB"<br />
<br />
ventana.obj: ventana.h ventana.cpp<br />
CL ventana.CPP /MD /W3 /GX /O2 /D "WIN32" /D "NDEBUG" /D "_WINDOWS" /D "_AFXDLL" /D "_MBCS" /FD /c<br />
<br />
ventanaDlg.obj: ventanaDlg.h ventanaDlg.cpp<br />
CL ventanaDlg.CPP /MD /W3 /GX /O2 /I "d:\ACE_wrappers" /I "d:\ACE_wrappers\TAO" /I "d:\ACE_wrappers\TAO\orbsvcs" /D "WIN32" /D "NDEBUG" /D "_WINDOWS" /D "_AFXDLL" /D "_MBCS" /FD /c<br />
<br />
imevos.obj: imevos.cpp imevos.h<br />
CL imevos.CPP /MD /W3 /GX /O2 /I "d:\ACE_wrappers" /I "d:\ACE_wrappers\TAO" /I "d:\ACE_wrappers\TAO\orbsvcs" /D "WIN32" /D "NDEBUG" /D "_WINDOWS" /D "_MBCS" /FD /c<br />
<br />
imevoc.obj: imevoc.cpp imevoc.h<br />
CL imevoC.CPP /MD /W3 /GX /O2 /I "d:\ACE_wrappers" /I "d:\ACE_wrappers\TAO" /I "d:\ACE_wrappers\TAO\orbsvcs" /D "WIN32" /D "NDEBUG" /D "_WINDOWS" /D "_MBCS" /FD /c<br />
<br />
imevo_i.obj: imevo_i.h imevo_i.cpp imevoS.h imevo.h imevo.cpp<br />
CL imevo_i.CPP /MD /W3 /GX /O2 /I "d:\ACE_wrappers" /I "d:\ACE_wrappers\TAO" /I "d:\ACE_wrappers\TAO\orbsvcs" /D "WIN32" /D "NDEBUG" /D "_WINDOWS" /D "_MBCS" /FD /c<br />
<br />
imevo.obj: imevo.h imevo.cpp<br />
CL imevo.CPP /MD /W3 /GX /O2 /D "WIN32" /D "NDEBUG" /D "_WINDOWS" /D "_MBCS" /FD /c<br />
<code><br />
And the nmake throws:<br />
<code><br />
LINK : fatal error LNK1561: entry point must be defined<br />
NMAKE : fatal error U1077: 'link.exe' : return code '0x619'<br />
Stop.<br />
when it ends compiling.
servidor and cliente are OK.
Which could be the problem?
Thanks!
|
|
|
|
|
Do any of the following modules contain a WinMain(), or equivalent, function:
ventana.cpp
ventanaDlg.cpp
imevoc.cpp
imevos.cpp
imevo_i.cpp
imevo.cpp
"The pointy end goes in the other man." - Antonio Banderas (Zorro, 1998)
|
|
|
|
|
I think so since I've created the ventana.dsw project and in other projects I had no problems, but I don't really know which is the function that begins here
When I build my project in Visual C++ instead of DOS console with nmake, I get this different message error:
<br />
ventanaDlg.obj : error LNK2001: unresolved external symbol "protected: virtual void __thiscall CVentanaDlg::OnOK(void)" (?OnOK@CVentanaDlg@@MAEXXZ)<br />
Release/ventana.exe : fatal error LNK1120: 1 unresolved externals<br />
The error that I get in the DOS console is about the entry point as I told you... I can't see the relationship between these errors.
Waiting for your help and knowledge 
Thanks!
|
|
|
|
|
Why don't you open the ventana.dsw workspace, click on Project/Export Makefile. Compare this .mak file with the one you are currently using. Notice that it probably contains a lot more .cpp files.
"The pointy end goes in the other man." - Antonio Banderas (Zorro, 1998)
|
|
|
|
|
Hello,
I need to control a webcam and analyze picture by picture (and pixel by pixel) but I do not really know where to to start. Do you have to have the manufacturers API or is there any windows standard interface that you may use? Can you use VC++ or VB classes? Do you poll frame by frame or do you get a continuous stream? What format would you expect to get on the pics/stream, complete pics or changes? etc etc.
Thanks for any help I may get.
kodvar
|
|
|
|
|
I am trying to compile my application from command line
but somehow i can't do it here is the input for compiling my application with
registry tool and i want to use the different .exe file for this application
cl RegistryTools.cpp MyApplication.cpp -Fe MyApplication2.exe
thanks
Shin
|
|
|
|
|
There are lots of options that are set in project settings, things like INCLUDE paths, DEFINE-d symbols, and the like.
You say it doesn't do it, but you aren't giving any clues as to what errors you see.
Steve S
|
|
|
|
|
now i am one step forward and only problem is the following
cl RegistryTools.cpp MyApplication.cpp -FeMyApplication2.exe
> nafxcw.lib(thrdcore.obj) : error LNK2001: unresolved external symbol
> __endthreadex
> nafxcw.lib(thrdcore.obj) : error LNK2001: unresolved external symbol
> __beginthreadex
|
|
|
|
|
|
thanks,
i decided to use namke instead of cl.exe
thanks for your input.
Shinya
|
|
|
|
|
Hello,
I was wondering if anyone here knows how to listen to keyboard input in Windows platform by means of using MFC.
To be more exact, whenever this specific application of mine is running, CTRL + DEL (among other keyb combinations) cannot reach the OS and must be filtered by the App, which will prevent the user from invoking Task Manager / Logging Off / Shutding Down (though there is always Reset/Power Off), etc.
Any idea would be much appreciated.
________________________
dNimrod#X
|
|
|
|
|
Read about hooking starting from SetWindowsHookEx using WH_KEYBOARD_LL hook type.
You can hook ALT+CTRL+DEL by i think that the OS won't let yu block it. The dialog will be opened anyway.
However,you can disable the buttons of the opened window by setting some values in the registry Software\\Microsoft\\Windows\\CurrentVersion\\Policies\\Explorer.
Read Disable Windows NT alt-ctrl-del dialog button
|
|
|
|
|
Dudi Avramov wrote:
However,you can disable the buttons of the opened window by setting some values in the registry Software\\Microsoft\\Windows\\CurrentVersion\\Policies\\Explorer.
Thanks a lot for the reply. I have heard certain OSes do not allow you to have full control over the CTRL+ALT+DEL feature.
However, what's so important about the app ?
Well I have an app which needs to be invulnerable to the more naive (or ignorant, should I say) users because some extremelly important analysis & update process has to be carried out and whilst it is being done, no keyboard input should be allowed.
Does anyone have any ideas as to what I should do?
Thanks very much for the replies. 
dNimrod#X
________________________
|
|
|
|
|
If it's NT, 2K or 2.03K, you can't do it that way, the SAS will always be picked up, for obvious security reasons. If it's Win9x/ME then it is simpler.
However, what's so important about the app ?
Steve S
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
