Re: Command Prompt
From: Admiral Q (Star_Fleet_Admiral_Q(NOSPAM)_at_(SPAMNOT)hotmail.com)
Date: 02/04/05
- Next message: Ti: "Brightness and darkness"
- Previous message: Rick S.: "Re: Print Directory??????"
- In reply to: MikeC_2: "Re: Command Prompt"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 3 Feb 2005 20:28:43 -0500
Not trying to be condescending, but my interpretation was:
1) If you have a problem with command prompt update the video driver.
2) Your next statement says you had a problem with command prompt
rebooting the PC when opened.
3) After updating problem went away,
Statement 1 did not "qualify the problem" as to what it was, Statement 2
sounds as if it is an "example" of what could be one of many problems.
Statement 3 shows it went away after updating video drivers.
I could see what you were saying - I understood it, but would average
Joe/Jane Doe?
A more precise explanation:
1) PC rebooted every time I opened "command prompt".
2) I discovered, by updating my video card driver the problem went
away.
3) If you have problems with the PC rebooting when you open the
"command prompt", you may wish to update your video card drivers - although
your mileage may vary. (Meaning it may/may not fix your reboot problem when
opening the command prompt).
Just trying to help you "help" others "better" :-)
-- Star Fleet Admiral Q @ your service! "Google is your Friend!" www.google.com *********************************************** "MikeC_2" <MikeC2@discussions.microsoft.com> wrote in message news:4F25BF79-6C3A-4DDE-B10B-6BEC8A426103@microsoft.com... > I thought I made it clear that when I tried to go to Command Prompt by > clicking on it in All Programs>Accessories> Command Prompt that the process > of clicking on it rebooted my computer. (Same thing when I tried to execute > command prompt by Run> CMD.) (Maybe I wasn't so clear.) > > It was the video driver that caused the problem. As soon as I installed the > new driver all was fixed. > > Sorry if I confused anyone. > > "Admiral Q" wrote: > > > So your saying if for instance someone is typing in "ipconfig /all" at > > the CMD prompt, and they are getting "ipconfig is not recognized as an > > internal or external command, operable program or batch file", then I sh ould > > update my nVidia AGP card driver, instead of investigating why the PATH to > > ipconfig has gotten corrupted? > > Be careful what you say and remember, you are speaking in a peer-to-peer > > newsgroup, with many readers who have the knowledge to use their computer > > efficiently, but when it comes to IT support issues, such as the one I > > quoted, they have no clue the PATH variable is messed up - they just know > > they are having "a command prompt problem" and finding your post, they will > > blindly load a Video card driver, which most of the time will cause more > > issues than it resolved, because they most likely loaded the wrong one. > > > > -- > > Star Fleet Admiral Q @ your service! > > "Google is your Friend!" > > www.google.com > > > > *********************************************** > > > > "MikeC_2" <MikeC2@discussions.microsoft.com> wrote in message > > news:F8AAB4CC-C785-421F-ACC8-74FD8C819D8D@microsoft.com... > > > Anyone with a Command Prompt problem should first update the driver for > > the > > > video card. > > > > > > In my case Command Prompt was rebooting my computer. > > > (You might have other symtems.) > > > > > > I went to www.ati.com (my video card mfg), downloaded and installed the > > new > > > updated driver and poof, just like magic the problem went away! > > > > > >
- Next message: Ti: "Brightness and darkness"
- Previous message: Rick S.: "Re: Print Directory??????"
- In reply to: MikeC_2: "Re: Command Prompt"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|
