Welcome to GameHourz.com!
FAQFAQ      ProfileProfile    Private MessagesPrivate Messages   Log inLog in

Computer Diagnosis Tips

 
   Game Forums (Home) -> Flight-Sim RSS
Next:  Flight Simulation PC  
Author Message
Vernon Balbert

External


Since: Sep 08, 2006
Posts: 617



(Msg. 1) Posted: Sun Mar 16, 2008 3:20 pm
Post subject: Computer Diagnosis Tips
Archived from groups: alt>games>microsoft>flight-sim (more info?)

I see an awful lot of questions involving errors and problems people get
with their computers. I happen to enjoy helping people fix these
problems (no wonder I've been doing tech support for so long) but there
are some ways to make the job easier for you and fix the problem a lot
faster than posting a question here and then waiting to see if anybody
has an answer.

1) Google Is Your Friend
Sit in the closest approximation to the lotus position you can achieve
and chant the following:

Google is my friend
Google is my friend
Google is my friend

If you don't like Google, substitute your favorite search engine name.
For just about any error message you get you can put it into Google and
find exactly what you're looking for. The ease of doing this makes it
so I put in very little effort for a number of problems that people ask
me about. Try it sometime and you may be surprised at how quickly you
can get an answer to your problem. Google even reports messages from
forums and Microsoft knowledgebase articles. Helps an awful lot.

2) Startup Folder
Computers are complex machines and the software is even more complex.
The interactions between hardware and software can get pretty hairy
sometimes and it can be intimidating to try to understand what's going
on. Frankly, when XP came out it became quite a bit harder to
troubleshoot because none of the old standbys were available, such as
editing the AUTOEXEC.BAT and other simple stuff. You can't create a
simplified boot disk to make it so you can run your favorite game so
there are other strategies to use. However, there are still some simple
things you can do to try to diagnose things.

One of the best things to do is to reboot the machine and when the
machine displays the Welcome screen in XP (or the login screen if you
use it) (not sure about Vista) hold down the Shift key until the system
has completed rebooting. This will temporarily disable running anything
in the Startup folder. If there are any conflicts caused by anything in
the Startup folder this will eliminate it. If this is the case, run
each program that's in the Startup folder, try to duplicate your
original error between each startup program you run and see if you can
duplicate the error.

The only real problem with this is that it might be a combination of two
or more programs that are in your Startup folder which cause the
problem. If it gets too complicated, go ahead and ask for help.

3) MSCONFIG
There's a nifty utility included with Windows called MSCONFIG. It
allows you to see almost everything that's started when you boot your
computer. All you have to do is go to the Start menu, select Run and
type in MSCONFIG and hit Enter.

For the purposes of simplicity stick to the Startup tab. Not only will
you see the items in your Startup folder in there, but you'll see
programs that are put into a couple of special registry keys that start
things up behind the scenes. These entries can be cryptic, but there
are some ways to help figure out what's going on.

You'll see three columns: Startup Item, Command and Location.
Sometimes it's pretty easy to tell what you're looking at just by the
name in the Startup column. For example, Yahoo! Messenger's item shows
"YahooMessenger". Pretty simple, huh? But what if you don't understand
what you're seeing? For example, if you see "Smax4", can you remove
this without causing problems? This is where the Command column comes
in. On my system "Smax4" has a command line of:

"C:\Program Files\Analog Devices\SoundMAX\Smax4.exe" /tray

This must have something to do with my sound card because it's loading
from the SoundMAX folder.

But then there are some cryptic names, such as "NvMcTray". What is
this, some kind of McDonald's item? Would you like fries with that?
The command line is no help:

RUNDLL32.EXE C:\WINDOWS\system32\NvMcTray.dll,NvTaskbarInit

So what to do? Remember step one? Google Is Your Friend. (Don't leave
your homepage without it!) This stuff is pretty well documented on the
web. Googling for NvMcTray comes up with the information in the first
link: It's the nVidia Media Center Library.

If you don't understand what you see and a search on Google still leaves
you confused, don't muck with it without asking for help.

