rspahitz
asked on
RichEd32.dll usage
We recently had to deal with the Nimda virus, and upon cleaning it up, found that it had infected RichEd32.dll so we removed all references (where the date was today.)
After this was done, we had lots of problems related to this file not being registered, so I tried to register it and was told:
"
C:...riched32.dll was loaded, but the DllRegisterServer entry point was not found.
DllRegsiterServer may not be exported, or a corrupt version of C:...riched32.dll may be in memory. Consider using PView to detect and remove it.
"
1. Does anyone know what this message means?
2. Is RichEd32 a Windows file (and not just a VB file?)
3. Is this something that can be registered when we install our application? If so, how? (We tried and the registration failed (using Installshield Express.)
After this was done, we had lots of problems related to this file not being registered, so I tried to register it and was told:
"
C:...riched32.dll was loaded, but the DllRegisterServer entry point was not found.
DllRegsiterServer may not be exported, or a corrupt version of C:...riched32.dll may be in memory. Consider using PView to detect and remove it.
"
1. Does anyone know what this message means?
2. Is RichEd32 a Windows file (and not just a VB file?)
3. Is this something that can be registered when we install our application? If so, how? (We tried and the registration failed (using Installshield Express.)
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
OK...who needs the points most, or should I simply split it?
It was nice that wileecoy gave me the link so I could get right to it (when will I learn to go to the MS site first for MS questions???)
It was nice that wileecoy gave me the link so I could get right to it (when will I learn to go to the MS site first for MS questions???)
ASKER
Since I heard no response, I'll give the points to wileecoy here, and to acperkins in another question.
Thanks.
By the way, this exercise allowed us to totally remove the dll (via minor redesign) from our app so we didn't have to worry about it anymore!!!
Thanks.
By the way, this exercise allowed us to totally remove the dll (via minor redesign) from our app so we didn't have to worry about it anymore!!!
Thanks
EE was down for a while and I was to busy to keep checking if it was up. Sorry for not getting back.
Thanks again.
Wileecoy.
EE was down for a while and I was to busy to keep checking if it was up. Sorry for not getting back.
Thanks again.
Wileecoy.
INFO: Distribution Issues with Riched32.dll (Q197580)
Anthony