C / C++ / MFC

WMI copy file to remote host

28-Apr-09 9:42

If you are simply wanting to convert an IP address to its host name, use gethostbyaddr().

"Old age is like a bank account. You withdraw later in life what you have deposited along the way." - Unknown

"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons

Jack Rong28-Apr-09 8:41

Jack Rong

28-Apr-09 8:41

I would like to copy file from local to remote machine using WMI in C++. Not quite sure how to do this.

According to MS doc, "Win32_Directory" can be a good candidate. Anybody got idea? Thanks in advance.

Jack Rong

Nicely spammed into 4 forums

led mike28-Apr-09 8:57

led mike

28-Apr-09 8:57

Must be URGENT Roll eyes | :rolleyes:

Re: Nicely spammed into 4 forums

CPallini28-Apr-09 9:25

CPallini

28-Apr-09 9:25

led mike wrote:
Must be URGENT

Must be URGENTZ

fixed.

Re: Nicely spammed into 4 forums

led mike28-Apr-09 10:39

led mike

28-Apr-09 10:39

CPallini wrote:
fixed

tnk u plzzzzzzzz

Re: WMI copy file to remote host

David Crow28-Apr-09 9:39

CListCtrl flickers on Vista

28-Apr-09 9:39

Jack Rong wrote:
Anybody got idea?

Such as this?

00.Siddu28-Apr-09 5:40

28-Apr-09 5:40

Hi,

My application uses a dialog with CListCtrl in report view, this list control gets updated heavily and frequently.
To stop flickering i have used SetRedraw(FALSE) before the update operation, like-

SetRedraw(FALSE);
//Update();
SetRedraw(TRUE);
Invalidate();

This trick is working fine with Win XP, but its unable to stop flickering on Vista.
I have also tried LockWindowUpdate(), but the problem remains.

Is there any known issue with using CListCtrl on Vista?
What else could be tried to stop Flickering?

Siddu

David Crow28-Apr-09 8:28

28-Apr-09 8:28

Member 4682688 wrote:
Invalidate();

Is this necessary?

00.Siddu28-Apr-09 9:36

28-Apr-09 9:36

