Quick Fix Blog

Calendar

Archive
June 2008 (1 post)
April 2008 (2 posts)
March 2008 (2 posts)
February 2008 (3 posts)
November 2007 (1 post)
July 2007 (2 posts)

Popular Posts
Basic rules of IT
Installing PHP 5 on IIS

You are viewing all posts from February, 2008. To return to the front page, click here.

DLL Errors Explained and Defined

Tuesday 26th February 2008 9:20 PM

DLL Errors Explained and Defined
Causes of DLL Errors
A Windows computer contains hundreds of Dynamic Link Library (DLL) files. Many of these files are essential for your Windows computer, and are shipped along with the operating system. Several of them come later when you install additional tools and software programs on the system.
DLL errors can be caused due to many different reasons. Some of the most commons causes are:
  • Missing, incompatible, or outdated DLLs
  • Malfunctioning hardware or device drivers
  • Virus/spyware infections
  • Corrupt registry entries
If you start encountering frequent DLL errors on your system, then it is said to be in DLL Hell.

How To Fix Dll Errors
DLL errors are fixed depending on what actually caused the error.
If the DLL errors follow a software install, it is quite likely that the new software has overwritten currently existing DLLs with incompatible or older DLL versions. If this happens, then the first thing you need to do is to search on the Website of the software manufacturer to see if any update for the product is available. If you find one, download and install it on your computer. If you are lucky, doing this will resolve your problem.
If no update is available, try to search for the required DLL files on the Internet or another computer with similar configuration as yours. If you find the required DLL files, download and copy them to their location on the computer. If required, register the files using the RegSvr32 command. If nothing works, you may have to use the System Restore utility to rollback your system files back to the time when your system was running properly.
If the DLL errors follow a program uninstall, it is quite likely that one or more required shared DLL files were deleted when the programs were uninstalled. If this happens, reinstall the program, and then uninstall it again. But, this time make sure that when your system prompts you whether to keep or delete shared DLL files, choose to retain them on the system.
If DLL errors start generating soon after you add a new hardware device or install a driver update, they might be the culprit. Try to disconnect the hardware to see if the error disappears. If it does, get your hardware checked to ensure that it is working without any problems. If the errors appear after you install a new driver update, then this driver update may be faulty. You can resolve this problem by rolling back the update using the Device Manager tool. To do this, perform the following steps:
  1. At Start > Run, type sysdm.cpl, and then press Enter.
  2. On the Hardware tab, select Device Manager.
  3. Double-click on the hardware for which you install the faulty update.
  4. On the Driver tab, select Rollback driver.
Note: In case the error occurs due to problems with the currently installed driver, on theDrivertab, selectUninstallto remove the currently installed driver and then perform a fresh driver install after restarting your system.
To prevent Windows XP DLL errors caused due to malware infections and registry errors, it is important for you to regularly scan your system and the registry. To scan, remove and prevent malware infections, you must use reliable antivirus and antispyware tools. And to scan, repair, and maintain the registry, you must use an efficient and compatible registry cleaner and repair tool.

diggslashdotredditnetscapetechnoratinewsvinemixxfacebookdeliciousstumbleuponfurlsquidoomagnoliayahoomywebgooglebookmarkswindowsliverss

Posted 9:20 PM | 0 Comments | Permalink

Spam and those NDR's that say I sent an email....

Friday 15th February 2008 10:20 AM

We've all had emails in our inbox saying we tried to email someone we've never heard of and that the email couldn't be delivered, what are they? Well, simply put, they are the result of spammers trying to send junk to people who don't exist.

One of the major characteristics of the emails which spammers' send out is the fact that they spoof the original email senders address.

If that spam then can't be delivered it's natural for the Internet to send a Non Delivery Report ( NDR ) to who it thinks the sender was... you....

The fact that you get the NDR in no way means that you sent the original email, just that your email address was chosen as a spoof.

The address that is chosen to spoof from is usually taken at random from the list of email addresses that the spammer is sending his junk out to, so it's not uncommon for you to get several or several 10's or even several 100's per day saying you sent the original email. Usually the spoofed address will change at random and often, but if your address is used just for 10 minutes it could be responsible for 1000s of spam messages going out.

The process of spoofing your senders address is really quite easy to do but the ISP's and the people who manage the servers which accept emails for delivery to the Internet have put in place safeguards to stop people 'spoofing'.

Simply put, a rule has been accepted amongst the Internet that whoever supplies your connection to the Internet also supplies an SMTP server for you to post out your email messages, the ISP can then check if you are a spammer and take action to stop you.

Sometimes you 'roam' around the country or globe with a laptop and your connection method to the interenet changes, it would be unreasonable to expect you to change your Outlook settings every time you visit a new hotel, business or Interenet Cafe, with that in mind, you can purchase the use of an SMTP relay, usually for between £10(GB) and £20 per year, when you send emails via that server you 'authenticate' with a username and password in your email program.

This is where the plan falls apart, some people have SMTP servers which are known to be 'open relay' - no username and password are needed to use it, and no rules are on the server to say it has restricted use, until they are ALL secured the likelihood of spam will continue and the likelihood of random NDRs will be the natural off spin of the failed spams.

diggslashdotredditnetscapetechnoratinewsvinemixxfacebookdeliciousstumbleuponfurlsquidoomagnoliayahoomywebgooglebookmarkswindowsliverss

Posted 10:20 AM | 0 Comments | Permalink

DLink DSL-504 Series II and DSL-500 reset

Thursday 14th February 2008 11:36 AM

So you have one of the old faithfull DLink DSL-504 Series II or a DSL-500 router and you have lost the Username and Password, simple, reset the box and set it up again.... wrong, there's no reset button on these units.

Instead, follow these instructions to get the unit to give up it's username and password.

You must use an RS-232 serial cable using terminal emulation software such as Microsoft HyperTerminal.

Connect the cable from your computer to the console port on the DSL-500 or DSL-504.

Step 1 Go to Start>Programs>Accessories>Communications>Hyperterminal.

Step 2 Enter a name for your connection and choose the default icon selected.



Step 3 Select a COM port (usually 1 or 2) and click OK.



Step 4 The terminal parameters will need to be set to as follows:



Step 5 At the command prompt type isfs cat inituser and press enter. You will now see the username and password.

diggslashdotredditnetscapetechnoratinewsvinemixxfacebookdeliciousstumbleuponfurlsquidoomagnoliayahoomywebgooglebookmarkswindowsliverss

Posted 11:36 AM | 0 Comments | Permalink

[Front Page]

| Subscribe to this page's news feed | What's this?