Advice needed to install a registry and dll file.

Do you have a question? Post it now! No Registration Necessary.  Now with pictures!

Threaded View
I'm having problems getting a program to work.
I've found off the internet a helpfile that claims to solve my
The solution involves activating a registry file and placing a dll file
in a specific directory.

I've virus checked both files... and nothing.

I've looked inside the registry file with notepad, all I can see is
numbers and letters.
I've tried opening the dll file with notepad and all I can see is junk.
(Erm... yes you've guessed it... a newbie when it comes to these

Can someone tell me:

- Is it dangerous to install the registry file?
- How can I make sure the dll file isn't a virus?



Re: Advice needed to install a registry and dll file. wrote:
Quoted text here. Click to load it


There is no way to ensure this.

But: what are you talking about?

If class libraries are compared to animals, MFC is the slime-warts toad.

Re: Advice needed to install a registry and dll file.

See all programs need the registry file and dll ( Dynamic Link
Libraries ) which are necessary for their proper working. Now if
registry file fails or get corrupted then windows can not determine if
the software ur using ( i.e. ur program) is registered to windows (
i.e. operating system ur using) or not. The DLL files consists of
linking to the driver files ( i.e. configuration files of ur hardware)
so that the program can access them. Somtimes the reg installation may
be dangerous. But if ur downloading the files from trusted website then
its ok. U can install the reg file and also copy the DLL file to
specific folder ( mostly in C:\windows\sytem32 or smthing like that).

Re: Advice needed to install a registry and dll file.

Quoted text here. Click to load it

Anywhere from "possibly" to "definitely".

Quoted text here. Click to load it

You can't.

So, the question now comes - what do you know about the person or
organisation providing the fix?

Is it a recognised provider of consistently reliable fixes, or a
fly-by-night hackish individual with no reputation?

The best place to get patches, of course, is usually the place where you got
the original software - although with incursions at many public distribution
points in the past, that might not be such a safe assumption.

The worst place to get patches is from random individuals with no
reputation.  You have no idea what you're getting into.

As a user with admittedly little knowledge, you need to work purely on the
basis of trust.

Do you have a reason to trust this patch?  Have others used it successfully?
Does it even do what it claims to do?

Note that I'm not saying the patch is dangerous - it could be that this is
exactly what you need.  There are lots of really nice people on the
Internet - it's just that the really bad people are the ones getting all the
press.  Unfortunately, it takes just one bad person to infect your system.

Gauge your level of risk - make up some numbers of how much you trust the
provider, what chance you think there is that the provider might have a
motive to provide you with an unsafe patch, and then compare that against
how useful your software is without the patch, or with the patch.


Site Timeline