| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 59444 | 2005-07-03 00:50:00 | Another ipconfig problem | Greg (193) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 368778 | 2005-07-03 00:50:00 | Just been reading NZhawk's ipconfig query (www.pressf1.co.nz) and wondered if his cure would sort my issue: When I try ipconfig in RUN I get a command box (www.zu.co.nz) open very briefly and then it instantly closes (about .5 second). How come it doesn't work? (I can do other stuff from command line tho, like ping etc). XP Pro SP1 |
Greg (193) | ||
| 368779 | 2005-07-03 01:07:00 | If using NT based O/Ss (Win NT, 2000, XP) you go to run, type in cmd (or command) and then type ipconfig in the 'dos' shell that opens. Why is it like this?? Who knows... ask Unca Bill :p |
Myth (110) | ||
| 368780 | 2005-07-03 01:09:00 | Are you typing ipconfig in the run box or the command box. | Safari (3993) | ||
| 368781 | 2005-07-03 01:15:00 | That's not a problem - it's designed that way, inadvertently perhaps. ipconfig simply returns network interface status. It is not a program that can accept and return input. When you call it from CMD, it outputs current network adapter status to console, and closes, and you get your CMD prompt back. When you call it from RUN, it calls it, outputs it to screen (the few split seconds you talked of), and closes - this time returning you to the previous prompt. Basically, it's job is to ouput, and it will close immediately after it does so. However, when you see it do this in CMD, you can actually see the output because the console keeps the window open. |
Growly (6) | ||
| 368782 | 2005-07-03 01:33:00 | Thanks guys - sorted. I was trying to run it from RUN, but when I tried it from command line it outputted the results and stayed open. It's not something I really use, but was just confused about it, after being able to use winipcfg from my previous (W98) o/s. Cheers! |
Greg (193) | ||
| 1 | |||||