Re: DLL nightmares ...
From: Alex K. Angelopoulos [MVP] (aka-at-mvps-dot-org)
Date: 06/27/04
- Next message: Alex K. Angelopoulos [MVP]: "Re: DLL nightmares ..."
- Previous message: Spin: "Re: Background Intelligent Service"
- In reply to: Sarah Tanembaum: "Re: DLL nightmares ..."
- Next in thread: root: "Re: DLL nightmares ..."
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 27 Jun 2004 11:29:40 -0500
Reordered a bit. I tossed a coin, and came up with oldest -> newest top ->
bottom... :)
Comments inline, but you may want to mention the actual problem; your title
indicates a specific issue (possibly a versioning issue with something while
installing RealPlayer and some version of Office), but your question is
about a very broad area of enterprise management.
Sarah Tanembaum wrote:
>> Sarah Tanembaum wrote:
>>> Assuming that I just installed a new Windows 2003 Server on a brand
>>> new machine. Then I installed a few application such as MS Office and
>>> other third party software such as Real Player.
> "Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]"
> wrote in message news:40DD181E.10501@pacbell.net...
>> Why are you installing Office and Real player on your server? Server
>> should only have server applications on that system.
>>
>> Don't install Office on your server.
>> Don't install real player on your server.
> Why does it matter? I might want it to use using the terminal services
> feaatures.
As an aside before addressing your questions - you may find that RealPlayer
is not very helpful on a TS. The audio quality is limited and RealPlayer in
its various incarnations tends to be a bad citizen on a multitasking system.
>>> During installation of any application, some(if not all) put files
>>> under system directories and program files directories, and various
>>> registry settings.
>>>
>>> Q1. Is there any tools to to take the inventory of all files and
>>> registry setting before(the virgin OS) and after(OS plus apps)?
There are some which can export information at certain points. I don't use
commercial ones much since I don't think that flat snapshots are very
useful, but you can even do a batch registry export and save a recursive
file listing with dates/sizes/checksums to compare to a later point in time.
In general this is most useful as a tool category for exploring, not for
specificallly to resolve a particular install problem or automate a process.
>>> Q2. Is there tools that take the diff of those two states?
Yes, and this is MUCH more compact than a snapshot, since it only checks
differences.
Symantec and most installer OEMs have tools which do this; I'm not familiar
with product names in general. :(
For easy use if you don't want to script this yourself you may want to try
InCtrl5; it is free.
>>> Q3. Is it possible to put all the 3rd party dll(including MS Apps)
>>> into different location other than the windows system directory?
Yes, and this should happen for files which are not operating system
updates. It doesn't happen with legacy apps automatically. Core OS files are
generally protected and won't be replaced by a bad app.
> How?
It depends on what the tool is and how you need to use it. With COM DLLs, as
long as they are versioned correctly you should be able to freely rename
them and use them where you need, as long as you register them. If the
versioning is messed up, you may need to copy and colocate the DLLs with the
calling app, registering it with its base name, but walking you through that
can take a while if it isn't the problem.
Standard C++ DLLs need to be within the search path of the calling
application.
>>> I know that we can install where the apps executables should be, but
>>> the stray dll files that are installed in the systems directory and
>>> program files directory that of my concern. I'd like to put all those
>>> DLL into a directory other than system directory and keep system
>>> directory as clean as possible from the clutter of 3rd party apps.
That's going to be tough. What's your overall problem and goal here?
- Next message: Alex K. Angelopoulos [MVP]: "Re: DLL nightmares ..."
- Previous message: Spin: "Re: Background Intelligent Service"
- In reply to: Sarah Tanembaum: "Re: DLL nightmares ..."
- Next in thread: root: "Re: DLL nightmares ..."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|