Lyrics & Knowledge Personal Pages Record Shop Auction Links Radio & Media Kids Membership Help
The Mudcat Cafesj

Post to this Thread - Sort Descending - Printer Friendly - Home


TECH: And now it's the dll files...

GUEST,JTT 07 Aug 02 - 11:29 AM
Max 07 Aug 02 - 11:43 AM
MMario 07 Aug 02 - 11:44 AM
GUEST,JTT 07 Aug 02 - 11:53 AM
JohnInKansas 07 Aug 02 - 12:37 PM
JohnInKansas 07 Aug 02 - 12:53 PM
JohnInKansas 07 Aug 02 - 01:04 PM
DMcG 07 Aug 02 - 02:51 PM
Stilly River Sage 07 Aug 02 - 08:28 PM
Stilly River Sage 07 Aug 02 - 08:31 PM
JohnInKansas 08 Aug 02 - 05:24 AM
GUEST 08 Aug 02 - 07:32 AM
Stilly River Sage 09 Aug 02 - 12:44 AM
Stilly River Sage 11 Aug 02 - 02:23 PM
JohnInKansas 11 Aug 02 - 05:11 PM
Mr Red 11 Aug 02 - 09:14 PM
JohnInKansas 11 Aug 02 - 10:27 PM
Share Thread
more
Lyrics & Knowledge Search [Advanced]
DT  Forum Child
Sort (Forum) by:relevance date
DT Lyrics:





Subject: And now it's the dll files...
From: GUEST,JTT
Date: 07 Aug 02 - 11:29 AM

So there I am, not a wink of sleep all night, the printer broken when I need to give my book proposal to my (non-email-using) agent, the Teamsters deciding to lend their support to the Citizens' Grass-'Em-Up Bureau. link fixed by JoeClone

I decide to try installing the bit of software that should make my TV card's remote control work. But it says it can't find a missing Dynamic Link Library - one of those hellish little .dll files that make our hair go grey.

Apparently you can find these things on the Web - the .dlls, I mean. But what do you do with them when you find them? Anyone know?


Post - Top - Home - Printer Friendly - Translate

Subject: RE: BS: And now it's the dll files...
From: Max
Date: 07 Aug 02 - 11:43 AM

It depends. Most .dll's are found in the /windows/system/ directory, but it could belong in the folder the program is in, like /program files/tvcard/. You're best bet is to reinstall the software or driver. That should replace the .dll.


Post - Top - Home - Printer Friendly - Translate

Subject: RE: BS: And now it's the dll files...
From: MMario
Date: 07 Aug 02 - 11:44 AM

copy them to the location where the error message says it cannot find it. If the error message doesn't give you a location - put it in the directory with most of youw windows files.


Post - Top - Home - Printer Friendly - Translate

Subject: RE: BS: And now it's the dll files...
From: GUEST,JTT
Date: 07 Aug 02 - 11:53 AM

Oh, thanks, mmario and Max. I tried reinstalling the software, and uninstalling it and reinstalling it, but keep getting the same message.

Nice poem here, by the way:

http://www.tryoung.com/trspage/politicalpoetry/america.html

link fixed by JoeClone


Post - Top - Home - Printer Friendly - Translate

Subject: RE: BS: And now it's the dll files...
From: JohnInKansas
Date: 07 Aug 02 - 12:37 PM

Some install programs "create" dll files from the driver files, which are usually .oem or some such. Often, when this is the case, a direct copy of a .dll into even the right directory won't make it work right, since other parts of the driver setup are still missing.

Assuming that the missing file is supposed to be part of the TVCard setup, I'd suggest seeing if the Card mfr - or whoever you got it from - has a web site with any information (especially driver downloads) that might help.

Occasionally, a right click on another file in the installation, and a look at "Properties" will identify a software vendor (who made the program for the card mfr), that could lead you to a source for the missing file.

Reinstalling software sometimes will fail if you just reinstall on top of the existing files. If you didn't already, you might try going to Start - Settings - Control Panel - Add/Remove Software and see if there is an Uninstall for the program. If there is, run it, and then reinstall.

Occasionally you may find software that doesn't "register" an uninstall, in which case it won't show in Control Panel - but there may be an uninstall.exe in the directory where the software is living.

If you want to "cheap out" and just kill the error message, there is a fair chance that the "call" for the .dll comes from a shortcut in the StartUp directory, and you could just delete the shortcut. (A "safer" procedure would be to cut and paste (move) the file somewhere else, and see if everything still works - before you actually delete it.)

In Win98, look for C:\Windows\StartMenu\Programs\StartUp. Other systems vary the location - use WindowsExplorer Find or Search and look for StartUP if it's not there. Note that if you find the shortcut, right click & look at properties may tell you "who" created it, which could give you a clue to actually fixing things.

John


Post - Top - Home - Printer Friendly - Translate

Subject: RE: BS: And now it's the dll files...
From: JohnInKansas
Date: 07 Aug 02 - 12:53 PM

