Error - template LAYOUT-DATA-WRAPPER not found

A configuration error was detected in the CGI script; the LAYOUT-DATA-WRAPPER template could not be found.

Error - template STYLE-SHEET not found

A configuration error was detected in the CGI script; the STYLE-SHEET template could not be found.

Error - template SUB-TOP-BANNER not found

A configuration error was detected in the CGI script; the SUB-TOP-BANNER template could not be found.
Subject:
From:
Paul Bailey <[log in to unmask]>
Reply To:
PCSOFT - Personal Computer software discussion list <[log in to unmask]>
Date:
Sat, 19 Feb 2000 21:04:23 -0000
Content-Type:
text/plain
Parts/Attachments:
text/plain (58 lines)
----- Original Message -----
From: Automatic digest processor <[log in to unmask]>
To: Recipients of PCSOFT digests <[log in to unmask]>
Sent: 19 February 2000 05:37
Subject: PCSOFT Digest - 17 Feb 2000 to 18 Feb 2000 (#2000-50)


.

>   1. DLL association (2)

Original message:

.NET>
> Subject: Re: DLL association
>
> > -----Original Message-----
> I use Remove It 95 to delete orphan files like .dll's and .ini's. The
> problem I'm having is trying to determine what program or programs uses
> that specific .dll. Is the program even still on the hard drive. Remove
> It tells me that I have 76 orphan .dll's taking up 13,462,910 bytes, here
> are an example of what comes up:
> snip:
>
> I have no idea what programs use these .dll's and most reside in Windows\
> System. I don't want to delete any file and then find out that some
> program using that file won't work because it can't find the link it
> needs. I've also run Clean System Directory but it only comes up with
> about 20-30 .dll's. Who do you believe? How do you find out what program
> is referenced by these .dll's.
>
> TIA
> Lynn Kucera
>
> ------------------------------
> Lynn

There is a useful source of information on the Microsoft web site at
http://msdn.microsoft.com/isapi/msdnlib.idc?theURL=/library/techart/DLLdange
r1.htm

There is also a dll database query function, whereby you can enter a dll
file and version number, and get a listing of when it was introduced and
what applications used the dll file.

There is also a freely distributed dll problem finder program at the link I
gave previously, but I have not used this yet and am not sure how advanced
you need to be to do so: the DLL Universal Problem Solver (DUPS) package,
which is fully documented with complete source code in the Microsoft
Knowledge Base article Q247957: "SAMPLE: Using the DUPS Package to Resolve
DLL Compatibility Problems."

Paul Bailey

      "Hold No Punches.." Rode brings you great shareware/freeware
        programs with his honest opinions in this weekly column.
                         http://nospin.com/rode

ATOM RSS1 RSS2

LISTSERV.ICORS.ORG Secured by F-Secure Anti-Virus CataList Email List Search Powered by LISTSERV