|
oh dear, I though I did.
Fixed and deleted original message
Darka [ Xanya]
"I am not a slave to a god that doesn't exist."
|
|
|
|
|
We need more info.
If you send us the details of the project your university has given you, then we may be able to help but without further information, we cannot.
i.e. Exactly what was the question being asked ?
Darka [ Xanya]
"I am not a slave to a god that doesn't exist."
|
|
|
|
|
Hi All,
I have a CListCtrl in report view with images. Whenever an Item gets highlighted, I lose the image.
Can anyone tell me how to keep the image from dissapearing?
P1p3r
|
|
|
|
|
How are you setting the item's image?
I_IMAGECALLBACK or an index into your image list?
|
|
|
|
|
Hi Mark,
Thanks for the info.
I finally figured it out. I had set the color wrong when I created the image.
Thanks again.
P1p3r
|
|
|
|
|
I'd make sure that the mask in the imagelist is correct. The most common way is to have a unique color in the bitmap that becomes transparent when drawn on the screen.
|
|
|
|
|
Hi Michael,
Thanks for the heads up.
I guess that's what I needed.
|
|
|
|
|
I come from the managed world and have no idea about unmanaged dlls!
So, I have a few unmanaged dlls I want to interop with using pinvoke, etc...
However, these dlls are undocumented so I have no idea, what parameters the methods take, or return.. I don't even know what methods are in the dll at all!
How can I peek into the unmanaged dll to see a signature of the methods? I've been messing around with dependency walker and pe explorer and those enable me to see what methods are inside the dll but neither of them provide information regarding the parameters or return types.
Am I just using them wrong? How can I get this information?
/\ |_ E X E GG
|
|
|
|
|
eggie5 wrote: However, these dlls are undocumented so I have no idea, what parameters the methods take, or return.. I don't even know what methods are in the dll at all!
How do you know you want to interop with them then?
Mark
|
|
|
|
|
I JUST know...
/\ |_ E X E GG
|
|
|
|
|
eggie5 wrote: I JUST know...
Fair enough 
I don't think there's any requirement that calling parameters be exported from a dll.
If you can even see the names you are lucky. They could just be ordinals
You need to get your hands on header and def files!
Mark
|
|
|
|
|
Oh, ok, header (.h) files, thanks for pointing me in the right direction
/\ |_ E X E GG
|
|
|
|
|
|
What, am I still confused?
/\ |_ E X E GG
|
|
|
|
|
eggie5 wrote: What, am I still confused?
I think I am at this point.
I assumed you DIDN'T have access to header and/or def files since you wanted to look right
in the DLL for that information. Having those files makes it way easier since DLLs aren't self-
describing like managed asemblies.
Based on my assumption, i figured you were being sarcastic saying thanks for pointing me in the
right direction. Therefore, I laughed
Mark
|
|
|
|
|
|
APPLIES TO
• The Microsoft Library Manager (LIB.EXE), when used with:
Microsoft Visual C++ 2.0 Professional Edition
Microsoft Visual C++ 2.1
Microsoft Visual C++ 4.0 Standard Edition
Microsoft Visual C++ 5.0 Standard Edition
|
|
|
|
|
Still applies  DLLs have been around a while.
So have those tools.
Mark
|
|
|
|
|
eggie5 wrote: How can I peek into the unmanaged dll to see a signature of the methods?
With undname.exe.
"Approved Workmen Are Not Ashamed" - 2 Timothy 2:15
"Judge not by the eye but by the heart." - Native American Proverb
|
|
|
|
|
I just tried this: undname C:\vws\usb.dll and it stated to output a bunch of jibbersh to the console and sounding my computer's internal speaker... Any idea on how to use this with C:\vws\usb.dll?
/\ |_ E X E GG
|
|
|
|
|
eggie5 wrote: Any idea on how to use this with C:\vws\usb.dll?
Well, first you need to get the mangled names from usb.dll (use either depends or dumpbin). Then you can unmangle those using undname.exe.
"Approved Workmen Are Not Ashamed" - 2 Timothy 2:15
"Judge not by the eye but by the heart." - Native American Proverb
|
|
|
|
|
Well, I wish they were mangled! All I have is a method name, no underscores or jibberish...
/\ |_ E X E GG
|
|
|
|
|
eggie5 wrote: dependency walker and pe explorer and those enable me to see what methods are inside the dll but neither of them provide information regarding the parameters or return types.
Are you seeing the C++ decorated names ?@@LikeThis@Z or plain names _LikeThis? If the former, Depends has a button labeled "C++" that unmangles the names so you can see the entire prototype. If it's the latter, there's no way to reconstruct the prototype, you'll need to get documentation for the DLL that says how to call the exported functions.
|
|
|
|
|
Neither! I don't even get an underscore. Anybody every heard of a library USB.dll with these methods?
USBCheck
USBClearDeviceBuffer
USBClose
USBGetError
USBGetStatus
USBOpen
USBRead
USBSetSerial
USBStopSerial
USBWrite
/\ |_ E X E GG
|
|
|
|
|
I was looking thought this library in the dissembler(pe explorer) and noticed that USBOpen is just a wrapper for doing standard USB HID stuff. But I really dont know what I'm looking at, all I can make sense of is the calls to windows API functions like CreateFile...
If anybody wants to take a look and give me info, the .dll is here:
http://www.wpmc2006.org/uploads/usb.dll[^]
I really need to know what USBRead is doing. Also, USBSetSerial is really strange, I have no idea what that could be....
PS. this is all for a weather station (Oregon scientific wmr100a). I'm trying to talk to it via C#.
Right now I can read data from the device, but it's strange 'cause the HID class says that the report length is only 9 wide, now why would a weather station with 100s of readings only return 9 numbers per read? I know this is weird because it comes with weather station software (it's using usb.dll) and it is getting all kinds of readings, so i'm thinking it's not sticking to the HID standard and just using that so it doesn't nag for drivers when you plug it into windows.... but i really don't know.
/\ |_ E X E GG
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