4) Ask
Don't be afraid to ask here what to do. You can help by telling us what
you found out in steps 1 through 3, but if you're confused by doing
those things or are just lazy, ask anyway. Smile If you don't understand
what you see or what to do with the information you've gathered, unless
you like experimenting and are willing to accept the fallout of a
botched fix, then don't hesitate to ask those of us who continually
screw things up just to find out if something will work better.

Somebody might suggest booting into Safe Mode. For the most part, I
don't consider booting into Safe Mode to be an acceptable diagnosis tool
because it removes too many things that are necessary to running many
games. But it can be helpful if you're running into problems that
aren't game related.

Hope that helps and makes things easier for you!

--
The reason Chuck Norris is short is because God was afraid if he was too
tall Chuck Norris could catch him.

 >> Stay informed about: Computer Diagnosis Tips 
Back to top
Login to vote
Tom Garrett

External


Since: Jan 14, 2008
Posts: 85



(Msg. 2) Posted: Sun Mar 16, 2008 3:20 pm
Post subject: Re: Computer Diagnosis Tips [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

"Vernon Balbert" <vbalbert RemoveThis @gmail.nospam.com> wrote in message
news:uVaDj.32385$J41.27337@newssvr14.news.prodigy.net...
>I see an awful lot of questions involving errors and problems people get
>with their computers. I happen to enjoy helping people fix these problems
>(no wonder I've been doing tech support for so long) but there are some
>ways to make the job easier for you and fix the problem a lot faster than
>posting a question here and then waiting to see if anybody has an answer.
>
> 1) Google Is Your Friend
> Sit in the closest approximation to the lotus position you can achieve and
> chant the following:
>
> Google is my friend
> Google is my friend
> Google is my friend
>
> If you don't like Google, substitute your favorite search engine name. For
> just about any error message you get you can put it into Google and find
> exactly what you're looking for. The ease of doing this makes it so I put
> in very little effort for a number of problems that people ask me about.
> Try it sometime and you may be surprised at how quickly you can get an
> answer to your problem. Google even reports messages from forums and
> Microsoft knowledgebase articles. Helps an awful lot.
>
> 2) Startup Folder
> Computers are complex machines and the software is even more complex. The
> interactions between hardware and software can get pretty hairy sometimes
> and it can be intimidating to try to understand what's going on. Frankly,
> when XP came out it became quite a bit harder to troubleshoot because none
> of the old standbys were available, such as editing the AUTOEXEC.BAT and
> other simple stuff. You can't create a simplified boot disk to make it so
> you can run your favorite game so there are other strategies to use.
> However, there are still some simple things you can do to try to diagnose
> things.
>
> One of the best things to do is to reboot the machine and when the machine
> displays the Welcome screen in XP (or the login screen if you use it) (not
> sure about Vista) hold down the Shift key until the system has completed
> rebooting. This will temporarily disable running anything in the Startup
> folder. If there are any conflicts caused by anything in the Startup
> folder this will eliminate it. If this is the case, run each program
> that's in the Startup folder, try to duplicate your original error between
> each startup program you run and see if you can duplicate the error.
>
> The only real problem with this is that it might be a combination of two
> or more programs that are in your Startup folder which cause the problem.
> If it gets too complicated, go ahead and ask for help.
>
> 3) MSCONFIG
> There's a nifty utility included with Windows called MSCONFIG. It allows
> you to see almost everything that's started when you boot your computer.
> All you have to do is go to the Start menu, select Run and type in
> MSCONFIG and hit Enter.
>
> For the purposes of simplicity stick to the Startup tab. Not only will
> you see the items in your Startup folder in there, but you'll see programs
> that are put into a couple of special registry keys that start things up
> behind the scenes. These entries can be cryptic, but there are some ways
> to help figure out what's going on.
>
> You'll see three columns: Startup Item, Command and Location. Sometimes
> it's pretty easy to tell what you're looking at just by the name in the
> Startup column. For example, Yahoo! Messenger's item shows
> "YahooMessenger". Pretty simple, huh? But what if you don't understand
> what you're seeing? For example, if you see "Smax4", can you remove this
> without causing problems? This is where the Command column comes in. On
> my system "Smax4" has a command line of:
>
> "C:\Program Files\Analog Devices\SoundMAX\Smax4.exe" /tray
>
> This must have something to do with my sound card because it's loading
> from the SoundMAX folder.
>
> But then there are some cryptic names, such as "NvMcTray". What is this,
> some kind of McDonald's item? Would you like fries with that? The command
> line is no help:
>
> RUNDLL32.EXE C:\WINDOWS\system32\NvMcTray.dll,NvTaskbarInit
>
> So what to do? Remember step one? Google Is Your Friend. (Don't leave
> your homepage without it!) This stuff is pretty well documented on the
> web. Googling for NvMcTray comes up with the information in the first
> link: It's the nVidia Media Center Library.
>
> If you don't understand what you see and a search on Google still leaves
> you confused, don't muck with it without asking for help.
>
> 4) Ask
> Don't be afraid to ask here what to do. You can help by telling us what
> you found out in steps 1 through 3, but if you're confused by doing those
> things or are just lazy, ask anyway. Smile If you don't understand what you
> see or what to do with the information you've gathered, unless you like
> experimenting and are willing to accept the fallout of a botched fix, then
> don't hesitate to ask those of us who continually screw things up just to
> find out if something will work better.
>
> Somebody might suggest booting into Safe Mode. For the most part, I don't
> consider booting into Safe Mode to be an acceptable diagnosis tool because
> it removes too many things that are necessary to running many games. But
> it can be helpful if you're running into problems that aren't game
> related.
>
> Hope that helps and makes things easier for you!
>
> --
> The reason Chuck Norris is short is because God was afraid if he was too
> tall Chuck Norris could catch him.
Thanks for the infor, Vernon. I appreciate it and will use it from now
on...which based on my experience in screwing things up, will be in the next
three days.
Tom in Tucson

 >> Stay informed about: Computer Diagnosis Tips 
