Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Identifying the Proper .DLL When Copying Software to an Alternate Hard

Status
Not open for further replies.

fourls

Technical User
Oct 18, 2001
38
US
Hi:

I am wondering if there is a means of detecting and copying ALL of the files necessary to execute software after the package has been copied to another disk. From experience, virtually every attempt to copy Excel or Lotus 1-2-3 or whatever from the C-drive to, say the D-drive, makes me think that I have copied the software only to discover when I try to run the software from the D-drive that an error message appears stating that a certain .DLL file cannot be found.

My question is can that .DLL be identified before the software is copied to ensure that the .DLL is also copied?
Or is that merely a 'disguised' message telling the user that the software has to be set up on the recipient drive?

Thanks,

Fourls
 
You can transfer programs this way but it can be a apin sometimes. One way is to do a search and find *.dll on the installation disk or you can copy the dll's from the original computer on to a floppy (depending on size) or on to a zip or cd. When the error could not find whatever.dll comes up you can copy and paste into the path it gives you. This will work in most cases but not all. If you are networked you can simply copy from the other HD. The message is a true message. If you run into missing registered components, you have to install the software. Hope this helps.
 
A couple of things that may be somewhat useful when trying to pinpoint files associated with an app is to do a search based on time/date stamps. Basically, look for those exact matches between the program executable and other files.

Another more complex method is to use a Microsoft tool called Dependency Walker (Depends). You can use it to load a file and determine what it hooks..then work your way through each Dll.

You should keep in mind though that there may be registry entries for these applications that specify working or support directories that will be invalid if the app is moved to another drive or system.
Doug
dxd_2000@yahoo.com

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top