C / C++ / MFC

CPallini1-Apr-09 7:46

CPallini

1-Apr-09 7:46

Randyqiu wrote:
Who can give me some entire source code about conventing 32bits to 8bits?

Randyqiu wrote:
Plesase give me an entire code like this :
void true32to8color(pszFile)
{
.......
}

Randyqiu wrote:
because I don't have so much time to learn this.

I suppose 'rent a coder' is the viable solution.
Smile | :)

If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.

This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke

[My articles]

ThatsAlok1-Apr-09 18:13

ThatsAlok

1-Apr-09 18:13

CPallini wrote:
I suppose 'rent a coder' is the viable solution.

GetAFreeLancer.com might be fruitfull

"Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow
Never mind - my own stupidity is the source of every "problem" - Mixture

cheers,
Alok Gupta
VC Forum Q&A :- I/IV
Support CRY- Child Relief and You

Stuart Dootson1-Apr-09 8:57

Stuart Dootson

1-Apr-09 8:57

If you're just going to mooch software, then at least have the courtesy to Google for an image processing library[^] before demanding complete functions.

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

ThatsAlok1-Apr-09 18:14

ThatsAlok

1-Apr-09 18:14

Get any Image Library..

cheers,
Alok Gupta
VC Forum Q&A :- I/IV
Support CRY- Child Relief and You

mfc42.dll, error application crash, ModVersion-6.2.4131.0

ThatsAlok1-Apr-09 18:16

ThatsAlok

1-Apr-09 18:16

try searching CodeProject for same, you will find multiple library who support conversion of 32 bit Image to 8 bit image

cheers,
Alok Gupta
VC Forum Q&A :- I/IV
Support CRY- Child Relief and You

Syamlal S Nair1-Apr-09 7:15

Syamlal S Nair

1-Apr-09 7:15

the following work arounds are tried.
1. Format and reinstalling OS
2. Reinstalling driver for the hardware
3. Removing the old copies of mfc42.dll
4. Copying mfc42.dll from working machine.
5. Disabling mcaffee anti virus, removing network cable etc.

Any help would be appreciated.

SYAMLAL

Re: mfc42.dll, error application crash, ModVersion-6.2.4131.0

David Crow1-Apr-09 7:18

David Crow

1-Apr-09 7:18

What is ModVersion-6.2.4131.0?

"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

Re: mfc42.dll, error application crash, ModVersion-6.2.4131.0

Syamlal S Nair1-Apr-09 7:22

Syamlal S Nair

1-Apr-09 7:22

that is the version of the dll shown in the windows error message

SYAMLAL

Re: mfc42.dll, error application crash, ModVersion-6.2.4131.0

David Crow1-Apr-09 7:26

David Crow

1-Apr-09 7:26

Yes, but what is ModVersion?

Re: mfc42.dll, error application crash, ModVersion-6.2.4131.0

Syamlal S Nair1-Apr-09 7:28

Syamlal S Nair

1-Apr-09 7:28

Module Version.
Excerpts from the error dialog is : "ModVer 6.2.4131.0"

SYAMLAL

Re: mfc42.dll, error application crash, ModVersion-6.2.4131.0

Stuart Dootson1-Apr-09 9:30

Stuart Dootson

1-Apr-09 9:30

SyamlalS wrote:
error application crash

What application?

If it's your own application...here's your response:

So, the first thing you suspect is a problem with MFC or the configuration of your machine?

Nah - it's going to be a bug. In your code. Really. Break out the debugger and look for it.

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

DLL basic question

grassrootkit1-Apr-09 5:22

1-Apr-09 5:22

When I export a class in a DLL, I'm not actually dealing with dllmain or those DLL_PROCESS_ATTACH , DETACH thing. I just simply export it as a class. Then how things work without implementing these?

led mike1-Apr-09 5:27

1-Apr-09 5:27

grassrootkit wrote:
Then how things work without implementing these?

That depends. If, for example, your DLL was using COM and your host wasn't, it wouldn't work if you didn't handle the thread attach event and initialize COM. All the COM calls would fail because that's how COM works. So it depends on what you are doing in your DLL. In other words all DLL's are not equal.

grassrootkit1-Apr-09 5:35

1-Apr-09 5:35

So it should concern us only if we are dealing with COM?

led mike1-Apr-09 5:43

1-Apr-09 5:43

Really? That's your interpretation of my post?

good luck

grassrootkit1-Apr-09 6:15

1-Apr-09 6:15

your DLL was using COM and your host wasn't, it wouldn't work if you didn't handle the thread attach event and initialize COM.

You mean "if my DLL is a COM dll" and the hosting application not using COM? Confused | :confused:

I'm really not able to follow you. Can you explain a bit more without taking out the stick?

led mike1-Apr-09 7:33

1-Apr-09 7:33

grassrootkit wrote:
Can you explain a bit more

Um I already did explain more, maybe you missed those parts?

led mike wrote:
That depends.

led mike wrote:
If, for example, your DLL was using COM

led mike wrote:
because that's how COM works.

led mike wrote:
So it depends on what you are doing in your DLL.

led mike wrote:
In other words all DLL's are not equal.

By the way, that's not a stick, that's just quoting what I already posted.

grassrootkit1-Apr-09 8:25

1-Apr-09 8:25

led mike wrote:
In other words all DLL's are not equal.

I just asked I should take care of dllmain when I'm writing a simple C++ exported class. And you replied with reference to COM! That was little vague or may be I couldn't follow your language. That's why I asked the question again but anyway Cedric moonen got it quite right.

led mike1-Apr-09 9:31

1-Apr-09 9:31

grassrootkit wrote:
Cedric moonen got it quite right.

Cedric Moonen wrote:
But for a plain dll (not COM), you don't have to do anything in them

No, that is not correct.

In a "not COM" DLL you don't have to initialize COM, but you may need to do something else, DEPENDING ON WHAT THE FRACK YOU ARE DOING IN YOUR DLL!!!!

There is no way to make that point more clear. If you can't understand it, you should change careers.

BTW, I find your refusal to read what I post in reply to your question, very rude. Therefore I don't give a rats ass what you think is rude. Get it? Got it? Good.

bulg1-Apr-09 10:48

bulg

1-Apr-09 10:48

Having a bad day?

led mike1-Apr-09 11:12

1-Apr-09 11:12

Was I talking to you? Well now I am so f*** off a**hole

CPallini1-Apr-09 11:13

CPallini

1-Apr-09 11:13

Actually he was pretty nice today. Never heard about 'Terrible Led Mike' before?
Smile | :)

Cedric Moonen1-Apr-09 20:19

Cedric Moonen

1-Apr-09 20:19

led mike wrote:
No, that is not correct.

In a "not COM" DLL you don't have to initialize COM, but you may need to do something else, DEPENDING ON WHAT THE FRACK YOU ARE DOING IN YOUR DLL!!!!

That's what I was saying in my second sentence: you might want to initialize stuff depending on what your dll is doing Smile | :)

Cédric Moonen
Software developer

Charting control [v1.5]
OpenGL game tutorial in C++

led mike2-Apr-09 5:34

2-Apr-09 5:34

I know that but the monkey can't seem to understand it.

Changing subjects, the voting in this thread is a perfect example of how off it can be, my actual (and correct) answer to the question get's no votes but my post flaming someone else get's a '5' Laugh | :laugh: