Pfsszxt wrote:
See Nil, he's back.
> For some reason MS(?) has changed the XP system! "ipconfig" has been
> disabled! It produces a screen for about a third of a second and then
> it disappears. I tried the same on a Vista machine and there ipconfig
> has been disabled too!
ipconfig and many other utilities are console-mode programs. They don't
have a GUI (nice pretty window). They spew any output to stdout
(standard output) which is the console. The "console" is a screen
presented by a program where output gets directed (stdout), where input
comes from (stdin), and where errors are shown (stderr).
If you run a console program like you have, Windows opens a console
(shell) for that program, runs the program, and then closes the console
(exits the shell) because the program isn't running anymore.
If you want the console to remain open after the console-mode program
terminates then you load a console using a program, like the command-
line interpreter. The one you probably have has a filename of cmd.exe.
You'll find shortcuts for it in the Start menu, probably called
something like Command Prompt. When you run cmd.exe, you'll see a
console appear and stay there. You then run your console-mode programs
inside that shell. When they exit, the program that loaded the console
(cmd.exe) is still running. You can either enter 'exit' to exit that
shell and the console disappears or click the X titlebar button.
So, what YOU need to do is:
- Run 'cmd.exe'.
That loads a shell with a console.
- Run 'ipconfig <parms>'.
When it exits, its output (stdout) is still displayed because the
console remains (from cmd.exe still running).
The only reason it is curious to you is that you aren't old enough in
experience with operating systems to have used MS/IBM DOS where you
didn't get pretty windows. You just got a black screen with a blinking
cursor and maybe a line showing the current/working directory.
> And, a generic Linksys address (192.168.1.1) which presumably gives
> one factory settings for a provided model also doesn't work!
> Anyone want to explain all this??
Oh, "doesn't work". Yep, there's only one thing that happens in that
case, uh uh. Something happens but you won't say. An error message
shows up, a program crashes, or some behavior. Something DOES happen.
You're just not telling us ... again lacking the details.
What web browser are you using? What DOES happen when you enter
http://192.168.1.1/ in its address bar? Are you wired connected to the
router?
Oh, forget it. I'm not going down this bumpy dark road again.
Bye bye.