Back to top
Login to vote
RandyL

External


Since: May 20, 2007
Posts: 168



(Msg. 3) Posted: Sun Mar 16, 2008 3:20 pm
Post subject: Re: Computer Diagnosis Tips [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

Hi Vernon,
All excellent points, thanks for sharing them with everyone. I would add
one more item:
Don't be afraid to take the cover off of your computer. Case in point: I
was recently having problems with my computer shutting completely off at
random after flying FSX for around 5-10 minutes. I took the case off my
computer and looked at the CPU cooling unit on the motherboard and
discovered that the cooling radiator fins and fan blades were caked with
dust. This computer is only about 1 year old. The dust was causing the CPU
to overheat and shut the computer down to protect itself. I blew out the CPU
cooler and all of the cooling fans with a can of compressed air and have not
had any problems since. I would suggest that everyone remove their computer
case every 6 months or so and inspect the interior. Blow out the inside of
their computer with compressed air, paying close attention to the cooling
fans. You may think that you have a clean, dust-free house, but you will be
amazed at the amount of dust that attaches itself to the inside of a
computer.
Thanks for your tips...

Randy L.

--
A problem is only a problem
if we make it a problem.


"Vernon Balbert" <vbalbert.TakeThisOut@gmail.nospam.com> wrote in message
news:uVaDj.32385$J41.27337@newssvr14.news.prodigy.net...
> I see an awful lot of questions involving errors and problems people get
> with their computers. I happen to enjoy helping people fix these problems
> (no wonder I've been doing tech support for so long) but there are some
> ways to make the job easier for you and fix the problem a lot faster than
> posting a question here and then waiting to see if anybody has an answer.
>
> 1) Google Is Your Friend
> Sit in the closest approximation to the lotus position you can achieve and
> chant the following:
>
> Google is my friend
> Google is my friend
> Google is my friend
>
> If you don't like Google, substitute your favorite search engine name. For
> just about any error message you get you can put it into Google and find
> exactly what you're looking for. The ease of doing this makes it so I put
> in very little effort for a number of problems that people ask me about.
> Try it sometime and you may be surprised at how quickly you can get an
> answer to your problem. Google even reports messages from forums and
> Microsoft knowledgebase articles. Helps an awful lot.
>
> 2) Startup Folder
> Computers are complex machines and the software is even more complex. The
> interactions between hardware and software can get pretty hairy sometimes
> and it can be intimidating to try to understand what's going on. Frankly,
> when XP came out it became quite a bit harder to troubleshoot because none
> of the old standbys were available, such as editing the AUTOEXEC.BAT and
> other simple stuff. You can't create a simplified boot disk to make it so
> you can run your favorite game so there are other strategies to use.
> However, there are still some simple things you can do to try to diagnose
> things.
>
> One of the best things to do is to reboot the machine and when the machine
> displays the Welcome screen in XP (or the login screen if you use it) (not
> sure about Vista) hold down the Shift key until the system has completed
> rebooting. This will temporarily disable running anything in the Startup
> folder. If there are any conflicts caused by anything in the Startup
> folder this will eliminate it. If this is the case, run each program
> that's in the Startup folder, try to duplicate your original error between
> each startup program you run and see if you can duplicate the error.
>
> The only real problem with this is that it might be a combination of two
> or more programs that are in your Startup folder which cause the problem.
> If it gets too complicated, go ahead and ask for help.
>
> 3) MSCONFIG
> There's a nifty utility included with Windows called MSCONFIG. It allows
> you to see almost everything that's started when you boot your computer.
> All you have to do is go to the Start menu, select Run and type in
> MSCONFIG and hit Enter.
>
> For the purposes of simplicity stick to the Startup tab. Not only will
> you see the items in your Startup folder in there, but you'll see programs
> that are put into a couple of special registry keys that start things up
> behind the scenes. These entries can be cryptic, but there are some ways
> to help figure out what's going on.
>
> You'll see three columns: Startup Item, Command and Location. Sometimes
> it's pretty easy to tell what you're looking at just by the name in the
> Startup column. For example, Yahoo! Messenger's item shows
> "YahooMessenger". Pretty simple, huh? But what if you don't understand
> what you're seeing? For example, if you see "Smax4", can you remove this
> without causing problems? This is where the Command column comes in. On
> my system "Smax4" has a command line of:
>
> "C:\Program Files\Analog Devices\SoundMAX\Smax4.exe" /tray
>
> This must have something to do with my sound card because it's loading
> from the SoundMAX folder.
>
> But then there are some cryptic names, such as "NvMcTray". What is this,
> some kind of McDonald's item? Would you like fries with that? The command
> line is no help:
>
> RUNDLL32.EXE C:\WINDOWS\system32\NvMcTray.dll,NvTaskbarInit
>
> So what to do? Remember step one? Google Is Your Friend. (Don't leave
> your homepage without it!) This stuff is pretty well documented on the
> web. Googling for NvMcTray comes up with the information in the first
> link: It's the nVidia Media Center Library.
>
> If you don't understand what you see and a search on Google still leaves
> you confused, don't muck with it without asking for help.
>
> 4) Ask
> Don't be afraid to ask here what to do. You can help by telling us what
> you found out in steps 1 through 3, but if you're confused by doing those
> things or are just lazy, ask anyway. Smile If you don't understand what you
> see or what to do with the information you've gathered, unless you like
> experimenting and are willing to accept the fallout of a botched fix, then
> don't hesitate to ask those of us who continually screw things up just to
> find out if something will work better.
>
> Somebody might suggest booting into Safe Mode. For the most part, I don't
> consider booting into Safe Mode to be an acceptable diagnosis tool because
> it removes too many things that are necessary to running many games. But
> it can be helpful if you're running into problems that aren't game
> related.
>
> Hope that helps and makes things easier for you!
>
> --
> The reason Chuck Norris is short is because God was afraid if he was too
> tall Chuck Norris could catch him.
 >> Stay informed about: Computer Diagnosis Tips 
