|
You sure the values your are returning when you respond to those requests are correct?
|
|
|
|
|
Hi
i add a .dll file using #import.
When i try to get handle i shows class not registered.
what should
manu
|
|
|
|
|
I'm not sure that you're using C++ ? If you are, I guess it's COM, is your dll registered ? With regsvr32 ?
Christian Graus - Microsoft MVP - C++
Metal Musings - Rex and my new metal blog
|
|
|
|
|
I have written a C++/CLI wrapper for a C++ SDK, and tested it in a simple C# app, it runs fine. When I move the code into my production app, the call that initialises the SDK returns a value of 3145990. According to the docs, this is a Windows API error, a WMI error, or an STI error. However, FormatMessage won't do anything with this value, nor is it a WMI or STI error as far as I can tell. Can anyone suggest what it might be ? It is NOT an error defined by the SDK, I checked that first.
Christian Graus - Microsoft MVP - C++
Metal Musings - Rex and my new metal blog
|
|
|
|
|
Are you doing anything that involves an external library, like Winsock? If so, you will need to tell FormatMessage(...) to look in that external DLL to find the correct message string.
Peace!
-=- James If you think it costs a lot to do it right, just wait until you find out how much it costs to do it wrong! Avoid driving a vehicle taller than you and remember that Professional Driver on Closed Course does not mean your Dumb Ass on a Public Road! DeleteFXPFiles & CheckFavorites (Please rate this post!)
|
|
|
|
|
The only external library I know I am using is the one that generates the error, but the docs say that the error is a GetLastError code, or a WMI/STI error.
Christian Graus - Microsoft MVP - C++
Metal Musings - Rex and my new metal blog
|
|
|
|
|
3145990 == 0x00300106
That isn't an HRESULT failure code, since the high bit isn't set. Some of the Win error codes are defined relative to a base number -- eg, ERROR_INTERNET_* errors start at 12000 -- so I'd hazard a guess (based on how close the number is to a nice round hex number) that you're seeing a code from some subsystem. I haven't been able to find the #define for it either, though.
|
|
|
|
|
Hi All,
I have got two applications which communicate via DDE. It works fine in Windows 2000 but when I run the applications in Win98, the string passed via DDE changes when it reaches the DDE Server. Any specific changes that I must do to make it work with Win98?
Thanks...
---
Hakuna-Matada
It means no worries for the rest of your days...
It's our problem free, Philosophy
"I think my response was 'What idiot dreamed this up?'" -- Mary Ann Davidson, Oracle's chief security officer, in typical blunt manner, remembering her reaction to the company's scheme to brand its databases as "unbreakable."
|
|
|
|
|
it isn't a Unicode versus Ascii issue ?
|
|
|
|
|
|
HakunaMatada wrote: Windows 98 supports Unicode right?
I don't think it does dude, recompile the application using Ascii and bet it will work fine.
|
|
|
|
|
So what you mean is change all TCHAR to CHAR and changes like those?
---
Hakuna-Matada
It means no worries for the rest of your days...
It's our problem free, Philosophy
"I think my response was 'What idiot dreamed this up?'" -- Mary Ann Davidson, Oracle's chief security officer, in typical blunt manner, remembering her reaction to the company's scheme to brand its databases as "unbreakable."
|
|
|
|
|
No you don't need to that, just define _MBCS instead of _UNICODE in you preprocessor definitions. See Chris Mauder's article on it.
|
|
|
|
|
Ray Kinsella wrote: _MBCS instead of _UNICODE
_MBCS is defined instead of _UNICODE! But it still doesn't work.
---
Hakuna-Matada
It means no worries for the rest of your days...
It's our problem free, Philosophy
"I think my response was 'What idiot dreamed this up?'" -- Mary Ann Davidson, Oracle's chief security officer, in typical blunt manner, remembering her reaction to the company's scheme to brand its databases as "unbreakable."
|
|
|
|
|
The string changes in what way, what length is it. ?
|
|
|
|
|
The Length of the String is somewhere around 268 characters and when it reaches the DDE Server, it adds random characters at the end increasing the length of the string to 284. Any idea why this happens?
---
Hakuna-Matada
It means no worries for the rest of your days...
It's our problem free, Philosophy
"I think my response was 'What idiot dreamed this up?'" -- Mary Ann Davidson, Oracle's chief security officer, in typical blunt manner, remembering her reaction to the company's scheme to brand its databases as "unbreakable."
|
|
|
|
|
sounds like a string termination problem, Windows NT manages memory slightly better, sounds like when you are copying the string into the DDE buffer you aren't terminating it in whatever way it wants it to be terminated. Look up the documentation ... but as a quick fix I would try using ZeroMemory on the buffer before I copied anything into it.
|
|
|
|
|
Thanks a lot. Will look into it and get back to you tomorrow.
Again... Thanks for helping me out.
---
Hakuna-Matada
It means no worries for the rest of your days...
It's our problem free, Philosophy
"I think my response was 'What idiot dreamed this up?'" -- Mary Ann Davidson, Oracle's chief security officer, in typical blunt manner, remembering her reaction to the company's scheme to brand its databases as "unbreakable."
|
|
|
|
|
|
do you can help me with rational rose please?
|
|
|
|
|
You could get help from this[^] forum.
|
|
|
|
|
hey guys... im sure someone here will be able to help me with this one.
Im looking at a log file that contains hex values
I have a hex string that contains a date and time
0xd4, 0x16, 0x12, 0xbe
The date is Word1 and the time is word2:
The date is contained in 0xd4, 0x16
The time is contained in 0x12, 0xbe
I know that each one of these 0x hex vlaues is a byte.
I know that a word is two bytes
Now here is where i am stuck because i dont know how to amalgamate the two bytes together.
Should i be adding them togther or should i be using the MAKELONG API which puts 1 byte
as the high word and the second as the lowword??
|
|
|
|
|
MAKELONG won't do it, a LONG is too big.
0xd4 << 8 + 0x16 will do it, in the first instance. You need to shift one value by 8 bits, so it sits above the other one.
Christian Graus - Microsoft MVP - C++
Metal Musings - Rex and my new metal blog
|
|
|
|
|
ahhh.. i see what your saying..
so 0xd4 = 11010100 and 0x16 = 00010110.
by shifting 0xd4 8 places it becomes 1101010000000000 which leaves room to add the 0x16 to become 1101010000010110 (54294 dec)
Thats excellent.. Thanks mate.
is this the normal way i should be amalgamting hex values then?
|
|
|
|
|
hey Christian, i seem to be tripping up over myself here.
so that works for the date part.. I did the same with the time part. So:
0xd4 <<8 + 0x16 = 54294 (date)
0x12 <<8 + 0xbe = 4798 (time)
now do i add these two results to equal 59092 or do i need to do:
54294 << 16 + 4798.
Doing this though me a massive value: 3558211584
|
|
|
|