Memory comes and goes in flashes - - -

There is a KNOWN VIRUS that can cause a "link to missing .dll," if your antivirus "stops" but doesn't "clean" completely.

If the missing .dll happens to be called sp.dll, you may have been hit by the Troj/JetHome virus. It has a couple of other names, and the .dll name may vary. It is relatively innocuous.

This virus attempts to change your home page, either to a "fantastic financial offer" or to a porn site, and sets itself up to re-run everytime you boot up. Norton, McAfee, or any other good av program will usually prevent it from executing, but frequently will let it put its shortcut into StartUp before it gets "killed." Then, since the program is no longer there, the shortcut "fails" every time you start.

Check your favorite AV site for details if there's a possibility this might be what you're getting.

John


Post - Top - Home - Printer Friendly - Translate

Subject: RE: BS: And now it's the dll files...
From: JohnInKansas
Date: 07 Aug 02 - 01:04 PM

Site for info:

Troj/JetHome, Sophos

A JavaScript variant, similar, is at:

Troj/JetHome-M, Sophos

Note that the "usual" link is to sp.dll, but that can be changed by any a-hole that restarts this one.

Note also, that dll link failures are common enought that it remains likely that the problem cited is just a setup glitch.

John


Post - Top - Home - Printer Friendly - Translate

Subject: RE: BS: And now it's the dll files...
From: DMcG
Date: 07 Aug 02 - 02:51 PM

If you think you have the right DLL but it isn't being used, it could be worth trying

regsvr32 c:\WINNT\SYSTEM32\MYDLL.DLL

or whatever the full path of the dll is. If the DLL contains registry information, this will cause it to put the right stuff into the windows registry so it can be found.

As with all registry work, its a good idea to save a copy of the registry beforehand!


Post - Top - Home - Printer Friendly - Translate

Subject: RE: BS: And now it's the dll files...
From: Stilly River Sage
Date: 07 Aug 02 - 08:28 PM

I'll stick another question in here instead of starting a new thread, since JohnInKansas would probably be answering it whereever it ended up.

I am locked out of my email program. Two days ago I started getting an error message from Pegasus and it shuts down before opening at all. I get a message that says:

"The email you are attempting to use appears to be locked by another process." Later it says, in a Windows dialog box "winpm-32.exe has generated errors and will be closed by Windows. You need to restart the program. an error log is being created."

I use Windows 2000 Professional, which is pretty stable. I have searched in various places and using the search program the pops up with the Start button, but am unable to find this particular error message. Once I know more about it, I'll try to visit the Microsoft Knowledge Base, or send an email to the support folks at Pegasus. Does anyone know how to find error logs so I can get to the correct message?

My attempts so far: I've downloaded the newer version of P-Mail and installed it over the old one. It is supposed to now leave all settings in place, and all old email files. This didn't change anything. I have a backup of my email files now, and will backup my other important files before I try anything major. I called the computer IP guy at work (in a library with lots of troubleshooting going all day long) and he suggested setting up to reinstall Win2000, and see if it notes the previously installed version. Sometimes other Windows versions would ask if you want to repair or reinstall. That might be a help, but no until I finish the backups, just in case.

Any helpful suggestions out there? I use a dual platform, and if push comes to shove I can put my files on the other side (ME came on the computer, and drives things that I don't have software for on the Win2000 (NT) side. Programs came preloaded and I can't move them around). I'd prefer to continue working on the 2000 side and leave ME for when the kids want to watch a DVD or when I burn CD's.

SRS


Post - Top - Home - Printer Friendly - Translate

Subject: RE: BS: And now it's the dll files...
From: Stilly River Sage
Date: 07 Aug 02 - 08:31 PM

Make that the computer "IT" guy at work. ;-)


Post - Top - Home - Printer Friendly - Translate

Subject: RE: TECH: And now it's the dll files...
From: JohnInKansas
Date: 08 Aug 02 - 05:24 AM

SRS -

About the only thing I can offer immediately is that you need to log on as "Administrator" to get to most of the logs that Win2K keeps routinely. The same may apply to any "special log" created for this problem.

It is possible, although difficult, to set up Win2K without an "administrator" identity, so I'm assuming you have an Admin identity set up, and remember the password.

"Start - Programs - Accessories - System Tools - System Information" can tell you quite a bit about what's going on, even if you're logged on only as a "normal user," although even there you get more access - and more information - as Administrator.

I'll have to wait until my 2K user goes to bed to look at her machine, as I don't have 2K on mine, and don't really remember where all the stuff is without a refresher.

John


Post - Top - Home - Printer Friendly - Translate

Subject: RE: TECH: And now it's the dll files...
From: GUEST
Date: 08 Aug 02 - 07:32 AM

It does not "depend". There is no single right location for a dll as Windows uses a search to find them. This is how it works according to the Win32 SDK help file. Windows searches:

1. The directory that contains the module for the current process.

2. The current directory.

3. The Windows system directory. The GetSystemDirectory function retrieves the path of this directory.