I agree, Invalidate() is not necessary, I'd have put it there while trying to eliminate flickering any how.. $Shucks | :-\$
I have also tried with Invalidate(FALSE), which i suppose, would have stopped background repaint. With or without Invalidate(), flickering remains on Vista. Frown | :(

David Crow28-Apr-09 9:45

28-Apr-09 9:45

00.Siddu wrote:
...flickering remains on Vista.

How often is the control updated, and with how many items?

00.Siddu28-Apr-09 22:07

28-Apr-09 22:07

How often is the control updated, and with how many items?

Well, Control is updated as mouse moves over the screen, with 100 to 125 items.
The list gets updated in a loop in which data is being collected in a vector first, and then injected in the list.

Steve Thresher29-Apr-09 2:32

Steve Thresher

29-Apr-09 2:32

Have you tried SetWindowRedraw(), it works for comboboxes?

http://blogs.msdn.com/oldnewthing/archive/2007/02/22/1742084.aspx[^]

AxisFirst For Business

00.Siddu4-May-09 3:16

LNK2005 Error: basic_string already defined

4-May-09 3:16

Tried, it didn't help, flickring still exist Frown | :(

sending email

santanukarmakar28-Apr-09 5:12

santanukarmakar

28-Apr-09 5:12

may i know how to send email from my application to my rediffmail account,PLZ someone help.thanks in advance.

Re: sending email

Stuart Dootson28-Apr-09 5:23

Stuart Dootson

28-Apr-09 5:23

This[^] may help. Or this[^]. Or this[^]. Or maybe a basic ability to use search engines might help you?

Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p

SkysTheLimit28-Apr-09 4:35

SkysTheLimit

28-Apr-09 4:35

Hello

I am attempting to build a console application that depends on 4 other libraries using Visual Studio 2008. I was able to build the application in a previous version of Visual Studio.

3 of the libraries are in C code and the other is in C++.

I have checked (more than once) that all the libraries and my application are all compiled using the multi-threaded DLL (/MD). My command line compile options for each library and my application are as follows:

Lib1: /Ox /Op /MD
Lib2&3: /Od /D "WIN32" /D "NDEBUG" /D "_CONSOLE" /D "_VC80_UPGRADE=0x0710" /D "_MBCS" /FD /EHsc /MD /W3 /c /Tc
Lib4: /MD /EHsc /RTC1 /D "WIN32" /D "_MBCS" /W2 /DNDEBUG
App: /Od /D "WIN32" /D "NDEBUG" /D "_CONSOLE" /D "_VC80_UPGRADE=0x0710" /D "_MBCS" /FD /EHsc /MD /W3 /c /TP

Link: /INCREMENTAL /MANIFEST:NO /NODEFAULTLIB:"libcpmt.lib" /NODEFAULTLIB:"libc.lib" /NODEFAULTLIB:"libcmt.lib"

I get 25 LNK2005 errors regarding basic_string already being defined in my application. I suspect it has something to do with lib4 because when I take it out of the project the LNK2005 errors go away and I get unresolved external errors for the functions I use out of that library (although I'm not sure what order those errors are generated in).

I have tried ignoring msvcprt.lib but I get unresolved externals for other functions. Frown | :(

I have turned on verbose to see what libraries are being included and they are as follows:
lib4
lib2
lib3
lib1
zlib1.lib
szlibdll.lib
OLDNAMES.lib
MSVCRT.lib
msvcprt.lib (where the errors are given)
uuid.lib
kernel32.lib

Stuart Dootson28-Apr-09 5:45

Stuart Dootson

28-Apr-09 5:45

Wow - you've already done a lot more investigation than most people who ask questions here Smile | :)

What can I suggest....

1. I notice that some of your libs use "/Od" and others don't and others use "/Ox". This will affect how methods of template classes (like std::basic_string) are inlined in your libraries - it's possible (I think) that a std::basic_string method may be embedded in an object file and then re-exported from a library?

2. I'd be tempted to use dumpbin (it comes with VS) or objdump (comes with GCC, if you have that installed) to dump various properties of the lib files (use dumpbin /all library-name) and then search through the resultant text for names of basic_string methods that look like they're defined rather than referenced?

3. Or maybe delete lib4, then add object files back into lib4 one by one, to see when the LNK2005 occurs?

So - no concrete answers, just possibilities Frown | :-(

Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p

SkysTheLimit28-Apr-09 7:52

SkysTheLimit

28-Apr-09 7:52

Thank you for your comprehensive reply Smile | :)

Suggestion 1 didn't work, but it is probably better to have them all the same anyway, considering what affect that option has.

I used dumpbin on the offending library. It looks to me like it is defined but I would just like to check.

In the exports table the functions (e.g. resize) that the linker complains about are external and prefixed with __imp_. Is this why the linker is complaining?

Basically, one of the files in lib4 creates its own class which inherits from std::string. For older versions of C++, it has the lines
#using std::string
#define std_string string
in the header file.
For newer versions of Visual C++, it simply has
#define std_string std::string

What is the difference between these two?

As far as I can see, the header file calls the functions in inline functions without the specifier std::
Other than that those functions aren't overridden or referred to anywhere else.

Stuart Dootson28-Apr-09 8:37

Stuart Dootson

28-Apr-09 8:37

WendyS56 wrote:
In the exports table the functions (e.g. resize) that the linker complains about are external and prefixed with __imp_. Is this why the linker is complaining?

No - that's correct linkage to a function defined in a DLL.

WendyS56 wrote:
What is the difference between these two?

The first replaces std_string by string and relies on the using (not #using, I believe) statement to make string resolve to std::string. The second just replaces std_string by std::string.

BTW - can you post the exact text of the LNK2005 message?

Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p