Back to top
Login to vote
SnakeEyes

External


Since: Apr 18, 2007
Posts: 399



(Msg. 4) Posted: Sun Mar 16, 2008 3:20 pm
Post subject: Re: Computer Diagnosis Tips [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

On Mar 16, 11:20 am, Vernon Balbert <vbalb....TakeThisOut@gmail.nospam.com> wrote:

>
> Hope that helps and makes things easier for you!

Many thanks for taking the time to give us this very informative
information. There have been many occasions in the past years, when I
have become frustrated with the machine but have always been able to
work things out. My nephew, who considers himself somewhat of a
computer guru, gave me a good piece of advice one day after I climbed
the mountain and approached him in a tent surrounded by incense smoke
and half-naked concubines serving him tofu.....and he said: "Don't
explore parts of your computer when you have absolutely no idea where
you are going and what to do about it when you get there......leave
that to tech support" He is a wise guru.

.......and I say, thank goodness for India. Now, if I could only
understand what they are talking about.

Arthur
(Toronto)
 >> Stay informed about: Computer Diagnosis Tips 
Back to top
Login to vote
Vernon Balbert

External


Since: Sep 08, 2006
Posts: 617



(Msg. 5) Posted: Sun Mar 16, 2008 3:21 pm
Post subject: Re: Computer Diagnosis Tips [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

On 3/16/2008 9:18 AM, SnakeEyes went clickity clack on the keyboard and
produced this interesting bit of text:
> On Mar 16, 11:20 am, Vernon Balbert <vbalb....TakeThisOut@gmail.nospam.com> wrote:
>
>> Hope that helps and makes things easier for you!
>
> Many thanks for taking the time to give us this very informative
> information. There have been many occasions in the past years, when I
> have become frustrated with the machine but have always been able to
> work things out. My nephew, who considers himself somewhat of a
> computer guru, gave me a good piece of advice one day after I climbed
> the mountain and approached him in a tent surrounded by incense smoke
> and half-naked concubines serving him tofu.....and he said: "Don't
> explore parts of your computer when you have absolutely no idea where
> you are going and what to do about it when you get there......leave
> that to tech support" He is a wise guru.
>
> .......and I say, thank goodness for India. Now, if I could only
> understand what they are talking about.

Your guru nephew is indeed wise, but if you're like me and want to learn
how things work, you gotta break that rule. If you're like most people,
you don't want to break that precious bit of hardware, so keep your
hands off what you don't understand.

--
Chuck Norris doesn’t wash his clothes, he disembowels them.
 >> Stay informed about: Computer Diagnosis Tips 
Back to top
Login to vote
Vernon Balbert

External


Since: Sep 08, 2006
Posts: 617



(Msg. 6) Posted: Sun Mar 16, 2008 3:21 pm
Post subject: Re: Computer Diagnosis Tips [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

On 3/16/2008 9:11 AM, RandyL went clickity clack on the keyboard and
produced this interesting bit of text:
> Hi Vernon,
> All excellent points, thanks for sharing them with everyone. I would
> add one more item:
> Don't be afraid to take the cover off of your computer. Case in
> point: I was recently having problems with my computer shutting
> completely off at random after flying FSX for around 5-10 minutes. I
> took the case off my computer and looked at the CPU cooling unit on the
> motherboard and discovered that the cooling radiator fins and fan blades
> were caked with dust. This computer is only about 1 year old. The dust
> was causing the CPU to overheat and shut the computer down to protect
> itself. I blew out the CPU cooler and all of the cooling fans with a can
> of compressed air and have not had any problems since. I would suggest
> that everyone remove their computer case every 6 months or so and
> inspect the interior. Blow out the inside of their computer with
> compressed air, paying close attention to the cooling fans. You may
> think that you have a clean, dust-free house, but you will be amazed at
> the amount of dust that attaches itself to the inside of a computer.
> Thanks for your tips...

Definitely, routine maintenance is important to make sure your system is
running.

--
You can tell the size of a man by the size of the thing that makes him
mad. — Adlai Stevenson II
 >> Stay informed about: Computer Diagnosis Tips 
Back to top
Login to vote
Iain Smith

External


Since: May 29, 2007
Posts: 459



(Msg. 7) Posted: Sun Mar 16, 2008 6:04 pm
Post subject: Re: Computer Diagnosis Tips [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

Excellent stuff Vernon. What a helpful chap you are! Totally in the spirit
of this NG. Thanks for taking the time.

--
Iain
Rugby, UK
 >> Stay informed about: Computer Diagnosis Tips 
Back to top
Login to vote
Vernon Balbert

External


Since: Sep 08, 2006
Posts: 617



(Msg. 8) Posted: Sun Mar 16, 2008 11:27 pm
Post subject: Re: Computer Diagnosis Tips [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

On 3/16/2008 11:04 AM, Iain Smith went clickity clack on the keyboard
and produced this interesting bit of text:
> Excellent stuff Vernon. What a helpful chap you are! Totally in the spirit
> of this NG. Thanks for taking the time.

Thank you for your kind words, Iain. Always my pleasure to make
somebody's life easier. (Except my sister. I love making things
complicated for her. Hee, hee!)

--
The last time anybody made a list of the top hundred character
attributes of New Yorkers, common sense snuck in at number 79. - Douglas
Adams, "Mostly Harmless"
 >> Stay informed about: Computer Diagnosis Tips 
Back to top
Login to vote
WayPoint

External


Since: Jan 21, 2008
Posts: 132



(Msg. 9) Posted: Mon Mar 17, 2008 12:01 am
Post subject: Re: Computer Diagnosis Tips [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

Hi Vernon
Thanks so much for all that info.
I've copied & pasted to a special text file which I will keep handy on the
desktop.

If all else fails - I can just turn the power off & drop kick the darn thing
out the window. Wink)

--
Bruce (Au)



"Vernon Balbert" <vbalbert RemoveThis @gmail.nospam.com> wrote in message
news:uVaDj.32385$J41.27337@newssvr14.news.prodigy.net...
>I see an awful lot of questions involving errors and problems people get
>with their computers. I happen to enjoy helping people fix these problems
>(no wonder I've been doing tech support for so long) but there are some
>ways to make the job easier for you and fix the problem a lot faster than
>posting a question here and then waiting to see if anybody has an answer.
>
> 1) Google Is Your Friend
> Sit in the closest approximation to the lotus position you can achieve and
> chant the following:
>
> Google is my friend
> Google is my friend
> Google is my friend
>
> If you don't like Google, substitute your favorite search engine name. For
> just about any error message you get you can put it into Google and find
> exactly what you're looking for. The ease of doing this makes it so I put
> in very little effort for a number of problems that people ask me about.
> Try it sometime and you may be surprised at how quickly you can get an
> answer to your problem. Google even reports messages from forums and
> Microsoft knowledgebase articles. Helps an awful lot.
>
> 2) Startup Folder
> Computers are complex machines and the software is even more complex. The
> interactions between hardware and software can get pretty hairy sometimes
> and it can be intimidating to try to understand what's going on. Frankly,
> when XP came out it became quite a bit harder to troubleshoot because none
> of the old standbys were available, such as editing the AUTOEXEC.BAT and
> other simple stuff. You can't create a simplified boot disk to make it so
> you can run your favorite game so there are other strategies to use.
> However, there are still some simple things you can do to try to diagnose
> things.
>
> One of the best things to do is to reboot the machine and when the machine
> displays the Welcome screen in XP (or the login screen if you use it) (not
> sure about Vista) hold down the Shift key until the system has completed
> rebooting. This will temporarily disable running anything in the Startup
> folder. If there are any conflicts caused by anything in the Startup
> folder this will eliminate it. If this is the case, run each program
> that's in the Startup folder, try to duplicate your original error between
> each startup program you run and see if you can duplicate the error.
>
> The only real problem with this is that it might be a combination of two
> or more programs that are in your Startup folder which cause the problem.
> If it gets too complicated, go ahead and ask for help.
>
> 3) MSCONFIG
> There's a nifty utility included with Windows called MSCONFIG. It allows
> you to see almost everything that's started when you boot your computer.
> All you have to do is go to the Start menu, select Run and type in
> MSCONFIG and hit Enter.
>
> For the purposes of simplicity stick to the Startup tab. Not only will
> you see the items in your Startup folder in there, but you'll see programs
> that are put into a couple of special registry keys that start things up
> behind the scenes. These entries can be cryptic, but there are some ways
> to help figure out what's going on.
>
> You'll see three columns: Startup Item, Command and Location. Sometimes
> it's pretty easy to tell what you're looking at just by the name in the
> Startup column. For example, Yahoo! Messenger's item shows
> "YahooMessenger". Pretty simple, huh? But what if you don't understand
> what you're seeing? For example, if you see "Smax4", can you remove this
> without causing problems? This is where the Command column comes in. On
> my system "Smax4" has a command line of:
>
> "C:\Program Files\Analog Devices\SoundMAX\Smax4.exe" /tray
>
> This must have something to do with my sound card because it's loading
> from the SoundMAX folder.
>
> But then there are some cryptic names, such as "NvMcTray". What is this,
> some kind of McDonald's item? Would you like fries with that? The command
> line is no help:
>
> RUNDLL32.EXE C:\WINDOWS\system32\NvMcTray.dll,NvTaskbarInit
>
> So what to do? Remember step one? Google Is Your Friend. (Don't leave
> your homepage without it!) This stuff is pretty well documented on the
> web. Googling for NvMcTray comes up with the information in the first
> link: It's the nVidia Media Center Library.
>
> If you don't understand what you see and a search on Google still leaves
> you confused, don't muck with it without asking for help.
>
> 4) Ask
> Don't be afraid to ask here what to do. You can help by telling us what
> you found out in steps 1 through 3, but if you're confused by doing those
> things or are just lazy, ask anyway. Smile If you don't understand what you
> see or what to do with the information you've gathered, unless you like
> experimenting and are willing to accept the fallout of a botched fix, then
> don't hesitate to ask those of us who continually screw things up just to
> find out if something will work better.
>
> Somebody might suggest booting into Safe Mode. For the most part, I don't
> consider booting into Safe Mode to be an acceptable diagnosis tool because
> it removes too many things that are necessary to running many games. But
> it can be helpful if you're running into problems that aren't game
> related.
>
> Hope that helps and makes things easier for you!
>
> --
> The reason Chuck Norris is short is because God was afraid if he was too
> tall Chuck Norris could catch him.
 >> Stay informed about: Computer Diagnosis Tips 
Back to top
Login to vote
Display posts from previous:   
Related Topics:
Tips for getting back after switching programs? - When minimizing FS9, or switching between windowed and non-windowed view, freezes were not unknown. I found that minimizing (with the Windows key) usually was pretty clean, and sometimes if things did freeze I could go into display settings, set..

Grumman Goose FSX tips over when branking on land - Grumman Goose FSX tips over when using the brakes on land. I dit not experince whit with other planes. It is fenomenon realistic ? /Nic

New Computer for FSX - I have an older system that struggles to run FS9 at a decent framerate under many circumstances. If it weren't for Flight Simulator, I could probably get by with this system for sometime to come, but I'm getting the urge to buy a new one, largely..

New Computer Being Built 4 Me - As I've casually mentioned, next April 21st is my birthday and I decided to give myself a gift, since I am not on the receiving end of very many....so yesterday, I ordered a custom-built computer to use mostly for FS9 and lessly, for important lifestyle....

Installing FS9 (Again) on New Computer - I'm going to take the plunge and install FS9 tomorrow right out of the box on my new computer. Then, I'm going to install the 9.1 patch, FSPassengers, Ultimate Traffic, Ultimate Terrain Canada/AK. I am considering buying Ultimate Terrain USA as well..
   Game Forums (Home) -> Flight-Sim All times are: Ekaterinburg, Islamabad, Karachi, Tashkent (change)
Page 1 of 1

 
You can post new topics in this forum
You can reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum



[ Contact us | Terms of Service/Privacy Policy ]