4. The Windows directory. The GetWindowsDirectory function retrieves the path of this directory.

5. The directories listed in the PATH environment variable.

In the case of load time (statically linked) dlls:

If the system cannot locate a specified DLL, it terminates the process and displays a dialog box that reports the error. Otherwise, the system maps the DLL modules into the virtual address space of the process and increments the DLL reference count.

In the case of run time (dynamic) dlls.

Run-time dynamic linking enables the process to continue running even if a DLL is not available. The process can then use an alternate method to accomplish its objective. For example, if a process is unable to locate one DLL, it can try to use another, or it can notify the user of an error. If the user can provide the full path of the missing DLL, the process can use this information to load the DLL even though it is not in the normal search path. This situation contrasts with load-time linking, in which the operating system simply terminates the process if it cannot find the DLL.


Post - Top - Home - Printer Friendly - Translate

Subject: RE: TECH: And now it's the dll files...
From: Stilly River Sage
Date: 09 Aug 02 - 12:44 AM

John,

Thanks for the reminder about the Administrator function. I have it set up to assume that the administrator will be using it, but it does a double log-on routine. I'll have to see what I can do next time I turn it off and log back on again.

I'm going to attempt a repair over the weekend (when I have day or two to conceivably waste if it messes up the whole thing and I have to do something major like reformat or reload stuff).

SRS


Post - Top - Home - Printer Friendly - Translate

Subject: RE: TECH: And now it's the dll files...
From: Stilly River Sage
Date: 11 Aug 02 - 02:23 PM

John,

I finally bit the bullet, backed up everything, and before doing something so foolhardy as reinstalling my Win2000, on a hunch I uninstalled the email and installed the new version. It works, and I have to eventually merge my saved files with the new program, but that is not too much trouble.

I was ready to tackle the Windows problem, but you can bet I'm tickled pink that I didn't have to do it.

SRS


Post - Top - Home - Printer Friendly - Translate

Subject: RE: TECH: And now it's the dll files...
From: JohnInKansas
Date: 11 Aug 02 - 05:11 PM

SRS -

Good to hear that you fixed the problem - and that you didn't go for the "reinstall Windows" advice.

I had a Techie at a former place of employment whose only answer to every problem was "reformat the hard drive." It's amazing how many times I've seen people backup everything, reformat, reinstall; and then copy the "problem" back onto the machine from backup. "Reinstall Windows" should also usually be interpreted as "I don't know what's goind on - but this will keep you busy for a while." There are times when it's appropriate, but I usually resist strongly, until a specific "something" that causes the problem is identified.

Good job. Save your notes.

John


Post - Top - Home - Printer Friendly - Translate

Subject: RE: TECH: And now it's the dll files...
From: Mr Red
Date: 11 Aug 02 - 09:14 PM

all the updates I found recently come as installation packages, sometimes if you have two copies it can go wally - particularly if they are different versions and you run two aps that invoke their own pet version.
Am I wrong - but doesn't windows go looking for the .DLL and then report it missing - I guess it looks in the obvious directories first - like those already mentioned.


Post - Top - Home - Printer Friendly - Translate

Subject: RE: TECH: And now it's the dll files...
From: JohnInKansas
Date: 11 Aug 02 - 10:27 PM

Mr Red -

Many(?) programs recommend that you "uninstall" your old version prior to installing an upgrade - where the upgrade contains "the whole package." If files from the older version remain, they can "confuse" the new one, or enough of the old one is left to permit it to try to load, but it can't work with files modified for the new version.

An upgrade that only adds or "tweaks" a few files, though, may depend on the earlier version being present. A "licensed" upgrade may also look for the old version, and refuse to install if its not there.

A program can "call" for a .dll by its generic name. Windows does have a "search hierarchy" that prescribes the order in which various directories should be searched, and can usually find the right file if its in any of the "usual locations."

Many programs, though, will call for the .dll by its full path name. If the call is to a particular file in a particular location, the call will fail if the file has been moved or deleted. Windows will not search elsewhere in this case.

A common "failed call" source is the shortcuts in the Startup directory. Shortcuts are invariably to a particular file in a particular location - and will usually fail if the "target" file is moved or deleted.

It is considered good programming practice to get subordinate files by generic calls that allow Windows (or whatever the OS) to look for them - where possible; but doing this in every case would prevent you from having more than one version of any program on the machine.

In any case of a "missing" .dll, or any other missing file, the critical thing that needs to be determined is "what process is looking for it?". Randomly copying .dll files elsewhere is not likely to provide a "real" solution to most such problems.

John


Post - Top - Home - Printer Friendly - Translate
  Share Thread:
More...


This Thread Is Closed.


Mudcat time: 20 December 8:31 AM EST

[ Home ]

All original material is copyright © 2022 by the Mudcat Café Music Foundation. All photos, music, images, etc. are copyright © by their rightful owners. Every effort is taken to attribute appropriate copyright to images, content, music, etc. We are not a copyright resource.