-=PCTechTalk=- Re: Interesting entries in mscofig startup

Don,
    I figured you'd want to continue the hunt, as I have come to learn that 
you're a curious fella (like myself).  The RyanVM forums have a ton of 
background info on many of these processes since a lot of that utility's 
users are looking to do similar things (remove unnecessary components from 
their Win install disks).

    Anything that is meant to be 'cloaked' would not show up at all within 
MSCONFIG, so my answer would also have to be 'none'.  As I mentioned 
earlier, they are both most likely the result of an incomplete installation. 
Before removing them entirely, I would reinstall Sonic and see how that 
affects the two entries.  You just might gain an additional function or two 
that you never knew existed.  Then again, you may then decide you don't care 
for them and remove them anyway.       lol

Peace,
G

"The only dumb questions are the ones that are never asked"

----- Original Message ----- 
From: "Don101" <don101@xxxxxxxxxx>
To: <pctechtalk@xxxxxxxxxxxxx>
Sent: Saturday, May 31, 2008 7:19 AM
Subject: -=PCTechTalk=- Re: Interesting entries in mscofig startup


>I had come to the same conclusion when I began to see what was involved in
> answering the question.  Especially since everything is working OK so far.
> However, it is interesting to see the long list of "stuff" that starts up
> everytime I start the computer.  I will spend some time researching those
> "file not found" items and will also look at some of the other "stuff" to
> get an idea of what might be able to be done away with.  That should help 
> in
> deciding nLite what components to eliminate.
>
> I have a working XP in a VM that I will use to disable some and see what
> happens.  I hope eliminating identifiable items, such as security system
> components and at least some OS components will whittle the list down to a
> far less imposing list.
>
> First thing I will do is disable the two items in question and then see 
> what
> breaks.
>
> Question:  *IF* the two items are cloaked intentionally by the mother ship
> and are actually loading at startup, to what legitimate reason might they 
> be
> cloaked?  I suspect the answer is None and that they are literally items
> that do not exist (and should not be there) but msconfig was told that
> something belonged there and it should list them just to befuddle users 
> like
> me.
>
>
> Don 


---------------------------------------------------------------
Please remember to trim your replies (including this sentence and everything 
below it) and adjust the subject line as necessary.

To unsubscribe or change your email settings:
http://www.freelists.org/webpage/pctechtalk

To access our Archives:
http://groups.yahoo.com/group/PCTechTalk/messages/
http://www.freelists.org/archives/pctechtalk/

To contact only the PCTT Mod Squad, write to:
pctechtalk-moderators@xxxxxxxxxxxxx
---------------------------------------------------------------

Other related posts: